Changes

From Wazeopedia

Road types

367 bytes removed, 3 months ago
m
Emergency Vehicle and DOT Service Roads: typo
{{mbox
| type = critical| imageright = [[File:Alley.gif|100px|alt=alley]]| imagerightwidth=100px| textstyle = color: red; font-weight: bold; font-style: italic;| text = The contents {{As of this page were completely revamped starting 19 April 2014|2018|10|31|df=us}}, to incorporate an entirely the new set of guidelines road type {{Passageway}} is not suitable for map editing. All use in the US editors should familiarize themselves with the contents of this page. Please see [http://www.waze.com/forum/viewtopic.php?f=276&t=85397 At this topic] time, DO NOT use the {{Passageway}} road type in the USA without explicit champ approval for detailseach instance.
}}
{{UpdatedBanner
|majorDate = 1/14/15
|majorDesc = Clarify when to use PLR vs Private Road for apartment complexes, trailer parks, schools, universities, etc.
|majorForum = http://www.waze.com/forum/viewtopic.php?f=276&t=124820}}
'''Road types''' in the United States can be divided into three categories: public roads, other drivable roads, and non-drivable roads.
Public road types in Waze are determined by the FHWA functional classification of the road and, where applicable, by the highway system to which the road belongs.
{{LocalGuidance|link=Mapping resources/USA/States}}
<br/>
== {{@|Overview}} ==
 
=== {{@|A hybrid system}} ===
 
Road types in the United States are determined through a hybrid system of FHWA functional classification and U.S., state, and sometimes county highway systems. These systems work together to create a harmonious Waze map with excellent routing characteristics. Neither of these two facets of the road type system should be considered sufficient on its own, without the other. The road type guidance has been carefully crafted to join these two systems into one single contiguous Waze road type system.
 
==== {{@|Functional classification}} ====
 
Functional classifications (FC) are determined using a set of criteria selected by the [[wikipedia:Federal Highway Administration|Federal Highway Administration]] (FHWA). These criteria include not only the physical attributes of the road but also efficiency of travel, number of access points, speed limits, route spacing, actual usage, and continuity. This can lead to quite different classifications for roads that appear similar. For example, a six-lane divided road in an urbanized area may be a Collector (Primary Street); a two-lane road through the middle of a town may be a principal arterial (Major Highway).
 
Functional classification is a national standard, but functional classification maps are published by state departments of transportation. Links to functional classification maps for each state can be found on [[National resources/USA/Functional classification|the USA functional classification page]].
 
==== {{@|Highway systems}} ====
 
The '''[[wikipedia:Interstate Highway System|Interstate Highway System]]''' (formally, the Dwight D. Eisenhower National System of Interstate and Defense Highways) is a nationwide network of freeways designated by Congress and administered by the FHWA and [[wikipedia:American Association of State Highway and Transportation Officials|AASHTO]], a nationwide organization of state departments of transportation with governmental support. The system facilitates high-speed travel throughout the nation.
 
The [[wikipedia:United States Numbered Highways|United States Numbered Highways]], or '''U.S. Highways''', system is a nationwide integrated network of roads also designated by Congress and administered by the FHWA and AASHTO. While many of the routes in this system have been superseded by the Interstate Highway System, they remain important as direct links between regions not served by the new system, and as alternatives to Interstate travel in the case of heavy traffic or incident.
 
Each of the fifty states (along with the District of Columbia and some of the United States's overseas territories) has a numbered '''[[wikipedia:state highway|state highway]] system'''. These systems are designated and administered by their respective state legislatures and departments of transportation as statewide networks of important travel links between cities and communities of those states. The roads in these systems, while of lesser national importance, are nevertheless essential for travel within the state.
 
In addition to their state highway systems, some states designate [[wikipedia:County highway|county routes]] which are important for travel within a county. These routes serve important functions in a short-distance capacity.
=== {{@|Importance of road types}} ===
#* Since freeways are given the highest priority of all, having other high-type roads is necessary to provide viable alternatives to the routing server in case freeways are clogged with traffic.
# When viewing the map, more important roads should appear at the far zoom levels. Without proper types, the zoomed out display can be misleading.
 The {{Freeway}} and {{Ramp}} # Certain [[#Other drivable roads|other drivable road types each have their own special rules. The {{Major Highway}}, {{Minor Highway}}, and {{Primary Street}} types are designated using a set of minimum criteria, as explained ]] generate [[Routing penalties#HighwaysSegment properties|belowtransition penalties]]. Occasionally, if deemed necessary for proper routing, when a route leaves them onto a particular different road's type may be set higher than as prescribed in these rules. If a road has a '''higher''' type than set forth in these rules, there may #* This can be a reason useful for it. In rare cases, a particular road may require a '''lower''' type than as prescribed in these rules. Contact your regional coordinator before lowering the type of any road past the bounds of the rules. Special rules are used to determine the road types of areas like [[Creating and Editing a roundabout#Road typePrivate Installations|roundaboutsprivate installations]] but can also cause dramatic and [[At-grade connectors#How to label the connector type|at-grade connectors]]. Road types do not affect naming. See [[Road Naming (USA)]]unexpected routing results.
=== {{@|Before editing}} ===
* [[Creating and Editing a roundabout]]
* [[At-grade connectors]]
 
Road types do not affect naming. See [[Road names]].
== {{@|Public roads}} ==
Public roads are those who that can be driven by anyone. Naturally, they are by far the most important roads on the Waze map.
The {{Freeway}} and {{Ramp}} road types each have their own special rules. The {{Major Highway}}, {{Minor Highway}}, and {{Primary Street}} types are designated using a set of minimum criteria, as explained [[#Highways|below]].
{{mbox | type = warning | text = <div style="font-size:smaller">Public roads are designated by a series of '''minimum criteria'''.
If a road meets the criteria for multiple types, the highest of those types must be used, to satisfy every "at least" rule.</div>}}
=== {{@|A hybrid system}} ===
 
Public road types in the United States are determined through a hybrid system of FHWA functional classification and U.S., state, and sometimes county highway systems. These systems work together to create a harmonious Waze map with excellent routing characteristics. Neither of these two facets of the road type system should be considered sufficient on its own, without the other. The road type guidance has been carefully crafted to join these two systems into one single contiguous Waze road type system.
 
==== {{@|Functional classification}} ====
 
Functional classifications (FC) are determined using a set of criteria selected by the [[wikipedia:Federal Highway Administration|Federal Highway Administration]] (FHWA). These criteria include not only the physical attributes of the road but also efficiency of travel, number of access points, speed limits, route spacing, actual usage, and continuity. This can lead to quite different classifications for roads that appear similar. For example, a six-lane divided road in an urbanized area may be a Collector (Primary Street); a two-lane road through the middle of a town may be a principal arterial (Major Highway).
 
Functional classification is a national standard, but functional classification maps are published by state departments of transportation. Links to functional classification maps for each state can be found on [[National resources/Functional classification|the functional classification page]].
 
==== {{@|Highway systems}} ====
 
The '''[[wikipedia:Interstate Highway System|Interstate Highway System]]''' (formally, the Dwight D. Eisenhower National System of Interstate and Defense Highways) is a nationwide network of freeways designated by Congress and administered by the FHWA and [[wikipedia:American Association of State Highway and Transportation Officials|AASHTO]], a nationwide organization of state departments of transportation with governmental support. The system facilitates high-speed travel throughout the nation.
 
The [[wikipedia:United States Numbered Highways|United States Numbered Highways]], or '''U.S. Highways''', system is a nationwide integrated network of roads also designated by Congress and administered by the FHWA and AASHTO. While many of the routes in this system have been superseded by the Interstate Highway System, they remain important as direct links between regions not served by the new system, and as alternatives to Interstate travel in the case of heavy traffic or incident.
 
Each of the fifty states (along with the District of Columbia and some of the United States's overseas territories) has a numbered '''[[wikipedia:state highway|state highway]] system'''. These systems are designated and administered by their respective state legislatures and departments of transportation as statewide networks of important travel links between cities and communities of those states. The roads in these systems, while of lesser national importance, are nevertheless essential for travel within the state.
 
In addition to their state highway systems, some states designate [[wikipedia:County highway|county routes]] which are important for travel within a county. These routes serve important functions in a short-distance capacity.
=== {{@|Highways}} ===
*various County (or Parish) Highway systems, in some states
Waze's definition of "highways" includes all theseInterstate, US and state highways, but it also includes all other roads that are classified as arterial roads under the FHWA functional classification lists maintained by state governments, even though they may not necessarily a be part of any numbered highway system. In other words Functional classification of roads is determined more by how the roads are used than by how they are constructed, think of and the dictionary definition criteria are slightly different between urban and rural areas. Because of "this, some urban roads may be classified as arterials and have highway" ("a main roadtypes in Waze, espeven though they appear very similar to other non-highway roads. one connecting major towns or cities") rather than In using functional classification and numbered highway systems, the decision on which roads should be classified as highways rests ultimately with the legal definition of governments that build and maintain the termroads.
Waze distinguishes three classes of highway: {{Freeway}}, {{Major Highway}}, and {{Minor Highway}}.
*Signed, numbered '''county routes''' (and, in Louisiana, parish routes) paved with a hard surface.
*Business (BUS) and Loop state highways, and Spur state highways which are not used as connectors, paved with a hard surface.
*{{Anchor|Frontage road|Frontage roads|Frontage Road|Frontage Roads}}'''[[wikipedia:Frontage road|Frontage road]]s''' which serve as the means of access between freeways/expressways and surface streets, if not otherwise classified.
**Some functional classification maps are not produced in high enough detail to determine the class of frontage roads. On maps that are produced in high detail, frontage roads are almost universally classified as Major Collectors or higher.
Unpaved roads – including gravel, macadam, and dirt roads – are considered on a regional basis. Check your [[Mapping resources/USA|state page]] or contact your regional coordinator.
Note: Some states or counties may designate county routes differently than others. Check your state's page for possible exceptions to this rule.
====Street {{Street|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}} {{Anchor|street|St|st}} {{@||Street}} ====
[[Image:RoadPicN4.jpg|right|400px200px]]
Any road for public travel which does not meet the criteria for any other type shall be classified as a {{Street}}. Shown as "local roads" in some functional classification maps; not shown at all in others.
{{clear}}
 
===={{@|Passageway}}====
{{Anchor|Narrow Street}}[[File:Alley.gif|right|200px|alt=alley]]{{As of |2018|10|31|df=us}}, the new road type {{Passageway}} should not be used in the USA. This road type is designed for other parts of the world, where some public roads accomodate only vehicles narrower than cars. At this time, DO NOT use the {{Passageway}} road type in the USA without explicit champ approval for each instance.
==== {{@|Service Road}} ====
| text = The Service Road type is no longer available. '''Use other road types for service roads.'''
}}
:For guidance on mapping service roads AKA frontage roads, see the [[House_Numbers_on_Service_Roads|service road page]] and the [[#Frontage roads|section above]].{{clear}}
=== {{Anchor|FC cross reference}} {{@|Quick reference chart}} ===
|}
</div>
 
===Exceptions===
 
If a road has a higher or lower type than what's specified in these rules, there may be a reason for it. Special rules are used to determine the road types of [[Creating and Editing a roundabout#Road type|roundabouts]] and [[At-grade connectors#How to label the connector type|at-grade connectors]].
 
==== Routing road type ====
Apart from changing the nominal road type, level {{rank|routing}} editors can also change the [[Creating and editing road segments#Special properties|routing road type]] (also known as routing preference) to one type higher or lower, which only affects [[Routing server#Changes in routes due to different route lengths|long-distance aspects]] of road type behavior while maintaining the same appearance, [[How Waze determines turn / keep / exit maneuvers#Best Continuation|best continuation]] and [[Detour Prevention Mechanisms|detour prevention behavior]] of the nominal road type. These exceptions to the rules should be reviewed with local leadership before implementation.
 
====Continuity====
[[File:35-71.png|thumb|300x300px|SR-435 has the Minor Arterial functional class , so it would normally have the Minor Highway road type in Waze. Since it is signed as the way from one Freeway (US-35) to another (I-71), its routing road type has been promoted to Major Highway, enabling the routing server to use it on routes from WV to IL. It's nominal road type remains Minor Highway to preserve appearance and detour prevention.]]
[[File:M55-66.png|thumb|300x300px|These Michigan State Trunkline Highways have the Minor Arterial functional class, so they would normally have the Minor Highway road type. However, even without signage indicating their longer-distance use, they have been upgraded to Major Highway in order to be used in routes between southwestern Michigan and the Upper Peninsula.]]
One common reason for a road to be set to a higher type is for the purpose of maintaining '''continuity''' between two roads with higher types. Promotion for continuity is usually indicated by signage: A certain less important road is signed as the way to get between two different more important roads.
 
For example, a freeway exit from I-70 is signed as "Exit 142: US-40 / Gratiot", indicating that this is the intended way to get to US-40, with Principal Arterial functional class. Between the ramps and US-40 is CR-30 with Local functional class. The rules on this page would normally dictate that this road be set to Primary Street, but in long-distance routing it may be removed from consideration, or '''[[Routing server#Pruning|pruned]]'''. This can be prevented either by assigning the Major Highway type outright or by assigning the Minor Highway type with a +1 routing road type, which would cause it to be treated like a Major Highway for long-distance routing. Use of routing road type is preferable to avoid unintended side effects on the behavior and display of the road.
 
Certain situations may require continuity upgrades even without signage to support them. Examples include but are not limited to:
* Sparsely populated areas connected by long roads with lower functional class
* Places where highway designations end abruptly, such as jurisdictional boundaries
* Alternate routes used as detours for main highways subject to frequent or long-term closures
* Urban or suburban areas in the midst of redevelopment, where functional class may be out of date
* Connecting roads that may be too short to be noticed during state functional class assignment
 
When promoting for continuity, the effective road type of the connecting road should match the ''lower'' of the two roads that it connects, similar to type selection for at-grade connectors, up to Major Highway. Since Major Highway is never pruned, there is no need to promote something to Freeway with routing road type for continuity reasons alone, and the nominal Freeway road type should only be used for controlled-access highways that meet the criteria [[#Freeway|above]].
 
Continuity upgrades prevent Waze from pruning out valid routes, and in extreme cases they can mean the difference between getting a good route and getting no route at all.
=== Unpaved checkbox [[File:Checkbox.png|50px]]===
 
The [[FIle:Unpaved attribute.png|90px]] checkbox is an attribute that can be applied to any road type. It indicates that a road is not paved with asphalt or concrete. The unpaved attribute affects routing over drivable road types; it does not really affect non-drivable road types, since the client does not use them for routing. Based on user preference, destination, and other settings options, the Waze client may avoid routing them over otherwise drivable segments when the 'unpaved' attribute is checked.
[[File:RoadPicN6.jpg|right|300px|RoadPicN6.jpg]]
==== When to select the Unpaved attribute ====
 
'''Any drivable road which is not paved with asphalt or concrete''' should have the Unpaved attribute box checked.
 
<sub>Check your [[Mapping resources|state's page]] for details on whether there are additional guidelines for roads that are in '''''uncommonly poor condition by local standards''''' or contact your [[Regional Coordinator]] for further guidance.</sub>
 
==== User setting options for the Unpaved attribute ====
This attribute has the unique property in that Waze users may select when not to be routed over unpaved road segments. Users may choose:
* 'Dirt roads - Don't allow' - Avoids through-routing on all unpaved roads
* 'Dirt roads - Avoid long ones' - Avoids through-routing on long unpaved roads
* 'Dirt roads - Allow' - Allows through-routing that could include unpaved road(s) (i.e. ignores whether roads have the unpaved attribute checked)
:''The Client still refers to these settings as "Dirt Roads", but it will be updated soon to read "Unpaved Roads". Rest assured they apply to this [[FIle:Unpaved attribute.png|90px]] attribute, and not to the {{Off-road}} type.
== {{@|Other drivable roads}} ==
=== Off-road / Not maintained Road {{Off-road|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}} {{anchor|Dirt|Dirt Road|Dirt road|Dirt road / 4X4 trail|4X4 Trail|4X4 trail|4x4 Trail|4x4 trail|dirt road}} {{@||Off-road / Not maintained road}} ===
 
{{mbox
| type = critical
| textstyle = font-style: italic;
| text = Use extreme caution when mapping '''through roads''' with this type! In an emergency, such as wildfire or flooding, Waze responders may mark primary through roads in an area as closed on behalf of public safety. However, if off-road segments appear to provide alternate through routes, and responders miss closing them, Waze may offer those segments instead '''regardless of penalty'''. Waze may also route using off-road segments if they appear to bypass private or fee-collection gates.
{{As of|2018|10}} '''do not map through roads using this type''' unless you make certain that the roads (1) are passable, if only barely, by ordinary passenger vehicles or (2) would not be routed as alternate routes in emergencies or into restricted areas.
}}
 
[[File:Off_Road_Not_Maintained.jpg|right|300px|Off_Road_Not_Maintained.jpg]]
=== Dirt Road / 4X4 Trail The {{Dirt Road / 4X4 Trail|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Off-road}} {{anchor|Dirt|(formerly Dirt Road|Dirt road|Dirt road / 4X4 trail|4X4 Trail|4X4 trail|4x4 Trail|4x4 trail|dirt road}} {{@||Dirt Road / 4X4 Trail}} ===and Unpaved) segment type had the unique property that Waze users could ask not to be routed over it. That function has now shifted to the Unpaved attribute check box (see above).
[[File:RoadPicN6{{Off-road}} roads are typically deeply rutted with thick mud, irregularly shaped rocks, fallen trees, branches, and deep streams, creeks, or river crossings.jpg|right|300px|RoadPicN6 A typical car would bottom out, get stuck, or even break an axle trying to traverse these types of road segments. The vast majority of vehicles would not be traveling down these roads. This segment type should strictly be used by a type of hard terrain/special vehicle.jpg]]
The Any road for which high-clearance vehicles are recommended or required should be assigned the {{Dirt Road / 4X4 TrailOff-road}} type has the unique property that Waze users may ask not to be routed over it. Users may ask to avoid , if it for is mapped at all through routing with the settings option "Dirt roads - Don't allow", or to avoid it for through routing longer than 300 m (984 ft) with the option "Dirt roads - Avoid long ones"regardless of its maintenance status.
Because of this propertyCurrently, this Waze does not plan to support a 4X4 vehicle type typically represents public side roads that some fraction of local drivers habitually avoid due to surface quality. In metropolitan or other urbanized regionsin the client app, but the developers have left this generally means unpaved (dirtoption for editors to map these paths, gravel, crushed rock) roads, or roads in uncommonly poor condition by local standardsso they can be displayed on the map. In other areas, roads They have an extremely high penalty associated with unpaved surfaces may them and will not be essential suggested for any through routes and thus necessarily set to other types such as Street, Primary Street, or even higher, as if they were pavedin most ordinary circumstances.
Check your [[Mapping resources/USA|state page]] for details on whether your state follows unique guidelines for dirt hard terrain/special vehicle roads, or contact your regional coordinator [[Regional Coordinator]] for further guidance. {{clear}}
=== Parking Lot Road {{PLR|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}} {{anchor|Parking lot road|PLR|plr|Plr}} {{@||Parking Lot Road}} ===
[[File:RoadPicN7.jpg|right|300px|RoadPicN7.jpg]] Parking lots, along with other publicly accessible roads such as '''alleys''' that should not be used for traffic routing unless directly at the start or end point of a route.
*Do not map the rows within parking lots because it clutters the map. See this additional page for [[Best map editing practice#Parking Lots|more details on how to map parking lots]].
{{mbox|type=caution|text=This section was updated {{As of |2015|01|14|df=us|lc=yes}} to clarify when to use {{PLR|PLR}} vs {{Private Road|Private Roads}}.}}
*Use {{Parking Lot Road}} type for all [[Best map editing practice#Parking Lots|necessary segments]] in the Parking Lot.
*{{Parking Lot Road}} type should be used inside Apartment Complexes, Trailer Parks, Schools, and Universities unless it meets the criteria for Private Road found in the next section below.
*{{Parking Lot Road|Parking Lot Roads}} have a [[Routing penalties|transition penalty]] when exiting the Parking Lot road segment. This should prevent Waze from routing you through a Parking Lot or an alley as a shortcut.
* {{Parking Lot Road|Parking Lot Roads}} can be used to avoid "missing road" automated Map Problem reports.
*Schools and Universities (gates / guard)
*Businesses with controlled access (gates / guard)
*Campgrounds or trailer parks (designed for short term guests)
However, using private roads in some of these situations may require more complex mapping as covered in the article [[Private Installations]]. Be sure to read through that article before setting a whole neighborhood to all private roads.
{{clear}}
==== {{@|Non-drivable roadsEmergency Vehicle and DOT Service Roads}} == '''Your car should not be here!''' *{{As of|2015|4}} the Waze app is intended only for drivers of motor vehicles, and Waze has no plans ever to support any other application. In fact, cyclists and pedestrians who use Waze near drivable roads can damage Waze's speed and traffic database! '''Editors should not map <u>any</u> road type for the sole purpose of encouraging non-driving Wazers.'''*It may be useful to map certain non-drivable roads as navigational references if they are '''visually obvious to drivers''', for example by showing where a turn lies in relation to a railroad crossing (use the Railroad type) or a major Rails-to-Trails right-of-way (use the Pedestrian Boardwalk type).*If the GPS Points layer clearly shows frequent improper Wazing on a non-vehicle route near drivable roads, marking this route with a non-drivable road type can prevent damage to Waze's speed and traffic database. Do not, however, use the Walking Trail type for this purpose.*The Walking Trail road type, although listed as non-drivable, is fully routable and should only be used by experts in very limited cases.*{{As of|2015|6}}, the non-drivable road types of Pedestrian Boardwalk, Stairway and Runway/Taxiway should '''not have any type of junction with a drivable road'''. When crossing drivable roads, these non-drivable road types should be bridged across without a junction and set at a different elevation. ''Note: this guidance is subject to change.''* ''It is OK to junction drivable roads with the Railroad type.'' See specific details in the Railroad section later on this page.*{{Red|Walking Trails, and other non-drivable road type which are visible in the app, can cause significant routing issues.}} If a walking trail (even when not connected to any other drivable segment) is closest to the latitude and longitude of the search result, the routing server will route you to the spot on the segment closest to that walking trail.<br/><br/>In the sketch below, if you assume the Place target is a latitude and longitude returned by a Google search result, you would think that the actual destination would be the parking lot segment because it is the closest reachable/connected segment to the target. But it won't be. The actual destination will be where the green spot is, because the closest segment to the latitude and longitude is the walking trail, and the closest Waze can route to the walking trail is to where the green spot is. [[File:Walking trail dest.png|center|Walking trail dest.png]]==
[[File:Emergency.jpg|right|300px|Emergency.jpg]] Limited-access service roads, such as those marked for "emergency and authorized vehicles only" should not generally be mapped, and if there is a need to map them, they should not support routing nor appear like other roads. The clearest way to do this is to map them using the {{Private Road}} type, add [[partial restrictions]] on them to prohibit routing for all times and vehicle types and include a description within the restriction to explain the reason for mapping. Another, older method also involves using the {{Private Road}} type, disconnecting the limited-access road and locking as high as possible. This is also valid. Examples of such roads include fire roads prohibited to all non-service motor vehicles, patrol roads for park service vehicles, and service cutoffs across the medians of divided highways.
{{clear}}
=== {{@|Ferry}} ===
{{Ferry|&nbsp;}}
{{mbox
| type = important
| text = {{As of|2016|alt= Prior to 2016}} the Ferry Road type was not to be used. Since that time, there have been changes to the [[Routing server]] that allow the use of the Ferry Road type.
}}
The ferry road type should only be used where a road crosses a body of water through the use of an automotive ferry. For more on how to map ferries see [[Ferries]]. The ferry road type is useful because it causes the Waze client to display a "ferry" symbol for routes that include a ferry segment.
The ferry road type is treated by the [[routing server]] as a minor highway. The speed for the ferry road type is fixed at a very slow speed typical of watercraft, and not estimated from user speeds.
{{mbox|type=important|text== {{@If the ferry you are working on crosses an area well covered with GPS traces, OR [[Wikipedia:List_of_HSC_ferry_routes|Emergency Vehicle and DOT Service Roadstravels at higher than normal speeds]], please notify your [[Regional Coordinator]]. '''Additionally, if you have issues with routes passing thru a ferry segment, please contact your [[Regional Coordinator]].'''}} ===
[[File:Emergency.jpg|right|300px|Emergency.jpg]] "Emergency and Authorized Vehicles Only" and DOT Service Roads are to be treated as Non-drivable roads. These are found primarily through the median of divided highways to connect opposite direction lanes. If mapped, they should not be connected to any drivable road, with properties set to road type Private Road, and lock the segment at as high a rank as possible, up to rank 5. {{clear}} === {{@|Walking Trails}} === <!Non-- [[File:RoadPicN9.jpg|right|300px|RoadPicN9.jpg]] THIS FIGURE OF A PLEASANT LEAFY WALKING TRACK COMMENTED OUT UNTIL A MORE APPROPRIATE IMAGE CAN BE FOUND. --DwarfLord, June 6 2015 --> {{mbox|type=caution|text=This section is new {{As of |2015|05|24|df=us|lc=yesdrivable roads}}. For details, pleasesee the [http://www.waze.com/forum/viewtopic.php?f=276&t=98949 forum discussion].}} Use Walking Trails only with assistance from an expert in Walking Trails. They should only be used in rare cases. Walking Trails may have strange side effects on nearby routing. Never use the Walking Trail road type for ordinary hiking paths or bike paths. Most hiking and bicycling paths should not be on the map at all. The WME lists the Walking Trail road type as non-drivable. However, {{as of|2015|5|lc=yes}}, Walking Trails are fully routable and even support Waze House Numbers. Waze treats them in some ways like "Dirt road / 4X4 Trail" but displays them differently. Historically, editors have disconnected Walking Trails to make sure Waze doesn't route drivers over them. This doesn't always work as desired. If a disconnected Walking Trail comes closer to a destination than any other road, Waze may route drivers to a location nearer to the Walking Trail than to the destination. This problem can be severe for Walking Trails passing close to many destinations in a dense neighborhood. '''Connected or not, the Walking Trail type should never be used where effects on local routing are not desired.'''
The name "Walking Trail" suggests that Waze wants to support pedestrians and cyclists. === However, {{as ofAnchor|2015Pedestrian Boardwalks|4Stairways}}{{@|lc=yesWalking Trails}}, Waze focuses on drivers of motor vehicles and has no plans to encourage or support any other application. In fact, pedestrians and cyclists using the Waze app may damage Waze. By Wazing at speeds different from nearby traffic, they can create false traffic indications and even influence Waze's records of average road and turn speeds.===
Because For further information on the mapping of this effect, {{Walking Trail}} (known as '''editors should not map Walking Trails, or any other road type, for the sole purpose of encouraging non-driving Wazers.routable pedestrian path''' See the descriptions of other non-drivable road types for recommended applications of those types. If the GPS Points layer shows clearly that pedestrians and cyclists already use Waze on a path or trail that lies parallel to a drivable road, thenin US English), {{as of|2015|5|lc=yes}}, the path may be mapped with a Pedestrian Boardwalk. Doing so will limit the damage these Wazers would otherwise cause to the road's speed data. Such paths should only be mapped once it is clear Wazers regularly use them. ==== {{@|Applications}} ==== In rare cases, connected Walking Trails can bring drivers to destinations where otherwise Waze might fail to offer the best route. For example: *A concert pavilion in an urban park accessed by a pedestrian path from a distant parking lot. *A train station reachable from either side of the tracks but with no drivable road across them. *A destination addressed on a (known as '''non-drivable footpath. A connected Walking Trail may be used to route drivers to such destinations. If the Walking Trail goes through from one drivable road to another, ensure that outgoing turn restrictions are red to disallow through routing via the Walking Trail. Lock the Walking Trail as this is uncommon usage that may puzzle other editors. Orientation or destination applications involving foot or bicycle paths that do not require routing, such as marking where an obvious bicycle routable pedestrian path crosses a road ''' in US English or where a trailhead is located, should not use the Walking Trail type. Use Pedestrian Boardwalks, Stairways, or Point Places as appropriate. ==== {{@|NamingStairway}} ==== If destinations are addressed using House Numbers on a Walking Trail, it is essential that the Walking Trail's name and city fields be set accordingly so that routing to the addresses will work. For other routing situationsroad types, Walking Trails should be named to alert drivers that they must leave their car. For example, a Walking Trail connecting the two sides of a train station may be named "Station Access Footpath".{{clear}} === {{@|Pedestrian Boardwalks}} ==={{Pedestrian Boardwalk|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}}see [[File:RoadPicN10.jpg|right|300px|RoadPicN10.jpgpedestrian path]] {{clear}} === {{@|Stairway}} ==={{Stairway|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}}[[File:RoadPicN11.jpg|right|300px|RoadPicN11.jpg]] {{clear}}
=== {{@|Railroad}} ===
 [[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]The {{Railroad|&nbsp;}} road {{mbox| type serves three purposes in Waze. First, it provides drivers with visual orientation relative to railroad and light-rail tracks. More importantly, in the common case where passenger-carrying tracks lie parallel with roads, mapping the tracks allows Waze = important| text = The guidelines below have been updated to recognize spurious speed data from people Wazing reflect new standards on the train and prevent it from corrupting speed data for the adjacent road. Finallynaming of railroads as of June 28th, when a railroad crosses a drivable road segment at grade (same elevation) the routing server can better determine delays at that crossing2016.{{clear}} 
{{mbox
| type = important
| text = The guidelines below which allow have been updated to reflect new standards on junctioning of railroads to drivable segments is new railroad grade crossings as of October 24September 19, 2014.#There is no need to make mass railroad changes immediately.#Railroad junctions are expected to be made gradually over time. #There is to be no massive railroad updating project2018.
}}
{{As of[[File:RailroadTracksVanishingPoint.jpg|2015right|7}} the automated [[Map Problems in Waze Map Editor300px|Map ProblemRoadPicN11.jpg]] search algorithm will identify suspected errors at The railroad crossingsroad type serves two purposes in Waze. It is common First, it provides drivers with visual orientation relative to see railroad and light-rail tracks. More importantly, in the “restricted turn might be allowed” error common case where a railroad crosses a drivable segment nearby passenger-carrying tracks lie parallel with roads, mapping the tracks allows Waze to where another drivable segment also crossesrecognize and discard spurious speed data from people Wazing on the train. These kinds This prevents corruption of map error should be marked as “Not Identified” so that they are not shown again at that location. Do not enable turns at railroad crossingsspeed data for the adjacent road.{{clear}}
Use the following guidelines when '''mapping''' railroad segments:
* By default, '''Do NOT''' enter "Railroad" a name for the street name of every railroad segmentunless the tracks are historical in nature, a major landmark, or a routine destination for Wazers and your local state/regional wiki guidelines allow for such naming. The Waze app now renders railroad tracks as such so naming serves little purpose any longer. (See more below on Naming railroad segments.)
* Always select "None" for the city name. This avoids [[City smudge|city smudging]].
* Lock the segment at L2.
* Do not map railroads below ground, as they do not serve any either of the three two purposes outlined above. This is especially true in urban areas where underground rail lines are common, and their appearance on the map would be confusing to drivers.
* Set the elevation just as you would a drivable segment. When tracks junction a road on the ground, the Elevation should be set to Ground.
* Create In specific circumstances, create junctions between drivable roads and railroadsat grade crossings.{{ref label|rr|rr}}Otherwise, do not junction grade crossings. The resulting elevation conflicts are acceptable.
* Set railroad to 2-way directionality
* Restrict turns ''to and from'' the railroad segments.
* When mapping railroad tracks, focus on those near drivable roads.
* Map rail yards simply, with one railroad segment along either edge of the yard's tracks.
* Map industrial spurs only if they cross drivable roads.
* Do not map '''every''' piece of parallel track, such as in sidings or yards, or industrial spurs that don't do not cross any roads. Your work may otherwise be seen as clutter, much like mapping every parking lot row.
* Multiple parallel lines at crossings:
** At most crossings, there should be only one railroad segment mapped and no more than two parallel railroads mapped at any crossing.
* {{Red|Do not map railroads using a drivable road type}} (streets, primary streets, etc.); it could be a hazard to human life if drivers were routed to them.
<small>{{note|rr|rr}} ''Note: The routing server will properly account Adding a junction node for delays at railroad crossings through a segment without a grade crossing only benefits routing if both (1) between the existing junctionnodes on the drivable road on either side of the grade crossing, there is at least one destination on one side of the crossing '''and''' room for cars to back up waiting on the other; '''and''' (2) the tracks support regular, scheduled train traffic. HoweverIf either of these elements is missing, with adding a junction, the historical data node for the rail grade crossing will be more accuratenot benefit routing and may in some cases degrade routing. If it is difficult to determine whether regular, scheduled trains use the tracks, you may assume they do if the tracks appear active and well maintained.''</small> 
Use the following guidelines when '''naming''' railroad segments:* For commercially-controlled right-of-ways, rather than apply the default "Railroad" name, you may optionally use the owner's full legal name spelled out without acronyms or abbreviations (e.g. "New Orleans Public Belt Railroad"). Some owners' names incorporate what appear to be or once were acronyms but are actually part of the legal name (e.g., "BNSF Railway", "CSX Railroad").** In case of uncertain ownership, do not guess. Use the default "Railroad" name.** Do not name a railroad segment for a passenger operator that uses it, regardless of how many passengers or how little freight it may carry, unless you are absolutely certain that the passenger operator owns the track. For example, do not name a segment "Amtrak" unless Amtrak actually owns the track ([http://en.wikipedia.org/only if allowed by your local wiki/Amtrak#Trains_and_tracks it usually does not], except in the [httpguidelines://en.wikipedia.org/wiki/Northeast_Corridor|Northeast Corridor] and in a few other areas).** Do not apply "fallen flags" (former owners that no longer exist due to bankruptcy or merger) in the alternate field.** Keep in mind that should the name of the owner change, due to bankruptcy, merger, or other business decision, you or another editor will need to come back and fix all now-incorrect segments. Railroads can change names often; for example, BNSF Railway has been known by that name only since 2005, and its previous name was in use for only eight years. * For urban rapid transit and light rail systems, rather than apply the default "Railroad" name, you may optionally use the name of the transit authority and the name of the line, separated by a hyphen (e.g., "MBTA - Green Line", "RTA - Riverfront Streetcar").
** If a system has only one line, of course, use its name alone (e.g., "Detroit People Mover").
** If multiple lines share the same track or run on parallel tracks, include all lines (e.g., "Metro Rail - Red/Purple Lines").
** However, if a rapid transit system is so complex that including all line names would lead to an absurd result on some railroad segments, use the name of the system alone (e.g., "BART", "MTA") throughout the system.
* Federal DOT Railroad GIS: http://fragis.fra.dot.gov/Apps/GISFRASafety/
   '''Waze - Support''' '''Railroads should be labeled as such in the editor. For the time being they won't make it to the client indeed, but in the future we might want to use them for display purposes.''' '''The "railroad" road type in the editor is under "non drivable" so it should not cause any issue to the routing.'''<br>
For specific recommendations in other countries outside the United States, please see the [[Road types and names|entry for the country in question here]]. {{clear}}
=== {{@|Runway/Taxiway}} ===[[File:Service roadRunways.png|200pxright|Service road.png300px]] {{Anchor|Runway|/Taxiway}} {{@||Runway/Taxiway&nbsp;}}=== 
Airport runways and private airstrips may be mapped using the Runway/Taxiway road type. The Runway/Taxiway type is for display only and must never connect to drivable road segments. If a drivable road and a runway cross, set the [[elevation]] of the road below that of the runway and ensure there is no connection. Draw each runway as a single segment and lock it to prevent lower-ranking editors from attaching a road. Do not form junctions where runways cross each other.
Name each runway using the word ''Runway'' and the runway designations with the lower number first and a hyphen between runway numbers (e.g., "Runway 16R-34L".) <!-- The preferred airport identifier is the [http://en.wikipedia.org/wiki/International_Air_Transport_Association_airport_code IATA] [http://en.wikipedia.org/wiki/List_of_airports 3-letter code], for example "SFO", "LAX", "JFK", etc. If the airport in question is not included in that list, use the [http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO] [http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code#Prefixes 4-letter code] instead. If the airport is not included in that list use the [http://www.faa.gov/air_traffic/publications/atpubs/lid/lidhme.htm FAA identifier]. --> For the "City" field of runway segments, check "None" to avoid any chance of [[City smudge|city smudging]]. {{clear}}
[[File:Fly-inCommunity.png|right|250px]]
Despite its title, the Runway/Taxiway road type should never be used for an aircraft taxiway because it would render the same as a runway and confuse the display. Taxiways not intended for frequent access by street vehicles should not be mapped at all with any road type. Taxiways that do commonly serve street vehicles as well as aircraft, for example at [http://www.waze.com/editor/?zoom=5&lat=38.68054&lon=-120.98836&env=usa&layers=389 fly-in communities], may be mapped as Streets provided they remain disconnected from any runway.
{{clear}}
 
=== {{@||Ferry}} ===
{{mbox
| type = important
| text = {{As of|2016|alt= Prior to 2016}} the Ferry Road type was not to be used. Since that time, there have been changes to the [[Routing server]] that allow the use of the Ferry Road type.
}}
{{clear}}
 
The Ferry road type should only be used where a road crosses a body of water through the use of an automotive ferry. For more on how to map ferries see [[Ferries/USA]]. The Ferry Road type is useful because it causes the Waze App to display a "ferry" symbol for routes that include a {{Ferry}} segment.
 
The Ferry road type is treated by the [[Routing server]] as a minor highway.The speed for the ferry road type is fixed at a very slow speed typical of watercraft, and not estimated from user speeds.
 
{{mbox|type=important|text=If the ferry you are working on crosses an area well covered with GPS traces, OR [[Wikipedia:List_of_HSC_ferry_route| travels at higher than normal speeds]], please notify your [[Regional Coordinator]]. '''Additionally, if you have issues with routes passing thru a ferry segment, please contact your [[Regional Coordinator]].'''}}
 
== Roundabouts [[Image:Round.png |50px]] ==
{{clear}}
[[Image:RoadPicN8.jpg |right|300px]]
 
Roundabouts have few principles:
 
The first one, each node on the roundabout can only be connected to no more than one segment.
 
Each connection has a spectrum that exists in order to notify the Client on how to define the message (Go straight, exit through the 2nd / 3rd / 4th exit).
{{clear}}
 
[[Image:Round2.png |right|200px]]
 
The system will include the radius border from the center and notify the user accordingly.
 
For more information on when to create a Roundabout or a loop instead, please review the [[Junction Style Guide]].<br/>
For information on what type of road to set a Roundabout to, please review [[Creating_and_Editing_a_roundabout#Road_Type|Creating and Editing a Roundabout]]
{{clear}}
=== {{@|Bus or cab taxi only lanes}} ===When a road or lane is designated for bus or cab taxi use only, mark that road segment(s) with an allowed time based segment restriction for bus and/or taxi. The entire segment, right lane, center lane, or middle lane can be selected as a '''Private Road''' to appropriate on the second pop up window of the time based segment restriction. This will prevent the Waze router from using that segment(s) for general traffic, since the majority of the users will not be able to use that lane. It will only route if the taxi or bus type of vehicle is also advisable to set in the user's settings. (Taxi is currently available but bus is a potential future selection). Set the turn restrictions to prevent turns into that segment(s), but permit turns exiting as appropriate for the segmentlegal usage by taxi and/or bus vehicles.
If a Change the road is one-way, but allows bus or cab traffic segment(s) to flow the other direction, leave proper road type based on the road as one-way with functional classification and the normal flow of trafficWaze correlation table. There A {{Private Road|Private Road}} segment is '''no need to create a second road traveling the opposite direction for the bus and cab-only trafficlonger required'''.
If a road is one-way, but allows bus or taxi traffic to flow the other direction, leave the road as one-way with the normal flow of traffic, add the time based segment restriction for the Bus and/or Taxi in the appropriate direction. There is no need to create a second road traveling the opposite direction for the bus and taxi-only traffic.
=== {{@|Driveways}} ===
Most Many residents of urban communities have very short driveways between the named road that they live on and the garage or carport on their property. In general these very short segments should not be mapped , because they have no name, would clutter the map in the client app, take a lot of time to draw, and would greatly increase the overall size of the Waze mapping database with very little return.
In the case of very long driveways, it may be helpful to a driver to see the driveway mapped on the client app or even necessary for Waze to determine how to reach the destination. In those cases it may be prudent to add a road. See the article on [[Driveways]] for more information.
== {{@|See Also}} ==
* [[Road names/USA]]<br>* [[Junction Style Guide]]<br>[[United Kingdom/Roads]]<br>
[[Category:USA]][[Category:Review redirects]][[Category:Style Guidesguide]]
1,270
edits