903.12 Changeable Message Signs (MUTCD Chapter 2L) - Revision history

HogsettC: /* {{SpanID|903.12.5}}903.12.5 Message Length and Units of Information (MUTCD Section 2L.05) */

2025-12-10T22:52:10Z

{{SpanID|903.12.5}}903.12.5 Message Length and Units of Information (MUTCD Section 2L.05)

← Older revision		Revision as of 17:52, 10 December 2025
Line 184:		Line 184:
	\|-		\|-
	\| colspan="3" style="text-align: left; background-color: #ffffff;min-width: 400px;" \| Note: the following is an example of a two-phase message that could be developed<br />from the four information units shown in this table:<br />		\| colspan="3" style="text-align: left; background-color: #ffffff;min-width: 400px;" \| Note: the following is an example of a two-phase message that could be developed<br />from the four information units shown in this table:<br />
	<div style="text-align: center;"><span style="display: inline-block">~~[[File:UnitsofInformationPhase1.png\|center\|200px\|alt="Major Crash at Exit 12", Phase 1]]~~</span>   <span style="display: inline-block">[[File:~~UnitsofInformationPhase2~~.png\|center\|~~200px~~\|alt="Use Route 46 to New York", Phase 2]]</span></div>		<div style="text-align: center;"><span style="display: inline-block"></span>   <span style="display: inline-block">[[File:UnitsofInformationPhase1-2.png\|center\|400px\|alt="Use Route 46 to New York", Phase 2]]</span></div>
	\|}		\|}
	</center>		</center>

HogsettC: /* {{SpanID|903.12.5}}903.12.5 Message Length and Units of Information (MUTCD Section 2L.05) */

2025-12-10T22:50:17Z

{{SpanID|903.12.5}}903.12.5 Message Length and Units of Information (MUTCD Section 2L.05)

← Older revision		Revision as of 17:50, 10 December 2025
Line 184:		Line 184:
	\|-		\|-
	\| colspan="3" style="text-align: left; background-color: #ffffff;min-width: 400px;" \| Note: the following is an example of a two-phase message that could be developed<br />from the four information units shown in this table:<br />		\| colspan="3" style="text-align: left; background-color: #ffffff;min-width: 400px;" \| Note: the following is an example of a two-phase message that could be developed<br />from the four information units shown in this table:<br />
	<div style="text-align: center;"><span style="display: inline-block">[[File:~~UnitsOfInformation_Phase1~~.png\|center\|alt="Major Crash at Exit 12", Phase 1]]</span>   <span style="display: inline-block">[[File:~~UnitsOfInformation_Phase2~~.png\|center\|alt="Use Route 46 to New York", Phase 2]]</span></div>		<div style="text-align: center;"><span style="display: inline-block">[[File:UnitsofInformationPhase1.png\|center\|200px\|alt="Major Crash at Exit 12", Phase 1]]</span>   <span style="display: inline-block">[[File:UnitsofInformationPhase2.png\|center\|200px\|alt="Use Route 46 to New York", Phase 2]]</span></div>
	\|}		\|}
	</center>		</center>

HogsettC: /* {{SpanID|903.12.5}}903.12.5 Message Length and Units of Information (MUTCD Section 2L.05) */

2025-12-10T13:54:17Z

{{SpanID|903.12.5}}903.12.5 Message Length and Units of Information (MUTCD Section 2L.05)

← Older revision		Revision as of 08:54, 10 December 2025
Line 184:		Line 184:
	\|-		\|-
	\| colspan="3" style="text-align: left; background-color: #ffffff;min-width: 400px;" \| Note: the following is an example of a two-phase message that could be developed<br />from the four information units shown in this table:<br />		\| colspan="3" style="text-align: left; background-color: #ffffff;min-width: 400px;" \| Note: the following is an example of a two-phase message that could be developed<br />from the four information units shown in this table:<br />
	<div style="text-align: center;"><span style="display: inline-block">[[File:UnitsOfInformation_Phase1.png\|center\|alt="Major Crash at Exit 12", Phase 1]]</span>   <span style="display: inline-block">[[File:~~UnitsOfInformation_Phase1~~.png\|center\|alt="Use Route 46 to New York", Phase 2]]</span></div>		<div style="text-align: center;"><span style="display: inline-block">[[File:UnitsOfInformation_Phase1.png\|center\|alt="Major Crash at Exit 12", Phase 1]]</span>   <span style="display: inline-block">[[File:UnitsOfInformation_Phase2.png\|center\|alt="Use Route 46 to New York", Phase 2]]</span></div>
	\|}		\|}
	</center>		</center>
