Difference between revisions of "Road names/USA"

From Wazeopedia
(Exit ramps and entrance ramps (on-ramps){{Anchor|Exit|Entrance|Ramp}}: Deprecate inclusion of unsigned exit identifiers in generic USA guidance, as per forum discussion.)
 
(164 intermediate revisions by 32 users not shown)
Line 1: Line 1:
[[Map Editing (new Editor)#Editing Manual |Back to Map Editing]]
+
For Road Types in the editor see [[Road types/USA]]
  
 +
''This page covers road names for the country listed in the page title. For other countries see [[Road types and names|this page]].''
  
''Please note UK-specific guidelines can be found [http://www.waze.com/wiki/index.php/How_to_label_and_name_roads_%28United_Kingdom%29#Road_types here]''
+
==Road naming==
  
==Labeling; giving your road the correct road type==
+
'''NOTE''': we are in the process of revising the names as they appear in WME. In the future we may be able to display alternate names for each segment / road, and choose which one of these is the 'common' name. This is also true for road shield generation which is partially broken so shields may or may not be displayed in your area.
''For more help on labeling roads, see [[Map Legend]].''
 
  
While editing the maps, you will notice that some of the roads are not labeled properly. This means, the road type might be wrong (a highway is marked as a street) or that one road has a few road types (a highway is marked as Freeway, highway and primary at different segments).
+
If you are not sure about changing the name of a road, it is best to ask in the forum or wait until the changes described above are implemented.
  
The importance of proper labeling is in two aspects:
+
'''IMPORTANT! Due to upgrades in the client, some naming conventions have changed. The altered conventions will be marked with a bolded *NEW*.''' These changes have now been finalized. Thank you for your cooperation.
1. When viewing the map, the 'bigger' roads should appear at the far zoom levels. Without proper labels, the 'zoomed out' display can be very confusing.
 
2. When planning a route, major roads will get priority over smaller roads. For example, 6 miles on the US Hwy 101 are better than 6 miles on El Camino Real.
 
  
When editing your area and labeling roads, please work with these definitions in mind
+
All roads in our base maps came with the names as defined in the US TIGER dataset.
  
===='''Freeway'''====
+
However, you might notice a few problems with the original road names:
These are interstates (such as I-90), highways, freeways and expressways that '''are multi-lane, divided roads with no stops''' (no traffic lights, exit and entrance from/to the road is through ramps) <br/>
+
Some of the names are not the 'common' names (usually, waze will display the 'name' of the hwy while most people know this hwy by its number).
  
===='''Major Highway'''====
+
On other examples, the same highway will have a different name on each side (for example, US Hwy 101 going North, and Bayshore Fwy going South).
A big highway, usually 3+ lanes, with minimal stops – mostly exits and interchanges, but possibly with some intersections and junctions (most US Highways and some State Highways)<br/>
 
  
===='''Minor Highways'''====
+
Some roads actually have two 'common' names (for example, the NJ Turnpike is also I-95 and both are relevant names), but currently we can only display one name per road.
Usually a narrower highway, 2 lanes or less, that has stops or traffic lights at almost every intersection, but is still a highway (minor US or state highway).  These roads are generally important thoroughfare that goes through several cities or towns. <br/>
 
  
===='''Ramps'''====
+
For all these issues, we ask that you currently leave the situation as is. We are working on a few fixes, that will automate the proper naming and also allow multiple names for each segments (with a 'Primary' name as the one being displayed, but other names that bring up the same search results).
When traffic moves between two roads or highways that are at different grades without the use of traffic lights or stop signs, they use ramps. The typical example is the on-ramps or off-ramps of a highway.  Roads connecting a highway with a rest/service/parking area should be treated as ramps as well and named accordingly (e.g. "Exit to Service Area").
 
  
When traffic moves between two roads that are at the '''same''' grade, these connecting segments are not technically ramps to WazeThese cases should be treated as [[At-Grade Connectors]].
+
===Concurrent names===
 +
'''Overlapping Highways -''' When two or more numbered highways (or interstates) run concurrently (one stretch of road has multiple route numbers), the segment should be named after the '''primary''' of the routes.  The primary route will usually have one or more of the following attributes:
 +
* The route whose mile markers are used for the concurrent segment
 +
* The route whose exit numbers are used for the concurrent segment
 +
* When the concurrency ends, the route whose path does '''not''' get signed as a numbered exit.
 +
The other route number(s) can be entered as alternate namesIf alternate names are entered, be sure not to introduce any alternate name discontinuities which may trigger the [[Detour Prevention Mechanisms/USA|big detour prevention mechanism]].
  
===='''Primary Street'''====
+
'''Highways through cities/towns -''' In situations where a highway passes through a town, the road in those areas is typically named something other than the numbered route. In these situations the road should be named based on the following conditions:
These are major roads or boulevards in urban and suburban areas and have large amounts of use (such as Middlefield Rd. in Menlo Park, Park blvd. in Oakland, Constitution Ave. in Washington, DC).  In less urban environments they are main thoroughfares in towns that are not US or state highways. <br/>
+
* If the local street signs provide guidance with the local name, that should be used as the primary name in the Waze map. The numbered route should be added as an alternate name.  
 +
* If the local signs only indicate the route number, then that should be the primary name and the local road name should be added as an alternate name.
  
===='''Street'''====
+
===United States Interstate Highway System  [[Image:I-95.svg.png|28px]]  [[Image:I-695.svg.png|35px]]===
These are normal streets that hold only a normal amount of traffic. <br/>
+
: Components of the Interstate Highway System should be denoted as shown:
 +
:: '''I-10 E''' for Interstate 10, Eastbound
 +
:: '''I-310 S''' for Interstate 310, Southbound
 +
:: '''I-35E N''' for Interstate 35E, Northbound (Letter suffixes are only in Minnesota and Texas)
 +
: Nearly all interstates are divided highways by necessity, and they should be drawn as such in the map for navigational accuracy.
  
===='''Parking Lot Roads'''====
+
===United States Numbered Highways  [[Image:US 20.svg.png|30px]]===
These streets are the entrances and exits, or otherwise main roads going through large parking lots to direct traffic, especially at traffic lights at major boulevards (e.g., shopping malls and commuter parking lots).  Do not map the rows within parking lots because it clutters the map.
 
  
The "parking lot road" designation is also very useful for indicating segments which are driveable but undesirable for routing, such as alleyways (source: gettingthere and ircphoenix). Some exceptions for using this for alleys, are the recently popular residential design which has the main house driveway/garage be "behind" the house on an alley and not the front of the house. In these cases, it is advisable to use Private Road type.
+
The naming of highways is, of course, somewhat more complex than that of normal roads. Therefore, conventions must be followed to assure consistency throughout the map.
  
With the current high penalty assigned to parking lot segments, Waze will do almost anything other than routing along a parking lot segment unless there is no other path at all. Using parking lot roads for ALL roads within a parking lot is not recommended as this will cause Waze to choose a route which has the least number of parking lot segments, which means it will also choose to go against turn restrictions from main roads.
+
Certain formatting guidelines must be followed to ensure that highway shields are shown in the Live Map and in the client. Note that currently shield generation is not currently operating at 100%, so some areas do not have the shields on all roads. Waze has said that there will eventually be a process allowing map editors to add shields to road segments in a way that is not connected to the name OF that segment.
  
The current recommendation is to use a single parking lot segment for every location which connects to external streets and then use street type segments for all main drive segments within the parking lot itself. This reduces the penalties and Waze will choose better routes within parking lots and not go against turn restrictions. But because that single parking lot segment is there, Waze should not route through the parking lot to get to other destinations.
+
; US Highways
 +
: Federal highways should be denoted as follows. Note that the trailing N, S, E, W cardinal direction indicator is used for numbered highways and interstates which are split into two 1-way segments, [[Best_map_editing_practice#When_.28Not.29_to_Split_a_Two-Way_Road|per the guidelines]].
  
Parking lot roads also provide the benefit of allowing turn restrictions to be properly set upon entry and exit of the parking lotIn addition, the proper use of parking lot roads can also help to avoid automated traffic jam reports as well as Papyrus Map Problems related to Wazers driving in unmapped parking lots. http://www.waze.com/forum/viewtopic.php?f=10&t=13825&start=20#p117202
+
:: '''US-61 S''' for U.S. Highway 61, Southbound
 +
:: '''US-425 W''' for U.S. Highway 425, Westbound
 +
:: '''US-90 BUS S''' for U.S. Highway 90 Business, Southbound
 +
:::(note that BUS should be all uppercase for TTS to pronounce as "business""Bus", "bus", etc. will pronounce as "Bus".)
 +
:: '''US-90 ALT E''' for U.S. Highway 90 Alternate, Eastbound
 +
:: '''US-199 SPUR''' for U.S. Highway 199 Spur
  
===='''Service Roads'''====
+
: Also refer to the [[#Concurrent_names|concurrent names]] section when the highway passes through a city or town that also has a local name for the road.
These are streets, sometimes called frontage roads, that are typically adjacent to a freeway (or major highway). These could be access roads to the highway itself, but have the property of a regular or primary street.<br/>
 
  
===='''Private Roads'''====
+
===State highways  [[Image:State Hwy Sign 35.svg.png|30px]] [[Image:South_Carolina_170.svg.png|38px]] [[Image:Florida_60.svg.png|30px]] [[Image:Louisiana 3234.svg.png|30px]] [[Image:Alabama_5.svg.png|30px]] [[Image:MT-sec-326.svg.png|30px]] [[Image:North_Dakota_23.svg.png|30px]] [[Image:Hawaii_marker.png|30px]]===
A road that is not open to the public. You can drive on it, physically, but there may be legal (and physical) restrictions or it is a privately maintained road on private land. Private Roads are also acceptable for residential areas where the garage entry for homeowners is a common alley between a row of houses. This type of back-of-house garage has become popular in recent years.
+
; State Highways
 +
: The Live Map will parse "State Rte xx" and "State Hwy yyy" and show a sign badge. However, as different states have different naming conventions (and different shields), this is not optimal for ramps. Local naming conventions are preferred for ramps and exits; this will be discussed below. Consistency within each state is key. '''*NEW*'''
 +
: The same note for U.S. Highways above applies for state highways.  LA-308 in Golden Meadow should have "E Main St" as its primary name since that is the name used in addresses of houses and businesses along the highway.
 +
: State routes may also be split if it [[Best_map_editing_practice#When_.28Not.29_to_Split_a_Two-Way_Road|meets the guidelines]].
  
==Naming: giving your road the proper name==
+
: Each state may use a longer or shorter naming format. See the [[Highway naming/USA|highway naming by state]] table for specific formatting of each state.
  
'''NOTE''': we are in the process of revising the names as they appear in the cartouche. In the near future we will be able to display alternate names for each segment / road, and choose which one of these is the 'common' name. <br/>
+
: Long Names
If you are not sure about changing the name of a road, it is best to ask in the forum or wait until the changes described above are implemented.
+
:: '''State Hwy 6''' for state highway 6
 +
:: '''State Hwy 99W S''' for state highway 99W, southbound
 +
:: '''State Rte 96''' for state route 96
  
'''IMPORTANT! Due to upgrades in the client, some naming conventions have changed. The altered conventions will be marked with a bolded *NEW*.''' These changes have now been finalized. Thank you for your cooperation.
+
: Short Names
 +
:: Use the '''SR-xxx''' or '''SH-xxx''' formats instead of '''State Rte xxx''' and '''State Hwy xxx''' format as appropriate for the state, while keeping the same cardinal, business, etc. extensions as described above. These shortened formats are now preferred over the Long Names for all applications.
  
====Highways====
+
::{{Red|'''NOTE:''' In some states there are other formats used, e.g., in Louisiana, use the LA-xxx format. Refer to the [[Highway naming/USA|highway naming by state]] table for specific formatting of each state.}}
  
The naming of highways is, of course, somewhat more complex than that of normal roads.  Therefore, conventions must be followed to assure consistency throughout the map.
+
: Also refer to the [[#Concurrent_names|concurrent names]] section when the highway passes through a city or town that also has a local name for the road.
  
<blockquote>'''NOTE:''' All roads in our base maps came with the names as defined in the US TIGER dataset. <br/>
+
===County and township highways and roads  [[Image:Baldwin County Route 64 AL.svg.png|35px]] [[Image:St Louis County Route 7 MN.svg.png|35px]]===
However, you might notice a few problems with the original road names:
 
Some of the names are not the 'common' names (usually, waze will display the 'name' of the hwy while most people know this hwy by its number) <br/>
 
On other examples, the same highway will have a different name on each side (for example, US Hwy 101 going North, and Bayshore Fwy going South).<br/>
 
Some roads actually have two 'common' names (for example, the NJ Turnpike is also I- 95 and both are relevant names), but currently we can only display one name per road.<br/>
 
  
For all these issues, we ask that you currently leave the situation as is. We are working on a few fixes, that will automate the proper naming and also allow multiple names for each segments (with a 'Primary' name as the one being displayed, but other names that bring up the same search results).</blockquote>
+
Text to speech on the client reads CR- as "County Road." So "CR-10" is read as "County Road Ten"
  
'''Highways in the United States'''
+
Where road names are the same as cardinal directions (N, S, E, W), [[Road_names/USA#United_States_Numbered_Highways|no special modification is necessary]] so that the voice prompt will read the letter and not say it as a direction. Ensure there are no spaces between the hyphen and the letter. Double or triple-letter roads with directional letters (e.g. CR-EN, CR-SAL) will not be spoke as directions, but might be pronounced as if a word.
  
Certain formatting guidelines must be followed to ensure that highway shields are shown in the Live Map and in the client.
+
There is no other TTS abbreviation for county owned roads in any capacity except those listed here. For these reasons: that county shields may someday be supported (and a named standard makes this easier to implement), and for brevity's sake in turn instructions and map displays, it is suggested (but by no means required) that individual states adopt one of these standards;
 +
*CR-
 +
*CH-
 +
*TR-
 +
*TH-
  
; Interstate Highways '''*NEW*'''
+
Another standard in use (which is longer, but you may see) is 'County Hwy XX'. The shortened format of CH- is available and is encouraged to be adopted when CR- is not appropriate.
: Components of the Interstate Highway System should be denoted as shown:
 
:: '''I-10 E''' for Interstate 10, Eastbound
 
:: '''I-310 S''' for Interstate 310, Southbound
 
:: '''I-35E N''' for Interstate 35E, Northbound (this is a rare case)
 
: Nearly all interstates are divided highways by necessity, and they should be drawn as such in the map for navigational accuracy.
 
  
: When two or more interstates run concurrently (one stretch of road has multiple route numbers), the segment should be named after the '''primary''' of the routes. The primary route will usually have one or more of the following attributes:
+
Many states have adopted the short format '''CR-xxx''' instead of the longer format. See the [[Highway naming/USA|highway naming by state]] table for specific formatting of each state.
:* The route whose mile markers are used for the concurrent segment
 
:* The route whose exit numbers are used for the concurrent segment
 
:* When the concurrency ends, the route whose path does '''not''' get signed as a numbered exit.
 
: The other route number or numbers can be entered as alt names via the old editor (Cartouche), but shields are currently not being generated for alt names.
 
  
; US Highways
+
: Also refer to the [[#Concurrent_names|concurrent names]] section when the highway passes through a city or town that also has a local name for the road.
: Federal highways should be denoted as follows. Note that the trailing N, S, E, W directionality indicator is used for highways and interstates which are split into two 1-way segments, [[Best_map_editing_practice#When_.28Not.29_to_Split_a_Two-Way_Road|per the guidelines]].
 
:: '''US Hwy 61 S''' for U.S. Highway 61, Southbound
 
:: '''US Hwy 90 W''' for U.S. Highway 425, Westbound
 
:: '''US Hwy 90 Bus S''' for U.S. Highway 90 Business, Southbound
 
:: '''US Hwy 90 Alt E''' for U.S. Highway 90 Alternate, Eastbound
 
:: '''US Hwy 199 Spur''' for U.S. Highway 199 Spur
 
: Use this format and not "US-90" or "US- 90" because this is the format that the Live Map and client will parse.
 
: U.S. Highways will often have local road names (such as Airline Hwy for US 61 and Claiborne Ave for US 90, among others).  Use these street names as the '''primary''' name for such highways if said name is used for addresses of houses and businesses along the highway.
 
  
; State Highways
+
For regions that have township highways, the shortened formats of TH- and TR- are also available.
: The Live Map will parse "State Rte xx" and "State Hwy yyy" and show a sign badge. However, as different states have different naming conventions (and different shields), this is not optimal for ramps. Local naming conventions are preferred for ramps and exits; this will be discussed below. Consistency within each state is key. '''*NEW*'''
 
: The same note for U.S. Highways above applies for state highways.  LA-308 in Golden Meadow should have "E Main St" as its primary name since that is the name used in addresses of houses and businesses along the highway.
 
: State routes may also be split if it [[Best_map_editing_practice#When_.28Not.29_to_Split_a_Two-Way_Road|meets the guidelines]]. Similar to interstates and US highways, state routes are named as follows:
 
:: '''State Hwy 6''' for state route/highway 6
 
:: '''State Hwy 99W S''' for state route 99W, southbound
 
:: '''State Rte 96''' for state route 96
 
  
====Exit ramps and Entrance ramps (on-ramps)====
+
===Exit ramps and entrance ramps (on-ramps){{Anchor|Exit|Entrance|Ramp}}===
 +
{{construction
 +
| contact    = http://www.waze.com/forum/viewtopic.php?f=276&t=101346&start=30
 +
| contacttype = forum
 +
| draft      = no
 +
| open        = no
 +
| revision    = yes
 +
| section    = yes
 +
| talk        = no
 +
}}
  
Exit ramps and Entrance ramps are to be set as Ramp road type. The name of the ramp should match the exit or entrance signage as closely as possible. Minimal disparity between sign and instruction is our goal. If done properly, the driver will not have to struggle to compare Waze's on-screen or verbal instructions with what he or she sees in real life on the road.
+
[[Image:Exit1.JPG|right|200px]][[Image:Exit2.jpg|right|200px]]
* If the exit sign shows a number as well as a street or highway name, the exit ramp should be named "Exit 24: Schwarzenegger Rd". '''*NEW*'''
+
Exit ramps and Entrance ramps are to be set as {{Ramp}} road type. The name of the ramp should match the exit or entrance signage as closely as possible. Minimal disparity between sign and instruction is our goal. If done properly, the driver will not have to struggle to compare Waze's on-screen or verbal instructions with what he or she sees in real life on the road.
** A colon has been added because it adds a pause, making Text-to-Speech directions easier to understand.
+
* If an exit is signed and numbered, name the exit ramp as such: "Exit 24: US-103 / Schwarzenegger Rd". In other words, start with the word "Exit" followed by the exit number, follow the exit number with a colon (": "), and separate all elements (shields and names) after the colon with slashes (" / ").
* If the exit is not numbered, "Exit to Kindergarten Ct" will do.
+
* If an exit is signed and unnumbered, name the exit ramp as such: "to SR-33 / Kindergarten Ct". In other words, start with the word "to" (lowercase) followed by all elements on the sign (shields and names), separated with slashes (" / "). {{Red|'''(Rule change: August 2014.)'''}}
* If a single exit serves multiple roads, use a slash with leading and trailing spaces: "Exit 32: Terminator Blvd / Total Recall Rd". '''*NEW*'''
+
** If the exit identifier does not appear on any signs, then do not include it, even if it is documented elsewhere. Including unsigned information in Waze instructions can confuse drivers. Some states may have exceptions to this guideline; check your [[Mapping resources/USA|state page]] for details.  {{Red|'''(Rule change: May 2016.)'''}}
 +
* If an exit is unsigned, include the designation and/or name of the road as if it is signed (i.e., starting with "to"). For example, if an unsigned exit serves "US-12", a signed highway which is locally known as "Michigan Ave", name the ramp segment "to US-12 / Michigan Ave". If only a local name or only a highway designation are present, use only that.
 +
* If a single exit serves multiple roads or cities, use a slash with leading and trailing spaces: "Exit 32: Terminator Blvd / Total Recall Rd".
 +
* If an exit number contains one or more letters, include it exactly as displayed on the sign: "Exit 33B: Running Man St", or "Exits 35C-B-A: Junior Dr / Twins Ave / Jingle Allthe Way".
 +
** Separate sub-exit letters with a hyphen. Do not leave spaces between the hyphen and the adjacent characters.
 
* Include everything that is present on the last sign prior to the exit. Do not combine all possible pre-ramp signage into the single ramp segment name.
 
* Include everything that is present on the last sign prior to the exit. Do not combine all possible pre-ramp signage into the single ramp segment name.
* If the exit off the main interstate or highway serves multiple exits further down the road, it may be advisable not to name the first exit ramp, to name only the ramps which are the first one to a distinct destination. The Waze client will give all the proper exit and keep left or right instructions to guide the driver to the correct exit, even if the first one is not named. That said, this should only be done if the signage for the first ramp is the same as that on the subsequent, named ramp.
+
* Remember to abbreviate common words following the [[abbreviations and acronyms/USA]] page.
 +
* If the exit off the main interstate or highway serves multiple exits further down the road, it may be advisable not to name the first exit ramp, but rather name only the ramps which are the first one to a distinct destination. The Waze client will give all the proper exit and keep left or right instructions to guide the driver to the correct exit, even if the first one is not named. That said, this should only be done if the signage for the first ramp is the same as that on the subsequent, named ramp.
  
 
For entrance ramps, use this format: "to [street name] [direction] / [control city]", where applicable.  For example,
 
For entrance ramps, use this format: "to [street name] [direction] / [control city]", where applicable.  For example,
 
* "to I-10 W / Baton Rouge"
 
* "to I-10 W / Baton Rouge"
 
* "to Clearview Pkwy N / Mandeville"
 
* "to Clearview Pkwy N / Mandeville"
* "to US Hwy 90 Bus W"
+
* "to US-90 BUS W"
* "to LA-1 Thibodaux / Lockport" '''*NEW*'''
+
* "to LA-1 / Thibodaux / Lockport"
 
* Similar to combined exit ramps, when multiple on-ramps combine before merging into the main interstate or highway, it is advised to name the last common ramp with the conventions listed above. This will usually be the last ramp which is the one which actually joins the main interstate or highway.
 
* Similar to combined exit ramps, when multiple on-ramps combine before merging into the main interstate or highway, it is advised to name the last common ramp with the conventions listed above. This will usually be the last ramp which is the one which actually joins the main interstate or highway.
 
* Using "Ramp to", "West", "WB", and "Westbound" should be avoided as "WB" is pronounced "double-you bee" and not 'westbound.'  Further, the "to" will be automatically omitted from Text-to-Speech instructions. Do not omit the word "to", because this could cause confusion with, say, the "Select entire street" function.
 
* Using "Ramp to", "West", "WB", and "Westbound" should be avoided as "WB" is pronounced "double-you bee" and not 'westbound.'  Further, the "to" will be automatically omitted from Text-to-Speech instructions. Do not omit the word "to", because this could cause confusion with, say, the "Select entire street" function.
* '''State highways:''' When naming ramps and exits that lead to state highways, local naming should be used. This will maximize the clarity of navigation prompts for the majority of users in a given area. '''*NEW*''' For example,
+
* '''State highways:''' When naming ramps and exits that lead to state highways, local naming should be used. This will maximize the clarity of navigation prompts for the majority of users in a given area. For example,
 
** In New Jersey, highways are generally colloquially referred to as "routes". To distinguish from other (federal) highways, a sign for State Route 45 in New Jersey should say "to State Rte 45". In this case, the abbreviation "to SR-45" may also be used.
 
** In New Jersey, highways are generally colloquially referred to as "routes". To distinguish from other (federal) highways, a sign for State Route 45 in New Jersey should say "to State Rte 45". In this case, the abbreviation "to SR-45" may also be used.
** In Tennessee, highways are generally colloquially referred to as "highways". To distinguish from other (federal) highways, a sign for Tennessee Highway 62 should say "to State Hwy 62".
+
** In Louisiana, state highways are generally colloquially referred to as "LA" (ell-ay) followed by the highway number. A ramp to Louisiana Highway 308 should be say "to LA-308".
** In Louisiana, state highways are generally colloquially referred to as "LA" followed by the highway number. A ramp to Louisiana Highway 308 should be say "to LA-308".
 
** In Pennsylvania, state routes are generally colloquially referred to as "PA" followed by the route number. A ramp to Pennsylvania Route 308 should be say "to PA-308".
 
 
** In North Carolina (NC), state routes are generally colloquially referred to as "NC" followed by the route number. A ramp to NC Highway 55 should be say "to NC-55".
 
** In North Carolina (NC), state routes are generally colloquially referred to as "NC" followed by the route number. A ramp to NC Highway 55 should be say "to NC-55".
* Similar to exit ramps, put multiple destination information, even from multiple signage, onto the single on-ramp name. Major destinations or highways/interstates can be included, but don't go crazy and add every possible town and city in that direction.  "to US Hwy 90 Bus W to I-10 W Miss River Br / Baton Rouge" is fine.
+
** In general, follow the chart in the [[road naming by state]] article.
 +
* Similar to exit ramps, put multiple destination information, even from multiple signage, onto the single on-ramp name. Major destinations or highways/interstates can be included, but don't go crazy and add every possible town and city in that direction.  "to US-90 BUS W / to I-10 W / Miss River Brg / Baton Rouge" is fine.
 +
 
 +
===New streets===
 +
 
 +
Sometimes, there is a brand new road that does not yet have a name visible to drivers. Or the person who used the pave option did not leave a note giving the name of the new road. In these cases, it is okay to leave the name of the road blank by marking the "None" checkbox next to the '''Name''' field in the [[Creating and editing road segments#Address Properties|Address Properties]] in the editor. Always make sure to choose the proper [[Road types/USA|road type]] and [[Creating and editing road segments#Confirm the road by updating details|confirm the other road details]] to ensure that the road appears on the client app.
 +
 
 +
=== Incomplete segments or red roads ===
 +
 
 +
[[File:Incomplete.jpg|right|120px|Incomplete.jpg]] Be sure to select country, state, enter the city name or check "None", and enter a street name, or check "None". Until you do this, your road will not be routable and will not show on the client map. These incomplete segments are colored bright red in WME.
 +
 
 +
This must be done on all streets created in WME, and on all streets created with the client "Pave" function.
  
====New streets====
+
"Paved" streets must also be connected to their adjacent roads, and [[Creating and editing road segments#Set allowed turns .28connections.29 turn restrictions|turn restrictions]] must be set in order to be routable.
  
In some cases, there is no prior name since it is a new road that you just recorded. In this case, make sure to choose the proper road type. <br/>
+
For more detailed instructions on how to address red roads see: [[Creating and editing road segments#Confirm the road by updating details|Confirming the road by updating details]]
  
== Abbreviations ==
+
=== Navigation instructions for unnamed segments  ===
Expansion of this section is pending.
+
{{User:PesachZ/Navigation instructions for unnamed segments/Conditions|transclude=yes}}
 +
 
 +
== Abbreviations and acronyms ==
  
 
Only abbreviations that Waze recognizes should be used within the editor. Since Waze uses TTS (Text-to-Speech) prompting, it is important that the correct abbreviations are used to produce the correct speech output.
 
Only abbreviations that Waze recognizes should be used within the editor. Since Waze uses TTS (Text-to-Speech) prompting, it is important that the correct abbreviations are used to produce the correct speech output.
  
Please refer to the following Waze forum for a "work in progress" list of abbreviations that are being tested, currently available and proposed:
+
A basic rule of thumb is, "when in doubt, spell it out".
 +
 
 +
Refer to the [[Abbreviations and acronyms/USA]] page for a list of suffix and recommended abbreviations.
 +
 
 +
== {{Anchor|Construction zone}}Construction zones and closed roads ==
 +
''{{Red|This standard has recently changed {{As of|2014|12|df=us|lc=y}}. Please pay close attention to the changes.}}''
 +
 
 +
This section describes the naming of roads that are closed. See the article [[Real time closures]] for instructions on how to enact a closure on a road segment. The closure should be enacted before renaming the road segments.
 +
 
 +
This section also describes what actions to take when a road remains open, but there are significant changes to it while construction completes.
 +
 
 +
===Brief closures===
 +
{{Red|Roads can be closed using the Waze application for brief closures.}} Don't change the map for closures that will last less than about a month. Instead, use the Waze app Road Closed reporting function.
 +
 
 +
===Long term closures===
 +
 
 +
'''Updated {{As of | 2014 | 12 | df=us | lc=y}}'''<br />
  
http://www.waze.com/forum/viewtopic.php?f=10&t=15178
+
The requirement to add '(Closed)' to a road segment has been deprecated. Adding this phrase to a road segment can cause routing/navigation issues for Wazers.
  
Also refer to the other various ongoing discussions regarding abbreviations and TTS in the Waze forums.
+
===Major construction without closure===
  
== Construction Zones; naming large sections of major roads that are under construction ==
+
'''Updated {{As of | 2014 | 12 | df=us | lc=y}}<br />
  
===Basic Rules===
+
{{Red|''It is no longer necessary to add '(Construction Zone)' to any road under construction.  Adding this phrase can cause routing/navigation issues and serves no purpose in the app or for the Wazer.''}}
  
Start by following the naming rules for your major roads. Interstate as "I-10 S". 
+
If there is a significant change to traffic patterns or geometry (lane shifts), adjust the geometry, connections, and restrictions of the segments to match the current traffic pattern. You must be able to monitor the area, and readjust once the construction is complete, or when additional changes are made during construction.
US highways as "US Hwy 90".  To show that the segments are part of a construction zone, just add the suffix "CONST ZN".  "I-10 S" becomes "I-10 S CONST ZN".
 
"US Hwy 90" becomes "US Hwy 90 CONST ZN".
 
  
When temporarily re-setting road geometry, closely monitor recent GPS points as the aerial maps will likely display an out-dated view. Also, be sure to closely monitor these sections of roadway and remove the CONST ZN suffix whenever the construction is done.
+
== Official sources of mapping information ==
  
 +
Being in the Waze community of editors means sharing information you discover and learning from the discoveries of others! You can see some of the (old) [http://www.waze.com/forum/viewtopic.php?f=129&t=13695 official sources of mapping information (US only) provided in the forum] or check out the (new) [[Mapping resources/USA|mapping resources]] wiki page (preferred).
  
== Official Sources of Mapping information ==
+
Feel free to add new resources as you find them.
  
Being in the Waze community of editors means sharing information you discover and learning from the discoveries of others! You can see some of the [http://www.waze.com/forum/viewtopic.php?f=129&t=13695| official sources of mapping information (US only) provided in the forum] and feel free to add new ones.
+
{{ReturnTo | Editing manual | the editing manual}}
  
  
[[Map Editing (new Editor)#Editing Manual |Back to Map Editing]]
+
[[Category:USA]]
 +
[[Category:Review redirects]]

Latest revision as of 14:54, 30 May 2016

For Road Types in the editor see Road types/USA

This page covers road names for the country listed in the page title. For other countries see this page.

Road naming

NOTE: we are in the process of revising the names as they appear in WME. In the future we may be able to display alternate names for each segment / road, and choose which one of these is the 'common' name. This is also true for road shield generation which is partially broken so shields may or may not be displayed in your area.

If you are not sure about changing the name of a road, it is best to ask in the forum or wait until the changes described above are implemented.

IMPORTANT! Due to upgrades in the client, some naming conventions have changed. The altered conventions will be marked with a bolded *NEW*. These changes have now been finalized. Thank you for your cooperation.

All roads in our base maps came with the names as defined in the US TIGER dataset.

However, you might notice a few problems with the original road names: Some of the names are not the 'common' names (usually, waze will display the 'name' of the hwy while most people know this hwy by its number).

On other examples, the same highway will have a different name on each side (for example, US Hwy 101 going North, and Bayshore Fwy going South).

Some roads actually have two 'common' names (for example, the NJ Turnpike is also I-95 and both are relevant names), but currently we can only display one name per road.

For all these issues, we ask that you currently leave the situation as is. We are working on a few fixes, that will automate the proper naming and also allow multiple names for each segments (with a 'Primary' name as the one being displayed, but other names that bring up the same search results).

Concurrent names

Overlapping Highways - When two or more numbered highways (or interstates) run concurrently (one stretch of road has multiple route numbers), the segment should be named after the primary of the routes. The primary route will usually have one or more of the following attributes:

  • The route whose mile markers are used for the concurrent segment
  • The route whose exit numbers are used for the concurrent segment
  • When the concurrency ends, the route whose path does not get signed as a numbered exit.

The other route number(s) can be entered as alternate names. If alternate names are entered, be sure not to introduce any alternate name discontinuities which may trigger the big detour prevention mechanism.

Highways through cities/towns - In situations where a highway passes through a town, the road in those areas is typically named something other than the numbered route. In these situations the road should be named based on the following conditions:

  • If the local street signs provide guidance with the local name, that should be used as the primary name in the Waze map. The numbered route should be added as an alternate name.
  • If the local signs only indicate the route number, then that should be the primary name and the local road name should be added as an alternate name.

United States Interstate Highway System I-95.svg.png I-695.svg.png

Components of the Interstate Highway System should be denoted as shown:
I-10 E for Interstate 10, Eastbound
I-310 S for Interstate 310, Southbound
I-35E N for Interstate 35E, Northbound (Letter suffixes are only in Minnesota and Texas)
Nearly all interstates are divided highways by necessity, and they should be drawn as such in the map for navigational accuracy.

United States Numbered Highways US 20.svg.png

The naming of highways is, of course, somewhat more complex than that of normal roads. Therefore, conventions must be followed to assure consistency throughout the map.

Certain formatting guidelines must be followed to ensure that highway shields are shown in the Live Map and in the client. Note that currently shield generation is not currently operating at 100%, so some areas do not have the shields on all roads. Waze has said that there will eventually be a process allowing map editors to add shields to road segments in a way that is not connected to the name OF that segment.

US Highways
Federal highways should be denoted as follows. Note that the trailing N, S, E, W cardinal direction indicator is used for numbered highways and interstates which are split into two 1-way segments, per the guidelines.
US-61 S for U.S. Highway 61, Southbound
US-425 W for U.S. Highway 425, Westbound
US-90 BUS S for U.S. Highway 90 Business, Southbound
(note that BUS should be all uppercase for TTS to pronounce as "business". "Bus", "bus", etc. will pronounce as "Bus".)
US-90 ALT E for U.S. Highway 90 Alternate, Eastbound
US-199 SPUR for U.S. Highway 199 Spur
Also refer to the concurrent names section when the highway passes through a city or town that also has a local name for the road.

State highways State Hwy Sign 35.svg.png South Carolina 170.svg.png Florida 60.svg.png Louisiana 3234.svg.png Alabama 5.svg.png MT-sec-326.svg.png North Dakota 23.svg.png Hawaii marker.png

State Highways
The Live Map will parse "State Rte xx" and "State Hwy yyy" and show a sign badge. However, as different states have different naming conventions (and different shields), this is not optimal for ramps. Local naming conventions are preferred for ramps and exits; this will be discussed below. Consistency within each state is key. *NEW*
The same note for U.S. Highways above applies for state highways. LA-308 in Golden Meadow should have "E Main St" as its primary name since that is the name used in addresses of houses and businesses along the highway.
State routes may also be split if it meets the guidelines.
Each state may use a longer or shorter naming format. See the highway naming by state table for specific formatting of each state.
Long Names
State Hwy 6 for state highway 6
State Hwy 99W S for state highway 99W, southbound
State Rte 96 for state route 96
Short Names
Use the SR-xxx or SH-xxx formats instead of State Rte xxx and State Hwy xxx format as appropriate for the state, while keeping the same cardinal, business, etc. extensions as described above. These shortened formats are now preferred over the Long Names for all applications.
NOTE: In some states there are other formats used, e.g., in Louisiana, use the LA-xxx format. Refer to the highway naming by state table for specific formatting of each state.
Also refer to the concurrent names section when the highway passes through a city or town that also has a local name for the road.

County and township highways and roads Baldwin County Route 64 AL.svg.png St Louis County Route 7 MN.svg.png

Text to speech on the client reads CR- as "County Road." So "CR-10" is read as "County Road Ten"

Where road names are the same as cardinal directions (N, S, E, W), no special modification is necessary so that the voice prompt will read the letter and not say it as a direction. Ensure there are no spaces between the hyphen and the letter. Double or triple-letter roads with directional letters (e.g. CR-EN, CR-SAL) will not be spoke as directions, but might be pronounced as if a word.

There is no other TTS abbreviation for county owned roads in any capacity except those listed here. For these reasons: that county shields may someday be supported (and a named standard makes this easier to implement), and for brevity's sake in turn instructions and map displays, it is suggested (but by no means required) that individual states adopt one of these standards;

  • CR-
  • CH-
  • TR-
  • TH-

Another standard in use (which is longer, but you may see) is 'County Hwy XX'. The shortened format of CH- is available and is encouraged to be adopted when CR- is not appropriate.

Many states have adopted the short format CR-xxx instead of the longer format. See the highway naming by state table for specific formatting of each state.

Also refer to the concurrent names section when the highway passes through a city or town that also has a local name for the road.

For regions that have township highways, the shortened formats of TH- and TR- are also available.

Exit ramps and entrance ramps (on-ramps)

This revision of a section is currently undergoing modifications. The information and guidance is currently considered accurate enough to be followed now. Content is being prepared by one or more users. Do not make any changes before you post a message in this forum.
Exit1.JPG
Exit2.jpg

Exit ramps and Entrance ramps are to be set as  Ramp  road type. The name of the ramp should match the exit or entrance signage as closely as possible. Minimal disparity between sign and instruction is our goal. If done properly, the driver will not have to struggle to compare Waze's on-screen or verbal instructions with what he or she sees in real life on the road.

  • If an exit is signed and numbered, name the exit ramp as such: "Exit 24: US-103 / Schwarzenegger Rd". In other words, start with the word "Exit" followed by the exit number, follow the exit number with a colon (": "), and separate all elements (shields and names) after the colon with slashes (" / ").
  • If an exit is signed and unnumbered, name the exit ramp as such: "to SR-33 / Kindergarten Ct". In other words, start with the word "to" (lowercase) followed by all elements on the sign (shields and names), separated with slashes (" / "). (Rule change: August 2014.)
    • If the exit identifier does not appear on any signs, then do not include it, even if it is documented elsewhere. Including unsigned information in Waze instructions can confuse drivers. Some states may have exceptions to this guideline; check your state page for details. (Rule change: May 2016.)
  • If an exit is unsigned, include the designation and/or name of the road as if it is signed (i.e., starting with "to"). For example, if an unsigned exit serves "US-12", a signed highway which is locally known as "Michigan Ave", name the ramp segment "to US-12 / Michigan Ave". If only a local name or only a highway designation are present, use only that.
  • If a single exit serves multiple roads or cities, use a slash with leading and trailing spaces: "Exit 32: Terminator Blvd / Total Recall Rd".
  • If an exit number contains one or more letters, include it exactly as displayed on the sign: "Exit 33B: Running Man St", or "Exits 35C-B-A: Junior Dr / Twins Ave / Jingle Allthe Way".
    • Separate sub-exit letters with a hyphen. Do not leave spaces between the hyphen and the adjacent characters.
  • Include everything that is present on the last sign prior to the exit. Do not combine all possible pre-ramp signage into the single ramp segment name.
  • Remember to abbreviate common words following the abbreviations and acronyms/USA page.
  • If the exit off the main interstate or highway serves multiple exits further down the road, it may be advisable not to name the first exit ramp, but rather name only the ramps which are the first one to a distinct destination. The Waze client will give all the proper exit and keep left or right instructions to guide the driver to the correct exit, even if the first one is not named. That said, this should only be done if the signage for the first ramp is the same as that on the subsequent, named ramp.

For entrance ramps, use this format: "to [street name] [direction] / [control city]", where applicable. For example,

  • "to I-10 W / Baton Rouge"
  • "to Clearview Pkwy N / Mandeville"
  • "to US-90 BUS W"
  • "to LA-1 / Thibodaux / Lockport"
  • Similar to combined exit ramps, when multiple on-ramps combine before merging into the main interstate or highway, it is advised to name the last common ramp with the conventions listed above. This will usually be the last ramp which is the one which actually joins the main interstate or highway.
  • Using "Ramp to", "West", "WB", and "Westbound" should be avoided as "WB" is pronounced "double-you bee" and not 'westbound.' Further, the "to" will be automatically omitted from Text-to-Speech instructions. Do not omit the word "to", because this could cause confusion with, say, the "Select entire street" function.
  • State highways: When naming ramps and exits that lead to state highways, local naming should be used. This will maximize the clarity of navigation prompts for the majority of users in a given area. For example,
    • In New Jersey, highways are generally colloquially referred to as "routes". To distinguish from other (federal) highways, a sign for State Route 45 in New Jersey should say "to State Rte 45". In this case, the abbreviation "to SR-45" may also be used.
    • In Louisiana, state highways are generally colloquially referred to as "LA" (ell-ay) followed by the highway number. A ramp to Louisiana Highway 308 should be say "to LA-308".
    • In North Carolina (NC), state routes are generally colloquially referred to as "NC" followed by the route number. A ramp to NC Highway 55 should be say "to NC-55".
    • In general, follow the chart in the road naming by state article.
  • Similar to exit ramps, put multiple destination information, even from multiple signage, onto the single on-ramp name. Major destinations or highways/interstates can be included, but don't go crazy and add every possible town and city in that direction. "to US-90 BUS W / to I-10 W / Miss River Brg / Baton Rouge" is fine.

New streets

Sometimes, there is a brand new road that does not yet have a name visible to drivers. Or the person who used the pave option did not leave a note giving the name of the new road. In these cases, it is okay to leave the name of the road blank by marking the "None" checkbox next to the Name field in the Address Properties in the editor. Always make sure to choose the proper road type and confirm the other road details to ensure that the road appears on the client app.

Incomplete segments or red roads

Incomplete.jpg
Be sure to select country, state, enter the city name or check "None", and enter a street name, or check "None". Until you do this, your road will not be routable and will not show on the client map. These incomplete segments are colored bright red in WME.

This must be done on all streets created in WME, and on all streets created with the client "Pave" function.

"Paved" streets must also be connected to their adjacent roads, and turn restrictions must be set in order to be routable.

For more detailed instructions on how to address red roads see: Confirming the road by updating details

Navigation instructions for unnamed segments

When Waze gives navigation instructions to "turn", "exit", or "keep" onto an unnamed segment, it will look for a name it can use. If there is a named segment further along your route, it will use (inherit) that name in the instruction. Named segments connected to the unnamed segment which are not part of your provided route, are not relevant.

The inherited name is only used in the displayed and spoken instruction prompts, it does not affect the actual name of the segment.

This always works for  Freeways  and  Ramps .

As of January 2015, on all other road types (any road type which is not a Freeway or Ramp), this feature only works if:

  1. The combined length of the consecutive unnamed segments is shorter than 400 meters (1,312 feet),
    AND
  2. There are 3 or fewer unnamed segments in a row.


To explain the above conditions from another perspective: If the consecutive unnamed segments measured together are longer than 400 m (1,312 ft), or if there are 4 or more unnamed segments in a row, Waze will NOT show or speak a name in the instructions.


For a more detailed explanation, including side effects and usage examples, please see the Expanded Navigation instructions for unnamed segments page.

Abbreviations and acronyms

Only abbreviations that Waze recognizes should be used within the editor. Since Waze uses TTS (Text-to-Speech) prompting, it is important that the correct abbreviations are used to produce the correct speech output.

A basic rule of thumb is, "when in doubt, spell it out".

Refer to the Abbreviations and acronyms/USA page for a list of suffix and recommended abbreviations.

Construction zones and closed roads

This standard has recently changed as of December 2014. Please pay close attention to the changes.

This section describes the naming of roads that are closed. See the article Real time closures for instructions on how to enact a closure on a road segment. The closure should be enacted before renaming the road segments.

This section also describes what actions to take when a road remains open, but there are significant changes to it while construction completes.

Brief closures

Roads can be closed using the Waze application for brief closures. Don't change the map for closures that will last less than about a month. Instead, use the Waze app Road Closed reporting function.

Long term closures

Updated as of December 2014

The requirement to add '(Closed)' to a road segment has been deprecated. Adding this phrase to a road segment can cause routing/navigation issues for Wazers.

Major construction without closure

Updated as of December 2014

It is no longer necessary to add '(Construction Zone)' to any road under construction. Adding this phrase can cause routing/navigation issues and serves no purpose in the app or for the Wazer.

If there is a significant change to traffic patterns or geometry (lane shifts), adjust the geometry, connections, and restrictions of the segments to match the current traffic pattern. You must be able to monitor the area, and readjust once the construction is complete, or when additional changes are made during construction.

Official sources of mapping information

Being in the Waze community of editors means sharing information you discover and learning from the discoveries of others! You can see some of the (old) official sources of mapping information (US only) provided in the forum or check out the (new) mapping resources wiki page (preferred).

Feel free to add new resources as you find them.