Deprecated: WPDataTables\Vendor\DI\create(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\functions.php on line 35

Deprecated: WPDataTables\Vendor\DI\autowire(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\functions.php on line 48

Deprecated: WPDataTables\Vendor\DI\ContainerBuilder::writeProxiesToFile(): Implicitly marking parameter $proxyDirectory as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\ContainerBuilder.php on line 283

Deprecated: WPDataTables\Vendor\DI\Definition\Source\ReflectionBasedAutowiring::autowire(): Implicitly marking parameter $definition as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Definition\Source\ReflectionBasedAutowiring.php on line 19

Deprecated: WPDataTables\Vendor\DI\Definition\Source\Autowiring::autowire(): Implicitly marking parameter $definition as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Definition\Source\Autowiring.php on line 23

Deprecated: WPDataTables\Vendor\DI\Definition\Source\DefinitionFile::__construct(): Implicitly marking parameter $autowiring as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Definition\Source\DefinitionFile.php on line 28

Deprecated: WPDataTables\Vendor\DI\Definition\Source\DefinitionArray::__construct(): Implicitly marking parameter $autowiring as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Definition\Source\DefinitionArray.php on line 39

Deprecated: WPDataTables\Vendor\DI\Definition\Source\DefinitionNormalizer::normalizeRootDefinition(): Implicitly marking parameter $wildcardsReplacements as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Definition\Source\DefinitionNormalizer.php on line 46

Deprecated: WPDataTables\Vendor\DI\Proxy\ProxyFactory::__construct(): Implicitly marking parameter $proxyDirectory as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Proxy\ProxyFactory.php on line 43

Deprecated: WPDataTables\Vendor\DI\Container::__construct(): Implicitly marking parameter $definitionSource as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Container.php on line 87

Deprecated: WPDataTables\Vendor\DI\Container::__construct(): Implicitly marking parameter $proxyFactory as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Container.php on line 87

Deprecated: WPDataTables\Vendor\DI\Container::__construct(): Implicitly marking parameter $wrapperContainer as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Container.php on line 87

Deprecated: WPDataTables\Vendor\DI\Definition\ObjectDefinition::__construct(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Definition\ObjectDefinition.php on line 72

Deprecated: WPDataTables\Vendor\DI\Definition\ObjectDefinition::setClassName(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Definition\ObjectDefinition.php on line 88

Deprecated: WPDataTables\Vendor\DI\Definition\ObjectDefinition::setLazy(): Implicitly marking parameter $lazy as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Definition\ObjectDefinition.php on line 186

Deprecated: WPDataTables\Vendor\DI\Definition\Resolver\ObjectCreator::setPrivatePropertyValue(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Definition\Resolver\ObjectCreator.php on line 212

Deprecated: WPDataTables\Vendor\DI\Definition\Resolver\ParameterResolver::resolveParameters(): Implicitly marking parameter $definition as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Definition\Resolver\ParameterResolver.php on line 38

Deprecated: WPDataTables\Vendor\DI\Definition\Resolver\ParameterResolver::resolveParameters(): Implicitly marking parameter $method as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Definition\Resolver\ParameterResolver.php on line 38

Deprecated: WDTIntegration\Webhooks\WebhookManagerService::__construct(): Implicitly marking parameter $repository as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\tiers\pro\webhooks\Services\WebhookManagerService.php on line 24

Deprecated: WDTIntegration\Webhooks\WebhookDispatcherService::__construct(): Implicitly marking parameter $repository as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\tiers\pro\webhooks\Services\WebhookDispatcherService.php on line 30

Deprecated: WDTIntegration\Webhooks\WebhookDispatcherService::__construct(): Implicitly marking parameter $payloadBuilder as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\tiers\pro\webhooks\Services\WebhookDispatcherService.php on line 30

Deprecated: WDTIntegration\Webhooks\WebhooksAjaxController::__construct(): Implicitly marking parameter $manager as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\tiers\pro\webhooks\Controllers\WebhooksAjaxController.php on line 18

Deprecated: WDTIntegration\Webhooks\WebhooksAjaxController::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\tiers\pro\webhooks\Controllers\WebhooksAjaxController.php on line 18

Deprecated: WDTIntegration\Webhooks\WebhookDispatchHooks::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\tiers\pro\webhooks\Hooks\WebhookDispatchHooks.php on line 15
6.12 Signs on Horizontal Curves | Safe Design

6.12 Signs on Horizontal Curves

  • Use curve warning signs to communicate downstream changes in horizontal alignment to motorists. Signs need to include a directional arrow that indicates if a curve bends to the left or right. Advisory speed signs can also be used.
  • Table 6.5 contains placement guidelines for curve warning signs based on the posted or 85th percentile speed. There are no guidelines for cells that read n/a — placement will depend on site conditions and the presence of other signage. To determine how far upstream of a curve advance warning signs should be placed, first select the posted or 85th percentile speed. Next, determine the curve advisory speed. Then look for the appropriate cell. For example, if the posted or 85th percentile speed is 45 mph and the curve advisory speed is 10 mph, the curve warning sign should be placed 125 ft upstream of the curve.
Table 6.5 Distance Guidelines for Advance Placement of Curve Warning Signs
Posted or 85th Percentile Speed (mph) Advance Placement Distance (ft) Based on Curve Advisory Speed (mph)
10 20 30 40 50 60 70
20 n/a — — — — — —
25 n/a n/a — — — — —
30 n/a n/a — — — — —
35 n/a n/a n/a — — — —
40 n/a n/a n/a — — — —
45 125 n/a n/a n/a — — —
50 200 150 100 n/a — — —
55 275 225 175 100 n/a — —
60 350 300 250 175 n/a — —
65 425 400 350 275 175 n/a —
70 525 500 425 350 250 150 —
75 625 600 600 450 350 250 100
Table 6.6 Proper Chevron Spacing
Advisory Speed Limit (mph) Chevron Spacing (ft)
15 40
20 80
25 80
30 80
35 120
40 120
45 160
50 160
55 160
60 200
65 200

Do you have more questions? Get in touch!

[wpforms id="3461"]

CONTACT:

Jill Asher

Research Engineer 

jill.asher@uky.edu