Line 215:		Line 215:
	'''Support. '''[[#fig903.12.5.1\|Figures 913.12.5.1]] and [[#fig903.12.5.2\|903.12.5.2]] provide examples of message construction for CMS. Each example shows the message content, layout, and phasing for a potential message and an improved message. The improved message for each example has been optimized for recognition, comprehension, and effectiveness.		'''Support. '''[[#fig903.12.5.1\|Figures 913.12.5.1]] and [[#fig903.12.5.2\|903.12.5.2]] provide examples of message construction for CMS. Each example shows the message content, layout, and phasing for a potential message and an improved message. The improved message for each example has been optimized for recognition, comprehension, and effectiveness.

	See [[910.3 Dynamic Message Signs (DMS)#910.3.2.12_Congestion_Messages#910.3.2.8.1_Design_Characteristics_of_DMSs_(MUTCD_2L.04)\|EPG 910.3.2.8.1]] for additional information regarding Message Length and Units of Information for DMS.		See [[910.3 Dynamic Message Signs (DMS)#910.3.2.12_Congestion_Messages#910.3.2.8.1_Design_Characteristics_of_DMSs_(MUTCD_2L.04)\|EPG 910.3.2.8.1]] for additional information regarding Message Length and Units of Information for DMS.

	{{SpanID\|fig903.12.5.1}}		{{SpanID\|fig903.12.5.1}}
Line 228:		Line 228:
	Example 8: “SEAT BELTS SAVE LIVES” is improved to “STATE LAW FASTEN SEAT BELTS,” clarifying the regulatory requirement. Comments state slogan messages do not convey legal meaning.		Example 8: “SEAT BELTS SAVE LIVES” is improved to “STATE LAW FASTEN SEAT BELTS,” clarifying the regulatory requirement. Comments state slogan messages do not convey legal meaning.
	Example 9: “DON’T TEXT JUST DRIVE” and “IT CAN WAIT” become “NO HAND-HELD PHONE BY DRIVER” and “$250 FINE AND POINTS.” Comments state that slogan messages do not convey enforceable regulations and Phase 2 may be omitted.		Example 9: “DON’T TEXT JUST DRIVE” and “IT CAN WAIT” become “NO HAND-HELD PHONE BY DRIVER” and “$250 FINE AND POINTS.” Comments state that slogan messages do not convey enforceable regulations and Phase 2 may be omitted.
	Each row includes corresponding commentary explaining message clarity, abbreviation rules, safety communication, or regulatory requirements. The table emphasizes improved CMS message structure for readability, consistency, and compliance."		Each row includes corresponding commentary explaining message clarity, abbreviation rules, safety communication, or regulatory requirements. The table emphasizes improved CMS message structure for readability, consistency, and compliance." \|'''Figure 903.12.5.1''' Examples of Message Construction for CMS<br /><br />*Examples shown are for single-color CMS with pixel spacing greater than 20 mm and use all upper-case lettering. Multi-color, fullmatrix CMS with pixel spacing of 20 mm or less should use upper- and lower-case lettering where appropriate and proper legend and background colors.]]
	\|'''Figure 903.12.5.1''' Examples of Message Construction for CMS<br /><br />*Examples shown are for single-color CMS with pixel spacing greater than 20 mm and use all upper-case lettering. Multi-color, fullmatrix CMS with pixel spacing of 20 mm or less should use upper- and lower-case lettering where appropriate and proper legend and background colors.]]

	{{SpanID\|fig903.12.5.2}}		{{SpanID\|fig903.12.5.2}}

