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
Supplemental In-Lane Pavement Markings | Safe Design

Supplemental In-Lane Pavement Markings

Image Source: Julian, F. Horizontal Signing, A Proven Low-Cost Horizontal Curve Safety Countermeasure.2024 TRB International Roadside Safety Conference presentation.

DEFINITION AND DESCRIPTION

Regulatory, warning, or guidance messages provided by signs may also be placed in the lane using elongated pavement markings. Messages such as the posted speed limit or Stop Ahead or Curve Ahead markings may supplement signs by providing the same information in the driver’s direct line of sight.

Implementation Categories

Area(s) Design & Geometrics, Traffic Operations, HSIP
Safety Category 2, 4

CONSIDERATIONS

  • Due to their installation and maintenance costs, TO-504 limits the use of word markings to locations where there is a demonstrated need to provide motorists additional warning or guidance.
  • Send location of supplemental in-lane pavement markings to Traffic Operation to be inventoried. 

APPLICATION

  • May be installed where there is a difference between the posted speed and curve advisory speed, corridors where speed studies indicate excessive speeding, and in speed transition zones.
  • Follow Section 3B.20 and 3B.21 of the MUTCD for implementation.
  • With the exception of route marker symbols, horizontal signing placed on the pavement shall consist only of words and numbers.
  • Refer to the Pavement Markings Chapter of the Standard Highway Signs publication for installation of pavement marking letters and numerals. Letters and numerals should be 6 feet or more in height.

example

Image Source: FHWA

Complementary SSA Strategies

REFERENCES AND RESOURCES

Campbell, J., M. Lichty, J. Brown, C. Richard, J. Graving, J. Graham, M. O’Laughlin, D. Torbic, D. Harwood. (2012). NCHRP Report 600: Human Factors Guidelines for Road System, Second Edition, Washington, DC: Transportation Research Board..

Federal Highway Administration. Manual on Uniform Traffic Control Devices for Streets and Highways (MUTCD), Federal Highway Administration, U.S. Department of Transportation, Washington DC, 2023.  https://mutcd.fhwa.dot.gov/kno_11th_Edition.htm.

FHWA. Speed Management: A Manual for Local Rural Road Owners. Federal Highway Administration, U.S. Department of Transportation, Washington DC, 2012.  https://highways.dot.gov/safety/local-rural/speed-management-manual-local-rural-road-owners

Gross, F., Jagannathan, R., Persaud, B., Lyon, C., Eccles, K., Lefler, N., & Amjadi, R. (2008, March). Safety evaluation of STOP AHEAD pavement markings (Report No. FHWA-HRT-08-043). U.S. Department of Transportation, Federal Highway Administration. https://www.fhwa.dot.gov/publications/research/safety/08043/index.cfm

KYTC Traffic Operations Manual, TO-504

KYTC Complete Streets, Roads, and Highways Manual

KYTC Standard Drawings (2025). https://transportation.ky.gov/Highway-Design/Pages/Standard-Drawings.aspx. Typical Markings at Signalized Intersections TPM-203

Do you have more questions? Get in touch!

[wpforms id="3461"]

CONTACT:

Jill Asher

Research Engineer 

jill.asher@uky.edu