HogsettC: /* {{SpanID|903.12.5}}903.12.5 Message Length and Units of Information (MUTCD Section 2L.05) */

2025-12-01T14:17:02Z

{{SpanID|903.12.5}}903.12.5 Message Length and Units of Information (MUTCD Section 2L.05)

@@ Line 218: / Line 218: @@
 {{SpanID|fig903.12.5.1}}
-[[File:Figure 903.12.5.1 Examples of Message Construction for CMS.png|thumb|center|800px|alt=|'''Figure 903.12.5.1''' Examples of Message Construction for CMS<br /><br />*Examples shown are for single-color CMS with pixel spacing greater than 20 mm and use all upper-case lettering. Multi-color, fullmatrix CMS with pixel spacing of 20 mm or less should use upper- and lower-case lettering where appropriate and proper legend and background colors.]]
+[[File:Figure 903.12.5.1 Examples of Message Construction for CMS.png|thumb|center|800px|alt="The figure is a table titled “Examples of Potential and Improved CMS Messages,” showing nine examples of changeable message sign (CMS) messages with three columns: Potential Message, Improved Message, and Comments. Each row presents Phase 1 and Phase 2 messages, along with commentary explaining why the improved version is preferred.
 {{SpanID|fig903.12.5.2}}
-[[File:Figure 903.12.5.2 Examples of Message Construction for CMS.png|thumb|center|800px|alt=|'''Figure 903.12.5.2''' Examples of Message Construction for CMS<br /><br />*Examples shown are for a portable CMS where the display width is generally limited to 8 characters per line of legend.]]
+[[File:Figure 903.12.5.2 Examples of Message Construction for CMS.png|thumb|center|800px|alt="The figure shows a table with eight examples of potential and improved changeable message sign (CMS) messages. The table contains columns for Example number, Phase, Potential Message, Improved Message, and Comments. Each example lists Phase 1 and, if applicable, Phase 2 messages with commentary explaining why the improved message is preferred.
 =={{SpanID|903.12.6}}903.12.6  Travel Time Messages (MUTCD Section 2L.06)==

HogsettC: /* {{SpanID|903.12.4}}903.12.4 Design Characteristics of Messages (MUTCD Section 2L.04) */

2025-12-01T14:14:24Z

{{SpanID|903.12.4}}903.12.4 Design Characteristics of Messages (MUTCD Section 2L.04)

← Older revision		Revision as of 09:14, 1 December 2025
Line 158:		Line 158:

	{{SpanID\|fig903.12.4}}		{{SpanID\|fig903.12.4}}
	[[File:Figure 903.12.4 Example of Capability to display Sign Legends Based on Pixel Pitch.png\|thumb\|center\|600px\|alt=\|'''Figure 903.12.4''' Example of Capability to display Sign Legends Based on Pixel Pitch<br /><br />Notes:<ol><li>Pixel pitch is the distance from the center of a pixel to the center of an adjacent pixel.</li><li>The pixel pitch is described in Metric units because sign manufacturers only use Metric units.</li></ol>]]		[[File:Figure 903.12.4 Example of Capability to display Sign Legends Based on Pixel Pitch.png\|thumb\|center\|600px\|alt="The figure compares two changeable message sign (CMS) displays with different pixel densities. The top image shows a high-resolution full-matrix CMS capable of displaying detailed graphics. It presents a green sign with a blue and red Interstate 40 shield followed by the message “EAST CLOSED USE ALT ROUTE” in white text. A note beside the image explains that color full-matrix CMS with pixel pitches of 20 millimeters or less can display legends similar to conventional highway signs, including route shields and symbols.

			The bottom image shows a low-resolution CMS with larger pixel spacing. The display reads “I-40 EAST CLOSED USE ALT ROUTE” in amber text on a black background. The characters appear blockier and less detailed. A note beside the image explains that CMS with pixel pitches greater than 20 millimeters, whether color or monochrome, cannot adequately display conventional sign legends and should only be used for monochrome word messages."
			\|'''Figure 903.12.4''' Example of Capability to display Sign Legends Based on Pixel Pitch<br /><br />Notes:<ol><li>Pixel pitch is the distance from the center of a pixel to the center of an adjacent pixel.</li><li>The pixel pitch is described in Metric units because sign manufacturers only use Metric units.</li></ol>]]

	=={{SpanID\|903.12.5}}903.12.5 Message Length and Units of Information (MUTCD Section 2L.05)==		=={{SpanID\|903.12.5}}903.12.5 Message Length and Units of Information (MUTCD Section 2L.05)==

WilkeJ: /* {{SpanID|903.12.4}}903.12.4 Design Characteristics of Messages (MUTCD Section 2L.04) */

2025-12-01T13:26:35Z

{{SpanID|903.12.4}}903.12.4 Design Characteristics of Messages (MUTCD Section 2L.04)

← Older revision		Revision as of 08:26, 1 December 2025
Line 158:		Line 158:

	{{SpanID\|fig903.12.4}}		{{SpanID\|fig903.12.4}}
	[[File:Figure 903.12.4 Example of Capability to display Sign Legends Based on Pixel Pitch.png\|thumb\|center\|600px\|alt=\|'''Figure 903.12.4''' Example of Capability to display Sign Legends Based on Pixel Pitch<br /><br />Notes:<ol><li>Pixel pitch is the distance from the center of a pixel to the center of an adjacent pixel.</li><li>The pixel pitch is described in Metric units because sign manufacturers only use Metric units</li></ol>]]		[[File:Figure 903.12.4 Example of Capability to display Sign Legends Based on Pixel Pitch.png\|thumb\|center\|600px\|alt=\|'''Figure 903.12.4''' Example of Capability to display Sign Legends Based on Pixel Pitch<br /><br />Notes:<ol><li>Pixel pitch is the distance from the center of a pixel to the center of an adjacent pixel.</li><li>The pixel pitch is described in Metric units because sign manufacturers only use Metric units.</li></ol>]]

	=={{SpanID\|903.12.5}}903.12.5 Message Length and Units of Information (MUTCD Section 2L.05)==		=={{SpanID\|903.12.5}}903.12.5 Message Length and Units of Information (MUTCD Section 2L.05)==

RollerA: /* {{SpanID|903.12.5}}903.12.5 Message Length and Units of Information (MUTCD Section 2L.05) */

2025-11-25T02:55:26Z

{{SpanID|903.12.5}}903.12.5 Message Length and Units of Information (MUTCD Section 2L.05)

← Older revision		Revision as of 21:55, 24 November 2025
Line 215:		Line 215:

	{{SpanID\|fig903.12.5.1}}		{{SpanID\|fig903.12.5.1}}
	[[File:~~Table2L-3~~.png\|thumb\|center\|800px\|alt=\|'''Figure 903.12.5.1''' Examples of Message Construction for CMS<br /><br />*Examples shown are for single-color CMS with pixel spacing greater than 20 mm and use all upper-case lettering. Multi-color, fullmatrix CMS with pixel spacing of 20 mm or less should use upper- and lower-case lettering where appropriate and proper legend and background colors.]]		[[File:Figure 903.12.5.1 Examples of Message Construction for CMS.png\|thumb\|center\|800px\|alt=\|'''Figure 903.12.5.1''' Examples of Message Construction for CMS<br /><br />*Examples shown are for single-color CMS with pixel spacing greater than 20 mm and use all upper-case lettering. Multi-color, fullmatrix CMS with pixel spacing of 20 mm or less should use upper- and lower-case lettering where appropriate and proper legend and background colors.]]

	{{SpanID\|fig903.12.5.2}}		{{SpanID\|fig903.12.5.2}}
	[[File:~~Table2L-4_v2~~.png\|thumb\|center\|800px\|alt=\|'''Figure 903.12.5.2''' Examples of Message Construction for CMS<br /><br />*Examples shown are for a portable CMS where the display width is generally limited to 8 characters per line of legend.]]		[[File:Figure 903.12.5.2 Examples of Message Construction for CMS.png\|thumb\|center\|800px\|alt=\|'''Figure 903.12.5.2''' Examples of Message Construction for CMS<br /><br />*Examples shown are for a portable CMS where the display width is generally limited to 8 characters per line of legend.]]

	=={{SpanID\|903.12.6}}903.12.6 Travel Time Messages (MUTCD Section 2L.06)==		=={{SpanID\|903.12.6}}903.12.6 Travel Time Messages (MUTCD Section 2L.06)==

RollerA: /* {{SpanID|903.12.4}}903.12.4 Design Characteristics of Messages (MUTCD Section 2L.04) */

2025-11-25T02:51:57Z

{{SpanID|903.12.4}}903.12.4 Design Characteristics of Messages (MUTCD Section 2L.04)

← Older revision		Revision as of 21:51, 24 November 2025
Line 158:		Line 158:

	{{SpanID\|fig903.12.4}}		{{SpanID\|fig903.12.4}}
	[[File:~~Fig2L-1~~.png\|thumb\|center\|600px\|alt=\|'''Figure 903.12.4''' Example of Capability to display Sign Legends Based on Pixel Pitch<br /><br />Notes:<ol><li>Pixel pitch is the distance from the center of a pixel to the center of an adjacent pixel.</li><li>The pixel pitch is described in Metric units because sign manufacturers only use Metric units</li></ol>]]		[[File:Figure 903.12.4 Example of Capability to display Sign Legends Based on Pixel Pitch.png\|thumb\|center\|600px\|alt=\|'''Figure 903.12.4''' Example of Capability to display Sign Legends Based on Pixel Pitch<br /><br />Notes:<ol><li>Pixel pitch is the distance from the center of a pixel to the center of an adjacent pixel.</li><li>The pixel pitch is described in Metric units because sign manufacturers only use Metric units</li></ol>]]

	=={{SpanID\|903.12.5}}903.12.5 Message Length and Units of Information (MUTCD Section 2L.05)==		=={{SpanID\|903.12.5}}903.12.5 Message Length and Units of Information (MUTCD Section 2L.05)==

TaracksA at 17:38, 21 November 2025

2025-11-21T17:38:59Z

← Older revision		Revision as of 12:38, 21 November 2025
Line 1:		Line 1:
	[[Category:903 Highway Signing\|903.12]]		[[Category:903 Highway Signing (MUTCD Part 2)\|903.12]]
	=={{SpanID\|903.12.1}}903.12.1 Description of Changeable Message Signs (MUTCD Section 2L.01)==		=={{SpanID\|903.12.1}}903.12.1 Description of Changeable Message Signs (MUTCD Section 2L.01)==

HogsettC: /* {{SpanID|903.12.6}}903.12.6 Travel Time Messages (MUTCD Section 2L.06) */

2025-11-20T16:11:28Z

{{SpanID|903.12.6}}903.12.6 Travel Time Messages (MUTCD Section 2L.06)

← Older revision		Revision as of 11:11, 20 November 2025
Line 224:		Line 224:
	'''Support. '''Travel times provide road users useful information about the level of congestion on segments of highways where motorists experience frequent incidents that slow traffic. Travel times are only helpful to the road user if they have a general understanding of the length of the road segment the travel time is related to so that they can compare that to the time it takes them to travel a similar distance on a highway without congestion. However, travel time messages require road users to read and process a significant amount of information and careful consideration is needed to ensure the overall message is not overloading the motorist.		'''Support. '''Travel times provide road users useful information about the level of congestion on segments of highways where motorists experience frequent incidents that slow traffic. Travel times are only helpful to the road user if they have a general understanding of the length of the road segment the travel time is related to so that they can compare that to the time it takes them to travel a similar distance on a highway without congestion. However, travel time messages require road users to read and process a significant amount of information and careful consideration is needed to ensure the overall message is not overloading the motorist.

	'''Guidance. '''Travel times should be tied to the distance to a particular destination or junction so that road users can estimate the level of congestion based on the time to travel that distance. When travel times are displayed on CMS, such as during peak traffic conditions, the message should comply with the provisions of Sections [[--\|2E.49]] and [[--\|2E.50]]. If both a travel time and a distance are displayed, the sign should display only one destination. A distance displayed as part of a travel time message should be rounded to the nearest whole mile.		'''Guidance. '''Travel times should be tied to the distance to a particular destination or junction so that road users can estimate the level of congestion based on the time to travel that distance. When travel times are displayed on CMS, such as during peak traffic conditions, the message should comply with the provisions of Sections [[903.5 Guide Signs - Freeways and Expressways (MUTCD Chapter 2E) #903.5.47\|EPG 903.5.47]] and [[903.5 Guide Signs - Freeways and Expressways (MUTCD Chapter 2E) #903.5.48\|903.5.48]]. If both a travel time and a distance are displayed, the sign should display only one destination. A distance displayed as part of a travel time message should be rounded to the nearest whole mile.

	'''Option. '''When comparative travel time displays are used providing travel times on different routes to one destination, distances to that destination may be eliminated.		'''Option. '''When comparative travel time displays are used providing travel times on different routes to one destination, distances to that destination may be eliminated.

← Older revision		Revision as of 08:26, 1 December 2025
Line 158:		Line 158:

	{{SpanID\|fig903.12.4}}		{{SpanID\|fig903.12.4}}
	[[File:Figure 903.12.4 Example of Capability to display Sign Legends Based on Pixel Pitch.png\|thumb\|center\|600px\|alt=\|'''Figure 903.12.4''' Example of Capability to display Sign Legends Based on Pixel Pitch<br /><br />Notes:<ol><li>Pixel pitch is the distance from the center of a pixel to the center of an adjacent pixel.</li><li>The pixel pitch is described in Metric units because sign manufacturers only use Metric units</li></ol>]]		[[File:Figure 903.12.4 Example of Capability to display Sign Legends Based on Pixel Pitch.png\|thumb\|center\|600px\|alt=\|'''Figure 903.12.4''' Example of Capability to display Sign Legends Based on Pixel Pitch<br /><br />Notes:<ol><li>Pixel pitch is the distance from the center of a pixel to the center of an adjacent pixel.</li><li>The pixel pitch is described in Metric units because sign manufacturers only use Metric units.</li></ol>]]

	=={{SpanID\|903.12.5}}903.12.5 Message Length and Units of Information (MUTCD Section 2L.05)==		=={{SpanID\|903.12.5}}903.12.5 Message Length and Units of Information (MUTCD Section 2L.05)==

← Older revision		Revision as of 21:51, 24 November 2025
Line 158:		Line 158:

	{{SpanID\|fig903.12.4}}		{{SpanID\|fig903.12.4}}
	[[File:~~Fig2L-1~~.png\|thumb\|center\|600px\|alt=\|'''Figure 903.12.4''' Example of Capability to display Sign Legends Based on Pixel Pitch<br /><br />Notes:<ol><li>Pixel pitch is the distance from the center of a pixel to the center of an adjacent pixel.</li><li>The pixel pitch is described in Metric units because sign manufacturers only use Metric units</li></ol>]]		[[File:Figure 903.12.4 Example of Capability to display Sign Legends Based on Pixel Pitch.png\|thumb\|center\|600px\|alt=\|'''Figure 903.12.4''' Example of Capability to display Sign Legends Based on Pixel Pitch<br /><br />Notes:<ol><li>Pixel pitch is the distance from the center of a pixel to the center of an adjacent pixel.</li><li>The pixel pitch is described in Metric units because sign manufacturers only use Metric units</li></ol>]]

	=={{SpanID\|903.12.5}}903.12.5 Message Length and Units of Information (MUTCD Section 2L.05)==		=={{SpanID\|903.12.5}}903.12.5 Message Length and Units of Information (MUTCD Section 2L.05)==