https://www.waze.com/wiki/USA/api.php?action=feedcontributions&user=Qwaletee&feedformat=atomWazeopedia - User contributions [en]2024-03-28T11:44:38ZUser contributionsMediaWiki 1.40.2https://www.waze.com/wiki/USA/index.php?title=Places/Parking_lot&diff=164054Places/Parking lot2018-04-17T15:15:00Z<p>Qwaletee: Typo corrected Nassua -> Nassau</p>
<hr />
<div>{{mbox|text=New Parking features are being rolled out to display Parking Lot Areas in the client app. It is now encouraged to convert point places to area places. New parking lot point places can no longer be created.<br />
<br />
Waze is also importing Parking Lot Areas. Do not delete them unless instructed to do so. Use the guidance here to improve their name, data, shape, and placement. '''Current guidance is to add PLAs to the map, as the client is being updated.''' Initially we should focus on adding large and/or popular lots, but ''all'' lots should eventually be added.}}<br />
[[File:Parking_sign.png|300px|thumb|right]]<br />
<br />
The&nbsp;'''Parking Lot Area (PLA)'''&nbsp;Place marks a well-defined area constructed for off-street public or private parking, including parking structures and garages as well as at-grade lots. The parking lot feature in the app will recommend parking lots to Wazers navigating to a nearby destination. Waze will recommend lots within ⅔ mile of a Wazer's destination. As the feature matures, Waze will recommend the 'most popular' lots that other Wazers have chosen when navigating to the same destination.<br />
<br />
== {{@|Area or point}} ==<br />
{{Anchor|Area or Point}}Parking lots can ONLY be added as an area as of August 1st, 2016. They are a special place category; you cannot add other categories to a parking lot place, or convert/add a parking lot category to another kind of place.<br />
<br />
=== {{@|Parking lot point places}} ===<br />
{{Anchor|The Parking-Lot Point Place}}As of this writing, you can no longer add Parking Lots as a point place.<br />
<br />
Existing point places should be evaluated for inclusion and either converted to an area if applicable or deleted to solve the [[Map Problems in Waze Map Editor#Parking lot input as point|Map Problem]] (MP) report.<br />
<br />
== {{@|Scope}} ==<br />
{{Anchor|Principles|General Public Use|General Purpose Use|Distinctive and Significant|Interpreting_.27distinctive_and_significant.27}}At this time, parking lot areas (PLA) should be added to '''all lots''' including businesses with small parking lots (less than 10 spaces). Start by adding parking lots to event venues, shopping centers, airports, public use lots, garages, multi-use parking lots, popular lots with heavy usage or [[Glossary#UR|UR]]s, etc.<br />
[[File:Waze_PLA_Mall_Example.jpg|400px|thumb|right|Shopping Center PLA Example]]<br />
<u>For a mall or large shopping center</u>, break the parking lot up into multiple lots, as shown in the image to the right (use your discretion or discuss with your State Manager(s) or RC for official guidance if necessary.)<br />
<br />
<u>If a lot is stacked</u> (underground + surface), map it as one place covering the footprint of the parking lot / garage. Future UI enhancements may allow for better modeling of these lots.<br />
<br />
<u>If a lot has different entrances</u> serving different levels of a multi-level garage and you cannot drive from one level to another to park, but rather the levels are served independently by different entrances, then they should be mapped as multiple places. <br />
<br />
Care must be taken that stacked areas like this do not obscure each other. You do not want two areas with identical boundaries stacked on top of each other as it will be hard to notice or select the right one for editing in WME.<br />
<br />
As with all Area Places, a Parking Lot Area Place's geometry nodes should not be allowed to "snap" to adjacent road segments or junctions while being adjusted. Doing so can make the Area Place, as well as the adjacent segments or junctions, more difficult to modify.<br />
<br />
=== {{@|On-premises parking}} ===<br />
* It is important to create 2 separate places - one for the complex / place, and one for its designated parking lot.<br />
* Multiple parking lots for one premise: Create separate parking lots so the best parking lot can be recommended.<br />
* Valet parking - Valet is a service attribute of a place but is also an attribute for a parking lot.<br />
* Multi-level lots should be created as single place with the shape of the overall parking surface outlined.<br />
<br />
=== {{@|Underground parking lots}} ===<br />
* It is still important to map these correctly so they can be routed to properly, and recommended appropriately in the client to users. Since the underground portion of the garage is not visible to drivers, it is not important to be displayed fully in the app.<br />
* To support the internal features of the client; The polygon must include all above ground areas, and the areas where it starts to go underground. See the [[#Drawing|Drawing section]] below for more details and examples on how to draw these lots.<br />
* If parking lots overlap with a Place, do not add "Parking Lot" category to a Place. Create a separate Area polygon for the parking lot.<br />
<br />
=== {{@|Rental-car lots}} ===<br />
*{{Anchor|Rental-car return|Rental-car return lots}}With the availability of the "Car Rental" Place, rental car facilities and returns, including at airports, should be marked with the Car Rental Place category for the desk and/or the building. If there is any customer parking, or return vehicle parking, then mark that area with the parking lot category.<br />
<br />
=== {{@|Temporary lots}} ===<br />
* Temporary lots for use at festivals, parades, concerts, etc., where temporary parking is being established specifically for the event can be added and named accordingly. Taking care to ensure that any temporary lots that are added, are removed as soon as the event is complete. '''On-street parking should not be added as a temporary lot.'''<br />
<br />
== {{@|Creating and editing parking lot areas}} ==<br />
{{Anchor|Implementation}}<br />
{{mbox|type=caution|text=[[File:PlacesMenu.png|right]]<br />
When editing or creating parking lots and related URs, MPs, & PURs, please make sure you have the Parking Lots [[Map_Editor_Interface_and_Controls#Layers|layer]] enabled (under Places) so the existing PLAs on the map are not hidden.}}<br />
[[File:Waze_PLA_Example.jpg|300px|thumb|right|Outline building footprint only]]<br />
=== {{@|Drawing}} ===<br />
{{Anchor|Extent}}<br />
The Parking Lot Area (PLA) polygon should be drawn to include all parking spaces in the parking lot and the access lanes used to reach each parking space. To prevent creating overly complex polygons and unnecessary geometry points, small medians, curbed areas, and building corners on the scale of around 5 meters or less may be overlapped by the polygon and not cut out by extra geometry points. For multi-level garages, only the footprint of the structure should be outlined.<br />
<br />
Parking lots should never be attached, snapped or have their geometry extremely close to roads as this tends to make editing them difficult. Avoid including or touching any roads outside the parking lot. If a lot spans both sides of a street (excluding Parking Lot Roads), it must be mapped so '''the polygon does not overlap the street'''. This may require drawing the lot as separate places. ''If the lot is elevated above the street and the lot actually covers the street, then the PLA may overlap the street as well.''<br />
<br />
The entry/exit location should be added to the place and adjusted to the appropriate location.<br />
<br />
The following are examples of Parking Lot Areas with excessive and sufficient detail:<br />
<br />
<center><br />
{| class="wikitable"<br />
| style="background: red;"|[[File:Excessive_Detail.jpg|350px|thumb|center|Overly complex shape]]<br />
| style="background: lawngreen;"|[[File:Sufficient_Detail.jpg|350px|thumb|center|Accurate shape with sufficient detail]]<br />
|}</center><br />
<br />
For underground garages it is not important to draw the polygon to match the internal perimeter since there is no GPS signal underground. It is important that the polygon includes any above ground areas, and the underground areas near any entrances or exits in a single polygon. If a lot has more than one entrance/exit the polygon must be made to connect all the entrances and exits. You may use a PLR to show multiple entrances as well, allowing the routing to choose the best route to access the lot, just as an above ground lot is drawn. It is not important however to draw the polygon to the entire footprint of the garage. The accuracy of the entry point ([[Places#Setting_the_stop_point_for_a_Place|'''Setting the stop point''']]) is very important. {{Clear}}<br />
<center><br />
{| class="wikitable"<br />
| style="background: #BEDCE5;" colspan=2; align=center|'''[http://www.waze.com/editor/?env=usa&lon=-73.98899&lat=40.74062&zoom=7&venues=187433367.1874399210.3624518 Icon Parking]'''<br />
|-<br />
| style="background: red;"|[[File:Underground lot mapped to perimeter.png|400px|thumb|center|WRONG: Mapped to estimated underground Perimeter]]<br />
| style="background: lawngreen;"|[[File:Underground lot mapped to entrance.png|350px|thumb|center|CORRECT: mapped above ground, and entry/exit areas]]<br />
|-<br />
| style="background: #BEDCE5;" colspan=2; align=center|'''[http://www.waze.com/editor/?env=usa&lon=-85.75334&lat=38.25737&zoom=6&venues=179700095.1797328626.3614708 Parking Garage - Yum! Center]'''<br />
|-<br />
| style="background: red;"|[[File:Underground lot with multiple places.png|375px|thumb|center|WRONG: Multiple access points mapped as individual places for a single underground garage.]]<br />
| style="background: lawngreen;"|[[File:Underground lot with multiple access.png|350px|thumb|center|CORRECT: multiple access points included in a single polygon for an underground lot, the underground perimeter is not important.]]<br />
|-<br />
| style="background: #BEDCE5;" align=center|'''[http://www.waze.com/editor/?env=usa&lon=-123.03897&lat=44.94261&zoom=7&mode=0&venueFilter=2&venues=155320769.1552945550.3513573 Chemeketa Parkade]'''<br />
| style="background: #BEDCE5;" align=center|'''[http://www.waze.com/editor/?env=usa&lon=-73.58783&lat=40.73257&zoom=6&venueFilter=2 Nassau Community College]'''<br />
|-<br />
| style="background: lawngreen;"|[[File:Elevated lot over street.png|375px|thumb|center|CORRECT: Elevated lot built above street, mapped as a single PLA overlapping the street.]]<br />
| style="background: lawngreen;"|[[File:Ground level lots spanning streets mapped separate.png|375px|thumb|center|CORRECT:Ground level lots spanning streets mapped as separate PLAs. On-street parking not mapped as a PLA.]] <br />
<br />
|}</center><br />
<br />
=== {{@|Naming}} ===<br />
If a parking facility or area has a documented identity, such as {{nowrapcode|Beach Street Garage}}, {{nowrapcode|18th Avenue/Geary Lot}}, {{nowrapcode|Lot 7 - <Stadium name>}}, {{nowrapcode|Short-Term Parking - <Airport name>}}, {{nowrapcode|Cell Phone Lot - <Airport name>}}, etc., its Place should reflect that name to facilitate searches. Generic park-and-ride lots should be named consistently according to local custom, for example as {{nowrapcode|Park & Ride}}.<br />
<br />
The foundational guidance for naming a PLA when the lot serves another entity, is to follow this basic format:<br /><br />
'''<code>[Parking&nbsp;Descriptor]&nbsp;<restrictions>&nbsp;-&nbsp;[Entity&nbsp;served]</code>'''<br /><br />
The framework is {{u|not}} recursive. In other words, there is only one business served in any lot name, and the rest of the name is the descriptor. ''As a rule the descriptor will always have a word in it identifying it as parking, e.g. parking, garage, or lot.'' '''The descriptor can be:'''<br />
* '''Completely generic - ''' For single-business - single-lot<br />
:: {{nowrapcode|Parking - Starbucks}}<br />
* '''Purpose descriptive -''' Where there is only one lot of the type<br />
:: {{nowrapcode|Customer Parking - Office Depot}}, {{nowrapcode|Employee Parking - Office Depot}}, {{nowrapcode|Visitor Parking - LSU Eunice}}, {{nowrapcode|Employee Parking - MSY}} [airport]<br />
* '''Location descriptive -''' Where more than one lot serve the same purpose for the same place<br />
:: {{nowrapcode|Southeast Lot - Big Hill Shopping Center}}, {{nowrapcode|Macy's Lot - Big Hill Shopping Center}}, {{nowrapcode|Grand Blvd Lot - Big Hill Shopping Center}}, {{nowrapcode|Target Garage - Big Hill Shopping Center}}, {{nowrapcode|Dillard's South Lot - Big Hill Shopping Center}}, {{nowrapcode|North Lot - Offices at Buildingtown Plaza}}<br />
* '''Named -''' Where the lot is given an official name<br />
:: {{nowrapcode|Garage 2A - Mercedes-Benz Superdome}}, {{nowrapcode|Credit Card Lot - MSY}}<br />
<br />
==== {{@|Examples}} ====<br />
<br />
If a Parking Lot Area Place is contained within a larger Area Place, do not repeat the larger Area's full name. For example, if the Domestic Garage is contained within the "SFO San Francisco International Airport" Area Place boundaries, it need not be named "SFO San Francisco International Airport Domestic Garage"; "Domestic Garage - SFO" is sufficient.<br />
<br />
If a mall or shopping center has several lots which can be associated with various anchor stores in the mall/shopping center, the lots can be named for the anchor stores. For example: "Macy's Lot - Big Hill Shopping Center" <br />
<br />
In rare cases, a municipality or district provides public parking distinct from any other Area Place but without any documented or signed identity. These can be named after the municipality or district, for example, "Redwood City Public Parking". Do not use completely generic names such as "Parking" or "Public Parking" for anonymous parking facilities. <br />
<br />
A block range or specific address '''should not be used''' to name a lot. If the lot does not have an official and/or signed name, then leave the name blank, and be sure to add the address details in the address field. Some imported PLAs were created with the address or address block range as the name, these names should be removed accordingly. Check your local guidance for any variations.<br />
:'''NOTE:''' It is very important if there is no name for the lot that there be a proper address in the address field. If you don't know the exact address you should at least put the street the main entrance is on, and - if you can - an approximate house number. The address is needed to be displayed in the search results, and differentiate the lot from all the others. Users can see the address displayed, and know which lot it is when viewing the results list. <br />
<br />
==== {{@|Restricted parking}} ====<br />
If there are posted signs restricting the lot to only one certain category of users (e.g. Customers, Residents, Staff, Attendees, Permit Holders, Faculty, Students, etc.) ONLY, then put that restriction in the name. If the lot is restricted to more than one category of users, then put "(restricted access)" in the name. Also put the details of the restriction in the [[#description|description]].<br><br />
<br />
{{mbox|text=Omit the restriction in the name if it is self-explanatory (e.g., {{nowrapcode|Parking - Starbucks}}, is obviously for Starbucks patrons only).}}<br />
<br />
'''Examples:'''<br />
* {{nowrapcode|Parking - Starbucks (employees only)}} ''Different from the patron parking''<br />
* {{nowrapcode|Macy's Lot (customers only) - Big Hill Shopping Center}}<br />
* {{nowrapcode|Lot D (attendees only) - Cheery Stadium}}<br />
* {{nowrapcode|Alpha Lot (permit only) - StudyHard University}} ''Parking allowed by permit only ( even if permits are available to multiple groups (eg for Students, and Faculty)''<br />
* {{nowrapcode|123 Somewhere St Lot (residents only)}}<br />
* {{nowrapcode|Bravo Lot (restricted access) - StudyHard University}} ''Parking allowed for Students, and Faculty ONLY''<br />
* {{nowrapcode|345 Other St Lot (restricted access)}} ''Parking allowed for resident, guests, and staff''<br />
<br />
=== {{@|Description}} ===<br />
Any lot which is fully restricted in some way (e.g. permit/resident/customer only), and not open to the public for general parking, must include that information as the first line of the description. If only some of the available spots are restricted, but there are some spots in the lot open to the public for general parking, then it should not be mentioned.<br><br />
'''Examples:'''<br />
* "Parking by permit only."<br />
* "Parking only for customers of John Doe's Supermarket"<br />
* "Parking only for residents of 123 Something St, and their guests"<br />
* "Parking restricted to 15 minutes or less"<br />
* "Valet parking only"<br />
If you know the details or times of the restrictions you may add that information in the descriptions as well for users to see. This will also help for when those features become available in WME to have the details handy for mapping.<br />
<br />
=== {{@|Operator}} ===<br />
When there is a recognized parking operator, select it from the list, otherwise, leave this field blank. If an Operator is missing from the list that you feel should be added, please send the information to your [[Regional Coordinator]] (RC).<br />
<br />
==={{@|Lot Type}}===<br />
[[File:Parking lot type.png|right]]<br />
At the top of the 'More Info' tab when a parking lot is selected you can set the Primary Lot Type. This setting affects whether a lot will be recommended in the client app when a Wazer searches for nearby parking, or as a suggested lot when searching for a destination. '''Any lots marked here as Restricted or Private {{U|will not be recommended}} to any users in the app for the time being.''' As the feature is further developed, there will be the ability to set more details on these restrictions so the lots may be recommended under certain circumstances. {{As of|2017|03}} these are the guidelines accepted for the application of these settings, designed for optimal user experience.<br />
<br />
*Mark all parking lots with unrestricted public access as '''Public'''. This includes free and publicly owned parking lots, as well as for-profit garages, in which a Wazer may park, regardless of intent.<br />
*Mark parking lots where some restrictions apply (customers, patrons, visitors), but the ability to see or select between them is useful to a Wazer, as '''Public'''. For example, a university campus with multiple student, visitor, or faculty parking lots, or a large shopping center that contains multiple patron-only parking lots. A suburban fast food chain's parking lot is not.<br />
**Otherwise, mark parking lots where some restrictions apply (customers, patrons, visitors) as '''Restricted'''.<br />
*Mark parking lots where parking is restricted to a specific audience (residents of an apartment parking lot, employee garage of an office complex), but the ability to see or select between them is useful to a Wazer, as '''Public'''. For example, Employee, or permit parking at an airport, or large compound, large housing developments with multiple permitted lot, etc.<br />
**Otherwise, mark parking lots where parking is restricted to a specific audience (residents of an apartment parking lot, employee garage of an office complex) as '''Private'''.<br />
<br />
=== {{@|Locking standards}} ===<br />
Due to this major shift in editing guidelines, it is recommended that once a Parking Lot Area (PLA) has been added, that it be locked to 3 to avoid newer editors, or those not familiar with the change, from editing or deleting the PLA.<br />
<br />
== {{@|Interface - more info}} ==<br />
[[File:WME_PLA_UI_081016.jpg|400px|thumb|right|WME User Interface - More info tab]]<br />
<br />
'''Opening hours''' - Hours lot is open. Set open times for the lot or select each day and the ''All day'' radio button for lots open 24 hours a day / 7 days a week. <br />
*''Cars can exit when lot is closed'' - Check if the lot or garage does not restrict egress after the lot is considered closed.<br />
*'''Cost'''{{Anchor|Free versus paid parking}}<br />
**Cost determination should be made based on parking lot fees for other similar and nearby lots for the same type of venue.<br />
***Example #1: Adding / editing parking lots near an airport; terminal parking may be the most expensive at $25/day, express parking the next level down (moderate) at $15/day and remote parking the next best option at $5/day (low).<br />
***Example #2: Hotel parking; on-site $50/day (expensive), self-parking garage at $30/day (moderate), and off-site parking at $15/day (low)<br />
**Each lot within approximately ⅔ mile (1 km) radius should be taken into consideration for PLA cost determination where appropriate.<br />
<br />
*'''Services '''(select services listed below)<br />
**Reservations - Lot accepts reservations or accepts pre-paid parking passes or permits.<br />
**Disability parking - Spaces exist for handicap parking / wheelchair accessible spaces.<br />
**Carpool Parking - Reserved spots exist for people who carpool to the location.<br />
**EV Charging - Lot contains a station to charge electric vehicles.<br />
{{mbox | type = important| text = If adding the EV Charging Station attribute, also add a separate point Place for the EV station, as described in the [[Places/Charging station]] wiki.}}<br />
**Car wash - A car wash is on premises within the parking lot (some airports and other venues have amenities such as this for those parking within the lot).<br />
**Security - On-site security for the specific lot exists<br />
*'''Number of Spots'''<br />
**List the most accurate number of spots within the specified parking lot area polygon.<br />
*'''Contact info'''<br />
**A link to the main venue to which the parking lot belongs or to the parking lot vendor's site (if applicable) is permissible here.<br />
*'''Phone'''<br />
**The phone number for the main venue to which the parking lot belongs or to the parking lot vendor is permissible here.<br />
<br />
== {{@|Parking lot roads}} ==<br />
Don't forget to map any necessary [[parking lot roads]], to allow for proper navigation into and out of the parking lot. The parking lot place does not substitute roads needed for actual navigation.<br />
<br />
'''Parking lot roads are not required simply because a lot qualifies for a PLA.''' It is OK for small lots which do not qualify for their own PLRs to still be mapped as a PLA, the two features are independent of each other. PLRs have an effect on routing which can sometimes be detrimental. While it is important to map the ''necessary'' PLRs, please follow [[Parking lot roads|the guidance]] and do not add PLRs which are not necessary.<br />
<br />
== {{@|What does not qualify as a PLA?}} ==<br />
<br />
=== {{@|On-street parking}} ===<br />
[[File:LotsnoStreet.png|thumb|right|The surrounding parking lots have been mapped, but on-street parking along State St and College Ave has not been mapped.]]{{Anchor|Examples}}{{Red|On-street parking should not be added at this time.}}<br />
<br />
=== {{@|Gas stations}} ===<br />
<br />
[[Places/Gas station#Area_size|Gas stations]] are already drawn on the map as an area and typical usage includes parking to get gas or enter the convenience store (when present). They are therefore handled specially by the servers, and '''do not require an additional PLA to be drawn on top of the gas station area'''. However, if there is a significant parking area there which is worthy to be recommended to users who are navigating to nearby venues (e.g. a truck stop, etc.), then you ''may'' add a PLA there.<br />
<br />
=== {{@|Valet only facility}} ===<br />
Parking lots or garages accessed exclusively by valet staff, and situated away from the valet drop off point should not be added to the map. (If regular drivers are not allowed to drive up to the valet facility, and rather must drop the vehicle at a different location, and the valet drivers are the only ones driving to this facility location, then it serves no purpose being recommended ever.<br />
<br />
In such cases, where the valet drop off is not near the stop point for the place it services, the valet drop off may be added as a PLA, and marked as valet only in the name.<br />
<br />
If regular drivers are allowed to drop their vehicle at the valet facility, or there is mixed use of the facility where non-valet users can park as well, then a PLA '''should''' be added.<br />
<!--[[File:No_PLA.jpg|500px|thumb|center|Where PLAs are not needed]]--></div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=Junction_Style_Guide/Interchange&diff=159161Junction Style Guide/Interchange2017-07-16T16:35:23Z<p>Qwaletee: Roadtechie's link?</p>
<hr />
<div>{{ReturnTo | Junction_Style_Guide | the Junction Style Guide}}<br />
<br />
An '''interchange''' is a road junction where two roads are connected by dedicated roadways, called '''ramps'''. The roads connected by an interchange do not intersect one another directly, and if they cross, the crossing is grade-separated.<br />
<br />
Since interchanges often involve grade-separated crossings, the [[road elevation]] of the segments becomes important. If two roads cross without connecting directly, their elevations must be different.<br />
<br />
This article is a sub-article of the [[Junction Style Guide]]. As such, '''this article is a Style Guide''' as well. The following sections discuss the proper style for ramps, interchanges, and some common Interchange designs. Note that some interchanges may be a hybrid of these basic designs where one side or quadrant of the interchange may differ from the others.<br />
<br />
Before reading through this article, be sure to fully understand the information in the [[Junction Style Guide]].<br />
<br />
== Ramps ==<br />
<br />
Ramps have a very specific purpose in Waze. They are intended to connect segments of Minor Highways, Major Highways, and Freeways to roads where there are no at-grade crossings.<br />
<br />
The {{Ramp}} type is used extensively in interchanges for three reasons.<br />
* Ramp segment names are not displayed on the map.<br />
* Ramp segments have essentially no penalty, so they can be used to connect Freeways and Major Highways with each other without causing problems.<br />
* Ramp segments are relatively small but show at high zoom levels, so interchanges do not distract from highways but can be seen at high speeds.<br />
<br />
=== When to use ramps ===<br />
<br />
Use of the {{Ramp}} type is governed by the following rules:<br />
* [[Road types]]<br />
* [[At-grade connectors]]<br />
<br />
=== Ramp geometry and complexity ===<br />
<br />
When placing the beginning of a ramp, place the first [[geometry node]] of the ramp segment at the point where the solid white line begins, and extend the ramp naturally to create a junction with the road segment, typically at a 10–15° angle. This will allow for consistent timing of exit instructions.<br />
<br />
: [[Image:Exit-ramp-geom.png]]<br />
<br />
Do the same when placing the end of a ramp. This will allow for consistent auto-zoom functionality—the client remains zoomed in for the duration of the ramp, zooming out when the user gets on the freeway.<br />
<br />
: [[Image:Entrance-ramp-geom.png]]<br />
<br />
Rule #1 is still simpler is better. If there is no large distance between paths at the end of a ramp (either into or out of the ramp), a single segment connecting to a single junction node is all that is needed. The existence of a painted, concrete, or grass island is '''NOT''' enough of a reason to divide a ramp into multiple ramps.<br />
<br />
: [[Image:Jct_ramp_no_split.png]]<br />
<br />
When paths at the end of the ramp deviate significantly in distance, regardless of the existence of any type of island, then multiple ramps should be used.<br />
<br />
: [[Image:Jct_ramp_split.png]]<br />
<br />
== Interchange types ==<br />
These are junctions involving the three Highway/Freeway road types - {{Minor Highway}}, {{Major Highway}}, and {{Freeway}} -- as well as their {{Ramp|Ramps}}.<br />
<br />
Specific examples of how to handle common junction types are provided in later sections. All of those examples use the basic building blocks provided here.<br />
<br />
If you are unsure what road type you should use, refer to the '''[[road types]]''' article.<br />
<br />
=== Exits ===<br />
It is a basic Exit situation when a "straight" direction is obvious to a driver and navigation instructions are only needed for the non-straight direction (the exit.) If navigation instructions are required for both directions, see the [[#Wayfinders|Wayfinders]] section below.<br />
<br />
==== Exit geometry ====<br />
: [[Image:Jct_fwy_exit.png]] [[Image:Jct_maj_exit.png]] [[Image:Jct_min_exit.png]]<br />
<br />
To be treated as a basic Exit, the following must be true:<br />
# The entering segment and the continuing segment must be {{Freeway}}, {{Major Highway}}, or {{Minor Highway}} type,<br />
# The Freeway/Highway continuing segment should have close to a zero degree departure angle from the entering segment,<br />
# The other exiting segment must be of the type {{Ramp}}, and<br />
# The Ramp exiting segment should have a departure angle around 10–15 degrees from the entering segment, as explained above.<br />
<br />
When those conditions are met, the navigation will present an "Exit Right/Left" instruction when the ramp is to be used, and will remain silent when the continuing Freeway/Highway segment is to be used.<br />
<br />
==== Exit naming ====<br />
The Highway/Freeway segments before and after the junction should be named the same. The ramp segments should be named in accordance with the best practices in your location.<br />
<br />
[[Road names#Exit_ramps_and_Entrance_ramps_.28on-ramps.29|US Specific Ramp Names]]<br />
<br />
[[Road types and names|Naming standards for other areas]]<br />
<br />
Editors covering areas that do not have specific best practices should review the existing guides for other areas, and determine which best matches the roadways of your area.<br />
<br />
=== {{anchor|Freeway/highway splits}} Freeway/highway forks===<br />
A Highway/Freeway Fork is when a Highway/Freeway segment meets at a junction with two other Highway/Freeway segments and there is no obvious straight through direction to a driver. This is synonymous with the MUTCD term "split".<br />
<br />
==== {{anchor|Freeway split geometry}}Freeway fork geometry ====<br />
: [[Image:Jct_fwy_fwy_split.png]]<br />
<br />
To receive a navigation instruction for '''both''' branches of a fork, the following must be true:<br />
# Both exiting segments must be the same type (Freeway, Major Highway, Minor Highway).<br />
# Each exiting segment must have a name which is different from the name of the entering segment.<br />
# The two exiting segments should have departure angles around 10 to 15 degrees from the entering segment.<br />
<br />
With those conditions met, the junction will present "stay to the left" and "stay to the right" navigation instructions using the name of the appropriate exiting segment.<br />
<br />
==== {{anchor|Freeway split naming}}Freeway fork naming====<br />
<br />
The primary rule is that all 3 segments at the junction must have different names. That can be accomplished in one of two ways:<br />
# Using road names alone - It is an easy situation if all three roads which connect have different names. If "Highway A" forks into "Highway B" and "Highway C", then that is all we need to have a properly functioning fork.<br />
# Using signs and [[#Wayfinders|Wayfinder Segments]] - If one of the branches of the fork has the same name as the entering segment, we must create uniqueness at the junction. If "Highway X" forks off from "Highway Y" and "Highway X" continues as the other branch, the preferred approach is to use named [[#Wayfinders|Wayfinder Segments]].<br />
<br />
=== Wayfinders ===<br />
<br />
A '''wayfinder''' gives a user an instruction directing them how to continue on the road the user is already on, in situations where it may be unclear, and there would otherwise be no instruction.<br />
<br />
<br />
==== Terminology ====<br />
<br />
A '''travel lane''' is a lane which is long enough that a naïve driver might consider it a long-distance lane. For our purposes we will clarify this as any lane which;<br />
#before nearing the exit, is neither striped nor signed as a departing lane over a significant length (approximately ¾ a mile, or its full length, whichever is shorter), and<br />
#has not just started within a mile before the exit.<br />
<br />
The '''typical side''' for an exit depends on the traffic side for that country. In a country with [[Right-hand traffic]] i.e. the USA, the typical side for an exit is the right side.<br />
<br />
The '''atypical side''' for an exit is the opposite of the typical side described above.<br />
<br />
A '''continuation path''' or '''continuation''' is the group of lanes after the fork which continue to be the same road as it was before the fork. (In the following example, the lanes which continue to be I-47)<br />
<br />
[[File:Lane definitions.png|400px|thumbnail|center]]<br />
{{clear}}<br />
<br />
==== Criteria ====<br />
<br />
A wayfinder is warranted in the following cases:<br />
*The continuation path on a controlled-access highway or freeway, when an exit is present on the typical side, has at least two fewer ''travel lanes'' after the exit than before it;<br />
*The continuation path on a controlled-access highway or freeway has the same number of lanes as, or fewer lanes than, the exit path after the fork;<br />
*The continuation path on an uncontrolled highway, or when an exit is present on the atypical side of a controlled-access highway or freeway, has at least one fewer ''travel lane'' after the exit than before it;<br />
*The continuation path consists of a single lane; or<br />
*Other conditions exist that may suggest a fork, rather than an exit (use your better judgement, and discretion) -- for example:<br />
**The physical roadway itself forks or diverges with no clear straight-ahead direction;<br />
**The road which appears to be straight ahead is not the actual continuation;<br />
**Signage and striping do not clearly provide all expected "exit" indications, or do so inconsistently; or<br />
**Signs are present with arrows pointing left and right but no sign clearly establishes the continuation.<br />
<br />
<br />
{{NeedImage| Need sample images for "lane drops" and "non-obvious continuations"; also, example of BGS with lane arrows}}<br />
<br />
[[File:FreewayS-inS-out.png|200px|right]]<br />
In these cases, we need to use a wayfinder configuration. Each wayfinder configuration will have one "IN" segment and two "OUT" segments.<br />
<br />
==== Configuration ====<br />
<br />
These configurations have been designed based on a very in-depth understanding of [[How_Waze_determines_turn_/_keep_/_exit_maneuvers|Waze's standard rules for generating instructions]]. Please don't deviate from these precise configurations.<br />
<br />
* Each "stub" segment should be {{:Segment length/Minimum}} long. This is long enough so it will not cause routing problems, but it is short enough to suppress display of the names (on Freeway stubs) and keep freeways looking contiguous (on Ramp stubs).<br />
* The OUT segments should have a ''turn angle'' of 10°-20° off of the mid-line on opposite sides of each other, consistent with [[Junction_Style_Guide/Interchanges#Freeway_split_geometry|the geometry for freeway forks]]. This will allow for easy identification in WME, but still look seamless in the client app.<br />
<br />
<br />
To configure the wayfinder, <br />
* If the numbered/signed exit is on the '''right''', the OUT segments should be {{Ramp}} type. This will give an "exit right" instruction for the exit and a "stay to the left" instruction for the continuation. <br />
** For a basic [[Junction Style Guide/Interchanges#Exits|exit]], use a named Ramp stub for the continuation, and a standard Ramp for the exit.<br />
** For a [[Junction Style Guide/Interchanges#Freeway.2Fhighway splits|freeway fork]], use a Ramp stub on both sides.<br />
* If the numbered/signed exit is on the '''left''', the OUT segments type should be the same as {{Road|style=background-color: #fbe73f;|the IN segment}}, in the following examples we will use the {{Freeway}} type. This will give "stay to the" instructions on both sides (if {{Ramp}} segments were used, Waze would give a confusing "exit right" instruction for the continuation).<br />
** For a basic [[Junction Style Guide/Interchanges#Exits|exit]], use a named Freeway stub for the continuation, and an unnamed Freeway stub followed by a named Ramp for the exit.<br />
** For a [[Junction Style Guide/Interchanges#Freeway.2Fhighway splits|freeway fork]], use named Freeway stubs on both sides.<br />
<br />
<div style="font-size:smaller"><br />
{| class="wikitable" style="text-align:center"<br />
|-<br />
! Exit direction<br />
! Type<br />
! Left OUT configuration<br />
! Right OUT configuration<br />
! Example<br />
|-<br />
| Right<br />
| Basic exit<br />
| '''Continuation side'''<br/>{{Ramp|Named Ramp stub}} → {{Freeway|Named Fwy}}<br />
| '''Exit side'''<br/>{{Ramp|Named Ramp}}<br />
| [[File:RightExitRamp.png|191px]]<br />
|-<br />
| Right<br />
| Fwy fork<br />
| '''Continuation side'''<br/>{{Ramp|Named Ramp stub}} → {{Freeway|Named Fwy}}<br />
| '''Exit side'''<br/>{{Ramp|Named Ramp stub}} → {{Freeway|Named Fwy}}<br />
| [[File:RightExitSplit.png|191px]]<br />
|-<br />
| Left<br />
| Basic exit<br />
| '''Exit side'''<br/>{{Freeway|Unnamed Fwy stub}} → {{Ramp|Named Ramp}}<br />
| '''Continuation side'''<br/>{{Freeway|Named Fwy stub}} → {{Freeway|Named Fwy}}<br />
| [[File:LeftExitRamp.png|189px]]<br />
|-<br />
| Left<br />
| Fwy fork<br />
| '''Exit side'''<br/>{{Freeway|Named Fwy stub}} → {{Freeway|Named Fwy}}<br />
| '''Continuation side'''<br/>{{Freeway|Named Fwy stub}} → {{Freeway|Named Fwy}}<br />
| [[File:LeftExitSplit.png|191px]]<br />
|}<br />
</div><br />
<br />
==== Segment naming ====<br />
Keep these basic principles in mind:<br />
* The OUT segments must both be the same type (either {{Freeway}}, {{Major Highway}}, {{Minor Highway}}, or {{Ramp}}, as explained below).<br />
* Each OUT segment must have a name different than the IN segment.<br />
** '''NOTE:''' An unnamed segment (no-name box checked) is considered to have a blank name, and not the inherited name for these purposes. Therefore either both OUTs must be no-name, or both must have their own unique name.<br />
* OUT segments should be named with the information displayed on the roadway signs.<br />
** However, if this would leave an OUT segment with the same name as the IN segment, the OUT segment should be left unnamed (i.e., check the "no name" box).<br />
<br />
{{mbox|type=important|text=Previously in these situations segment naming was modified in one of the following ways {{u|''in order of preference''}}:<br />
#Add a control/destination city, if it is known, to the OUT segment name.<br />
#Remove the compass cardinal from the OUT segment name.<br />
#Add a space to the end of the OUT segment name (note that this will be flagged by the [[Community_Plugins,_Extensions_and_Tools#WME_Validator|WME Validator script]], if active, and possibly result in undoing by another editor)<br />
#Create a stub in the IN segment just before the junction with no street name.<br />
#*'''NOTE:''' This option should only be used as a last resort because it prevents the [[Routing_server|routing server]] from properly calculating [[Turn delays|turn delays]], and may result in inefficient routing through the area.<br />
<br />
If you see any of these set-ups, please correct it to one of the two proper methods listed above.}}<br />
<br />
If the continuation is '''signed''', and a wayfinder is warranted,<br />
* If the continuation sign contains the name or shield of the continuing road, do '''not''' use "to" at the beginning of the name of the OUT segment. e.g., a freeway fork where one side is the continuation of the same freeway (the user is already on the road, not going "to" it). Most wayfinders will fit this criterion.<br />
**If the name of the continuation is included but is not listed first on the sign, move the name of the continuing road to the beginning of the segment name. (e.g. In this wayfinder the highway you are on now, and continuing on is I-275, so the segment name should be "I-275 N / I-74 E / US-52 E / Cincinnati".)<br />
* If the continuation sign '''does not contain''' the name or shield of the continuing road, then the road name should begin with "to".<br />
<br />
<br />
If the word "TO" is explicitly included on the continuation sign,<br />
* [[File:Wayfinder To BGS.png|300px|thumbnail|right]]Move the shields or names affected by the "TO" to the end of the segment name after a slash (/). (The example BGS shown is for the continuation of I-80, which leads to I-280, with a control city Morristown.)<br />
** If any included control cities or road names correlate only to the roads affected by the "TO", then those control cities or road names should be moved after the "/ to [road(s)] /" on the segment name.<br />
*** [[File:Wayfinder To WME.png|300px|thumbnail|right]] If Morristown is served by I-280 and ''not'' by I-80, the continuation segment should be '''"I-80 / to I-280 / Morristown"'''.<br />
** If any included control cities or road names correlate to the roads '''not''' affected by the "TO", then those control cities or road names should remain in place before "/ to [road(s)]".<br />
*** If Morristown is served by I-80, the continuation segment should be named '''"I-80 / Morristown / to I-280"'''.{{clear}}<br />
<br />
<br />
If the continuation is '''not signed''', and a wayfinder is warranted,<br />
* If the OUT segment is a continuation of the same road, it should be left unnamed (check the "no name" box).<br />
* If the OUT segment is an exit, it should be named following the guidelines for an unsigned exit.<br />
* If the OUT segment is a short continuation of the same road leading to another road, name the segment starting with "to" followed by the name of the road to which the continuation leads, following these guidelines:<br />
** {{anchor|no BGS to}}[[File:No BGS To exit.PNG|300px|thumbnail|right]]Where the wayfinder is just before, but not at, the termination of a road, so the continuation OUT segment is named for the road that the continuation leads to at the termination. However you still must travel for a short distance on the continuation of this road until those exits/termination. [[File:No BGS To exit zoom out.PNG|300px|thumbnail|right]]Our example here is a wayfinder on US-1-9 N (Truck), the left OUT is the continuation, however the right OUT also continues on the same road until it intersects with SR-440, with an exit to SR-440 S along this short segment. There are no roadway signs for any of these forks, or exits/terminations. The OUT segment here would be named '''"to SR-440 S / Communipaw Ave"''', and the SR-440 exit will be named following the [[Road_names#Exit_ramps_and_entrance_ramps_.28on-ramps.29|unsigned exit guidelines]]. However it may be appropriate (if there are no House Numbers, or other on ramps past this wayfinder before it reaches the exit, to leave this entire portion with no name, and the instruction will inherit the name of the next road to which you are going.{{clear}}<br />
<br />
<br />
Wayfinder naming examples<br />
<div style="font-size:smaller"><br />
{| class="wikitable" style="text-align:center"<br />
|-<br />
! #<br />
! Continuation sign<br />
! Continuing road name<br />
! Rule<br />
! Waze road name<br />
|-<br />
| colspan="3" | [[File:Wayfinder I-10 BGS.png|225px|thumbnail|center]]<br />
| [[File:Wayfinder I-10 WME.png|225px|thumbnail|center]]<br />
| context image<br />
|-<br />
| 1<br />
| I-10 E / New Orleans Business District<br />
| I-10 E<br />
| Matches - do not use "to"<br />
| '''I-10 E / New Orleans Business District'''<br />
|-<br />
! #<br />
! Continuation sign<br />
! Continuing road name<br />
! Rule<br />
! Waze road name<br />
|-<br />
| colspan="3" | [[File:Wayfinder continuation TO I-71.png|225px|thumbnail|center]]<br />
| [[File:Wayfinder 471 close.png|225px|thumbnail|center]]<br />
| [[File:Wayfinder 471 context.png|225px|thumbnail|center]]<br />
|-<br />
| 2<br />
| I-71 N / Columbus<br />
| I-471 N<br />
| Does not match – use "to"<br />
| '''to I-71 N / Columbus'''<br />
|-<br />
! #<br />
! Continuation sign<br />
! Continuing road name<br />
! Rule<br />
! Waze road name<br />
|-<br />
| colspan="3" | [[File:Wayfinder continue last BGS.png|225px|thumbnail|center]]<br />
| [[File:Wayfinder 275 closeup.png|225px|thumbnail|center]]<br />
| [[File:Wayfinder continue last WME.png|225px|thumbnail|center]]<br />
|-<br />
| 3<br />
| I-74 E / US-52 E / I-275 N / Cincinnati<br />
| I-275 N<br />
| Included but not first – move to beginning<br />
| '''I-275 N / I-74 E / US-52 E / Cincinnati'''<br />
|-<br />
! #<br />
! Continuation sign<br />
! Continuing road name<br />
! Rule<br />
! Waze road name<br />
|-<br />
| colspan="3" | BGS image<br />
| WME image<br />
| context image<br />
|-<br />
| 4<br />
|<br />
|<br />
|<br />
| '''name'''<br />
|-<br />
! #<br />
! Continuation sign<br />
! Continuing road name<br />
! Rule<br />
! Waze road name<br />
|-<br />
| colspan="3" | image<br />
| image<br />
| image<br />
|-<br />
| 5<br />
|<br />
|<br />
|<br />
| '''name'''<br />
|}<br />
</div><br />
<br />
=== Ramp-ramp forks ===<br />
A ramp may itself fork and branch into two directions. If this is the case, "Exit Right" and "Exit Left" will be announced using the name of the appropriate exiting segment in all cases.<br />
<br />
==== Ramp fork geometry ====<br />
: [[Image:Jct_ramp_ramp_split.png]]<br />
<br />
==== Ramp fork naming ====<br />
If ramps are unnamed, the name of a subsequent ramp will propagate backwards. In the example above, if the two ramps exiting the junction are named, the ramp entering the junction can be left unnamed. Then any navigation instruction directing you onto the first ramp would use the name of the appropriate exiting ramp.<br />
<br />
'''Example:''' The two ramps exiting the junction are named "DestinationLeft" and "DestinationRight". The ramp that enters the junction is unnamed. If you need to "Exit Right" onto the unnamed ramp. If you are headed to "DestinationLeft", navigation would tell you:<br />
* Exit Right to Destination Left<br />
* Keep Left to Destination Left<br />
<br />
Using unnamed ramps is very useful to provide sufficient notification of an approaching decision point, as long as the names of both ramp forks are visible on signs at the start of the initial ramp.<br />
<br />
'''Example of good use of unnamed ramps:'''<br />
* Initial Exit Sign: to City A and City B<br />
* Destination Left Sign: to City A<br />
* Destination Right Sign: to City B<br />
Result: An unnamed initial ramp will provide accurate and informative navigation instructions to the driver.<br />
<br />
'''Example of poor use of unnamed ramps:'''<br />
* Initial Exit Sign: to Downtown<br />
* Destination Left Sign: to Downtown<br />
* Destination Right Sign: to Center St<br />
Result: An unnamed ramp may create confusion, since both destination ramp names are NOT listed on the initial exit sign. In this case, the initial ramp should be named.<br />
<br />
'''Example of modified use of unnamed ramps:'''<br />
<br />
* Initial Exit Sign: Exit 70A-B to City A and City B<br />
* Destination Left Sign: to City A<br />
* Destination Right Sign: to City B<br />
* Destination Left name in Waze: Exit 70A: City A<br />
* Destination Right name in Waze: Exit 70B: City B<br />
Result: By using a modified name for the destination ramps, we have combined information from two sets of signs to generate the advance notice a driver may need to prepare for a decision point.<br />
<br />
== Interchange configurations ==<br />
<br />
<br />
=== Diamond interchange ===<br />
: [[Image:Jct_diamond.png]]<br />
''See also: [[Wikipedia:Diamond_interchange|Diamond Interchange article on Wikipedia]]''<br />
<br />
Common in wide open spaces where land acquisition and geography are not concerns, this Interchange design has ramps equally distributed across all 4 quadrants.<br />
<br />
In the simplest form, this can be represented as single connections from the ramps to the surface street. <br />
<br />
The straight through motion from the exit ramp to the entrance ramp should typically be enabled, if legal to drive. Under normal circumstances, the Big Detour Prevention mechanism discourages the routing server from routing someone off the freeway and directly back on. When the freeway path between the ramps is closed, or slow enough to overcome the Detour penalty, this off-on route may be given as a desirable alternative.<br />
<br />
Be aware that the Big Detour Prevention penalty is intended to discourage routing that leaves a freeway (or highway) and returns to the same freeway (or highway). Therefore, at least one name (primary or alternate) of the freeway/highway segment before the exit ramp must exactly match one name (primary or alternate) of the freeway/highway segment after the entrance ramp to trigger the penalty. For further information see the [[Detour Prevention Mechanisms|Big Detour Prevention Mechanism]] page.<br />
<br />
:[[Image:Jct_diamond_simple_turns_new.png]]<br />
<br />
If the ramps connect to the surface street at multiple points, restrict turns which should use another ramp. Review the section on [[Junction Style Guide/Interchanges#Ramp geometry and complexity|ramp geometry and complexity]] for more details on this topic. <br />
<br />
First we see the turns that must be restricted for the exit ramps:<br />
<br />
: [[Image:Jct_diamond_cplx_turns_off_L_new.png]] [[Image:Jct_diamond_cplx_turns_off_R.png]]<br />
<br />
Then we see what must be restricted for the entrance ramps:<br />
<br />
: [[Image:Jct_diamond_cplx_turns_on.png]]<br />
<br />
'''Note on elevations:'''<br />
The single surface street segment between the inner most ramps should be either raised or lowered in relation to the freeway segments depending on the actual geography at the interchange.<br />
<br />
=== Cloverleaf interchange ===<br />
: [[Image:Jct_cloverleaf.png]]<br />
<br />
''See also: [[wikipedia:Cloverleaf_interchange|Cloverleaf Interchange article on Wikipedia]]''<br />
<br />
In a Cloverleaf Interchange, left turns are eliminated from all movements between the Freeway and the surface street. First check the exit ramps.<br />
<br />
: [[Image:Jct_cloverleaf_off_outer_turns.png]] [[Image:Jct_cloverleaf_off_inner_turns.png]]<br />
<br />
Then check the entrance ramps for illegal turns.<br />
<br />
: [[Image:Jct_cloverleaf_on_turns.png]]<br />
<br />
The connections to the Freeway segments may be treated in two ways:<br />
<br />
:[[Image:Jct_cloverleaf_options.png]]<br />
<br />
# (top) we can have the inner entrance and exit ramps have their own junction nodes with the Freeway. Do '''NOT''' use this approach if there are [[#Collector.2FDistributor_Lanes|Collector/Distributor Lanes]] (or a similar situation) involved.<br />
# (bottom) we can have the entrance and exit ramps share a single junction node with the Freeway. This allows us to eliminate the very short Freeway segment that may exist between the inner entrance and exit ramps.<br />It is best to offset this shared junction onto the Entrance ramp side of the surface street. This prevents the junction from accidentally being connected to the surface street or looking like it does. We favor the Entrance ramp side, because this would result in a slightly earlier exit instruction which is, of course, preferred over a late exit instruction. <br />
<br />
The determining factor of which design to use will partly depend on the actual size and scale of the specific interchange and if there is a [[#Collector.2FDistributor_Lanes|Collector/Distributor]] involved.<br />
<br />
'''Note on Elevation:'''<br />
The single surface street segment between the inner most ramps should be either raised or lowered in relation to the freeway segments depending on the actual geography at the interchange.<br />
<br />
=== Folded diamond interchange ===<br />
: [[Image:Jct_folded_diamond.png]]<br />
''See also: Discussion of Folded Diamonds and A2/B2 Partial Cloverleafs on the [[wikipedia:Partial_cloverleaf_interchange|Partial Cloverleaf Interchange article on Wikipedia]]''<br />
<br />
Geography or property ownership may prevent the ability for an interchange to be constructed with all ramps evenly distributed across the 4 quadrants of the interchange. When only two quadrants are used, it is typically called a Folded Diamond (basically a sub-type of a Partial Cloverleaf Interchange). The ramps may be all on one side (as in the examples in this section) or they may be located in diagonally opposed quadrants.<br />
<br />
The unique situation presented by the Folded Diamond arrangement is having both Entrance and Exit ramps terminating on the same side of the surface street. Ideally both ramps should terminate on the same junction node to permit us to easily restrict the illegal and usually impossible ramp-to-ramp movement.<br />
<br />
: [[Image:Jct_folded_diamond_u-turn.png]]'<br />
<br />
Like with a basic Diamond Interchange, often it will be necessary to represent the ramps making multiple connections to the surface street. Be sure to read the article [[Junction_Style_Guide#Simple_is_better|Simple is better]] in the Junction Style Guide. <br />
<br />
Restrict all non-permitted turns.<br />
<br />
: [[Image:Jct_folded_diamond_off_turns_L.png]] [[Image:Jct_folded_diamond_off_turns_R.png]] [[Image:Jct_folded_diamond_on_turns.png]]<br />
<br />
'''Note on Elevation:''' Similar to a basic Diamond interchange, in most cases only the segment of the surface street that crosses the Freeway segments will need to be adjusted up or down.<br />
<br />
=== Single-point urban interchange (SPUI) ===<br />
: [[Image:Jct_SPUI.png]]<br />
''See also: [[wikipedia:Single-point_urban_interchange|Single Point Urban Interchange article on Wikipedia]]''<br />
<br />
A SPUI is a very space and flow efficient design, but it takes extra attention to ensure the turns are correct. And as the name indicates, ideally there should be a single junction in the center. You may need to tweak the geometry of segments a bit off of alignment from the real physical world, but it should be minor if the interchange is a true SPUI.<br />
<br />
The outer branches of the exit ramps are similar to a diamond interchange and ramp to ramp routing should be enabled if possible and legal. However, in many SPUIs such ramp to ramp routing is not possible:<br />
<br />
: [[Image:Jct_SPUI_off_outer_turn.png]]<br />
<br />
Where things get complicated is the inner branches leading to the Single Point. You need to avoid ramp-to-ramp in two directions and a reverse flow turn. '''Note:''' The ramp-to-ramp motion to facilitate a U-Turn (the top left arrow in the image below) may or may not be allowed depending on the specific interchange. Please validate this turn.<br />
<br />
: [[Image:Jct_SPUI_off_inner_turn.png]]<br />
<br />
Luckily the entrance ramp restrictions are similar to the diamond interchange:<br />
<br />
: [[Image:Jct_SPUI_on_turn.png]]<br />
<br />
If you were to look at all the restricted turns at once, you may get the false impression that something is very wrong. But as you now know, a SPUI has almost as many restricted turns as allowed ones.<br />
<br />
: [[Image:Jct_SPUI_all_turns.png]]<br />
<br />
'''Note on Elevation:'''<br />
The two surface street segments (between the outer ramps and connected to the Single Point) and the 4 ramp segments connected to the single point should all be the same level, either one higher or one lower than the elevation of the freeway segments above/below the single point.<br />
<br />
=== Collector/Distributor Lanes ===<br />
<br />
These are lanes parallel to, but physically separated from, the lanes of a Freeway that serve to keep merging traffic out of the flow of through traffic on the mainline Freeway.<br />
<br />
Collector/distributor lanes serve as either:<br />
* some of the ramps in an '''interchange''', or<br />
* local lanes in configurations with '''[[wikipedia:local-express lanes|local-express lanes]]'''.<br />
<br />
<br />
==== Collector/distributor interchanges ====<br />
<br />
Some interchange configurations make use of collector/distributor lanes to separate lower-speed merging traffic from high-speed through traffic. This is often used in cloverleaf interchanges and in groups of nearby exits.<br />
<br />
===== Collector/distributor cloverleaf =====<br />
<br />
This is a cloverleaf interchange that is connected to a collector/distributor instead of directly to the main roadway. Map collector-distributor cloverleaf ramps as you would any other ramp.<br />
<br />
[[Image:Jct_fc_cloverleaf_bad.png]]<br />
<br />
The [[Detour Prevention Mechanisms|detour prevention mechanism]] will discourage Waze from routing users onto the collector-distributor and back onto the freeway – as long as the city name on the freeway is the same (or set to "no city") before, throughout, and after the collector-distributor. Previously this feature was not available and the ramps were set up to restrict the through route. Some of these ramp configurations may still be set up that way, so they can now be configured as pictured above with the through route enabled.<br />
<br />
==== Complex collector/distributor interchanges ====<br />
<br />
[[Image:Collector-distributor-exit.png|thumb|right|450px|Collector-distributor lanes used in an interchange on I-81 in Christiansburg, Virginia (Exits 118A-B-C)]]<br />
<br />
Where collector/distributor lanes are used as part of an interchange, use the {{Ramp}} type for the collector/distributor lanes. Name the ramp segments as you would any other ramp segment.<br />
<br />
Ensure that a name on the Freeway segments is consistent before and after the collector/distributor lanes, so that the [[Detour Prevention Mechanisms|detour prevention mechanism]] will prevent Waze from routing users erroneously.<br />
<br />
{{clear}}<br />
<br />
==== Local-express lanes ====<br />
<br />
[[Image:Local-express.png|thumb|right|450px|A local-express lane configuration on I-96 in Livonia, Michigan]]<br />
<br />
Local-express lanes are similar to collector/distributor interchange, but on a larger scale. While collector/distributor interchanges typically have an exit number or numbers, local-express lanes typically share the same name, differentiated by "Local" for the collector/distributor lanes and "Express" for the thru lanes.<br />
<br />
A local-express lane configuration is not technically an "interchange"; however, since its physical characteristics are similar to those of a complex collector/distributor interchange, it is discussed here.<br />
<br />
Where collector/distributor lanes are used as part of a local-express lane configuration,<br />
*use the same type (most likely {{Freeway}}) for the Local lanes as is used for the Express lanes, and<br />
*name the road as it is signed: typically "[Name] Local [Direction]": for example, "I-96 Local W" (and "I-96 Express W" for the Express lanes).<br />
<br />
{{clear}}<br />
<br />
=== {{Anchor| <br />
Diverging diamond interchange|Diverging_diamond_interchange|DDI}}Diverging diamond interchange (DDI) ===<br />
<br />
''See also:'' [[Wikipedia:Diverging_diamond_interchange|Diverging Diamond Interchange]] article on Wikipedia.<br />
[[File:DDI Example Dupont.png|thumb|845x845px|none]]<br />
Diverging diamond interchanges (DDI) are a type of diamond interchange in which the two directions of traffic cross one another on each side of a limited-access roadway. A DDI may pass over or under the limited-access roadway.<br />
<br />
This type of interchange is unusual, in that it requires traffic to briefly drive on the opposite side of the road from what is customary for the jurisdiction. However, the design of the Diverging Diamond Interchange controls the driver's line of sight to ensure the cross-over action feels natural and goes unnoticed.<br />
<br />
==== Segment directionality ====<br />
[[File:DDI Example Dupont - traffic flow.png|thumb|848x848px|Flow of traffic within a Diverging Diamond Interchange|none]]<br />
All ramp and surface street segments are set as one-way. If you are creating a DDI along a road which is not divided, divide the road, first. {{Details|Best map_editing_practice#Dividing_and_un-dividing_divided_highways{{!}}Best map editing practice § Dividing and un-dividing divided highways|how to properly divide/un-divide a road}}<br />
==== At-grade intersections ====<br />
<br />
===== Junctions =====<br />
<br />
As with all at-grade intersections in Waze, all DDI at-grade intersections are modeled with junction nodes, ''including'' the two signaled intersections where opposing directions of traffic "cross over" each other (inner surface road junctions). A DDI may also have two outer surface road junctions, where the one-way segments transition to two-way road segments.<br />
<br />
===== Turn restrictions =====<br />
<br />
====== Overview ======<br />
There are four junctions in a DDI at which the turn restrictions must be checked - two inner surface road junctions where traffic crosses, and two outer surface road junctions where the road divides/joins on each side of the DDI.[[File:DDI Example Dupont - turn restrictions.png|thumb|871x871px|All restricted turns within a DDI (displayed by using Shift+Z).|none]]<br />
<br />
====== Inner surface road junctions ======<br />
[[File:DDI Example Dupont - turn restrictions - inner - 01.png|none|thumb|871x871px]]<br />
[[File:DDI Example Dupont - turn restrictions - outer - 02.png|none|thumb|870x870px]]Disable the ''two'' turns from one-way segments to the segments carrying traffic the ''opposite'' direction at both inner surface road intersections, for a total of four disabled turns. <br />
<br />
====== Outer surface road junctions ======<br />
[[File:DDI Example Dupont - turn restrictions - outer.png|none|thumb|871x871px]]<br />
Disable the ''single'' turn from the one-way segment carrying traffic ''exiting'' the DDI to the one-way segment carrying traffic ''entering'' the DDI at both outer surface road intersections, for a total of two disabled turns.<br />
<br />
== See also ==<br />
<br />
Review the [[Wikipedia:Interchange_(road)|Wikipedia article on Road Interchanges]] for further information on this topic.<br />
<br />
{{ReturnTo | Junction_Style_Guide | the Junction Style Guide}}<br />
[[Category:Style Guide]]</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=Junction_Style_Guide/Interchange&diff=159160Junction Style Guide/Interchange2017-07-16T16:32:55Z<p>Qwaletee: /* Diverging diamond interchange (DDI) */ ANd DDI</p>
<hr />
<div>{{ReturnTo | Junction_Style_Guide | the Junction Style Guide}}<br />
<br />
An '''interchange''' is a road junction where two roads are connected by dedicated roadways, called '''ramps'''. The roads connected by an interchange do not intersect one another directly, and if they cross, the crossing is grade-separated.<br />
<br />
Since interchanges often involve grade-separated crossings, the [[road elevation]] of the segments becomes important. If two roads cross without connecting directly, their elevations must be different.<br />
<br />
This article is a sub-article of the [[Junction Style Guide]]. As such, '''this article is a Style Guide''' as well. The following sections discuss the proper style for ramps, interchanges, and some common Interchange designs. Note that some interchanges may be a hybrid of these basic designs where one side or quadrant of the interchange may differ from the others.<br />
<br />
Before reading through this article, be sure to fully understand the information in the [[Junction Style Guide]].<br />
<br />
== Ramps ==<br />
<br />
Ramps have a very specific purpose in Waze. They are intended to connect segments of Minor Highways, Major Highways, and Freeways to roads where there are no at-grade crossings.<br />
<br />
The {{Ramp}} type is used extensively in interchanges for three reasons.<br />
* Ramp segment names are not displayed on the map.<br />
* Ramp segments have essentially no penalty, so they can be used to connect Freeways and Major Highways with each other without causing problems.<br />
* Ramp segments are relatively small but show at high zoom levels, so interchanges do not distract from highways but can be seen at high speeds.<br />
<br />
=== When to use ramps ===<br />
<br />
Use of the {{Ramp}} type is governed by the following rules:<br />
* [[Road types]]<br />
* [[At-grade connectors]]<br />
<br />
=== Ramp geometry and complexity ===<br />
<br />
When placing the beginning of a ramp, place the first [[geometry node]] of the ramp segment at the point where the solid white line begins, and extend the ramp naturally to create a junction with the road segment, typically at a 10–15° angle. This will allow for consistent timing of exit instructions.<br />
<br />
: [[Image:Exit-ramp-geom.png]]<br />
<br />
Do the same when placing the end of a ramp. This will allow for consistent auto-zoom functionality—the client remains zoomed in for the duration of the ramp, zooming out when the user gets on the freeway.<br />
<br />
: [[Image:Entrance-ramp-geom.png]]<br />
<br />
Rule #1 is still simpler is better. If there is no large distance between paths at the end of a ramp (either into or out of the ramp), a single segment connecting to a single junction node is all that is needed. The existence of a painted, concrete, or grass island is '''NOT''' enough of a reason to divide a ramp into multiple ramps.<br />
<br />
: [[Image:Jct_ramp_no_split.png]]<br />
<br />
When paths at the end of the ramp deviate significantly in distance, regardless of the existence of any type of island, then multiple ramps should be used.<br />
<br />
: [[Image:Jct_ramp_split.png]]<br />
<br />
== Interchange types ==<br />
These are junctions involving the three Highway/Freeway road types - {{Minor Highway}}, {{Major Highway}}, and {{Freeway}} -- as well as their {{Ramp|Ramps}}.<br />
<br />
Specific examples of how to handle common junction types are provided in later sections. All of those examples use the basic building blocks provided here.<br />
<br />
If you are unsure what road type you should use, refer to the '''[[road types]]''' article.<br />
<br />
=== Exits ===<br />
It is a basic Exit situation when a "straight" direction is obvious to a driver and navigation instructions are only needed for the non-straight direction (the exit.) If navigation instructions are required for both directions, see the [[#Wayfinders|Wayfinders]] section below.<br />
<br />
==== Exit geometry ====<br />
: [[Image:Jct_fwy_exit.png]] [[Image:Jct_maj_exit.png]] [[Image:Jct_min_exit.png]]<br />
<br />
To be treated as a basic Exit, the following must be true:<br />
# The entering segment and the continuing segment must be {{Freeway}}, {{Major Highway}}, or {{Minor Highway}} type,<br />
# The Freeway/Highway continuing segment should have close to a zero degree departure angle from the entering segment,<br />
# The other exiting segment must be of the type {{Ramp}}, and<br />
# The Ramp exiting segment should have a departure angle around 10–15 degrees from the entering segment, as explained above.<br />
<br />
When those conditions are met, the navigation will present an "Exit Right/Left" instruction when the ramp is to be used, and will remain silent when the continuing Freeway/Highway segment is to be used.<br />
<br />
==== Exit naming ====<br />
The Highway/Freeway segments before and after the junction should be named the same. The ramp segments should be named in accordance with the best practices in your location.<br />
<br />
[[Road names#Exit_ramps_and_Entrance_ramps_.28on-ramps.29|US Specific Ramp Names]]<br />
<br />
[[Road types and names|Naming standards for other areas]]<br />
<br />
Editors covering areas that do not have specific best practices should review the existing guides for other areas, and determine which best matches the roadways of your area.<br />
<br />
=== {{anchor|Freeway/highway splits}} Freeway/highway forks===<br />
A Highway/Freeway Fork is when a Highway/Freeway segment meets at a junction with two other Highway/Freeway segments and there is no obvious straight through direction to a driver. This is synonymous with the MUTCD term "split".<br />
<br />
==== {{anchor|Freeway split geometry}}Freeway fork geometry ====<br />
: [[Image:Jct_fwy_fwy_split.png]]<br />
<br />
To receive a navigation instruction for '''both''' branches of a fork, the following must be true:<br />
# Both exiting segments must be the same type (Freeway, Major Highway, Minor Highway).<br />
# Each exiting segment must have a name which is different from the name of the entering segment.<br />
# The two exiting segments should have departure angles around 10 to 15 degrees from the entering segment.<br />
<br />
With those conditions met, the junction will present "stay to the left" and "stay to the right" navigation instructions using the name of the appropriate exiting segment.<br />
<br />
==== {{anchor|Freeway split naming}}Freeway fork naming====<br />
<br />
The primary rule is that all 3 segments at the junction must have different names. That can be accomplished in one of two ways:<br />
# Using road names alone - It is an easy situation if all three roads which connect have different names. If "Highway A" forks into "Highway B" and "Highway C", then that is all we need to have a properly functioning fork.<br />
# Using signs and [[#Wayfinders|Wayfinder Segments]] - If one of the branches of the fork has the same name as the entering segment, we must create uniqueness at the junction. If "Highway X" forks off from "Highway Y" and "Highway X" continues as the other branch, the preferred approach is to use named [[#Wayfinders|Wayfinder Segments]].<br />
<br />
=== Wayfinders ===<br />
<br />
A '''wayfinder''' gives a user an instruction directing them how to continue on the road the user is already on, in situations where it may be unclear, and there would otherwise be no instruction.<br />
<br />
<br />
==== Terminology ====<br />
<br />
A '''travel lane''' is a lane which is long enough that a naïve driver might consider it a long-distance lane. For our purposes we will clarify this as any lane which;<br />
#before nearing the exit, is neither striped nor signed as a departing lane over a significant length (approximately ¾ a mile, or its full length, whichever is shorter), and<br />
#has not just started within a mile before the exit.<br />
<br />
The '''typical side''' for an exit depends on the traffic side for that country. In a country with [[Right-hand traffic]] i.e. the USA, the typical side for an exit is the right side.<br />
<br />
The '''atypical side''' for an exit is the opposite of the typical side described above.<br />
<br />
A '''continuation path''' or '''continuation''' is the group of lanes after the fork which continue to be the same road as it was before the fork. (In the following example, the lanes which continue to be I-47)<br />
<br />
[[File:Lane definitions.png|400px|thumbnail|center]]<br />
{{clear}}<br />
<br />
==== Criteria ====<br />
<br />
A wayfinder is warranted in the following cases:<br />
*The continuation path on a controlled-access highway or freeway, when an exit is present on the typical side, has at least two fewer ''travel lanes'' after the exit than before it;<br />
*The continuation path on a controlled-access highway or freeway has the same number of lanes as, or fewer lanes than, the exit path after the fork;<br />
*The continuation path on an uncontrolled highway, or when an exit is present on the atypical side of a controlled-access highway or freeway, has at least one fewer ''travel lane'' after the exit than before it;<br />
*The continuation path consists of a single lane; or<br />
*Other conditions exist that may suggest a fork, rather than an exit (use your better judgement, and discretion) -- for example:<br />
**The physical roadway itself forks or diverges with no clear straight-ahead direction;<br />
**The road which appears to be straight ahead is not the actual continuation;<br />
**Signage and striping do not clearly provide all expected "exit" indications, or do so inconsistently; or<br />
**Signs are present with arrows pointing left and right but no sign clearly establishes the continuation.<br />
<br />
<br />
{{NeedImage| Need sample images for "lane drops" and "non-obvious continuations"; also, example of BGS with lane arrows}}<br />
<br />
[[File:FreewayS-inS-out.png|200px|right]]<br />
In these cases, we need to use a wayfinder configuration. Each wayfinder configuration will have one "IN" segment and two "OUT" segments.<br />
<br />
==== Configuration ====<br />
<br />
These configurations have been designed based on a very in-depth understanding of [[How_Waze_determines_turn_/_keep_/_exit_maneuvers|Waze's standard rules for generating instructions]]. Please don't deviate from these precise configurations.<br />
<br />
* Each "stub" segment should be {{:Segment length/Minimum}} long. This is long enough so it will not cause routing problems, but it is short enough to suppress display of the names (on Freeway stubs) and keep freeways looking contiguous (on Ramp stubs).<br />
* The OUT segments should have a ''turn angle'' of 10°-20° off of the mid-line on opposite sides of each other, consistent with [[Junction_Style_Guide/Interchanges#Freeway_split_geometry|the geometry for freeway forks]]. This will allow for easy identification in WME, but still look seamless in the client app.<br />
<br />
<br />
To configure the wayfinder, <br />
* If the numbered/signed exit is on the '''right''', the OUT segments should be {{Ramp}} type. This will give an "exit right" instruction for the exit and a "stay to the left" instruction for the continuation. <br />
** For a basic [[Junction Style Guide/Interchanges#Exits|exit]], use a named Ramp stub for the continuation, and a standard Ramp for the exit.<br />
** For a [[Junction Style Guide/Interchanges#Freeway.2Fhighway splits|freeway fork]], use a Ramp stub on both sides.<br />
* If the numbered/signed exit is on the '''left''', the OUT segments type should be the same as {{Road|style=background-color: #fbe73f;|the IN segment}}, in the following examples we will use the {{Freeway}} type. This will give "stay to the" instructions on both sides (if {{Ramp}} segments were used, Waze would give a confusing "exit right" instruction for the continuation).<br />
** For a basic [[Junction Style Guide/Interchanges#Exits|exit]], use a named Freeway stub for the continuation, and an unnamed Freeway stub followed by a named Ramp for the exit.<br />
** For a [[Junction Style Guide/Interchanges#Freeway.2Fhighway splits|freeway fork]], use named Freeway stubs on both sides.<br />
<br />
<div style="font-size:smaller"><br />
{| class="wikitable" style="text-align:center"<br />
|-<br />
! Exit direction<br />
! Type<br />
! Left OUT configuration<br />
! Right OUT configuration<br />
! Example<br />
|-<br />
| Right<br />
| Basic exit<br />
| '''Continuation side'''<br/>{{Ramp|Named Ramp stub}} → {{Freeway|Named Fwy}}<br />
| '''Exit side'''<br/>{{Ramp|Named Ramp}}<br />
| [[File:RightExitRamp.png|191px]]<br />
|-<br />
| Right<br />
| Fwy fork<br />
| '''Continuation side'''<br/>{{Ramp|Named Ramp stub}} → {{Freeway|Named Fwy}}<br />
| '''Exit side'''<br/>{{Ramp|Named Ramp stub}} → {{Freeway|Named Fwy}}<br />
| [[File:RightExitSplit.png|191px]]<br />
|-<br />
| Left<br />
| Basic exit<br />
| '''Exit side'''<br/>{{Freeway|Unnamed Fwy stub}} → {{Ramp|Named Ramp}}<br />
| '''Continuation side'''<br/>{{Freeway|Named Fwy stub}} → {{Freeway|Named Fwy}}<br />
| [[File:LeftExitRamp.png|189px]]<br />
|-<br />
| Left<br />
| Fwy fork<br />
| '''Exit side'''<br/>{{Freeway|Named Fwy stub}} → {{Freeway|Named Fwy}}<br />
| '''Continuation side'''<br/>{{Freeway|Named Fwy stub}} → {{Freeway|Named Fwy}}<br />
| [[File:LeftExitSplit.png|191px]]<br />
|}<br />
</div><br />
<br />
==== Segment naming ====<br />
Keep these basic principles in mind:<br />
* The OUT segments must both be the same type (either {{Freeway}}, {{Major Highway}}, {{Minor Highway}}, or {{Ramp}}, as explained below).<br />
* Each OUT segment must have a name different than the IN segment.<br />
** '''NOTE:''' An unnamed segment (no-name box checked) is considered to have a blank name, and not the inherited name for these purposes. Therefore either both OUTs must be no-name, or both must have their own unique name.<br />
* OUT segments should be named with the information displayed on the roadway signs.<br />
** However, if this would leave an OUT segment with the same name as the IN segment, the OUT segment should be left unnamed (i.e., check the "no name" box).<br />
<br />
{{mbox|type=important|text=Previously in these situations segment naming was modified in one of the following ways {{u|''in order of preference''}}:<br />
#Add a control/destination city, if it is known, to the OUT segment name.<br />
#Remove the compass cardinal from the OUT segment name.<br />
#Add a space to the end of the OUT segment name (note that this will be flagged by the [[Community_Plugins,_Extensions_and_Tools#WME_Validator|WME Validator script]], if active, and possibly result in undoing by another editor)<br />
#Create a stub in the IN segment just before the junction with no street name.<br />
#*'''NOTE:''' This option should only be used as a last resort because it prevents the [[Routing_server|routing server]] from properly calculating [[Turn delays|turn delays]], and may result in inefficient routing through the area.<br />
<br />
If you see any of these set-ups, please correct it to one of the two proper methods listed above.}}<br />
<br />
If the continuation is '''signed''', and a wayfinder is warranted,<br />
* If the continuation sign contains the name or shield of the continuing road, do '''not''' use "to" at the beginning of the name of the OUT segment. e.g., a freeway fork where one side is the continuation of the same freeway (the user is already on the road, not going "to" it). Most wayfinders will fit this criterion.<br />
**If the name of the continuation is included but is not listed first on the sign, move the name of the continuing road to the beginning of the segment name. (e.g. In this wayfinder the highway you are on now, and continuing on is I-275, so the segment name should be "I-275 N / I-74 E / US-52 E / Cincinnati".)<br />
* If the continuation sign '''does not contain''' the name or shield of the continuing road, then the road name should begin with "to".<br />
<br />
<br />
If the word "TO" is explicitly included on the continuation sign,<br />
* [[File:Wayfinder To BGS.png|300px|thumbnail|right]]Move the shields or names affected by the "TO" to the end of the segment name after a slash (/). (The example BGS shown is for the continuation of I-80, which leads to I-280, with a control city Morristown.)<br />
** If any included control cities or road names correlate only to the roads affected by the "TO", then those control cities or road names should be moved after the "/ to [road(s)] /" on the segment name.<br />
*** [[File:Wayfinder To WME.png|300px|thumbnail|right]] If Morristown is served by I-280 and ''not'' by I-80, the continuation segment should be '''"I-80 / to I-280 / Morristown"'''.<br />
** If any included control cities or road names correlate to the roads '''not''' affected by the "TO", then those control cities or road names should remain in place before "/ to [road(s)]".<br />
*** If Morristown is served by I-80, the continuation segment should be named '''"I-80 / Morristown / to I-280"'''.{{clear}}<br />
<br />
<br />
If the continuation is '''not signed''', and a wayfinder is warranted,<br />
* If the OUT segment is a continuation of the same road, it should be left unnamed (check the "no name" box).<br />
* If the OUT segment is an exit, it should be named following the guidelines for an unsigned exit.<br />
* If the OUT segment is a short continuation of the same road leading to another road, name the segment starting with "to" followed by the name of the road to which the continuation leads, following these guidelines:<br />
** {{anchor|no BGS to}}[[File:No BGS To exit.PNG|300px|thumbnail|right]]Where the wayfinder is just before, but not at, the termination of a road, so the continuation OUT segment is named for the road that the continuation leads to at the termination. However you still must travel for a short distance on the continuation of this road until those exits/termination. [[File:No BGS To exit zoom out.PNG|300px|thumbnail|right]]Our example here is a wayfinder on US-1-9 N (Truck), the left OUT is the continuation, however the right OUT also continues on the same road until it intersects with SR-440, with an exit to SR-440 S along this short segment. There are no roadway signs for any of these forks, or exits/terminations. The OUT segment here would be named '''"to SR-440 S / Communipaw Ave"''', and the SR-440 exit will be named following the [[Road_names#Exit_ramps_and_entrance_ramps_.28on-ramps.29|unsigned exit guidelines]]. However it may be appropriate (if there are no House Numbers, or other on ramps past this wayfinder before it reaches the exit, to leave this entire portion with no name, and the instruction will inherit the name of the next road to which you are going.{{clear}}<br />
<br />
<br />
Wayfinder naming examples<br />
<div style="font-size:smaller"><br />
{| class="wikitable" style="text-align:center"<br />
|-<br />
! #<br />
! Continuation sign<br />
! Continuing road name<br />
! Rule<br />
! Waze road name<br />
|-<br />
| colspan="3" | [[File:Wayfinder I-10 BGS.png|225px|thumbnail|center]]<br />
| [[File:Wayfinder I-10 WME.png|225px|thumbnail|center]]<br />
| context image<br />
|-<br />
| 1<br />
| I-10 E / New Orleans Business District<br />
| I-10 E<br />
| Matches - do not use "to"<br />
| '''I-10 E / New Orleans Business District'''<br />
|-<br />
! #<br />
! Continuation sign<br />
! Continuing road name<br />
! Rule<br />
! Waze road name<br />
|-<br />
| colspan="3" | [[File:Wayfinder continuation TO I-71.png|225px|thumbnail|center]]<br />
| [[File:Wayfinder 471 close.png|225px|thumbnail|center]]<br />
| [[File:Wayfinder 471 context.png|225px|thumbnail|center]]<br />
|-<br />
| 2<br />
| I-71 N / Columbus<br />
| I-471 N<br />
| Does not match – use "to"<br />
| '''to I-71 N / Columbus'''<br />
|-<br />
! #<br />
! Continuation sign<br />
! Continuing road name<br />
! Rule<br />
! Waze road name<br />
|-<br />
| colspan="3" | [[File:Wayfinder continue last BGS.png|225px|thumbnail|center]]<br />
| [[File:Wayfinder 275 closeup.png|225px|thumbnail|center]]<br />
| [[File:Wayfinder continue last WME.png|225px|thumbnail|center]]<br />
|-<br />
| 3<br />
| I-74 E / US-52 E / I-275 N / Cincinnati<br />
| I-275 N<br />
| Included but not first – move to beginning<br />
| '''I-275 N / I-74 E / US-52 E / Cincinnati'''<br />
|-<br />
! #<br />
! Continuation sign<br />
! Continuing road name<br />
! Rule<br />
! Waze road name<br />
|-<br />
| colspan="3" | BGS image<br />
| WME image<br />
| context image<br />
|-<br />
| 4<br />
|<br />
|<br />
|<br />
| '''name'''<br />
|-<br />
! #<br />
! Continuation sign<br />
! Continuing road name<br />
! Rule<br />
! Waze road name<br />
|-<br />
| colspan="3" | image<br />
| image<br />
| image<br />
|-<br />
| 5<br />
|<br />
|<br />
|<br />
| '''name'''<br />
|}<br />
</div><br />
<br />
=== Ramp-ramp forks ===<br />
A ramp may itself fork and branch into two directions. If this is the case, "Exit Right" and "Exit Left" will be announced using the name of the appropriate exiting segment in all cases.<br />
<br />
==== Ramp fork geometry ====<br />
: [[Image:Jct_ramp_ramp_split.png]]<br />
<br />
==== Ramp fork naming ====<br />
If ramps are unnamed, the name of a subsequent ramp will propagate backwards. In the example above, if the two ramps exiting the junction are named, the ramp entering the junction can be left unnamed. Then any navigation instruction directing you onto the first ramp would use the name of the appropriate exiting ramp.<br />
<br />
'''Example:''' The two ramps exiting the junction are named "DestinationLeft" and "DestinationRight". The ramp that enters the junction is unnamed. If you need to "Exit Right" onto the unnamed ramp. If you are headed to "DestinationLeft", navigation would tell you:<br />
* Exit Right to Destination Left<br />
* Keep Left to Destination Left<br />
<br />
Using unnamed ramps is very useful to provide sufficient notification of an approaching decision point, as long as the names of both ramp forks are visible on signs at the start of the initial ramp.<br />
<br />
'''Example of good use of unnamed ramps:'''<br />
* Initial Exit Sign: to City A and City B<br />
* Destination Left Sign: to City A<br />
* Destination Right Sign: to City B<br />
Result: An unnamed initial ramp will provide accurate and informative navigation instructions to the driver.<br />
<br />
'''Example of poor use of unnamed ramps:'''<br />
* Initial Exit Sign: to Downtown<br />
* Destination Left Sign: to Downtown<br />
* Destination Right Sign: to Center St<br />
Result: An unnamed ramp may create confusion, since both destination ramp names are NOT listed on the initial exit sign. In this case, the initial ramp should be named.<br />
<br />
'''Example of modified use of unnamed ramps:'''<br />
<br />
* Initial Exit Sign: Exit 70A-B to City A and City B<br />
* Destination Left Sign: to City A<br />
* Destination Right Sign: to City B<br />
* Destination Left name in Waze: Exit 70A: City A<br />
* Destination Right name in Waze: Exit 70B: City B<br />
Result: By using a modified name for the destination ramps, we have combined information from two sets of signs to generate the advance notice a driver may need to prepare for a decision point.<br />
<br />
== Interchange configurations ==<br />
<br />
<br />
=== Diamond interchange ===<br />
: [[Image:Jct_diamond.png]]<br />
''See also: [[Wikipedia:Diamond_interchange|Diamond Interchange article on Wikipedia]]''<br />
<br />
Common in wide open spaces where land acquisition and geography are not concerns, this Interchange design has ramps equally distributed across all 4 quadrants.<br />
<br />
In the simplest form, this can be represented as single connections from the ramps to the surface street. <br />
<br />
The straight through motion from the exit ramp to the entrance ramp should typically be enabled, if legal to drive. Under normal circumstances, the Big Detour Prevention mechanism discourages the routing server from routing someone off the freeway and directly back on. When the freeway path between the ramps is closed, or slow enough to overcome the Detour penalty, this off-on route may be given as a desirable alternative.<br />
<br />
Be aware that the Big Detour Prevention penalty is intended to discourage routing that leaves a freeway (or highway) and returns to the same freeway (or highway). Therefore, at least one name (primary or alternate) of the freeway/highway segment before the exit ramp must exactly match one name (primary or alternate) of the freeway/highway segment after the entrance ramp to trigger the penalty. For further information see the [[Detour Prevention Mechanisms|Big Detour Prevention Mechanism]] page.<br />
<br />
:[[Image:Jct_diamond_simple_turns_new.png]]<br />
<br />
If the ramps connect to the surface street at multiple points, restrict turns which should use another ramp. Review the section on [[Junction Style Guide/Interchanges#Ramp geometry and complexity|ramp geometry and complexity]] for more details on this topic. <br />
<br />
First we see the turns that must be restricted for the exit ramps:<br />
<br />
: [[Image:Jct_diamond_cplx_turns_off_L_new.png]] [[Image:Jct_diamond_cplx_turns_off_R.png]]<br />
<br />
Then we see what must be restricted for the entrance ramps:<br />
<br />
: [[Image:Jct_diamond_cplx_turns_on.png]]<br />
<br />
'''Note on elevations:'''<br />
The single surface street segment between the inner most ramps should be either raised or lowered in relation to the freeway segments depending on the actual geography at the interchange.<br />
<br />
=== Cloverleaf interchange ===<br />
: [[Image:Jct_cloverleaf.png]]<br />
<br />
''See also: [[wikipedia:Cloverleaf_interchange|Cloverleaf Interchange article on Wikipedia]]''<br />
<br />
In a Cloverleaf Interchange, left turns are eliminated from all movements between the Freeway and the surface street. First check the exit ramps.<br />
<br />
: [[Image:Jct_cloverleaf_off_outer_turns.png]] [[Image:Jct_cloverleaf_off_inner_turns.png]]<br />
<br />
Then check the entrance ramps for illegal turns.<br />
<br />
: [[Image:Jct_cloverleaf_on_turns.png]]<br />
<br />
The connections to the Freeway segments may be treated in two ways:<br />
<br />
:[[Image:Jct_cloverleaf_options.png]]<br />
<br />
# (top) we can have the inner entrance and exit ramps have their own junction nodes with the Freeway. Do '''NOT''' use this approach if there are [[#Collector.2FDistributor_Lanes|Collector/Distributor Lanes]] (or a similar situation) involved.<br />
# (bottom) we can have the entrance and exit ramps share a single junction node with the Freeway. This allows us to eliminate the very short Freeway segment that may exist between the inner entrance and exit ramps.<br />It is best to offset this shared junction onto the Entrance ramp side of the surface street. This prevents the junction from accidentally being connected to the surface street or looking like it does. We favor the Entrance ramp side, because this would result in a slightly earlier exit instruction which is, of course, preferred over a late exit instruction. <br />
<br />
The determining factor of which design to use will partly depend on the actual size and scale of the specific interchange and if there is a [[#Collector.2FDistributor_Lanes|Collector/Distributor]] involved.<br />
<br />
'''Note on Elevation:'''<br />
The single surface street segment between the inner most ramps should be either raised or lowered in relation to the freeway segments depending on the actual geography at the interchange.<br />
<br />
=== Folded diamond interchange ===<br />
: [[Image:Jct_folded_diamond.png]]<br />
''See also: Discussion of Folded Diamonds and A2/B2 Partial Cloverleafs on the [[wikipedia:Partial_cloverleaf_interchange|Partial Cloverleaf Interchange article on Wikipedia]]''<br />
<br />
Geography or property ownership may prevent the ability for an interchange to be constructed with all ramps evenly distributed across the 4 quadrants of the interchange. When only two quadrants are used, it is typically called a Folded Diamond (basically a sub-type of a Partial Cloverleaf Interchange). The ramps may be all on one side (as in the examples in this section) or they may be located in diagonally opposed quadrants.<br />
<br />
The unique situation presented by the Folded Diamond arrangement is having both Entrance and Exit ramps terminating on the same side of the surface street. Ideally both ramps should terminate on the same junction node to permit us to easily restrict the illegal and usually impossible ramp-to-ramp movement.<br />
<br />
: [[Image:Jct_folded_diamond_u-turn.png]]'<br />
<br />
Like with a basic Diamond Interchange, often it will be necessary to represent the ramps making multiple connections to the surface street. Be sure to read the article [[Junction_Style_Guide#Simple_is_better|Simple is better]] in the Junction Style Guide. <br />
<br />
Restrict all non-permitted turns.<br />
<br />
: [[Image:Jct_folded_diamond_off_turns_L.png]] [[Image:Jct_folded_diamond_off_turns_R.png]] [[Image:Jct_folded_diamond_on_turns.png]]<br />
<br />
'''Note on Elevation:''' Similar to a basic Diamond interchange, in most cases only the segment of the surface street that crosses the Freeway segments will need to be adjusted up or down.<br />
<br />
=== Single-point urban interchange (SPUI) ===<br />
: [[Image:Jct_SPUI.png]]<br />
''See also: [[wikipedia:Single-point_urban_interchange|Single Point Urban Interchange article on Wikipedia]]''<br />
<br />
A SPUI is a very space and flow efficient design, but it takes extra attention to ensure the turns are correct. And as the name indicates, ideally there should be a single junction in the center. You may need to tweak the geometry of segments a bit off of alignment from the real physical world, but it should be minor if the interchange is a true SPUI.<br />
<br />
The outer branches of the exit ramps are similar to a diamond interchange and ramp to ramp routing should be enabled if possible and legal. However, in many SPUIs such ramp to ramp routing is not possible:<br />
<br />
: [[Image:Jct_SPUI_off_outer_turn.png]]<br />
<br />
Where things get complicated is the inner branches leading to the Single Point. You need to avoid ramp-to-ramp in two directions and a reverse flow turn. '''Note:''' The ramp-to-ramp motion to facilitate a U-Turn (the top left arrow in the image below) may or may not be allowed depending on the specific interchange. Please validate this turn.<br />
<br />
: [[Image:Jct_SPUI_off_inner_turn.png]]<br />
<br />
Luckily the entrance ramp restrictions are similar to the diamond interchange:<br />
<br />
: [[Image:Jct_SPUI_on_turn.png]]<br />
<br />
If you were to look at all the restricted turns at once, you may get the false impression that something is very wrong. But as you now know, a SPUI has almost as many restricted turns as allowed ones.<br />
<br />
: [[Image:Jct_SPUI_all_turns.png]]<br />
<br />
'''Note on Elevation:'''<br />
The two surface street segments (between the outer ramps and connected to the Single Point) and the 4 ramp segments connected to the single point should all be the same level, either one higher or one lower than the elevation of the freeway segments above/below the single point.<br />
<br />
=== Collector/Distributor Lanes ===<br />
<br />
These are lanes parallel to, but physically separated from, the lanes of a Freeway that serve to keep merging traffic out of the flow of through traffic on the mainline Freeway.<br />
<br />
Collector/distributor lanes serve as either:<br />
* some of the ramps in an '''interchange''', or<br />
* local lanes in configurations with '''[[wikipedia:local-express lanes|local-express lanes]]'''.<br />
<br />
<br />
==== Collector/distributor interchanges ====<br />
<br />
Some interchange configurations make use of collector/distributor lanes to separate lower-speed merging traffic from high-speed through traffic. This is often used in cloverleaf interchanges and in groups of nearby exits.<br />
<br />
===== Collector/distributor cloverleaf =====<br />
<br />
This is a cloverleaf interchange that is connected to a collector/distributor instead of directly to the main roadway. Map collector-distributor cloverleaf ramps as you would any other ramp.<br />
<br />
[[Image:Jct_fc_cloverleaf_bad.png]]<br />
<br />
The [[Detour Prevention Mechanisms|detour prevention mechanism]] will discourage Waze from routing users onto the collector-distributor and back onto the freeway – as long as the city name on the freeway is the same (or set to "no city") before, throughout, and after the collector-distributor. Previously this feature was not available and the ramps were set up to restrict the through route. Some of these ramp configurations may still be set up that way, so they can now be configured as pictured above with the through route enabled.<br />
<br />
==== Complex collector/distributor interchanges ====<br />
<br />
[[Image:Collector-distributor-exit.png|thumb|right|450px|Collector-distributor lanes used in an interchange on I-81 in Christiansburg, Virginia (Exits 118A-B-C)]]<br />
<br />
Where collector/distributor lanes are used as part of an interchange, use the {{Ramp}} type for the collector/distributor lanes. Name the ramp segments as you would any other ramp segment.<br />
<br />
Ensure that a name on the Freeway segments is consistent before and after the collector/distributor lanes, so that the [[Detour Prevention Mechanisms|detour prevention mechanism]] will prevent Waze from routing users erroneously.<br />
<br />
{{clear}}<br />
<br />
==== Local-express lanes ====<br />
<br />
[[Image:Local-express.png|thumb|right|450px|A local-express lane configuration on I-96 in Livonia, Michigan]]<br />
<br />
Local-express lanes are similar to collector/distributor interchange, but on a larger scale. While collector/distributor interchanges typically have an exit number or numbers, local-express lanes typically share the same name, differentiated by "Local" for the collector/distributor lanes and "Express" for the thru lanes.<br />
<br />
A local-express lane configuration is not technically an "interchange"; however, since its physical characteristics are similar to those of a complex collector/distributor interchange, it is discussed here.<br />
<br />
Where collector/distributor lanes are used as part of a local-express lane configuration,<br />
*use the same type (most likely {{Freeway}}) for the Local lanes as is used for the Express lanes, and<br />
*name the road as it is signed: typically "[Name] Local [Direction]": for example, "I-96 Local W" (and "I-96 Express W" for the Express lanes).<br />
<br />
{{clear}}<br />
<br />
=== {{Anchor| Diverging diamond interchange|DDI}}Diverging diamond interchange (DDI) ===<br />
<br />
''See also:'' [[Wikipedia:Diverging_diamond_interchange|Diverging Diamond Interchange]] article on Wikipedia.<br />
[[File:DDI Example Dupont.png|thumb|845x845px|none]]<br />
Diverging diamond interchanges (DDI) are a type of diamond interchange in which the two directions of traffic cross one another on each side of a limited-access roadway. A DDI may pass over or under the limited-access roadway.<br />
<br />
This type of interchange is unusual, in that it requires traffic to briefly drive on the opposite side of the road from what is customary for the jurisdiction. However, the design of the Diverging Diamond Interchange controls the driver's line of sight to ensure the cross-over action feels natural and goes unnoticed.<br />
<br />
==== Segment directionality ====<br />
[[File:DDI Example Dupont - traffic flow.png|thumb|848x848px|Flow of traffic within a Diverging Diamond Interchange|none]]<br />
All ramp and surface street segments are set as one-way. If you are creating a DDI along a road which is not divided, divide the road, first. {{Details|Best map_editing_practice#Dividing_and_un-dividing_divided_highways{{!}}Best map editing practice § Dividing and un-dividing divided highways|how to properly divide/un-divide a road}}<br />
==== At-grade intersections ====<br />
<br />
===== Junctions =====<br />
<br />
As with all at-grade intersections in Waze, all DDI at-grade intersections are modeled with junction nodes, ''including'' the two signaled intersections where opposing directions of traffic "cross over" each other (inner surface road junctions). A DDI may also have two outer surface road junctions, where the one-way segments transition to two-way road segments.<br />
<br />
===== Turn restrictions =====<br />
<br />
====== Overview ======<br />
There are four junctions in a DDI at which the turn restrictions must be checked - two inner surface road junctions where traffic crosses, and two outer surface road junctions where the road divides/joins on each side of the DDI.[[File:DDI Example Dupont - turn restrictions.png|thumb|871x871px|All restricted turns within a DDI (displayed by using Shift+Z).|none]]<br />
<br />
====== Inner surface road junctions ======<br />
[[File:DDI Example Dupont - turn restrictions - inner - 01.png|none|thumb|871x871px]]<br />
[[File:DDI Example Dupont - turn restrictions - outer - 02.png|none|thumb|870x870px]]Disable the ''two'' turns from one-way segments to the segments carrying traffic the ''opposite'' direction at both inner surface road intersections, for a total of four disabled turns. <br />
<br />
====== Outer surface road junctions ======<br />
[[File:DDI Example Dupont - turn restrictions - outer.png|none|thumb|871x871px]]<br />
Disable the ''single'' turn from the one-way segment carrying traffic ''exiting'' the DDI to the one-way segment carrying traffic ''entering'' the DDI at both outer surface road intersections, for a total of two disabled turns.<br />
<br />
== See also ==<br />
<br />
Review the [[Wikipedia:Interchange_(road)|Wikipedia article on Road Interchanges]] for further information on this topic.<br />
<br />
{{ReturnTo | Junction_Style_Guide | the Junction Style Guide}}<br />
[[Category:Style Guide]]</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=Junction_Style_Guide/Interchange&diff=159159Junction Style Guide/Interchange2017-07-16T16:32:04Z<p>Qwaletee: /* Diverging diamond interchange (DDI) */ Anchor to old name</p>
<hr />
<div>{{ReturnTo | Junction_Style_Guide | the Junction Style Guide}}<br />
<br />
An '''interchange''' is a road junction where two roads are connected by dedicated roadways, called '''ramps'''. The roads connected by an interchange do not intersect one another directly, and if they cross, the crossing is grade-separated.<br />
<br />
Since interchanges often involve grade-separated crossings, the [[road elevation]] of the segments becomes important. If two roads cross without connecting directly, their elevations must be different.<br />
<br />
This article is a sub-article of the [[Junction Style Guide]]. As such, '''this article is a Style Guide''' as well. The following sections discuss the proper style for ramps, interchanges, and some common Interchange designs. Note that some interchanges may be a hybrid of these basic designs where one side or quadrant of the interchange may differ from the others.<br />
<br />
Before reading through this article, be sure to fully understand the information in the [[Junction Style Guide]].<br />
<br />
== Ramps ==<br />
<br />
Ramps have a very specific purpose in Waze. They are intended to connect segments of Minor Highways, Major Highways, and Freeways to roads where there are no at-grade crossings.<br />
<br />
The {{Ramp}} type is used extensively in interchanges for three reasons.<br />
* Ramp segment names are not displayed on the map.<br />
* Ramp segments have essentially no penalty, so they can be used to connect Freeways and Major Highways with each other without causing problems.<br />
* Ramp segments are relatively small but show at high zoom levels, so interchanges do not distract from highways but can be seen at high speeds.<br />
<br />
=== When to use ramps ===<br />
<br />
Use of the {{Ramp}} type is governed by the following rules:<br />
* [[Road types]]<br />
* [[At-grade connectors]]<br />
<br />
=== Ramp geometry and complexity ===<br />
<br />
When placing the beginning of a ramp, place the first [[geometry node]] of the ramp segment at the point where the solid white line begins, and extend the ramp naturally to create a junction with the road segment, typically at a 10–15° angle. This will allow for consistent timing of exit instructions.<br />
<br />
: [[Image:Exit-ramp-geom.png]]<br />
<br />
Do the same when placing the end of a ramp. This will allow for consistent auto-zoom functionality—the client remains zoomed in for the duration of the ramp, zooming out when the user gets on the freeway.<br />
<br />
: [[Image:Entrance-ramp-geom.png]]<br />
<br />
Rule #1 is still simpler is better. If there is no large distance between paths at the end of a ramp (either into or out of the ramp), a single segment connecting to a single junction node is all that is needed. The existence of a painted, concrete, or grass island is '''NOT''' enough of a reason to divide a ramp into multiple ramps.<br />
<br />
: [[Image:Jct_ramp_no_split.png]]<br />
<br />
When paths at the end of the ramp deviate significantly in distance, regardless of the existence of any type of island, then multiple ramps should be used.<br />
<br />
: [[Image:Jct_ramp_split.png]]<br />
<br />
== Interchange types ==<br />
These are junctions involving the three Highway/Freeway road types - {{Minor Highway}}, {{Major Highway}}, and {{Freeway}} -- as well as their {{Ramp|Ramps}}.<br />
<br />
Specific examples of how to handle common junction types are provided in later sections. All of those examples use the basic building blocks provided here.<br />
<br />
If you are unsure what road type you should use, refer to the '''[[road types]]''' article.<br />
<br />
=== Exits ===<br />
It is a basic Exit situation when a "straight" direction is obvious to a driver and navigation instructions are only needed for the non-straight direction (the exit.) If navigation instructions are required for both directions, see the [[#Wayfinders|Wayfinders]] section below.<br />
<br />
==== Exit geometry ====<br />
: [[Image:Jct_fwy_exit.png]] [[Image:Jct_maj_exit.png]] [[Image:Jct_min_exit.png]]<br />
<br />
To be treated as a basic Exit, the following must be true:<br />
# The entering segment and the continuing segment must be {{Freeway}}, {{Major Highway}}, or {{Minor Highway}} type,<br />
# The Freeway/Highway continuing segment should have close to a zero degree departure angle from the entering segment,<br />
# The other exiting segment must be of the type {{Ramp}}, and<br />
# The Ramp exiting segment should have a departure angle around 10–15 degrees from the entering segment, as explained above.<br />
<br />
When those conditions are met, the navigation will present an "Exit Right/Left" instruction when the ramp is to be used, and will remain silent when the continuing Freeway/Highway segment is to be used.<br />
<br />
==== Exit naming ====<br />
The Highway/Freeway segments before and after the junction should be named the same. The ramp segments should be named in accordance with the best practices in your location.<br />
<br />
[[Road names#Exit_ramps_and_Entrance_ramps_.28on-ramps.29|US Specific Ramp Names]]<br />
<br />
[[Road types and names|Naming standards for other areas]]<br />
<br />
Editors covering areas that do not have specific best practices should review the existing guides for other areas, and determine which best matches the roadways of your area.<br />
<br />
=== {{anchor|Freeway/highway splits}} Freeway/highway forks===<br />
A Highway/Freeway Fork is when a Highway/Freeway segment meets at a junction with two other Highway/Freeway segments and there is no obvious straight through direction to a driver. This is synonymous with the MUTCD term "split".<br />
<br />
==== {{anchor|Freeway split geometry}}Freeway fork geometry ====<br />
: [[Image:Jct_fwy_fwy_split.png]]<br />
<br />
To receive a navigation instruction for '''both''' branches of a fork, the following must be true:<br />
# Both exiting segments must be the same type (Freeway, Major Highway, Minor Highway).<br />
# Each exiting segment must have a name which is different from the name of the entering segment.<br />
# The two exiting segments should have departure angles around 10 to 15 degrees from the entering segment.<br />
<br />
With those conditions met, the junction will present "stay to the left" and "stay to the right" navigation instructions using the name of the appropriate exiting segment.<br />
<br />
==== {{anchor|Freeway split naming}}Freeway fork naming====<br />
<br />
The primary rule is that all 3 segments at the junction must have different names. That can be accomplished in one of two ways:<br />
# Using road names alone - It is an easy situation if all three roads which connect have different names. If "Highway A" forks into "Highway B" and "Highway C", then that is all we need to have a properly functioning fork.<br />
# Using signs and [[#Wayfinders|Wayfinder Segments]] - If one of the branches of the fork has the same name as the entering segment, we must create uniqueness at the junction. If "Highway X" forks off from "Highway Y" and "Highway X" continues as the other branch, the preferred approach is to use named [[#Wayfinders|Wayfinder Segments]].<br />
<br />
=== Wayfinders ===<br />
<br />
A '''wayfinder''' gives a user an instruction directing them how to continue on the road the user is already on, in situations where it may be unclear, and there would otherwise be no instruction.<br />
<br />
<br />
==== Terminology ====<br />
<br />
A '''travel lane''' is a lane which is long enough that a naïve driver might consider it a long-distance lane. For our purposes we will clarify this as any lane which;<br />
#before nearing the exit, is neither striped nor signed as a departing lane over a significant length (approximately ¾ a mile, or its full length, whichever is shorter), and<br />
#has not just started within a mile before the exit.<br />
<br />
The '''typical side''' for an exit depends on the traffic side for that country. In a country with [[Right-hand traffic]] i.e. the USA, the typical side for an exit is the right side.<br />
<br />
The '''atypical side''' for an exit is the opposite of the typical side described above.<br />
<br />
A '''continuation path''' or '''continuation''' is the group of lanes after the fork which continue to be the same road as it was before the fork. (In the following example, the lanes which continue to be I-47)<br />
<br />
[[File:Lane definitions.png|400px|thumbnail|center]]<br />
{{clear}}<br />
<br />
==== Criteria ====<br />
<br />
A wayfinder is warranted in the following cases:<br />
*The continuation path on a controlled-access highway or freeway, when an exit is present on the typical side, has at least two fewer ''travel lanes'' after the exit than before it;<br />
*The continuation path on a controlled-access highway or freeway has the same number of lanes as, or fewer lanes than, the exit path after the fork;<br />
*The continuation path on an uncontrolled highway, or when an exit is present on the atypical side of a controlled-access highway or freeway, has at least one fewer ''travel lane'' after the exit than before it;<br />
*The continuation path consists of a single lane; or<br />
*Other conditions exist that may suggest a fork, rather than an exit (use your better judgement, and discretion) -- for example:<br />
**The physical roadway itself forks or diverges with no clear straight-ahead direction;<br />
**The road which appears to be straight ahead is not the actual continuation;<br />
**Signage and striping do not clearly provide all expected "exit" indications, or do so inconsistently; or<br />
**Signs are present with arrows pointing left and right but no sign clearly establishes the continuation.<br />
<br />
<br />
{{NeedImage| Need sample images for "lane drops" and "non-obvious continuations"; also, example of BGS with lane arrows}}<br />
<br />
[[File:FreewayS-inS-out.png|200px|right]]<br />
In these cases, we need to use a wayfinder configuration. Each wayfinder configuration will have one "IN" segment and two "OUT" segments.<br />
<br />
==== Configuration ====<br />
<br />
These configurations have been designed based on a very in-depth understanding of [[How_Waze_determines_turn_/_keep_/_exit_maneuvers|Waze's standard rules for generating instructions]]. Please don't deviate from these precise configurations.<br />
<br />
* Each "stub" segment should be {{:Segment length/Minimum}} long. This is long enough so it will not cause routing problems, but it is short enough to suppress display of the names (on Freeway stubs) and keep freeways looking contiguous (on Ramp stubs).<br />
* The OUT segments should have a ''turn angle'' of 10°-20° off of the mid-line on opposite sides of each other, consistent with [[Junction_Style_Guide/Interchanges#Freeway_split_geometry|the geometry for freeway forks]]. This will allow for easy identification in WME, but still look seamless in the client app.<br />
<br />
<br />
To configure the wayfinder, <br />
* If the numbered/signed exit is on the '''right''', the OUT segments should be {{Ramp}} type. This will give an "exit right" instruction for the exit and a "stay to the left" instruction for the continuation. <br />
** For a basic [[Junction Style Guide/Interchanges#Exits|exit]], use a named Ramp stub for the continuation, and a standard Ramp for the exit.<br />
** For a [[Junction Style Guide/Interchanges#Freeway.2Fhighway splits|freeway fork]], use a Ramp stub on both sides.<br />
* If the numbered/signed exit is on the '''left''', the OUT segments type should be the same as {{Road|style=background-color: #fbe73f;|the IN segment}}, in the following examples we will use the {{Freeway}} type. This will give "stay to the" instructions on both sides (if {{Ramp}} segments were used, Waze would give a confusing "exit right" instruction for the continuation).<br />
** For a basic [[Junction Style Guide/Interchanges#Exits|exit]], use a named Freeway stub for the continuation, and an unnamed Freeway stub followed by a named Ramp for the exit.<br />
** For a [[Junction Style Guide/Interchanges#Freeway.2Fhighway splits|freeway fork]], use named Freeway stubs on both sides.<br />
<br />
<div style="font-size:smaller"><br />
{| class="wikitable" style="text-align:center"<br />
|-<br />
! Exit direction<br />
! Type<br />
! Left OUT configuration<br />
! Right OUT configuration<br />
! Example<br />
|-<br />
| Right<br />
| Basic exit<br />
| '''Continuation side'''<br/>{{Ramp|Named Ramp stub}} → {{Freeway|Named Fwy}}<br />
| '''Exit side'''<br/>{{Ramp|Named Ramp}}<br />
| [[File:RightExitRamp.png|191px]]<br />
|-<br />
| Right<br />
| Fwy fork<br />
| '''Continuation side'''<br/>{{Ramp|Named Ramp stub}} → {{Freeway|Named Fwy}}<br />
| '''Exit side'''<br/>{{Ramp|Named Ramp stub}} → {{Freeway|Named Fwy}}<br />
| [[File:RightExitSplit.png|191px]]<br />
|-<br />
| Left<br />
| Basic exit<br />
| '''Exit side'''<br/>{{Freeway|Unnamed Fwy stub}} → {{Ramp|Named Ramp}}<br />
| '''Continuation side'''<br/>{{Freeway|Named Fwy stub}} → {{Freeway|Named Fwy}}<br />
| [[File:LeftExitRamp.png|189px]]<br />
|-<br />
| Left<br />
| Fwy fork<br />
| '''Exit side'''<br/>{{Freeway|Named Fwy stub}} → {{Freeway|Named Fwy}}<br />
| '''Continuation side'''<br/>{{Freeway|Named Fwy stub}} → {{Freeway|Named Fwy}}<br />
| [[File:LeftExitSplit.png|191px]]<br />
|}<br />
</div><br />
<br />
==== Segment naming ====<br />
Keep these basic principles in mind:<br />
* The OUT segments must both be the same type (either {{Freeway}}, {{Major Highway}}, {{Minor Highway}}, or {{Ramp}}, as explained below).<br />
* Each OUT segment must have a name different than the IN segment.<br />
** '''NOTE:''' An unnamed segment (no-name box checked) is considered to have a blank name, and not the inherited name for these purposes. Therefore either both OUTs must be no-name, or both must have their own unique name.<br />
* OUT segments should be named with the information displayed on the roadway signs.<br />
** However, if this would leave an OUT segment with the same name as the IN segment, the OUT segment should be left unnamed (i.e., check the "no name" box).<br />
<br />
{{mbox|type=important|text=Previously in these situations segment naming was modified in one of the following ways {{u|''in order of preference''}}:<br />
#Add a control/destination city, if it is known, to the OUT segment name.<br />
#Remove the compass cardinal from the OUT segment name.<br />
#Add a space to the end of the OUT segment name (note that this will be flagged by the [[Community_Plugins,_Extensions_and_Tools#WME_Validator|WME Validator script]], if active, and possibly result in undoing by another editor)<br />
#Create a stub in the IN segment just before the junction with no street name.<br />
#*'''NOTE:''' This option should only be used as a last resort because it prevents the [[Routing_server|routing server]] from properly calculating [[Turn delays|turn delays]], and may result in inefficient routing through the area.<br />
<br />
If you see any of these set-ups, please correct it to one of the two proper methods listed above.}}<br />
<br />
If the continuation is '''signed''', and a wayfinder is warranted,<br />
* If the continuation sign contains the name or shield of the continuing road, do '''not''' use "to" at the beginning of the name of the OUT segment. e.g., a freeway fork where one side is the continuation of the same freeway (the user is already on the road, not going "to" it). Most wayfinders will fit this criterion.<br />
**If the name of the continuation is included but is not listed first on the sign, move the name of the continuing road to the beginning of the segment name. (e.g. In this wayfinder the highway you are on now, and continuing on is I-275, so the segment name should be "I-275 N / I-74 E / US-52 E / Cincinnati".)<br />
* If the continuation sign '''does not contain''' the name or shield of the continuing road, then the road name should begin with "to".<br />
<br />
<br />
If the word "TO" is explicitly included on the continuation sign,<br />
* [[File:Wayfinder To BGS.png|300px|thumbnail|right]]Move the shields or names affected by the "TO" to the end of the segment name after a slash (/). (The example BGS shown is for the continuation of I-80, which leads to I-280, with a control city Morristown.)<br />
** If any included control cities or road names correlate only to the roads affected by the "TO", then those control cities or road names should be moved after the "/ to [road(s)] /" on the segment name.<br />
*** [[File:Wayfinder To WME.png|300px|thumbnail|right]] If Morristown is served by I-280 and ''not'' by I-80, the continuation segment should be '''"I-80 / to I-280 / Morristown"'''.<br />
** If any included control cities or road names correlate to the roads '''not''' affected by the "TO", then those control cities or road names should remain in place before "/ to [road(s)]".<br />
*** If Morristown is served by I-80, the continuation segment should be named '''"I-80 / Morristown / to I-280"'''.{{clear}}<br />
<br />
<br />
If the continuation is '''not signed''', and a wayfinder is warranted,<br />
* If the OUT segment is a continuation of the same road, it should be left unnamed (check the "no name" box).<br />
* If the OUT segment is an exit, it should be named following the guidelines for an unsigned exit.<br />
* If the OUT segment is a short continuation of the same road leading to another road, name the segment starting with "to" followed by the name of the road to which the continuation leads, following these guidelines:<br />
** {{anchor|no BGS to}}[[File:No BGS To exit.PNG|300px|thumbnail|right]]Where the wayfinder is just before, but not at, the termination of a road, so the continuation OUT segment is named for the road that the continuation leads to at the termination. However you still must travel for a short distance on the continuation of this road until those exits/termination. [[File:No BGS To exit zoom out.PNG|300px|thumbnail|right]]Our example here is a wayfinder on US-1-9 N (Truck), the left OUT is the continuation, however the right OUT also continues on the same road until it intersects with SR-440, with an exit to SR-440 S along this short segment. There are no roadway signs for any of these forks, or exits/terminations. The OUT segment here would be named '''"to SR-440 S / Communipaw Ave"''', and the SR-440 exit will be named following the [[Road_names#Exit_ramps_and_entrance_ramps_.28on-ramps.29|unsigned exit guidelines]]. However it may be appropriate (if there are no House Numbers, or other on ramps past this wayfinder before it reaches the exit, to leave this entire portion with no name, and the instruction will inherit the name of the next road to which you are going.{{clear}}<br />
<br />
<br />
Wayfinder naming examples<br />
<div style="font-size:smaller"><br />
{| class="wikitable" style="text-align:center"<br />
|-<br />
! #<br />
! Continuation sign<br />
! Continuing road name<br />
! Rule<br />
! Waze road name<br />
|-<br />
| colspan="3" | [[File:Wayfinder I-10 BGS.png|225px|thumbnail|center]]<br />
| [[File:Wayfinder I-10 WME.png|225px|thumbnail|center]]<br />
| context image<br />
|-<br />
| 1<br />
| I-10 E / New Orleans Business District<br />
| I-10 E<br />
| Matches - do not use "to"<br />
| '''I-10 E / New Orleans Business District'''<br />
|-<br />
! #<br />
! Continuation sign<br />
! Continuing road name<br />
! Rule<br />
! Waze road name<br />
|-<br />
| colspan="3" | [[File:Wayfinder continuation TO I-71.png|225px|thumbnail|center]]<br />
| [[File:Wayfinder 471 close.png|225px|thumbnail|center]]<br />
| [[File:Wayfinder 471 context.png|225px|thumbnail|center]]<br />
|-<br />
| 2<br />
| I-71 N / Columbus<br />
| I-471 N<br />
| Does not match – use "to"<br />
| '''to I-71 N / Columbus'''<br />
|-<br />
! #<br />
! Continuation sign<br />
! Continuing road name<br />
! Rule<br />
! Waze road name<br />
|-<br />
| colspan="3" | [[File:Wayfinder continue last BGS.png|225px|thumbnail|center]]<br />
| [[File:Wayfinder 275 closeup.png|225px|thumbnail|center]]<br />
| [[File:Wayfinder continue last WME.png|225px|thumbnail|center]]<br />
|-<br />
| 3<br />
| I-74 E / US-52 E / I-275 N / Cincinnati<br />
| I-275 N<br />
| Included but not first – move to beginning<br />
| '''I-275 N / I-74 E / US-52 E / Cincinnati'''<br />
|-<br />
! #<br />
! Continuation sign<br />
! Continuing road name<br />
! Rule<br />
! Waze road name<br />
|-<br />
| colspan="3" | BGS image<br />
| WME image<br />
| context image<br />
|-<br />
| 4<br />
|<br />
|<br />
|<br />
| '''name'''<br />
|-<br />
! #<br />
! Continuation sign<br />
! Continuing road name<br />
! Rule<br />
! Waze road name<br />
|-<br />
| colspan="3" | image<br />
| image<br />
| image<br />
|-<br />
| 5<br />
|<br />
|<br />
|<br />
| '''name'''<br />
|}<br />
</div><br />
<br />
=== Ramp-ramp forks ===<br />
A ramp may itself fork and branch into two directions. If this is the case, "Exit Right" and "Exit Left" will be announced using the name of the appropriate exiting segment in all cases.<br />
<br />
==== Ramp fork geometry ====<br />
: [[Image:Jct_ramp_ramp_split.png]]<br />
<br />
==== Ramp fork naming ====<br />
If ramps are unnamed, the name of a subsequent ramp will propagate backwards. In the example above, if the two ramps exiting the junction are named, the ramp entering the junction can be left unnamed. Then any navigation instruction directing you onto the first ramp would use the name of the appropriate exiting ramp.<br />
<br />
'''Example:''' The two ramps exiting the junction are named "DestinationLeft" and "DestinationRight". The ramp that enters the junction is unnamed. If you need to "Exit Right" onto the unnamed ramp. If you are headed to "DestinationLeft", navigation would tell you:<br />
* Exit Right to Destination Left<br />
* Keep Left to Destination Left<br />
<br />
Using unnamed ramps is very useful to provide sufficient notification of an approaching decision point, as long as the names of both ramp forks are visible on signs at the start of the initial ramp.<br />
<br />
'''Example of good use of unnamed ramps:'''<br />
* Initial Exit Sign: to City A and City B<br />
* Destination Left Sign: to City A<br />
* Destination Right Sign: to City B<br />
Result: An unnamed initial ramp will provide accurate and informative navigation instructions to the driver.<br />
<br />
'''Example of poor use of unnamed ramps:'''<br />
* Initial Exit Sign: to Downtown<br />
* Destination Left Sign: to Downtown<br />
* Destination Right Sign: to Center St<br />
Result: An unnamed ramp may create confusion, since both destination ramp names are NOT listed on the initial exit sign. In this case, the initial ramp should be named.<br />
<br />
'''Example of modified use of unnamed ramps:'''<br />
<br />
* Initial Exit Sign: Exit 70A-B to City A and City B<br />
* Destination Left Sign: to City A<br />
* Destination Right Sign: to City B<br />
* Destination Left name in Waze: Exit 70A: City A<br />
* Destination Right name in Waze: Exit 70B: City B<br />
Result: By using a modified name for the destination ramps, we have combined information from two sets of signs to generate the advance notice a driver may need to prepare for a decision point.<br />
<br />
== Interchange configurations ==<br />
<br />
<br />
=== Diamond interchange ===<br />
: [[Image:Jct_diamond.png]]<br />
''See also: [[Wikipedia:Diamond_interchange|Diamond Interchange article on Wikipedia]]''<br />
<br />
Common in wide open spaces where land acquisition and geography are not concerns, this Interchange design has ramps equally distributed across all 4 quadrants.<br />
<br />
In the simplest form, this can be represented as single connections from the ramps to the surface street. <br />
<br />
The straight through motion from the exit ramp to the entrance ramp should typically be enabled, if legal to drive. Under normal circumstances, the Big Detour Prevention mechanism discourages the routing server from routing someone off the freeway and directly back on. When the freeway path between the ramps is closed, or slow enough to overcome the Detour penalty, this off-on route may be given as a desirable alternative.<br />
<br />
Be aware that the Big Detour Prevention penalty is intended to discourage routing that leaves a freeway (or highway) and returns to the same freeway (or highway). Therefore, at least one name (primary or alternate) of the freeway/highway segment before the exit ramp must exactly match one name (primary or alternate) of the freeway/highway segment after the entrance ramp to trigger the penalty. For further information see the [[Detour Prevention Mechanisms|Big Detour Prevention Mechanism]] page.<br />
<br />
:[[Image:Jct_diamond_simple_turns_new.png]]<br />
<br />
If the ramps connect to the surface street at multiple points, restrict turns which should use another ramp. Review the section on [[Junction Style Guide/Interchanges#Ramp geometry and complexity|ramp geometry and complexity]] for more details on this topic. <br />
<br />
First we see the turns that must be restricted for the exit ramps:<br />
<br />
: [[Image:Jct_diamond_cplx_turns_off_L_new.png]] [[Image:Jct_diamond_cplx_turns_off_R.png]]<br />
<br />
Then we see what must be restricted for the entrance ramps:<br />
<br />
: [[Image:Jct_diamond_cplx_turns_on.png]]<br />
<br />
'''Note on elevations:'''<br />
The single surface street segment between the inner most ramps should be either raised or lowered in relation to the freeway segments depending on the actual geography at the interchange.<br />
<br />
=== Cloverleaf interchange ===<br />
: [[Image:Jct_cloverleaf.png]]<br />
<br />
''See also: [[wikipedia:Cloverleaf_interchange|Cloverleaf Interchange article on Wikipedia]]''<br />
<br />
In a Cloverleaf Interchange, left turns are eliminated from all movements between the Freeway and the surface street. First check the exit ramps.<br />
<br />
: [[Image:Jct_cloverleaf_off_outer_turns.png]] [[Image:Jct_cloverleaf_off_inner_turns.png]]<br />
<br />
Then check the entrance ramps for illegal turns.<br />
<br />
: [[Image:Jct_cloverleaf_on_turns.png]]<br />
<br />
The connections to the Freeway segments may be treated in two ways:<br />
<br />
:[[Image:Jct_cloverleaf_options.png]]<br />
<br />
# (top) we can have the inner entrance and exit ramps have their own junction nodes with the Freeway. Do '''NOT''' use this approach if there are [[#Collector.2FDistributor_Lanes|Collector/Distributor Lanes]] (or a similar situation) involved.<br />
# (bottom) we can have the entrance and exit ramps share a single junction node with the Freeway. This allows us to eliminate the very short Freeway segment that may exist between the inner entrance and exit ramps.<br />It is best to offset this shared junction onto the Entrance ramp side of the surface street. This prevents the junction from accidentally being connected to the surface street or looking like it does. We favor the Entrance ramp side, because this would result in a slightly earlier exit instruction which is, of course, preferred over a late exit instruction. <br />
<br />
The determining factor of which design to use will partly depend on the actual size and scale of the specific interchange and if there is a [[#Collector.2FDistributor_Lanes|Collector/Distributor]] involved.<br />
<br />
'''Note on Elevation:'''<br />
The single surface street segment between the inner most ramps should be either raised or lowered in relation to the freeway segments depending on the actual geography at the interchange.<br />
<br />
=== Folded diamond interchange ===<br />
: [[Image:Jct_folded_diamond.png]]<br />
''See also: Discussion of Folded Diamonds and A2/B2 Partial Cloverleafs on the [[wikipedia:Partial_cloverleaf_interchange|Partial Cloverleaf Interchange article on Wikipedia]]''<br />
<br />
Geography or property ownership may prevent the ability for an interchange to be constructed with all ramps evenly distributed across the 4 quadrants of the interchange. When only two quadrants are used, it is typically called a Folded Diamond (basically a sub-type of a Partial Cloverleaf Interchange). The ramps may be all on one side (as in the examples in this section) or they may be located in diagonally opposed quadrants.<br />
<br />
The unique situation presented by the Folded Diamond arrangement is having both Entrance and Exit ramps terminating on the same side of the surface street. Ideally both ramps should terminate on the same junction node to permit us to easily restrict the illegal and usually impossible ramp-to-ramp movement.<br />
<br />
: [[Image:Jct_folded_diamond_u-turn.png]]'<br />
<br />
Like with a basic Diamond Interchange, often it will be necessary to represent the ramps making multiple connections to the surface street. Be sure to read the article [[Junction_Style_Guide#Simple_is_better|Simple is better]] in the Junction Style Guide. <br />
<br />
Restrict all non-permitted turns.<br />
<br />
: [[Image:Jct_folded_diamond_off_turns_L.png]] [[Image:Jct_folded_diamond_off_turns_R.png]] [[Image:Jct_folded_diamond_on_turns.png]]<br />
<br />
'''Note on Elevation:''' Similar to a basic Diamond interchange, in most cases only the segment of the surface street that crosses the Freeway segments will need to be adjusted up or down.<br />
<br />
=== Single-point urban interchange (SPUI) ===<br />
: [[Image:Jct_SPUI.png]]<br />
''See also: [[wikipedia:Single-point_urban_interchange|Single Point Urban Interchange article on Wikipedia]]''<br />
<br />
A SPUI is a very space and flow efficient design, but it takes extra attention to ensure the turns are correct. And as the name indicates, ideally there should be a single junction in the center. You may need to tweak the geometry of segments a bit off of alignment from the real physical world, but it should be minor if the interchange is a true SPUI.<br />
<br />
The outer branches of the exit ramps are similar to a diamond interchange and ramp to ramp routing should be enabled if possible and legal. However, in many SPUIs such ramp to ramp routing is not possible:<br />
<br />
: [[Image:Jct_SPUI_off_outer_turn.png]]<br />
<br />
Where things get complicated is the inner branches leading to the Single Point. You need to avoid ramp-to-ramp in two directions and a reverse flow turn. '''Note:''' The ramp-to-ramp motion to facilitate a U-Turn (the top left arrow in the image below) may or may not be allowed depending on the specific interchange. Please validate this turn.<br />
<br />
: [[Image:Jct_SPUI_off_inner_turn.png]]<br />
<br />
Luckily the entrance ramp restrictions are similar to the diamond interchange:<br />
<br />
: [[Image:Jct_SPUI_on_turn.png]]<br />
<br />
If you were to look at all the restricted turns at once, you may get the false impression that something is very wrong. But as you now know, a SPUI has almost as many restricted turns as allowed ones.<br />
<br />
: [[Image:Jct_SPUI_all_turns.png]]<br />
<br />
'''Note on Elevation:'''<br />
The two surface street segments (between the outer ramps and connected to the Single Point) and the 4 ramp segments connected to the single point should all be the same level, either one higher or one lower than the elevation of the freeway segments above/below the single point.<br />
<br />
=== Collector/Distributor Lanes ===<br />
<br />
These are lanes parallel to, but physically separated from, the lanes of a Freeway that serve to keep merging traffic out of the flow of through traffic on the mainline Freeway.<br />
<br />
Collector/distributor lanes serve as either:<br />
* some of the ramps in an '''interchange''', or<br />
* local lanes in configurations with '''[[wikipedia:local-express lanes|local-express lanes]]'''.<br />
<br />
<br />
==== Collector/distributor interchanges ====<br />
<br />
Some interchange configurations make use of collector/distributor lanes to separate lower-speed merging traffic from high-speed through traffic. This is often used in cloverleaf interchanges and in groups of nearby exits.<br />
<br />
===== Collector/distributor cloverleaf =====<br />
<br />
This is a cloverleaf interchange that is connected to a collector/distributor instead of directly to the main roadway. Map collector-distributor cloverleaf ramps as you would any other ramp.<br />
<br />
[[Image:Jct_fc_cloverleaf_bad.png]]<br />
<br />
The [[Detour Prevention Mechanisms|detour prevention mechanism]] will discourage Waze from routing users onto the collector-distributor and back onto the freeway – as long as the city name on the freeway is the same (or set to "no city") before, throughout, and after the collector-distributor. Previously this feature was not available and the ramps were set up to restrict the through route. Some of these ramp configurations may still be set up that way, so they can now be configured as pictured above with the through route enabled.<br />
<br />
==== Complex collector/distributor interchanges ====<br />
<br />
[[Image:Collector-distributor-exit.png|thumb|right|450px|Collector-distributor lanes used in an interchange on I-81 in Christiansburg, Virginia (Exits 118A-B-C)]]<br />
<br />
Where collector/distributor lanes are used as part of an interchange, use the {{Ramp}} type for the collector/distributor lanes. Name the ramp segments as you would any other ramp segment.<br />
<br />
Ensure that a name on the Freeway segments is consistent before and after the collector/distributor lanes, so that the [[Detour Prevention Mechanisms|detour prevention mechanism]] will prevent Waze from routing users erroneously.<br />
<br />
{{clear}}<br />
<br />
==== Local-express lanes ====<br />
<br />
[[Image:Local-express.png|thumb|right|450px|A local-express lane configuration on I-96 in Livonia, Michigan]]<br />
<br />
Local-express lanes are similar to collector/distributor interchange, but on a larger scale. While collector/distributor interchanges typically have an exit number or numbers, local-express lanes typically share the same name, differentiated by "Local" for the collector/distributor lanes and "Express" for the thru lanes.<br />
<br />
A local-express lane configuration is not technically an "interchange"; however, since its physical characteristics are similar to those of a complex collector/distributor interchange, it is discussed here.<br />
<br />
Where collector/distributor lanes are used as part of a local-express lane configuration,<br />
*use the same type (most likely {{Freeway}}) for the Local lanes as is used for the Express lanes, and<br />
*name the road as it is signed: typically "[Name] Local [Direction]": for example, "I-96 Local W" (and "I-96 Express W" for the Express lanes).<br />
<br />
{{clear}}<br />
<br />
=== {{Anchor| Diverging diamond interchange}}Diverging diamond interchange (DDI) ===<br />
<br />
''See also:'' [[Wikipedia:Diverging_diamond_interchange|Diverging Diamond Interchange]] article on Wikipedia.<br />
[[File:DDI Example Dupont.png|thumb|845x845px|none]]<br />
Diverging diamond interchanges (DDI) are a type of diamond interchange in which the two directions of traffic cross one another on each side of a limited-access roadway. A DDI may pass over or under the limited-access roadway.<br />
<br />
This type of interchange is unusual, in that it requires traffic to briefly drive on the opposite side of the road from what is customary for the jurisdiction. However, the design of the Diverging Diamond Interchange controls the driver's line of sight to ensure the cross-over action feels natural and goes unnoticed.<br />
<br />
==== Segment directionality ====<br />
[[File:DDI Example Dupont - traffic flow.png|thumb|848x848px|Flow of traffic within a Diverging Diamond Interchange|none]]<br />
All ramp and surface street segments are set as one-way. If you are creating a DDI along a road which is not divided, divide the road, first. {{Details|Best map_editing_practice#Dividing_and_un-dividing_divided_highways{{!}}Best map editing practice § Dividing and un-dividing divided highways|how to properly divide/un-divide a road}}<br />
==== At-grade intersections ====<br />
<br />
===== Junctions =====<br />
<br />
As with all at-grade intersections in Waze, all DDI at-grade intersections are modeled with junction nodes, ''including'' the two signaled intersections where opposing directions of traffic "cross over" each other (inner surface road junctions). A DDI may also have two outer surface road junctions, where the one-way segments transition to two-way road segments.<br />
<br />
===== Turn restrictions =====<br />
<br />
====== Overview ======<br />
There are four junctions in a DDI at which the turn restrictions must be checked - two inner surface road junctions where traffic crosses, and two outer surface road junctions where the road divides/joins on each side of the DDI.[[File:DDI Example Dupont - turn restrictions.png|thumb|871x871px|All restricted turns within a DDI (displayed by using Shift+Z).|none]]<br />
<br />
====== Inner surface road junctions ======<br />
[[File:DDI Example Dupont - turn restrictions - inner - 01.png|none|thumb|871x871px]]<br />
[[File:DDI Example Dupont - turn restrictions - outer - 02.png|none|thumb|870x870px]]Disable the ''two'' turns from one-way segments to the segments carrying traffic the ''opposite'' direction at both inner surface road intersections, for a total of four disabled turns. <br />
<br />
====== Outer surface road junctions ======<br />
[[File:DDI Example Dupont - turn restrictions - outer.png|none|thumb|871x871px]]<br />
Disable the ''single'' turn from the one-way segment carrying traffic ''exiting'' the DDI to the one-way segment carrying traffic ''entering'' the DDI at both outer surface road intersections, for a total of two disabled turns.<br />
<br />
== See also ==<br />
<br />
Review the [[Wikipedia:Interchange_(road)|Wikipedia article on Road Interchanges]] for further information on this topic.<br />
<br />
{{ReturnTo | Junction_Style_Guide | the Junction Style Guide}}<br />
[[Category:Style Guide]]</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=User:Qwaletee&diff=153018User:Qwaletee2017-03-31T15:20:21Z<p>Qwaletee: Ditto</p>
<hr />
<div>__NOINDEX__<br />
{{PrivateMessage}}<br />
<br />
== Overview ==<br />
*Joined Waze March 2013<br />
*State Manager (SM) for New York and New Jersey (especially Brooklyn, and Passaic, Bergen and Ocean Counties)<br />
*Map Editing Expert<br />
*Wiki Expert<br />
*Mentor<br />
<br/><br />
----<br />
<br/><br />
*View my [https://www.waze.com/forum/memberlist.php?mode=viewprofile&u=14073768 Forum Profile]<br />
*Send me a [https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14073768 Private Message] through the forums<br />
* [http://www.waze.com/forum/ucp.php?i=pm&mode=compose PM anyone]<br />
<br />
[[Tesrestery]]</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=User:Qwaletee&diff=153017User:Qwaletee2017-03-31T15:20:00Z<p>Qwaletee: /* Overview */ Testerestery</p>
<hr />
<div>__NOINDEX__<br />
{{PrivateMessage}}<br />
<br />
== Overview ==<br />
*Joined Waze March 2013<br />
*State Manager (SM) for New York and New Jersey (especially Brooklyn, and Passaic, Bergen and Ocean Counties)<br />
*Map Editing Expert<br />
*Wiki Expert<br />
*Mentor<br />
<br/><br />
----<br />
<br/><br />
*View my [https://www.waze.com/forum/memberlist.php?mode=viewprofile&u=14073768 Forum Profile]<br />
*Send me a [https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14073768 Private Message] through the forums<br />
* [http://www.waze.com/forum/ucp.php?i=pm&mode=compose PM anyone]<br />
<br />
Tesrestery</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=Road_names&diff=153016Road names2017-03-31T15:10:20Z<p>Qwaletee: /* Concurrent names */ Cardinals on alts</p>
<hr />
<div>For Road Types in the editor see [[Road types/USA]]<br />
<br />
''This page covers road names for the country listed in the page title. For other countries see [[Road types and names|this page]].''<br />
<br />
==Road naming==<br />
<br />
'''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.<br />
<br />
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.<br />
<br />
'''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.<br />
<br />
All roads in our base maps came with the names as defined in the US TIGER dataset.<br />
<br />
However, you might notice a few problems with the original road names:<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).<br />
<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 />
<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 />
<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).<br />
<br />
===Concurrent names===<br />
'''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:<br />
* The route whose mile markers are used for the concurrent segment<br />
* The route whose exit numbers are used for the concurrent segment<br />
* When the concurrency ends, the route whose path does '''not''' get signed as a numbered exit.<br />
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 [[Detour Prevention Mechanisms/USA|big detour prevention mechanism]]. In particular, use cardinal (directional) names on divided highways for both primary and alternate names.<br />
<br />
'''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:<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. <br />
* 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.<br />
<br />
===United States Interstate Highway System [[Image:I-95.svg.png|28px]] [[Image:I-695.svg.png|35px]]===<br />
: Components of the Interstate Highway System should be denoted as shown:<br />
:: '''I-10 E''' for Interstate 10, Eastbound<br />
:: '''I-310 S''' for Interstate 310, Southbound<br />
:: '''I-35E N''' for Interstate 35E, Northbound (Letter suffixes are only in Minnesota and Texas)<br />
: Nearly all interstates are divided highways by necessity, and they should be drawn as such in the map for navigational accuracy.<br />
<br />
===United States Numbered Highways [[Image:US 20.svg.png|30px]]===<br />
<br />
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.<br />
<br />
Certain formatting guidelines must be followed to ensure that highway shields are shown in the Live Map and in the client. Note that map shield generation is not implemented for all situations, so some roads will not display a shield. 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.<br />
<br />
; US Highways<br />
: 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]].<br />
<br />
:: '''US-61 S''' for U.S. Highway 61, Southbound<br />
:: '''US-425 W''' for U.S. Highway 425, Westbound<br />
:: '''US-90 BUS S''' for U.S. Highway 90 Business, Southbound<br />
:::(note that BUS should be all uppercase for TTS to pronounce as "business". "Bus", "bus", etc. will pronounce as "Bus".)<br />
:: '''US-90 ALT E''' for U.S. Highway 90 Alternate, Eastbound<br />
:: '''US-199 SPUR''' for U.S. Highway 199 Spur<br />
<br />
: 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.<br />
<br />
===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]]===<br />
; State Highways<br />
: 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*'''<br />
: 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.<br />
: State routes may also be split if it [[Best_map_editing_practice#When_.28Not.29_to_Split_a_Two-Way_Road|meets the guidelines]].<br />
<br />
: 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.<br />
<br />
: Long Names<br />
:: '''State Hwy 6''' for state highway 6<br />
:: '''State Hwy 99W S''' for state highway 99W, southbound<br />
:: '''State Rte 96''' for state route 96<br />
<br />
: Short Names<br />
:: 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.<br />
<br />
::{{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.}}<br />
<br />
: 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.<br />
<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]]===<br />
<br />
Text to speech on the client reads CR- as "County Road." So "CR-10" is read as "County Road Ten"<br />
<br />
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.<br />
<br />
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;<br />
*CR-<br />
*CH-<br />
*TR-<br />
*TH-<br />
<br />
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.<br />
<br />
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.<br />
<br />
: 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.<br />
<br />
For regions that have township highways, the shortened formats of TH- and TR- are also available.<br />
<br />
===Exit ramps and entrance ramps (on-ramps){{Anchor|Exit|Entrance|Ramp}}===<br />
{{construction<br />
| contact = http://www.waze.com/forum/viewtopic.php?f=276&t=101346&start=30<br />
| contacttype = forum<br />
| draft = no<br />
| open = no<br />
| revision = yes<br />
| section = yes<br />
| talk = no<br />
}}<br />
<br />
[[Image:Exit1.JPG|right|200px]][[Image:Exit2.jpg|right|200px]]<br />
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.<br />
* 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 (" / ").<br />
* 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.)'''}}<br />
** 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.)'''}}<br />
* 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.<br />
* If a single exit serves multiple roads or cities, use a slash with leading and trailing spaces: "Exit 32: Terminator Blvd / Total Recall Rd".<br />
* 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".<br />
** Separate sub-exit letters with a hyphen. Do not leave spaces between the hyphen and the adjacent characters.<br />
* 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.<br />
* Remember to abbreviate common words following the [[abbreviations and acronyms/USA]] page.<br />
* 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.<br />
<br />
For entrance ramps, use this format: "to [street name] [direction] / [control city]", where applicable. For example,<br />
* "to I-10 W / Baton Rouge"<br />
* "to Clearview Pkwy N / Mandeville"<br />
* "to US-90 BUS W"<br />
* "to LA-1 / Thibodaux / Lockport"<br />
* 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.<br />
* 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.<br />
* '''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,<br />
** 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.<br />
** 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".<br />
** 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".<br />
** In general, follow the chart in the [[road naming by state]] article.<br />
* 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.<br />
<br />
===New streets===<br />
<br />
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.<br />
<br />
=== Incomplete segments or red roads ===<br />
<br />
[[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.<br />
<br />
This must be done on all streets created in WME, and on all streets created with the client "Pave" function.<br />
<br />
"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.<br />
<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]]<br />
<br />
=== Navigation instructions for unnamed segments ===<br />
{{:Navigation instructions for unnamed segments/Conditions|transclude=yes}}<br />
<br />
== Abbreviations and acronyms ==<br />
<br />
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.<br />
<br />
A basic rule of thumb is, "when in doubt, spell it out".<br />
<br />
Refer to the [[Abbreviations and acronyms/USA]] page for a list of suffix and recommended abbreviations.<br />
<br />
== {{Anchor|Construction zone}}Construction zones and closed roads ==<br />
''{{Red|This standard has recently changed {{As of|2014|12|df=us|lc=y}}. Please pay close attention to the changes.}}''<br />
<br />
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.<br />
<br />
This section also describes what actions to take when a road remains open, but there are significant changes to it while construction completes.<br />
<br />
===Brief closures===<br />
{{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.<br />
<br />
===Long term closures===<br />
<br />
'''Updated {{As of | 2014 | 12 | df=us | lc=y}}'''<br /><br />
<br />
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.<br />
<br />
===Major construction without closure===<br />
<br />
'''Updated {{As of | 2014 | 12 | df=us | lc=y}}<br /><br />
<br />
{{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.''}}<br />
<br />
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.<br />
<br />
== Official sources of mapping information ==<br />
<br />
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).<br />
<br />
Feel free to add new resources as you find them.<br />
<br />
{{ReturnTo | Editing manual | the editing manual}}<br />
<br />
<br />
[[Category:USA]]<br />
[[Category:Review redirects]]</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=Road_names&diff=153015Road names2017-03-31T14:54:50Z<p>Qwaletee: /* United States Numbered Highways 30px */ Basic copyedits to highway shield para</p>
<hr />
<div>For Road Types in the editor see [[Road types/USA]]<br />
<br />
''This page covers road names for the country listed in the page title. For other countries see [[Road types and names|this page]].''<br />
<br />
==Road naming==<br />
<br />
'''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.<br />
<br />
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.<br />
<br />
'''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.<br />
<br />
All roads in our base maps came with the names as defined in the US TIGER dataset.<br />
<br />
However, you might notice a few problems with the original road names:<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).<br />
<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 />
<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 />
<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).<br />
<br />
===Concurrent names===<br />
'''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:<br />
* The route whose mile markers are used for the concurrent segment<br />
* The route whose exit numbers are used for the concurrent segment<br />
* When the concurrency ends, the route whose path does '''not''' get signed as a numbered exit.<br />
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 [[Detour Prevention Mechanisms/USA|big detour prevention mechanism]].<br />
<br />
'''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:<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. <br />
* 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.<br />
<br />
===United States Interstate Highway System [[Image:I-95.svg.png|28px]] [[Image:I-695.svg.png|35px]]===<br />
: Components of the Interstate Highway System should be denoted as shown:<br />
:: '''I-10 E''' for Interstate 10, Eastbound<br />
:: '''I-310 S''' for Interstate 310, Southbound<br />
:: '''I-35E N''' for Interstate 35E, Northbound (Letter suffixes are only in Minnesota and Texas)<br />
: Nearly all interstates are divided highways by necessity, and they should be drawn as such in the map for navigational accuracy.<br />
<br />
===United States Numbered Highways [[Image:US 20.svg.png|30px]]===<br />
<br />
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.<br />
<br />
Certain formatting guidelines must be followed to ensure that highway shields are shown in the Live Map and in the client. Note that map shield generation is not implemented for all situations, so some roads will not display a shield. 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.<br />
<br />
; US Highways<br />
: 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]].<br />
<br />
:: '''US-61 S''' for U.S. Highway 61, Southbound<br />
:: '''US-425 W''' for U.S. Highway 425, Westbound<br />
:: '''US-90 BUS S''' for U.S. Highway 90 Business, Southbound<br />
:::(note that BUS should be all uppercase for TTS to pronounce as "business". "Bus", "bus", etc. will pronounce as "Bus".)<br />
:: '''US-90 ALT E''' for U.S. Highway 90 Alternate, Eastbound<br />
:: '''US-199 SPUR''' for U.S. Highway 199 Spur<br />
<br />
: 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.<br />
<br />
===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]]===<br />
; State Highways<br />
: 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*'''<br />
: 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.<br />
: State routes may also be split if it [[Best_map_editing_practice#When_.28Not.29_to_Split_a_Two-Way_Road|meets the guidelines]].<br />
<br />
: 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.<br />
<br />
: Long Names<br />
:: '''State Hwy 6''' for state highway 6<br />
:: '''State Hwy 99W S''' for state highway 99W, southbound<br />
:: '''State Rte 96''' for state route 96<br />
<br />
: Short Names<br />
:: 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.<br />
<br />
::{{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.}}<br />
<br />
: 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.<br />
<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]]===<br />
<br />
Text to speech on the client reads CR- as "County Road." So "CR-10" is read as "County Road Ten"<br />
<br />
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.<br />
<br />
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;<br />
*CR-<br />
*CH-<br />
*TR-<br />
*TH-<br />
<br />
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.<br />
<br />
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.<br />
<br />
: 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.<br />
<br />
For regions that have township highways, the shortened formats of TH- and TR- are also available.<br />
<br />
===Exit ramps and entrance ramps (on-ramps){{Anchor|Exit|Entrance|Ramp}}===<br />
{{construction<br />
| contact = http://www.waze.com/forum/viewtopic.php?f=276&t=101346&start=30<br />
| contacttype = forum<br />
| draft = no<br />
| open = no<br />
| revision = yes<br />
| section = yes<br />
| talk = no<br />
}}<br />
<br />
[[Image:Exit1.JPG|right|200px]][[Image:Exit2.jpg|right|200px]]<br />
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.<br />
* 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 (" / ").<br />
* 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.)'''}}<br />
** 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.)'''}}<br />
* 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.<br />
* If a single exit serves multiple roads or cities, use a slash with leading and trailing spaces: "Exit 32: Terminator Blvd / Total Recall Rd".<br />
* 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".<br />
** Separate sub-exit letters with a hyphen. Do not leave spaces between the hyphen and the adjacent characters.<br />
* 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.<br />
* Remember to abbreviate common words following the [[abbreviations and acronyms/USA]] page.<br />
* 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.<br />
<br />
For entrance ramps, use this format: "to [street name] [direction] / [control city]", where applicable. For example,<br />
* "to I-10 W / Baton Rouge"<br />
* "to Clearview Pkwy N / Mandeville"<br />
* "to US-90 BUS W"<br />
* "to LA-1 / Thibodaux / Lockport"<br />
* 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.<br />
* 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.<br />
* '''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,<br />
** 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.<br />
** 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".<br />
** 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".<br />
** In general, follow the chart in the [[road naming by state]] article.<br />
* 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.<br />
<br />
===New streets===<br />
<br />
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.<br />
<br />
=== Incomplete segments or red roads ===<br />
<br />
[[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.<br />
<br />
This must be done on all streets created in WME, and on all streets created with the client "Pave" function.<br />
<br />
"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.<br />
<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]]<br />
<br />
=== Navigation instructions for unnamed segments ===<br />
{{:Navigation instructions for unnamed segments/Conditions|transclude=yes}}<br />
<br />
== Abbreviations and acronyms ==<br />
<br />
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.<br />
<br />
A basic rule of thumb is, "when in doubt, spell it out".<br />
<br />
Refer to the [[Abbreviations and acronyms/USA]] page for a list of suffix and recommended abbreviations.<br />
<br />
== {{Anchor|Construction zone}}Construction zones and closed roads ==<br />
''{{Red|This standard has recently changed {{As of|2014|12|df=us|lc=y}}. Please pay close attention to the changes.}}''<br />
<br />
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.<br />
<br />
This section also describes what actions to take when a road remains open, but there are significant changes to it while construction completes.<br />
<br />
===Brief closures===<br />
{{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.<br />
<br />
===Long term closures===<br />
<br />
'''Updated {{As of | 2014 | 12 | df=us | lc=y}}'''<br /><br />
<br />
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.<br />
<br />
===Major construction without closure===<br />
<br />
'''Updated {{As of | 2014 | 12 | df=us | lc=y}}<br /><br />
<br />
{{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.''}}<br />
<br />
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.<br />
<br />
== Official sources of mapping information ==<br />
<br />
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).<br />
<br />
Feel free to add new resources as you find them.<br />
<br />
{{ReturnTo | Editing manual | the editing manual}}<br />
<br />
<br />
[[Category:USA]]<br />
[[Category:Review redirects]]</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=Places/Parking_lot&diff=149515Places/Parking lot2016-08-28T21:36:36Z<p>Qwaletee: Warning box and clarity of some other text.</p>
<hr />
<div>{{mbox|type=important|text=New Parking features are being rolled out. Do not convert point places to area places, because {{red|'''currently they will be displayed as a visible area on the client map creating unwanted clutter.'''}} New point places are no longer possible, but very small area places can be used as a substitute.<br />
<br />
Waze is also importing test Parking Lot Areas. Do not delete them unless instructed to do so. Use the guidance here to improve their data, shape, and placement.}}<br />
[[File:Parking_sign.png|300px|thumb|right]]<br />
<br />
The '''Parking Lot Area (PLA)''' Place marks a well-defined area constructed for off-street public or private parking, including parking structures and garages as well as at-grade lots. The parking lot feature in the app will recommend parking lots to Wazers navigating to a nearby destination. Waze will recommend lots within ⅔ mile of a Wazer's destination. As the feature matures, Waze will recommend the 'most popular' lots that other Wazers have chosen when navigating to the same destination.<br />
<br />
== {{@|Area or point}} ==<br />
{{Anchor|Area or Point}}Parking lots can ONLY be added as an area as of August 1st, 2016. They are a special place category; you cannot add other categories to a parking lot place, or convert/add a parking lot category to another kind of place.<br />
<br />
=== {{@|Parking lot point places}} ===<br />
{{Anchor|The Parking-Lot Point Place}}As of this writing, you can no longer add Parking Lots as a point place.<br />
<br />
Existing point places should be evaluated for inclusion and either converted to an area if applicable or deleted to solve the [[Map Problems in Waze Map Editor#Parking lot input as point|Map Problem]] (MP) report.<br />
<br />
== {{@|Scope}} ==<br />
{{Anchor|Principles|General Public Use|General Purpose Use|Distinctive and Significant|Interpreting_.27distinctive_and_significant.27}}At this time, parking lot areas (PLA) should not be added to businesses like gas stations or businesses with small parking lots (less than 10 spaces). This guidance may change in the future as further enhancements are made to the parking lot UI. Start by adding parking lots to event venues, shopping centers, airports, public use lots, garages, multi-use parking lots, etc.<br />
[[File:Waze_PLA_Mall_Example.jpg|400px|thumb|right|Shopping Center PLA Example]]<br />
<u>For a mall or large shopping center</u>, break the parking lot up into multiple lots, as shown in the image to the right (use your discretion or discuss with your State Manager(s) or RC for official guidance if necessary.)<br />
<br />
<u>For underground garages</u> it is hard to know the exact polygon, so try to estimate it based on your knowledge of the place. The accuracy of the entry point ([https://wiki.waze.com/wiki/Places#Setting_the_stop_point_for_a_Place '''Setting the stop point''']) is very important.<br />
<br />
<u>If a lot is stacked</u> (underground + surface), map it as one place covering the footprint of the parking lot / garage. Future UI enhancements may allow for better modeling of these lots.<br />
<br />
<u>If a lot has different entrances</u> serving different levels of a multi-level garage and you cannot drive from one level to another to park, but rather the levels are served independently by different entrances, then they should be mapped as multiple places. <br />
<br />
Care must be taken that stacked areas like this do not obscure each other. You do not want two areas with identical boundaries stacked on top of each other as it will be hard to notice or select the right one for editing in WME.<br />
<br />
As with all Area Places, a Parking Lot Area Place's geometry nodes should not be allowed to "snap" to adjacent road segments or junctions while being adjusted. Doing so can make the Area Place, as well as the adjacent segments or junctions, more difficult to modify.<br />
<br />
=== {{@|On-premises parking}} ===<br />
* It is important to create 2 separate places - one for the complex / place, and one for its designated parking lot.<br />
* Multiple parking lots for one premise: Create separate parking lots so the best parking lot can be recommended.<br />
* Valet parking - Valet is a service attribute of a place but is also an attribute for a parking lot.<br />
* Multi-level lots should be created as single place with the shape of the overall parking surface outlined.<br />
<br />
=== {{@|Underground parking lots}} ===<br />
* Create a polygon surrounding the parking lot’s estimated perimeter (if you know its boundaries) and locate the entrance point in the original location.<br />
<br />
* If parking lots overlap with a Place, do not add "Parking Lot" category to a Place. Create a separate Area polygon for the parking lot.<br />
<br />
== {{@|Creating and editing parking lot areas}} ==<br />
{{Anchor|Implementation}}[[File:Waze_PLA_Example.jpg|300px|thumb|right|Outline building footprint only]]<br />
=== {{@|Drawing}} ===<br />
{{Anchor|Extent}}<br />
The Parking Lot Area (PLA) Place should never be attached/snapped to roads. Places snapped to roads are difficult to edit.<br />
<br />
For planned parking features to be announced later, it's important that the shape of the polygon be drawn as close as possible to the actual shape of the parking lot, including the entry/exit location. Keeping in mind that for multi-level garages, only the footprint of the structure should be outlined.<br />
<br />
=== {{@|Naming}} ===<br />
Like all Places, Parking Lot Area Places should be named.<br />
<br />
If a parking facility or area has a documented identity, such as "Beach Street Garage", "18th Avenue/Geary Lot", "Lot 7 - <Stadium name>", "Short-Term Parking - <Airport name>", "Cell Phone Lot - <Airport name>", etc., its Place should reflect that name to facilitate searches. Generic park-and-ride lots should be named consistently according to local custom, for example as "Park & Ride".<br />
<br />
If a Parking Lot Area Place is contained within a larger Area Place, do not repeat the larger Area's full name. For example, if the Domestic Garage is contained within the "SFO San Francisco International Airport" Area Place boundaries, it need not be named "SFO San Francisco International Airport Domestic Garage"; "Domestic Garage - SFO" is sufficient.<br />
<br />
If a mall or shopping center has several lots which can be associated with various anchor stores in the mall/shopping center, the lots can be named for the anchor stores. For example: "Macy's Lot - Big Hill Shopping Center" <br />
<br />
In rare cases, a municipality or district provides public parking distinct from any other Area Place but without any documented or signed identity. These can be named after the municipality or district, for example, "Redwood City Public Parking". Do not use completely generic names such as "Parking" or "Public Parking" for anonymous parking facilities. <br />
<br />
A block range or specific address can be used to name a lot if a more specific / official name does not exist. (e.g., 1201 Conti lot; 2400 block Washington Street garage). Check your local guidance for any variations.<br />
<br />
==== {{@|Restricted parking}} ====<br />
If there are posted signs restricting the lot to only one certain category of users (e.g. Customers, Residents, Staff, Attendees, Permit Holders, Faculty, Students, etc.) ONLY, then put that restriction in the name. If the lot is restricted to more than one category of users, then put "(restricted access)" in the name. Also put the details of the restriction in the [[#description|description]].<br><br />
'''Examples:'''<br />
* "Starbucks Parking (customers only)"<br />
* "Macy's Lot (customers only) - Big Hill Shopping Center"<br />
* Lot D (attendees only) - Cheery Stadium"<br />
* "Alpha Lot (permit only) - StudyHard University" ''Parking allowed by permit only ( even if permits are available to multiple groups (eg for Students, and Faculty)''<br />
* "Bravo Lot (restricted access) - StudyHard University" ''Parking allowed for Students, and Faculty ONLY''<br />
* "123 Somewhere St Lot (residents only)"<br />
* "345 Other St Lot (restricted access)" ''Parking allowed for resident, guests, and staff''<br />
<br />
=== {{@|Description}} ===<br />
Any lot which is fully restricted in some way (eg permit/resident/customer only), and not open to the public for general parking, must include that information as the first line of the description. If only some of the available spots are restricted, but there are some spots in the lot open to the public for general parking, then it should not be mentioned.<br><br />
'''Examples:'''<br />
* "Parking by permit only."<br />
* "Parking only for customers of John Doe's Supermarket"<br />
* "Parking only for residents of 123 Something St, and their guests"<br />
* "Parking restricted to 15 minutes or less"<br />
<br />
=== {{@|Operator}} ===<br />
When there is a recognized parking operator, select it from the list, otherwise, leave this field blank. If an Operator is missing from the list that you feel should be added, please send the information to your [[Regional Coordinator/USA|Regional Coordinator]] (RC).<br />
<br />
=== {{@|Locking standards}} ===<br />
Due to this major shift in editing guidelines, it is recommended that once a Parking Lot Area (PLA) has been added, that it be locked to 3 to avoid newer editors, or those not familiar with the change, from editing or deleting the PLA.<br />
<br />
== {{@|Interface - more info}} ==<br />
[[File:WME_PLA_UI_081016.jpg|400px|thumb|right|WME User Interface - More info tab]]<br />
<br />
'''Opening hours''' - Hours lot is open. Set open times for the lot or select each day and the ''All day'' radio button for lots open 24 hours a day / 7 days a week. <br />
*''Cars can exit when lot is closed'' - Check if the lot or garage does not restrict egress after the lot is considered closed.<br />
*'''Cost'''{{Anchor|Free versus paid parking}}<br />
**Cost determination should be made based on parking lot fees for other similar and nearby lots for the same type of venue.<br />
***Example #1: Adding / editing parking lots near an airport; terminal parking may be the most expensive at $25/day, express parking the next level down (moderate) at $15/day and remote parking the next best option at $5/day (low).<br />
***Example #2: Hotel parking; on-site $50/day (expensive), self-parking garage at $30/day (moderate), and off-site parking at $15/day (low)<br />
**Each lot within approximately ⅔ mile (1 km) radius should be taken into consideration for PLA cost determination where appropriate.<br />
<br />
*'''Services '''(select services listed below)<br />
**Reservations - Lot accepts reservations or accepts pre-paid parking passes or permits.<br />
**Disability parking - Spaces exist for handicap parking / wheelchair accessible spaces.<br />
**Car wash - A car wash is on premises within the parking lot (some airports and other venues have amenities such as this for those parking within the lot).<br />
**Security - On-site security for the specific lot exists<br />
*'''Number of Spots'''<br />
**List the most accurate number of spots within the specified parking lot area polygon.<br />
*'''Contact info'''<br />
**A link to the specific parking lot or vendor's site (if applicable) is permissible here.<br />
*'''Phone'''<br />
**The phone number for the main venue to which the parking lot belongs or to the parking lot vendor is permissible here.<br />
<br />
== {{@|Parking lot roads}} ==<br />
Don't forget to map any necessary [[parking lot roads]], to allow for proper navigation into and out of the parking lot. The parking lot place does not substitute roads needed for actual navigation.<br />
<br />
== {{@|What does not qualify as a PLA?}} ==<br />
{{Anchor|Examples}}{{Red|On-street parking should not be added at this time.}}<br />
<br />
Parking lots or garages used by valet only and situated away from the valet drop off point should not be added to the map. In such cases, where the valet drop off is not near the stop point for the place it services, the valet drop off may added as a lot.{{NeedImage|Image of properly mapped lots nearby lots with >10 spots, and street parking emphasizing that the latter should be added to the map as a PLA.}}<!--[[File:No_PLA.jpg|500px|thumb|center|Where PLAs are not needed]]--><br />
<br />
=== {{@|Rental-car return lots}} ===<br />
{{Anchor|Rental-car return}}With the availability of the "Car Rental" Place, rental car facilities and returns, including at airports, should be marked with that Place category. If the return location is a normal parking lot, then mark it with the parking lot category and the building as a separate place with the Car Rental category.</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=User:Nzahn1/Creating_and_editing_road_segments&diff=140768User:Nzahn1/Creating and editing road segments2016-03-23T18:35:46Z<p>Qwaletee: </p>
<hr />
<div>====Road Properties====<br />
{{mbox<br />
| type = important<br />
| textstyle = color: red;<br />
| text = It is important to follow the guidelines for setting road properties established by your [[Countries_and_Languages|country or region]].<br />
}}<br />
<noinclude>{{Related|Map Editor Interface and Controls #Left Pane with segment(s) selected|Creating_and_editing_road_segments#Road_Properties|Creating and editing road segments #Set Road Type, Direction, and Elevation}}</noinclude><br />
The road segment properties are below the address properties on the General Tab.<br />
<br />
=====Road Type=====<br />
[[Image:RoadType2015.png|right|thumb]]<br />
The road type is changed by selecting the appropriate road type from the drop down box.<br />
<br />
See the [[Road types and names]] page for your country for further guidance on selecting the correct road type.<br />
<br />
{{Clear}}<br />
<br />
=====Special Properties=====<br />
[[File:SpecialProperties2015.png|right|frame]]<br />
* [[Best_map_editing_practice#Toll_roads|Toll roads]] - Select the box for toll road if the segment meets the guidelines<br />
* [[Tunnel]] - Select the box for tunnel if the segment meets the guidelines.<br />
{{Clear}}<br />
<br />
=====Road Direction=====<br />
[[Image:RoadDirectionCB1.png|right|frame]]The direction of the road is changed by selecting the appropriate direction from the drop down box.<br />
<br />
If traffic may travel both ways on the road, select "Two way." If traffic may travel only one-way on the road in the direction from the [[image:ACB.png]] toward the [[image:BCB.png]] select "One way (A&rarr;B)." If traffic may travel only one-way on the road in the direction from the [[image:BCB.png]] toward the [[image:ACB.png]] select "One way (B&rarr;A)." <br />
<br />
After the road properties are saved, the direction is indicated by black arrows on the road.<br />
<br />
[[Image:OneWaySavedCB.png|center]]<br />
<br />
<br />
Base mapped roads are originally assigned the direction of unknown. When the direction is set to "Unknown", Waze automatically adjusts the directionality of the road as Wazers drive it. When editing, make every effort to determine the correct direction of the road and choose either "Two-way" or the appropriate "One-way" direction.<br />
<br />
See the article [[determining one-way streets]] for more information on determining the direction of a road as being one way or two way.<br />
<br />
=====Speed limit=====<br />
[[File:SpeedLimit.png|right|frame]]<br />
The speed limit fields are shown for the segment. These fields should be updated with the official speed limit as shown on speed limit signs. The speed limit is shown in km or miles (Km/h or mp/h), depending on which unit type is selected in the [[Map_Editor_Interface_and_Controls#Settings_Tab|settings tab]].<br />
<br />
[[File:VerifySL.png|right|frame]]<br />
In some locations Waze has run a program to predict speed limits and assign the assumption to segments. When a segment has an assumed speed limit, the limit will be ignored by the app until an editor verifies it. WME displays a *Verified* check box next to the speed limit field. If you verified that the correct speed limit shown is correct, turn on the Verified check mark. If you found it to be incorrect, replace the Waze-supplied limit with a correct limit (there is no need to check the Verified box). Either way, once you save, WME will stop displaying the Verified check box, since it is only needed until verified or corrected.<br />
<br />
For detailed information regarding speed limits policies and how to enter them, see the page on [[Speed_limits|Speed Limits]]. <br />
{{Clear}}<br />
<br />
=====Road elevation=====<br />
{{Anchor|Elevation}}<br />
[[File:RoadElevation.png|right|frame]]<br />
The Road Elevation should be changed where one road passes over another. By default, the Elevation of a segment is '''Ground''' (zero). When two segments overlap but do not actually connect in the real world, the value of Elevation for each segment must be different. This ensures that the Waze problem detection system doesn't flag the spot where two segments overlap as a location where a junction might be needed. <br />
<br />
The visual representation of the relative Road Elevation is different when viewed in the Waze Map Editor (WME) and the Client application.<br />
<br />
1. The Client App displays segment elevation based on the road type only, meaning Freeways are always on top, Major Highways are next, followed by Minor Highways, Ramps next, Primary Streets below all those, and finally Streets are at the bottom. This is the same order seen when setting the road type in the editor.<br />
<br />
2. The WME uses the Road Elevation setting to display the relative elevation of the road. It displays the road with the highest "elevation" number at the top of the visual stack and works its way down as would be expected.<br />
<br />
Although the client application does not benefit from the Road Elevation setting, it is recommended to set the Road Elevation relative to the physical mapping in the real world to enable possible future Client application updates to show the same visual representation as the WME.<br />
<br />
3. Elevation -5 is used for non-drivable roads to help ensure that the routing engine does not try to connect or route drivers from roads onto non-roads by mistake. It acts to prevent false system reporting that the roads should be connected.<br />
<br />
See [[Overpasses,_Underpasses_and_Bridges|Bridges]] for more information on elevation.<br />
<br />
=====Road lock=====<br />
[[File:RoadLock.png|frame|right]]<br />
The road lock menu displays locking levels available to each individual user. In the example to the right, the level 4 editor can assign a lock level of 1, 2, 3, or 4. Once the lock level is saved, an editor of an lower level will not be able to make changes to the segment. <br />
<br />
See [[Best_map_editing_practice#Locking_Segments|Locking segments]] for information.<br />
<br />
=====House numbers=====<br />
[[File:EditHouseNumbers.png|frame|right]]<br />
The house numbers is used to create and edit house numbers for named road segments.<br />
<br />
See [[House_Numbers_in_WME|House numbers]] for more information.</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=User:Nzahn1/Creating_and_editing_road_segments&diff=140767User:Nzahn1/Creating and editing road segments2016-03-23T18:33:53Z<p>Qwaletee: Language tweaks for speed limits</p>
<hr />
<div>====Road Properties====<br />
{{mbox<br />
| type = important<br />
| textstyle = color: red;<br />
| text = It is important to follow the guidelines for setting road properties established by your [[Countries_and_Languages|country or region]].<br />
}}<br />
<noinclude>{{Related|Map Editor Interface and Controls #Left Pane with segment(s) selected|Creating_and_editing_road_segments#Road_Properties|Creating and editing road segments #Set Road Type, Direction, and Elevation}}</noinclude><br />
The road segment properties are below the address properties on the General Tab.<br />
<br />
=====Road Type=====<br />
[[Image:RoadType2015.png|right|thumb]]<br />
The road type is changed by selecting the appropriate road type from the drop down box.<br />
<br />
See the [[Road types and names]] page for your country for further guidance on selecting the correct road type.<br />
<br />
{{Clear}}<br />
<br />
=====Special Properties=====<br />
[[File:SpecialProperties2015.png|right|frame]]<br />
* [[Best_map_editing_practice#Toll_roads|Toll roads]] - Select the box for toll road if the segment meets the guidelines<br />
* [[Tunnel]] - Select the box for tunnel if the segment meets the guidelines.<br />
{{Clear}}<br />
<br />
=====Road Direction=====<br />
[[Image:RoadDirectionCB1.png|right|frame]]The direction of the road is changed by selecting the appropriate direction from the drop down box.<br />
<br />
If traffic may travel both ways on the road, select "Two way." If traffic may travel only one-way on the road in the direction from the [[image:ACB.png]] toward the [[image:BCB.png]] select "One way (A&rarr;B)." If traffic may travel only one-way on the road in the direction from the [[image:BCB.png]] toward the [[image:ACB.png]] select "One way (B&rarr;A)." <br />
<br />
After the road properties are saved, the direction is indicated by black arrows on the road.<br />
<br />
[[Image:OneWaySavedCB.png|center]]<br />
<br />
<br />
Base mapped roads are originally assigned the direction of unknown. When the direction is set to "Unknown", Waze automatically adjusts the directionality of the road as Wazers drive it. When editing, make every effort to determine the correct direction of the road and choose either "Two-way" or the appropriate "One-way" direction.<br />
<br />
See the article [[determining one-way streets]] for more information on determining the direction of a road as being one way or two way.<br />
<br />
=====Speed limit=====<br />
[[File:SpeedLimit.png|right|frame]]<br />
The speed limit fields are shown for the segment. These fields should be updated with the official speed limit as shown on speed limit signs. The speed limit is shown in km or miles, depending on which unit type is selected in the [[Map_Editor_Interface_and_Controls#Settings_Tab|settings tab]].<br />
<br />
[[File:VerifySL.png|right|frame]]<br />
In some locations Waze has run a program to predict speed limits and assign the assumption to segments. When a segment has an assumed speed limit, the limit will be ignored by the app until an editor verifies it. WME displays a *Verified* check box next to the speed limit field. If you verified that the correct speed limit shown is correct, turn on the Verified check mark. If you found it to be incorrect, replace the Waze-supplied limit with a correct limit (there is no need to check the Verified box). Either way, once you save, WME will stop displaying the Verified check box, since it is only needed until verified or corrected.<br />
<br />
For detailed information regarding speed limits policies and how to enter them, see the page on [[Speed_limits|Speed Limits]]. <br />
{{Clear}}<br />
<br />
=====Road elevation=====<br />
{{Anchor|Elevation}}<br />
[[File:RoadElevation.png|right|frame]]<br />
The Road Elevation should be changed where one road passes over another. By default, the Elevation of a segment is '''Ground''' (zero). When two segments overlap but do not actually connect in the real world, the value of Elevation for each segment must be different. This ensures that the Waze problem detection system doesn't flag the spot where two segments overlap as a location where a junction might be needed. <br />
<br />
The visual representation of the relative Road Elevation is different when viewed in the Waze Map Editor (WME) and the Client application.<br />
<br />
1. The Client App displays segment elevation based on the road type only, meaning Freeways are always on top, Major Highways are next, followed by Minor Highways, Ramps next, Primary Streets below all those, and finally Streets are at the bottom. This is the same order seen when setting the road type in the editor.<br />
<br />
2. The WME uses the Road Elevation setting to display the relative elevation of the road. It displays the road with the highest "elevation" number at the top of the visual stack and works its way down as would be expected.<br />
<br />
Although the client application does not benefit from the Road Elevation setting, it is recommended to set the Road Elevation relative to the physical mapping in the real world to enable possible future Client application updates to show the same visual representation as the WME.<br />
<br />
3. Elevation -5 is used for non-drivable roads to help ensure that the routing engine does not try to connect or route drivers from roads onto non-roads by mistake. It acts to prevent false system reporting that the roads should be connected.<br />
<br />
See [[Overpasses,_Underpasses_and_Bridges|Bridges]] for more information on elevation.<br />
<br />
=====Road lock=====<br />
[[File:RoadLock.png|frame|right]]<br />
The road lock menu displays locking levels available to each individual user. In the example to the right, the level 4 editor can assign a lock level of 1, 2, 3, or 4. Once the lock level is saved, an editor of an lower level will not be able to make changes to the segment. <br />
<br />
See [[Best_map_editing_practice#Locking_Segments|Locking segments]] for information.<br />
<br />
=====House numbers=====<br />
[[File:EditHouseNumbers.png|frame|right]]<br />
The house numbers is used to create and edit house numbers for named road segments.<br />
<br />
See [[House_Numbers_in_WME|House numbers]] for more information.</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=User:CBenson/Necessary_junctions&diff=139062User:CBenson/Necessary junctions2016-03-03T22:26:07Z<p>Qwaletee: Fix bullet formatting</p>
<hr />
<div><!--<br />
#####-----#####-----#####-----#####-----#####-----#####-----#####-----#####-----<br />
#### This page has been curated ####<br />
#### to be included in the new ####<br />
#### Wazeopedia - GLOBAL Wiki. ####<br />
#### Please do not make any ####<br />
#### edits on this page without ####<br />
#### PRIOR CONSENSUS in the Wiki ####<br />
#### Updates and Discussions ####<br />
#### forum thread for this page. ####<br />
#### If a specific forum thread ####<br />
#### for this page doesn't exist ####<br />
#### please start one. ####<br />
#### www.waze.com/forum/ ####<br />
#### viewforum.php?f=276 ####<br />
#####-----#####-----#####-----#####-----#####-----#####-----#####-----#####--><br />
<br />
<!--This page is translcuded into other pages and is generally not expected to be viewed by readers on its own. However it does include basic information to prevent confusion for an otherwise unexplained list of bullets. The "onlyinclude" functions will only transclude that content into other pages requiring the list itself. The special "ifeq" template prevents hyperlinks to the same page into which it may be transcluded. All other pages would include the hyperlinks.<br />
--><br />
Junctions with three or more connected segments are necessary if the segments themselves are supposed to intersect for routing purposes. Generally speaking, most two-segment junctions are not required, however some of them are required to ensure the best operation of Waze. The list below includes examples where a two-segment junction is necessary and should NOT be removed.<br />
<br />
<onlyinclude>* '''Loop roads'''. A single segment cannot loop back upon itself, so a junction is required to create two separate segments. It does not matter where the junction is located, so long as each segment meets the {{#ifeq: {{PAGENAME}} | Segment length | minimum segment length | [[Segment length|minimum segment length]]}}. Some roads have two separate segments that share the same start and end junctions creating two alternate paths between them. These configurations cause routing problems and require one of the two segments to have a 2-segment junction. More details are covered in [[Junction Style Guide#Loops|Junction Style Guide on Loops]].<br />
<br />
* '''Ramp or freeway splits'''. There are cases where a freeway may split into two separate freeways. In order to provide navigation to drivers, it may be necessary to create short segments on the freeway to show the two different road names at the split. Under certain situations it may be best to make the segments as short as possible, so long as each segment meets the {{#ifeq: {{PAGENAME}} | Segment length | minimum segment length | [[Segment length|minimum segment length]]}}. This is covered in detail in the [[Junction_Style_Guide#Highway.2FFreeway_Splits|Junction Style Guide]].<br />
<br />
* '''Long segments'''. Segments are best kept under a certain distance. {{#ifeq: {{PAGENAME}} | Segment length |<!-- do nothing--> | See the article [[segment length]] for more information.}}</onlyinclude><br />
<br />
* '''Segment Property Change'''. When a segment property changes between intersections, a two-segment junction may be required:<br />
<br />
:* ''Road, city, or state name change''. When the road, city, or state name changes between intersections, add a junction so the segments on either side may have a different name. <br />
<br />
:* ''Elevation Change''. When [[Elevation#Road_elevation|elevation]] changes at complex interchanges, a junction can be added to introduce an elevation change.<br />
<br />
:* ''Speed Limit Change''. When the speed limit changes between intersections, add a junction so the segments on either side may have a different speed limit.<br />
<br />
For more information on this topic see [[Unnecessary junctions]].</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=Creating_and_editing_road_segments&diff=132312Creating and editing road segments2016-01-01T06:06:20Z<p>Qwaletee: /* Confirm the road by updating details */</p>
<hr />
<div><!--if the section parameter is defined, do not place the visible banner, only as the code block for the top of a section-->{{GlobalMark/visible}}<br />
<!--<br />
#####-----#####-----#####-----#####-----#####-----#####-----#####-----#####-----<br />
#### This page has been curated ####<br />
#### to be included in the new ####<br />
#### Wazeopedia - GLOBAL Wiki. ####<br />
#### Please do not make any ####<br />
#### edits on this page without ####<br />
#### PRIOR CONSENSUS in the Wiki ####<br />
#### Updates and Discussions ####<br />
#### forum thread for this page. ####<br />
#### If a specific forum thread ####<br />
#### for this page doesn't exist ####<br />
#### please start one. ####<br />
#### www.waze.com/forum/ ####<br />
#### viewforum.php?f=276 ####<br />
#####-----#####-----#####-----#####-----#####-----#####-----#####-----#####--><br />
<br />
{{ReturnTo | Editing manual | the editing manual}}<br />
<br />
This article covers creating and editing road segments. Be sure to read this whole article to ensure you fully understand all aspects of how segments operate in Waze before you start to create and edit roads on the map.<br />
<br />
==Creating a new road==<br />
If you find a road missing from the Waze map, such as a recent suburban development, follow the screenshots and instructions to add a road to Waze. The example is from Little Rock, Arkansas, USA, and we will add the missing roads in the highlighted area:<br />
<br />
[[Image:new_road_step_01_hilited.png|400px]]<br />
<br />
<br />
Zoom the map display so you can see the entire area where you need to add the road, if possible. Setting the zoom level appropriately allows you to follow the curves of the road as you draw it.<br />
<br />
There are five essential steps to add roads to the Waze map:<br />
# Draw the road.<br />
# Set or confirm the road properties.<br />
# Connect the road with junctions to existing segment(s) or another newly created segment(s).<br />
# Set allowed turns at junctions.<br />
# Save the changes.<br />
<br />
* [http://www.youtube.com/watch?&v=_Dlt7131dkc&hd=1 View a step-by-step video on how to add a road from an existing intersection]<br />
<br />
For more detail on creating road segments, see [[Map_Editing_Quick-start_Guide#Create_a_Road | Create a Road]].<br />
<br />
===Drawing the road===<br />
<br />
[[File:Create_Road_Drop_Down_Menu.png|left]] ''Hover'' the cursor over the curved road with a cross/plus sign icon at the top of the screen in the [[Map_Editor_Interface_and_Controls#The_Tool_Bar|toolbar]] and ''click'' '''Road'''. You can also use the [[keyboard shortcut]], which is the letter '''i''', for Insert. Move the cursor to the location you want to start drawing the road. This can be an empty location, or it can be on an existing segment where you want the intersection with this new road. The cursor has a small blue circle to indicate it is in drawing mode.<br />
<br />
When you hover over an existing segment, it highlights showing that if you click there, a junction is automatically added.<br />
<br />
[[Image:new_road_step_01.png]]<br />
<br />
Move your mouse along the path of the road, following the aerial view or GPS points for the new road. Every time you ''click'', a '''[[geometry node]]''' is added, aligning your new road with your cursor movement. When you reach the end location for the new road, ''double-click'' the mouse. You exit drawing mode, and the new road displays in orange to signify that it is unsaved. Don't worry if you made a mistake in drawing the shape of the road. Just click on the segment again and you can add, remove or reposition geometry nodes. If you want to remove the road just drawn, you can press the ESC key on the keyboard before you exit drawing mode.<br />
<br />
[[Image:new_road_step_02-04.png]]<br />
<br />
<br />
In our example, there is another road in this same view which is missing. We can add another road to the map without saving the first one. The next image shows the second road already added, and auto-junctioned to the first segment we just created.<br />
<br />
[[Image:new_road_step_05.png]]<br />
<br />
<br />
At this point, you can save the newly added roads if you wish. However, the process of properly adding the roads is not complete. All new roads are set as 1-way, with no associated city and no street name. Adding these details to the road is required before they show up in the Waze client app.<br />
<br />
'''Note''': When creating special roads like [[Roundabouts/USA|roundabout]]s and [[loop]]s, be sure to follow the special considerations for those roads in those linked sections.<br />
<br />
{{clear}}<br />
<br />
===Confirm the road by updating details===<br />
<br />
{{construction<br />
| contact = http://www.waze.com/forum/viewforum.php?f=276<br />
| contacttype = forum<br />
| draft = no<br />
| open = no<br />
| revision = yes<br />
| section = yes<br />
}}<br />
<br />
New road segment created via the app's "Pave road" function are not immediately displayed on the Waze app. They must first have city and street names confirmed, meaning that an editor adds that information. The editor will also have to connect them to the road network to make them usable.<br />
<br />
In the map editor, '''<span style="color:red;">roads are outlined in red</span> when city and street name properties have not been set''' (known as ''red roads'' or ''unconfirmed roads''). An editor should set the country; state (US only); city; street name; road type; and direction.<br />
<br />
{| class="wikitable" style="background:white; color:red; margin: 1em auto 1em auto" border="1" <br />
|-<br />
| Paved roads do not appear until being "touched" in the editor. This does not apply to roads created in the editor; when created in WME, roads can appear on the Waze app even if they are missing key properties.<br />
|-<br />
|}<br />
<br />
To confirm a road, select one or more segments with the mouse. You can add only one name at a time, but you can add it to multiple segments at the same time. Because of that, it is efficient to first select multiple segments that will share the same name, and then apply the name to them together. Notice below that for the first road there are now two one-way segments. This is because the second road we added has cut the original road into two segments.<br />
<br />
[[Image:confirm_roads_01.png]]<br />
<br />
[[Image:WMEGeneralTab.png|245px|border|right]] To edit the address details of the selected segment(s), find the phrase ''Unnamed segment'' in the upper left corner of the editor. There is a pencil icon next to it. Click the pencil icon. Make sure the Country and State values are correct. Next, enter the city and street name information. Sometimes, a segment is outside a municipality, or the municipality cannot be determined or is not relevant. If that is the case, then check the ''None'' box next to City. Similarly, some streets may not need a name, such as ramps, private roads, and parking lot roads. For those segments, use the ''None'' check box next to Street.<br />
<br />
Most [[Roundabouts/USA#Creating_a_roundabout_from_an_intersection|roundabouts]] also must not have a street name. Use the ''None'' box for them. This permits proper navigation instructions for the roundabout.<br />
<br />
[[File:RoadCrossDualCW.png|left|border|440px]]{{clear}}<br />
For segments that exist only to connect two one-way roads (''At-grade connectors''), do not name the segment. The city name is fine if the segment is clearly inside the city limits.<br />
<br />
'''Important:''' When complete, click the ''Apply'' button. If you do not click the Apply button, your changes will be discarded by WME without warning when you save or click another object in the editor. Please click the Apply button as soon as you finish entering information, so you do not lose your data.<br />
{{clear}}<br />
<br />
===Set Road Type, Direction, and Elevation===<br />
Set each of the fields [[Road types and names|Road Type]], Direction, and [[#Elevation|Elevation]]. For neighborhood streets in these examples, Street is appropriate, they are 2-way streets and they have no roads above or below them, so elevation '''Ground''' is correct. <br />
<br />
Review the article [[determining one-way streets]] for more information on directionality. <br />
<br />
* Please be aware the the directionality type 'Unknown' does not prevent Waze from routing onto a road. 'Unknown' really means 'Undefined'. When the direction is set to 'Unknown', Waze automatically adjust the directionality of the road as Wazers drive it. This is the initial directionality of all roads after a base map import. In addition, locking the segment does not prevent the directionality from changing on 'Unknown' roads as Wazers drive it.<br />
<br />
{{Clear}}<br />
You may choose to save now, but there is one more step before we can call this process complete: setting the allowed turns.<br />
<br />
===Set allowed turns (connections)===<br />
<br />
[[Image:new_road_turns_not_allowed.png|left]] We've added our roads and confirmed them, but we haven't set the legal directions to and from this segment. In the real world, there are barriers and signs which prevent travel in a certain direction, even though the roads connect to each other. In our suburban neighborhood example, none of these blockages exist, but our screenshot shows red arrows, meaning that Waze generally won't navigate that direction from the selected segment. Click on the red arrows to turn them green, and permit navigation in that direction. This needs to be done for each segment that is added to the map, as the default setting after connecting a new segment is to disallow all turns to the new segment.<br />
{{Clear}}<br />
In situations where not all turns are allowed, click on the arrow to turn it red for the disallowed direction from that segment. <br />
<br />
[[Image:select_junction.png|right]]If all turns are allowed at a junction, the fastest way to enable all turns is by selecting the junction and not the individual segments. ''Select'' the '''junction''' and it changes from an orange circle to a red circle with a white border. Note that if you have already selected a segment connected to that junction, click elsewhere on the map, or hit the ESC key to deselect that segment before you can select the junction.<br />
{{Clear}}<br />
<br />
[[Image:Junction_properties_example.png|left]] The Properties drawer shows action links for the selected junction. Depending on the current state of the junction, one or both of the links '''Allow all turns''' or '''Disallow all turns''' links appear. For example, if all turns are currently allowed, then only the '''Disallow all turns''' link appears.<br />
{{Clear}}<br />
To enable all turns at an intersection, ''click'' the '''Allow all turns''' link for the junction. Alternatively, you can use the keyboard shortcut '''w''' to allow all turns and the shortcut '''q''' to disallow all connections. A best practice when allowing all turns on a junction is to disallow all turns first, as it cleans up some legacy problems with the map.<br />
<br />
Other helpful turn arrow keyboard shortcuts are:<br />
<br />
{| class="Wikitable floatright"<br />
| '''Shift+Z''' - Toggles between: 1) showing the enabled and restricted turn arrows for the selected segment, and 2) showing all restricted turns (red arrows only) for every junction on the visible map (up to zoom level 4 or 500 ft in the lower left map legend).<br />
| [[File:ArrowShowAll1.png|130px|right]]<br />
| [[File:ArrowShowAll2.png|130px|right]]<br />
|}<br />
<br />
{| class="Wikitable floatright"<br />
| '''a''' - Toggles between making the turn restriction arrows directly selectable (opaque) or transparent. Transparency enables selecting objects below the arrow on the map.<br />
| [[File:ArrowTrans1.png|130px|right]]<br />
| [[File:ArrowTrans2.png|130px|right]]<br />
|}<br />
{| class="Wikitable floatright"<br />
| '''s''' - Toggles between separating turn arrows so they don't overlap or leaving them overlapping. This can also be used to refresh the screen when you have toggled visibility for all restricted turns, and you are modifying turn restrictions.<br />
| [[File:ArrowSpread1.png|130px|right]]<br />
| [[File:ArrowSpread2.png|130px|right]]<br />
|}<br />
<br />
To see all [[keyboard shortcuts]], press the '''?''' on the keyboard.<br />
<br />
When turns or parts of a road are restricted certain times of day or days of the week, you can use the [[Partial restrictions|scheduled restrictions]] feature.<br />
<br />
As the roads connecting to each other usually allow for all turn connection / direction, it is saves a lot of time for the editor to enable “draw new roads with all turns allowed” under the [[Map_Editor_Interface_and_Controls#Left_Pane|left pane]] “settings” tab during editing process. <br />
<br />
''See the section [[Map_Editing_Quick-start_Guide#Turn_restrictions_.28allowed_turns.29|turn restrictions]] for more information on all turn arrows.''<br />
<br />
{{Clear}}<br />
<br />
===Save===<br />
If you have saved your progress or not, ''click'' the '''Save''' button (or use the '''Ctrl + s''' keyboard shortcut) to send all of your updates to the Waze servers for processing. After the save is complete, and if there are no errors, you are presented with a view of the final product of this process:<br />
<br />
[[Image:new_road_final.png]]<br />
<br />
It is a good practice to save your changes often, and certainly when you get more than 10 unsaved changes pending. Sometimes you may run into a save error that you cannot determine what is wrong, and you have to '''undo''' many prior edits. Sometimes you have to undo all the way back to your first edit. Saving regularly limits chances of lost work in case of unresolvable errors.<br />
<br />
==Editing existing roads==<br />
Editing an existing road segment is not very different from creating a new road. Once a road is drawn from scratch, before it is saved, all of the editing functions described here work.<br />
<br />
===Adjusting road geometry (nodes)===<br />
{{construction<br />
| contact = http://www.waze.com/forum/viewforum.php?f=276<br />
| contacttype = forum<br />
| draft = no<br />
| open = no<br />
| revision = yes<br />
| section = yes<br />
}}<br />
<br />
Adjusting road geometry is changing the shape or appearance of a road segment. Real-world roads may be realigned, or mapped roads may be in the wrong place because the data from the basemap import was wrong. Sometimes we need to realign roads to improve navigation or spoken instructions in the Waze mobile app.<br />
<br />
The instructions here, while written for an existing road segment, also apply to a new road segment you just created, but have not yet saved. The editor treats them the same.<br />
<br />
[[Image:Adjust_geometry_1.png|320px|right]] To start adjusting the geometry of a segment, ''click'' on it. When you hover over the highlighted segment, [[Glossary#Geometry node|geometry nodes]] (<s>black squares</s> white circles) and [[Glossary#Geometry node|inter-geometry nodes]] (white dots circled in blue) display along the segment. Both of these are draggable so that you can reposition them wherever you need. When you drag an inter-geometry nodes from its default position half-way between two geometry nodes, it turns into a node.<br />
{{Clear}}<br />
[[Image:Adjust_geometry_2.png|320px|right]] To delete a node, ''hover'' the cursor over a node and hit the '''d''' key on the keyboard. This only works with nodes, not inter-geometry nodes. <br />
<br />
'''Tip: Straighten segments quickly'''<br />
If you have a segment that you need to clear all the geometry node quickly, select the segment and hold down the '''d''' key. Then move the mouse pointer near the geometry nodes you want to remove. With the '''d''' key held down it will automatically delete the node when the mouse hovers over it. To stop deleting nodes, stop pressing the '''d''' key.<br />
<br />
When you have a long, straight stretch of road, and there are geometry nodes located along its length, delete these nodes. It simplifies the road segment if you have to adjust it later, lightens the load on the database, and makes it easier to display on the Waze client app.<br />
<br />
{{Clear}}<br />
[[Image:Adjust_geometry_3.png|320px|right]] When your moves are complete, save, and the segment appears in the map with the new geometry.<br />
<br />
To see these operations in action, you can [http://youtu.be/Pm8zEmlD5bo?hd=1 watch a video of adjusting segment geometry].{{clear}}<br />
<br />
{{anchor|Fix the end-node on cul-de-sacs and dead-ends}}<br />
<br />
===Fix the end-node on culs-de-sac and dead-ends===<br />
{{Red|NOTE: The information shown in this section is only valid for segments which were paved from the Waze application. While they do NOT show in the editor when present, any segment drawn in the WME will have a junction node at its terminus.}}<br />
<br />
[[Image:FixDE-01.jpg|400px|right]]In order for the Waze Application to properly route from a location on a [[Junction_Style_Guide#Cul-de-sacs|cul-de-sac]] or dead-end road, the end of the last segment must have an end-node. Without this end-node, Waze gives the instruction ''Proceed to the highlighted route''. <br />
<br />
In the image to the right you can see a small blue diamond at the end of the long court, and no blue diamond at the end of the short court. The short court is missing an end-node at the end of the segment.{{clear}}<br />
<br />
[[Image:FixDE-02b.jpg|400px|left]][[Image:FixDE-02a.jpg|105px]]<br />
<br />
When you select each segment, putting them into an edit mode, you can see the difference between the two roads. The long court has the end-node (small white circle) and the short court has a geometry node (large black square) at the end of the segment.{{clear}}<br />
<br />
[[Image:FixDE-03.jpg|150px|left]]To add an end-node to the short court, a temporary road segment must be added to the current road. Start by not having the road selected (make sure it is white by clicking elsewhere on the map). ''Hover'' the cursor over the large + icon at the top of the screen in the [[Map_Editor_Interface_and_Controls#The_Tool_Bar|toolbar]] and ''click'' '''Road'''. You can also use the keyboard shortcut which is the letter '''i''', for Insert. Position the cursor so the blue circle appears at the end of the segment and Left-click the mouse to start the road.{{clear}}<br />
<br />
[[Image:FixDE-04.jpg|150px|left]][[Image:FixDE-06.jpg|150px|right]]<br />
Click some distance away from the end of the current road and double click to end road creation. Select the newly created segment and press the Delete key or the Trash Can icon from the toolbar.{{clear}}<br />
<br />
[[Image:FixDE-07.jpg|400px|left]]<br />
Save the changes and the result shows the small court now has the proper end-node as a small blue diamond (when not being edited or selected).<br />
<br />
Note that most cul-de-sac should not terminate in a roundabout or loop, but as a dead end as drawn here.{{clear}}<br />
<br />
===Junctions===<br />
Before making any change to a junction, be sure to review the [[Junction Style Guide]] for information on the best practices for creating junctions. There are many times when a junction may be drawn in a way that does not seem logical, but it is very important to the navigation engine in Waze. <br />
<br />
====Moving junctions====<br />
Moving a junction is as simple as dragging the junction to another location, however there are geometry nodes (the white circles seen when editing a segment) that might need to be moved or removed. <br />
<br />
[[Image:MoveJunc-1.png|200px|left]]First use the mouse to select the intersection of the road segments. This puts a red dot, circled in white, on the junction. This indicates you are moving '''all''' the segments connected to this junction. Note that if the red dot appears transparent, it means that one of the attached road segments is locked above your editing rank, and the junction cannot be moved by you. Release the mouse button and move the mouse away until the cursor appears as a 4-way crossed arrow [[Image:CrossedCursor.png|24px]]. <br />
{{clear}}<br />
[[Image:MoveJunc-2.png|right]]With the cursor as a crossed arrow, select the junction again and drag it to the desired location. The harsh angles in the segments in this example are caused by the geometry nodes and need to be adjusted. It is important to position the junction in a location that is not on top of a segment. This makes it difficult to adjust the geometry nodes, and in some cases tells the editor to merge junctions if one is present below the junction you are moving.<br />
{{clear}}<br />
[[Image:MoveJunc-3.png|left]]The black geometry nodes can be moved, removed, or added as explained in [[Creating and editing road segments#Adjusting road geometry .28nodes.29|detail above]]. Adjust them to align with the aerial views or the GPS tracks.<br />
<br />
{{clear}}<br />
===== Moving one junction onto another junction =====<br />
If two junctions are disconnected from each other, but should be joined into one junction, then dragging one of the junction nodes until it "snaps" to and connects to the other junction node will bring them together. <span style="color: red">Warning! Only use this technique if the two junctions are disconnected from each other. If there is a segment connecting the two, you could accidentally delete the segment in the process. This would also delete any traffic data and house numbers associated with the deleted segment.</span><br />
<br />
====Removing junctions with only two segments====<br />
There are times when only two segments are joined at a junction. In general this is not a problem, but it can slow down editing and it may be the source of incorrect turn restrictions and bad routing. So the best practice is to delete these junctions when found. However, it is very important to study the two segments before merging, to ensure the junction is not there for a purpose.<br />
<br />
{| class="wikitable unsortable" border="1"<br />
|-<br />
! Legitimate Reasons for Two-segment Junctions<br />
|- style="background:#FFFFFF; color:black"<br />
| {{:Necessary junctions}}<br />
|- <br />
|}<br />
<br />
Once you are certain there is no reason to have the extra junction, there are three methods to remove it. One method highlights the junction and deletes it, one highlights the two segments and bridges them together, and the last method drags one junction on top of the other junction.<br />
<br />
=====Delete key or trash can icon=====<br />
This method is the preferred method, because it enables the WME to alert you when there are legitimate differences between the segments. With the mouse select the junction point between the two segments. Look for the trash can icon at the upper right corner of the WME screen. If it appears press it to remove the junction. Alternatively, the Delete or Del key (not Backspace) removes the junction.<br />
<br />
Deletion of a node automatically places a geometry node at that point. If you need to remove the point, you can do so by highlighting the segment and hovering the mouse over the point of the prior junction. The WME displays the point and you can press the '''d''' key to remove it.<br />
<br />
If the trash can icon does not appear, something about those two segments is different, possibly the city name, street name, road type, or direction of travel.<br />
<br />
=====Bridge segments=====<br />
Generally do not use this method because it has two additional side effects that are not generally desired. <br />
# It increases the elevation of the resulting single segment by one.<br />
# It disconnects any other segments at that junction point, but leaves it directly below the geometry node potentially causing automated map problems if not moved.<br />
<br/><br />
[[Image:MergeJunc-2a.png|left|350px]]With the mouse, select one of the segments. Then, while holding down the multi-select key ('''Control''' for Windows/Linux and '''Command''' for Mac) select the second segment. If the two segments have the same properties including direction, a small bridge icon appears above the junction. Click the bridge to merge the two segments, eliminating the junction between them. A geometry node is placed where the junction was previously located. To remove the node (if necessary), select the segment and hover the mouse near the old junction. The geometry node should be displayed. Then, press the '''d''' key to remove the unwanted node.<br />
<br />
When the segments are '''different''', the bridge icon does '''not''' appear at the junction.{{clear}}<br />
<br />
====Cut a segment to create a new junction====<br />
If it is necessary to change road information in the middle of a segment (road name, direction, city, type, or other information changes at that point), you need to create a junction at that point. One way to do this is to create a new road connected to the previous road. Begin or end the new road on the previous road to create a new junction. Then delete the new road -- the junction remains, and the previous road segment has been cut at the point where you created and deleted the road.<br />
<br />
====Allow/Disallow connections====<br />
Changing the allowed and disallowed turns in a junction follows the same procedure for controlling them when updating a road segment [[Creating and editing road segments#Set allowed turns .28connections.29|described above]].<br />
<br />
===(Re)Moving a road from a junction===<br />
===Updating road details===<br />
The details of a road can be entered as discussed with regard to confirming the details of a new road above. The procedure is the same for updating the details of an existing road segment.<br />
<br />
To update details, first, select the segment(s) you need to update. Click on the segment and the segment turns blue.<br />
[[Image:SelectionCB1.png]]<br />
<br />
Multiple segments may be selected by holding down the modifier key and clicking additional segments. The modifier key for Mac is the command key, for Windows the control key and for Linux the control key. Each selected segment turns blue.<br />
[[Image:MultipleSelectionCB1.png]]<br />
<br />
Once selected, if the General tab is visible on the left side of the editor.<br />
<br />
[[Image:WMEGeneralTab.png]]<br />
<br />
====Address Properties====<br />
<br />
At the top of the properties toolbox are the address fields. The address fields include the street name, city name, State (currently only in the United States) and country. To edit the address details, ''click'' the '''Edit''' button (or press the 'e' shortcut key). This enables editing of fields above it.<br />
<br />
[[Image:WMEAddressProp.png]]<br />
<br />
The Country (and State) fields may be updated by selecting a different country (or state) from the dropdown selections. Selections are provided only for countries (or states) that are present on other nearby road segments.<br />
<br />
The city and street names may be updated by typing a new name. See the [[Road types and names|naming guidelines]] for guidance on choosing the correct street name. As a name is typed, Waze provides a list of similar names. These similar entries can be selected by clicking them. If the segment is in a location outside a city, the "None" check box should be selected and the city name left blank. If the road does not have a name, the "None" check box should be selected and street name left blank. Entries must be present for each address property. To eliminate a city name or street name the appropriate "None" boxes must be checked. When complete, ''click'' the '''Apply''' button. If no changes are to be made, ''click'' the '''Cancel''' button.<br />
<br />
If the above Address Properties are not set for a segment, the road displays as a '''red line''' in the editing map only and does not appear in the Waze client app after the next update. This process is part of the road verification process. When the Waze client app uses the pave option, the road is created in the edited Waze map only. That Wazer or another Wazer who is editing the map in that area must set these properties in this section in order for the road to be seen in the client.<br />
<br />
=====Alternate street names=====<br />
The subsection '''Alternate street names:''' lists the other names associated with all currently highlighted segments. It does not isolate individual alternate names for each segment, so if you want to be sure all the highlighted segments have a specific alternate name add it all the segments. For any segments that already have the alternate name, it will not be duplicated.<br />
<br />
The hyperlink titled '''Add alternate name''' brings up two selection boxes for the City name and Street name. If the City name is not applicable, select the '''None''' check box. Enter the street name and press Apply or hit the '''Enter''' key on the keyboard. This adds that name to the currently highlighted segments.<br />
<br />
To delete an alternate street name, click the [[image:DeleteAltCB.png]] next to the alternate name to be deleted. This deletes the alternate name for the highlighted segments.<br />
<br />
A future version of the Waze Map Editor is being considered to include road shields as part of the alternate street name field.<br />
<br />
====Road Properties====<br />
<br />
Below the address properties on the General Tab are the road segment properties.<br />
<br />
=====Road Type=====<br />
<br />
The road type is changed by selecting the appropriate road type from the drop down box.<br />
[[Image:RoadTypeCB1.png]]<br />
<br />
See the [[Road types and names]] for your country for further guidance on selecting the correct road type.<br />
<br />
=====Toll Road=====<br />
<br />
Select the box for toll road if the segment meets the requirements as outlined under [[Best_map_editing_practice#Toll_roads|toll roads]].<br />
<br />
=====Road Direction=====<br />
<br />
The direction of the road is changed by selecting the appropriate direction from the drop down box.<br />
<br />
[[Image:RoadDirectionCB1.png]]<br />
<br />
If traffic may travel both ways on the road, select "Two way." If traffic may travel only one-way on the road in the direction from the [[image:ACB.png]] toward the [[image:BCB.png]] select "One way (A&rarr;B)." If traffic may travel only one-way on the road in the direction from the [[image:BCB.png]] toward the [[image:ACB.png]] select "One way (B&rarr;A)." <br />
<br />
After the road properties are saved, the direction is indicated by blue chevrons on the road.<br />
<br />
[[Image:OneWaySavedCB.png]]<br />
<br />
<br />
Base mapped roads are originally assigned the direction of unknown. When the direction is set to "Unknown", Waze automatically adjusts the directionality of the road as Wazers drive it. When editing, make every effort to determine the correct direction of the road and choose either "Two-way" or the appropriate "One-way" direction.<br />
<br />
See the article [[determining one-way streets]] for more information on determining the direction of a road as being one way or two way.<br />
<br />
=====Road elevation=====<br />
{{Anchor|Elevation}}<br />
The Road Elevation should be changed where one road passes over another. By default, the Elevation of a segment is '''Ground''' (zero). When two segments overlap but do not actually connect in the real world, the value of Elevation for each segment must be different. This ensures that the Waze problem detection system doesn't flag the spot where two segments overlap as a location where a junction might be needed. <br />
<br />
The visual representation of the relative Road Elevation is different when viewed in the Waze Map Editor (WME) and the Client application.<br />
<br />
1. The Client App displays segment elevation based on the road type only, meaning Freeways are always on top, Major Highways are next, followed by Minor Highways, Ramps next, Primary Streets below all those, and finally Streets are at the bottom. This is the same order seen when setting the road type in the editor.<br />
<br />
2. The WME uses the Road Elevation setting to display the relative elevation of the road. It displays the road with the highest "elevation" number at the top of the visual stack and works its way down as would be expected.<br />
<br />
Although the client application does not benefit from the Road Elevation setting, it is recommended to set the Road Elevation relative to the physical mapping in the real world to enable possible future Client application updates to show the same visual representation as the WME.<br />
<br />
3. Elevation -5 is used for non-drivable roads to help ensure that the routing engine does not try to connect or route drivers from roads onto non-roads by mistake. It acts to prevent false system reporting that the roads should be connected.<br />
<br />
<br />
See [[Overpasses,_Underpasses_and_Bridges|Bridges]] for more information on elevation.<br />
<br />
See [[Editing_rank#Locked_segments|Locked Segments]] for information on road ranks.<br />
<br />
====Locked Box====<br />
<br />
The segment is locked by checking the locked check box which is associated with the segments lock rank. For information on the effect of checking the locked box see [[FAQ#What is a locked road?|Locked Roads]].<br />
<br />
====Changing turn restrictions====<br />
<br />
Each intersection of two or more segments keeps track of the allowed directions you can turn from one segment to another. Changing these turn restrictions follows the same procedure as outlined above in the section on [[Creating and editing road segments#Set allowed turns .28connections.29|Set allowed turns]].<br />
<br />
====Separator line (disabled)====<br />
<br />
[[Image:SeparatorLine.png|right|150px]]The original map editor before the Waze Map Editor had the ability to add a black separator line down the middle of a road segment. It caused difficulty with map editing and was removed as a feature from the updated WME. There was a time when the line appeared in the WME, but could not be removed. It has since been disabled and no longer appears.{{clear}}<br />
<br />
==Roundabouts==<br />
See [[Roundabouts/USA]] for guidance on roundabouts or traffic circles.<br />
<br />
<br />
{{ReturnTo | Editing manual | the editing manual}}<br />
<br />
[[Category:Waze Map Editor]]<br />
[[Category:Convert to Subpages]]</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=Creating_and_editing_road_segments&diff=132311Creating and editing road segments2016-01-01T06:04:22Z<p>Qwaletee: /* Confirm the road by updating details */</p>
<hr />
<div><!--if the section parameter is defined, do not place the visible banner, only as the code block for the top of a section-->{{GlobalMark/visible}}<br />
<!--<br />
#####-----#####-----#####-----#####-----#####-----#####-----#####-----#####-----<br />
#### This page has been curated ####<br />
#### to be included in the new ####<br />
#### Wazeopedia - GLOBAL Wiki. ####<br />
#### Please do not make any ####<br />
#### edits on this page without ####<br />
#### PRIOR CONSENSUS in the Wiki ####<br />
#### Updates and Discussions ####<br />
#### forum thread for this page. ####<br />
#### If a specific forum thread ####<br />
#### for this page doesn't exist ####<br />
#### please start one. ####<br />
#### www.waze.com/forum/ ####<br />
#### viewforum.php?f=276 ####<br />
#####-----#####-----#####-----#####-----#####-----#####-----#####-----#####--><br />
<br />
{{ReturnTo | Editing manual | the editing manual}}<br />
<br />
This article covers creating and editing road segments. Be sure to read this whole article to ensure you fully understand all aspects of how segments operate in Waze before you start to create and edit roads on the map.<br />
<br />
==Creating a new road==<br />
If you find a road missing from the Waze map, such as a recent suburban development, follow the screenshots and instructions to add a road to Waze. The example is from Little Rock, Arkansas, USA, and we will add the missing roads in the highlighted area:<br />
<br />
[[Image:new_road_step_01_hilited.png|400px]]<br />
<br />
<br />
Zoom the map display so you can see the entire area where you need to add the road, if possible. Setting the zoom level appropriately allows you to follow the curves of the road as you draw it.<br />
<br />
There are five essential steps to add roads to the Waze map:<br />
# Draw the road.<br />
# Set or confirm the road properties.<br />
# Connect the road with junctions to existing segment(s) or another newly created segment(s).<br />
# Set allowed turns at junctions.<br />
# Save the changes.<br />
<br />
* [http://www.youtube.com/watch?&v=_Dlt7131dkc&hd=1 View a step-by-step video on how to add a road from an existing intersection]<br />
<br />
For more detail on creating road segments, see [[Map_Editing_Quick-start_Guide#Create_a_Road | Create a Road]].<br />
<br />
===Drawing the road===<br />
<br />
[[File:Create_Road_Drop_Down_Menu.png|left]] ''Hover'' the cursor over the curved road with a cross/plus sign icon at the top of the screen in the [[Map_Editor_Interface_and_Controls#The_Tool_Bar|toolbar]] and ''click'' '''Road'''. You can also use the [[keyboard shortcut]], which is the letter '''i''', for Insert. Move the cursor to the location you want to start drawing the road. This can be an empty location, or it can be on an existing segment where you want the intersection with this new road. The cursor has a small blue circle to indicate it is in drawing mode.<br />
<br />
When you hover over an existing segment, it highlights showing that if you click there, a junction is automatically added.<br />
<br />
[[Image:new_road_step_01.png]]<br />
<br />
Move your mouse along the path of the road, following the aerial view or GPS points for the new road. Every time you ''click'', a '''[[geometry node]]''' is added, aligning your new road with your cursor movement. When you reach the end location for the new road, ''double-click'' the mouse. You exit drawing mode, and the new road displays in orange to signify that it is unsaved. Don't worry if you made a mistake in drawing the shape of the road. Just click on the segment again and you can add, remove or reposition geometry nodes. If you want to remove the road just drawn, you can press the ESC key on the keyboard before you exit drawing mode.<br />
<br />
[[Image:new_road_step_02-04.png]]<br />
<br />
<br />
In our example, there is another road in this same view which is missing. We can add another road to the map without saving the first one. The next image shows the second road already added, and auto-junctioned to the first segment we just created.<br />
<br />
[[Image:new_road_step_05.png]]<br />
<br />
<br />
At this point, you can save the newly added roads if you wish. However, the process of properly adding the roads is not complete. All new roads are set as 1-way, with no associated city and no street name. Adding these details to the road is required before they show up in the Waze client app.<br />
<br />
'''Note''': When creating special roads like [[Roundabouts/USA|roundabout]]s and [[loop]]s, be sure to follow the special considerations for those roads in those linked sections.<br />
<br />
{{clear}}<br />
<br />
===Confirm the road by updating details===<br />
<br />
{{construction<br />
| contact = http://www.waze.com/forum/viewforum.php?f=276<br />
| contacttype = forum<br />
| draft = no<br />
| open = no<br />
| revision = yes<br />
| section = yes<br />
}}<br />
<br />
New road segment created via the app's "Pave road" function are not immediately displayed on the Waze app. They must first have city and street names confirmed, meaning that an editor adds that information. The editor will also have to connect them to the road network to make them usable.<br />
<br />
In the map editor, '''<span style="color:red;">roads are outlined in red</span> when city and street name properties have not been set''' (known as ''red roads'' or ''unconfirmed roads''). An editor should set the country; state (US only); city; street name; road type; and direction.<br />
<br />
{| class="wikitable" style="background:white; color:red; margin: 1em auto 1em auto" border="1" <br />
|-<br />
| Paved roads do not appear until being "touched" in the editor. This does not apply to roads created in the editor; when created in WME, roads can appear on the Waze app even if they are missing key properties.<br />
|-<br />
|}<br />
<br />
To confirm a road, select one or more segments with the mouse. You can add only one name at a time, but you can add it to multiple segments at the same time. Because of that, it is efficient to first select multiple segments that will share the same name, and then apply the name to them together. Notice below that for the first road there are now two one-way segments. This is because the second road we added has cut the original road into two segments.<br />
<br />
[[Image:confirm_roads_01.png]]<br />
<br />
[[Image:WMEGeneralTab.png|245px|border|right]] To edit the address details of the selected segment(s), find the phrase ''Unnamed segment'' in the upper left corner of the editor. There is a pencil icon next to it. Click the pencil icon. Make sure the Country and State values are correct. Next, enter the city and street name information. Sometimes, a segment is outside a municipality, or the municipality cannot be determined or is not relevant. If that is the case, then check the ''None'' box next to City. Similarly, some streets may not need a name, such as ramps, private roads, and parking lot roads. For those segments, use the ''None'' check box next to Street.<br />
<br />
Most [[Roundabouts/USA#Creating_a_roundabout_from_an_intersection|roundabouts]] also must not have a street name. Use the ''None'' box for them. This permits proper navigation instructions for the roundabout.<br />
<br />
[[File:RoadCrossDualCW.png|left|border|440px]]{{clear}}<br />
For segments that exist only to connect two one-way roads (''At-grade connectors''), do not name the segment. The city name is fine if the segment is clearly inside the city limits.<br />
<br />
When complete, click the '''Apply''' button. '''Important:''' If you do not click teh Aply button, your changes can be discarded by WME without warning. Please click the Apply button as soon as you finish entering information, so you do not lose your data.<br />
{{clear}}<br />
<br />
===Set Road Type, Direction, and Elevation===<br />
Set each of the fields [[Road types and names|Road Type]], Direction, and [[#Elevation|Elevation]]. For neighborhood streets in these examples, Street is appropriate, they are 2-way streets and they have no roads above or below them, so elevation '''Ground''' is correct. <br />
<br />
Review the article [[determining one-way streets]] for more information on directionality. <br />
<br />
* Please be aware the the directionality type 'Unknown' does not prevent Waze from routing onto a road. 'Unknown' really means 'Undefined'. When the direction is set to 'Unknown', Waze automatically adjust the directionality of the road as Wazers drive it. This is the initial directionality of all roads after a base map import. In addition, locking the segment does not prevent the directionality from changing on 'Unknown' roads as Wazers drive it.<br />
<br />
{{Clear}}<br />
You may choose to save now, but there is one more step before we can call this process complete: setting the allowed turns.<br />
<br />
===Set allowed turns (connections)===<br />
<br />
[[Image:new_road_turns_not_allowed.png|left]] We've added our roads and confirmed them, but we haven't set the legal directions to and from this segment. In the real world, there are barriers and signs which prevent travel in a certain direction, even though the roads connect to each other. In our suburban neighborhood example, none of these blockages exist, but our screenshot shows red arrows, meaning that Waze generally won't navigate that direction from the selected segment. Click on the red arrows to turn them green, and permit navigation in that direction. This needs to be done for each segment that is added to the map, as the default setting after connecting a new segment is to disallow all turns to the new segment.<br />
{{Clear}}<br />
In situations where not all turns are allowed, click on the arrow to turn it red for the disallowed direction from that segment. <br />
<br />
[[Image:select_junction.png|right]]If all turns are allowed at a junction, the fastest way to enable all turns is by selecting the junction and not the individual segments. ''Select'' the '''junction''' and it changes from an orange circle to a red circle with a white border. Note that if you have already selected a segment connected to that junction, click elsewhere on the map, or hit the ESC key to deselect that segment before you can select the junction.<br />
{{Clear}}<br />
<br />
[[Image:Junction_properties_example.png|left]] The Properties drawer shows action links for the selected junction. Depending on the current state of the junction, one or both of the links '''Allow all turns''' or '''Disallow all turns''' links appear. For example, if all turns are currently allowed, then only the '''Disallow all turns''' link appears.<br />
{{Clear}}<br />
To enable all turns at an intersection, ''click'' the '''Allow all turns''' link for the junction. Alternatively, you can use the keyboard shortcut '''w''' to allow all turns and the shortcut '''q''' to disallow all connections. A best practice when allowing all turns on a junction is to disallow all turns first, as it cleans up some legacy problems with the map.<br />
<br />
Other helpful turn arrow keyboard shortcuts are:<br />
<br />
{| class="Wikitable floatright"<br />
| '''Shift+Z''' - Toggles between: 1) showing the enabled and restricted turn arrows for the selected segment, and 2) showing all restricted turns (red arrows only) for every junction on the visible map (up to zoom level 4 or 500 ft in the lower left map legend).<br />
| [[File:ArrowShowAll1.png|130px|right]]<br />
| [[File:ArrowShowAll2.png|130px|right]]<br />
|}<br />
<br />
{| class="Wikitable floatright"<br />
| '''a''' - Toggles between making the turn restriction arrows directly selectable (opaque) or transparent. Transparency enables selecting objects below the arrow on the map.<br />
| [[File:ArrowTrans1.png|130px|right]]<br />
| [[File:ArrowTrans2.png|130px|right]]<br />
|}<br />
{| class="Wikitable floatright"<br />
| '''s''' - Toggles between separating turn arrows so they don't overlap or leaving them overlapping. This can also be used to refresh the screen when you have toggled visibility for all restricted turns, and you are modifying turn restrictions.<br />
| [[File:ArrowSpread1.png|130px|right]]<br />
| [[File:ArrowSpread2.png|130px|right]]<br />
|}<br />
<br />
To see all [[keyboard shortcuts]], press the '''?''' on the keyboard.<br />
<br />
When turns or parts of a road are restricted certain times of day or days of the week, you can use the [[Partial restrictions|scheduled restrictions]] feature.<br />
<br />
As the roads connecting to each other usually allow for all turn connection / direction, it is saves a lot of time for the editor to enable “draw new roads with all turns allowed” under the [[Map_Editor_Interface_and_Controls#Left_Pane|left pane]] “settings” tab during editing process. <br />
<br />
''See the section [[Map_Editing_Quick-start_Guide#Turn_restrictions_.28allowed_turns.29|turn restrictions]] for more information on all turn arrows.''<br />
<br />
{{Clear}}<br />
<br />
===Save===<br />
If you have saved your progress or not, ''click'' the '''Save''' button (or use the '''Ctrl + s''' keyboard shortcut) to send all of your updates to the Waze servers for processing. After the save is complete, and if there are no errors, you are presented with a view of the final product of this process:<br />
<br />
[[Image:new_road_final.png]]<br />
<br />
It is a good practice to save your changes often, and certainly when you get more than 10 unsaved changes pending. Sometimes you may run into a save error that you cannot determine what is wrong, and you have to '''undo''' many prior edits. Sometimes you have to undo all the way back to your first edit. Saving regularly limits chances of lost work in case of unresolvable errors.<br />
<br />
==Editing existing roads==<br />
Editing an existing road segment is not very different from creating a new road. Once a road is drawn from scratch, before it is saved, all of the editing functions described here work.<br />
<br />
===Adjusting road geometry (nodes)===<br />
{{construction<br />
| contact = http://www.waze.com/forum/viewforum.php?f=276<br />
| contacttype = forum<br />
| draft = no<br />
| open = no<br />
| revision = yes<br />
| section = yes<br />
}}<br />
<br />
Adjusting road geometry is changing the shape or appearance of a road segment. Real-world roads may be realigned, or mapped roads may be in the wrong place because the data from the basemap import was wrong. Sometimes we need to realign roads to improve navigation or spoken instructions in the Waze mobile app.<br />
<br />
The instructions here, while written for an existing road segment, also apply to a new road segment you just created, but have not yet saved. The editor treats them the same.<br />
<br />
[[Image:Adjust_geometry_1.png|320px|right]] To start adjusting the geometry of a segment, ''click'' on it. When you hover over the highlighted segment, [[Glossary#Geometry node|geometry nodes]] (<s>black squares</s> white circles) and [[Glossary#Geometry node|inter-geometry nodes]] (white dots circled in blue) display along the segment. Both of these are draggable so that you can reposition them wherever you need. When you drag an inter-geometry nodes from its default position half-way between two geometry nodes, it turns into a node.<br />
{{Clear}}<br />
[[Image:Adjust_geometry_2.png|320px|right]] To delete a node, ''hover'' the cursor over a node and hit the '''d''' key on the keyboard. This only works with nodes, not inter-geometry nodes. <br />
<br />
'''Tip: Straighten segments quickly'''<br />
If you have a segment that you need to clear all the geometry node quickly, select the segment and hold down the '''d''' key. Then move the mouse pointer near the geometry nodes you want to remove. With the '''d''' key held down it will automatically delete the node when the mouse hovers over it. To stop deleting nodes, stop pressing the '''d''' key.<br />
<br />
When you have a long, straight stretch of road, and there are geometry nodes located along its length, delete these nodes. It simplifies the road segment if you have to adjust it later, lightens the load on the database, and makes it easier to display on the Waze client app.<br />
<br />
{{Clear}}<br />
[[Image:Adjust_geometry_3.png|320px|right]] When your moves are complete, save, and the segment appears in the map with the new geometry.<br />
<br />
To see these operations in action, you can [http://youtu.be/Pm8zEmlD5bo?hd=1 watch a video of adjusting segment geometry].{{clear}}<br />
<br />
{{anchor|Fix the end-node on cul-de-sacs and dead-ends}}<br />
<br />
===Fix the end-node on culs-de-sac and dead-ends===<br />
{{Red|NOTE: The information shown in this section is only valid for segments which were paved from the Waze application. While they do NOT show in the editor when present, any segment drawn in the WME will have a junction node at its terminus.}}<br />
<br />
[[Image:FixDE-01.jpg|400px|right]]In order for the Waze Application to properly route from a location on a [[Junction_Style_Guide#Cul-de-sacs|cul-de-sac]] or dead-end road, the end of the last segment must have an end-node. Without this end-node, Waze gives the instruction ''Proceed to the highlighted route''. <br />
<br />
In the image to the right you can see a small blue diamond at the end of the long court, and no blue diamond at the end of the short court. The short court is missing an end-node at the end of the segment.{{clear}}<br />
<br />
[[Image:FixDE-02b.jpg|400px|left]][[Image:FixDE-02a.jpg|105px]]<br />
<br />
When you select each segment, putting them into an edit mode, you can see the difference between the two roads. The long court has the end-node (small white circle) and the short court has a geometry node (large black square) at the end of the segment.{{clear}}<br />
<br />
[[Image:FixDE-03.jpg|150px|left]]To add an end-node to the short court, a temporary road segment must be added to the current road. Start by not having the road selected (make sure it is white by clicking elsewhere on the map). ''Hover'' the cursor over the large + icon at the top of the screen in the [[Map_Editor_Interface_and_Controls#The_Tool_Bar|toolbar]] and ''click'' '''Road'''. You can also use the keyboard shortcut which is the letter '''i''', for Insert. Position the cursor so the blue circle appears at the end of the segment and Left-click the mouse to start the road.{{clear}}<br />
<br />
[[Image:FixDE-04.jpg|150px|left]][[Image:FixDE-06.jpg|150px|right]]<br />
Click some distance away from the end of the current road and double click to end road creation. Select the newly created segment and press the Delete key or the Trash Can icon from the toolbar.{{clear}}<br />
<br />
[[Image:FixDE-07.jpg|400px|left]]<br />
Save the changes and the result shows the small court now has the proper end-node as a small blue diamond (when not being edited or selected).<br />
<br />
Note that most cul-de-sac should not terminate in a roundabout or loop, but as a dead end as drawn here.{{clear}}<br />
<br />
===Junctions===<br />
Before making any change to a junction, be sure to review the [[Junction Style Guide]] for information on the best practices for creating junctions. There are many times when a junction may be drawn in a way that does not seem logical, but it is very important to the navigation engine in Waze. <br />
<br />
====Moving junctions====<br />
Moving a junction is as simple as dragging the junction to another location, however there are geometry nodes (the white circles seen when editing a segment) that might need to be moved or removed. <br />
<br />
[[Image:MoveJunc-1.png|200px|left]]First use the mouse to select the intersection of the road segments. This puts a red dot, circled in white, on the junction. This indicates you are moving '''all''' the segments connected to this junction. Note that if the red dot appears transparent, it means that one of the attached road segments is locked above your editing rank, and the junction cannot be moved by you. Release the mouse button and move the mouse away until the cursor appears as a 4-way crossed arrow [[Image:CrossedCursor.png|24px]]. <br />
{{clear}}<br />
[[Image:MoveJunc-2.png|right]]With the cursor as a crossed arrow, select the junction again and drag it to the desired location. The harsh angles in the segments in this example are caused by the geometry nodes and need to be adjusted. It is important to position the junction in a location that is not on top of a segment. This makes it difficult to adjust the geometry nodes, and in some cases tells the editor to merge junctions if one is present below the junction you are moving.<br />
{{clear}}<br />
[[Image:MoveJunc-3.png|left]]The black geometry nodes can be moved, removed, or added as explained in [[Creating and editing road segments#Adjusting road geometry .28nodes.29|detail above]]. Adjust them to align with the aerial views or the GPS tracks.<br />
<br />
{{clear}}<br />
===== Moving one junction onto another junction =====<br />
If two junctions are disconnected from each other, but should be joined into one junction, then dragging one of the junction nodes until it "snaps" to and connects to the other junction node will bring them together. <span style="color: red">Warning! Only use this technique if the two junctions are disconnected from each other. If there is a segment connecting the two, you could accidentally delete the segment in the process. This would also delete any traffic data and house numbers associated with the deleted segment.</span><br />
<br />
====Removing junctions with only two segments====<br />
There are times when only two segments are joined at a junction. In general this is not a problem, but it can slow down editing and it may be the source of incorrect turn restrictions and bad routing. So the best practice is to delete these junctions when found. However, it is very important to study the two segments before merging, to ensure the junction is not there for a purpose.<br />
<br />
{| class="wikitable unsortable" border="1"<br />
|-<br />
! Legitimate Reasons for Two-segment Junctions<br />
|- style="background:#FFFFFF; color:black"<br />
| {{:Necessary junctions}}<br />
|- <br />
|}<br />
<br />
Once you are certain there is no reason to have the extra junction, there are three methods to remove it. One method highlights the junction and deletes it, one highlights the two segments and bridges them together, and the last method drags one junction on top of the other junction.<br />
<br />
=====Delete key or trash can icon=====<br />
This method is the preferred method, because it enables the WME to alert you when there are legitimate differences between the segments. With the mouse select the junction point between the two segments. Look for the trash can icon at the upper right corner of the WME screen. If it appears press it to remove the junction. Alternatively, the Delete or Del key (not Backspace) removes the junction.<br />
<br />
Deletion of a node automatically places a geometry node at that point. If you need to remove the point, you can do so by highlighting the segment and hovering the mouse over the point of the prior junction. The WME displays the point and you can press the '''d''' key to remove it.<br />
<br />
If the trash can icon does not appear, something about those two segments is different, possibly the city name, street name, road type, or direction of travel.<br />
<br />
=====Bridge segments=====<br />
Generally do not use this method because it has two additional side effects that are not generally desired. <br />
# It increases the elevation of the resulting single segment by one.<br />
# It disconnects any other segments at that junction point, but leaves it directly below the geometry node potentially causing automated map problems if not moved.<br />
<br/><br />
[[Image:MergeJunc-2a.png|left|350px]]With the mouse, select one of the segments. Then, while holding down the multi-select key ('''Control''' for Windows/Linux and '''Command''' for Mac) select the second segment. If the two segments have the same properties including direction, a small bridge icon appears above the junction. Click the bridge to merge the two segments, eliminating the junction between them. A geometry node is placed where the junction was previously located. To remove the node (if necessary), select the segment and hover the mouse near the old junction. The geometry node should be displayed. Then, press the '''d''' key to remove the unwanted node.<br />
<br />
When the segments are '''different''', the bridge icon does '''not''' appear at the junction.{{clear}}<br />
<br />
====Cut a segment to create a new junction====<br />
If it is necessary to change road information in the middle of a segment (road name, direction, city, type, or other information changes at that point), you need to create a junction at that point. One way to do this is to create a new road connected to the previous road. Begin or end the new road on the previous road to create a new junction. Then delete the new road -- the junction remains, and the previous road segment has been cut at the point where you created and deleted the road.<br />
<br />
====Allow/Disallow connections====<br />
Changing the allowed and disallowed turns in a junction follows the same procedure for controlling them when updating a road segment [[Creating and editing road segments#Set allowed turns .28connections.29|described above]].<br />
<br />
===(Re)Moving a road from a junction===<br />
===Updating road details===<br />
The details of a road can be entered as discussed with regard to confirming the details of a new road above. The procedure is the same for updating the details of an existing road segment.<br />
<br />
To update details, first, select the segment(s) you need to update. Click on the segment and the segment turns blue.<br />
[[Image:SelectionCB1.png]]<br />
<br />
Multiple segments may be selected by holding down the modifier key and clicking additional segments. The modifier key for Mac is the command key, for Windows the control key and for Linux the control key. Each selected segment turns blue.<br />
[[Image:MultipleSelectionCB1.png]]<br />
<br />
Once selected, if the General tab is visible on the left side of the editor.<br />
<br />
[[Image:WMEGeneralTab.png]]<br />
<br />
====Address Properties====<br />
<br />
At the top of the properties toolbox are the address fields. The address fields include the street name, city name, State (currently only in the United States) and country. To edit the address details, ''click'' the '''Edit''' button (or press the 'e' shortcut key). This enables editing of fields above it.<br />
<br />
[[Image:WMEAddressProp.png]]<br />
<br />
The Country (and State) fields may be updated by selecting a different country (or state) from the dropdown selections. Selections are provided only for countries (or states) that are present on other nearby road segments.<br />
<br />
The city and street names may be updated by typing a new name. See the [[Road types and names|naming guidelines]] for guidance on choosing the correct street name. As a name is typed, Waze provides a list of similar names. These similar entries can be selected by clicking them. If the segment is in a location outside a city, the "None" check box should be selected and the city name left blank. If the road does not have a name, the "None" check box should be selected and street name left blank. Entries must be present for each address property. To eliminate a city name or street name the appropriate "None" boxes must be checked. When complete, ''click'' the '''Apply''' button. If no changes are to be made, ''click'' the '''Cancel''' button.<br />
<br />
If the above Address Properties are not set for a segment, the road displays as a '''red line''' in the editing map only and does not appear in the Waze client app after the next update. This process is part of the road verification process. When the Waze client app uses the pave option, the road is created in the edited Waze map only. That Wazer or another Wazer who is editing the map in that area must set these properties in this section in order for the road to be seen in the client.<br />
<br />
=====Alternate street names=====<br />
The subsection '''Alternate street names:''' lists the other names associated with all currently highlighted segments. It does not isolate individual alternate names for each segment, so if you want to be sure all the highlighted segments have a specific alternate name add it all the segments. For any segments that already have the alternate name, it will not be duplicated.<br />
<br />
The hyperlink titled '''Add alternate name''' brings up two selection boxes for the City name and Street name. If the City name is not applicable, select the '''None''' check box. Enter the street name and press Apply or hit the '''Enter''' key on the keyboard. This adds that name to the currently highlighted segments.<br />
<br />
To delete an alternate street name, click the [[image:DeleteAltCB.png]] next to the alternate name to be deleted. This deletes the alternate name for the highlighted segments.<br />
<br />
A future version of the Waze Map Editor is being considered to include road shields as part of the alternate street name field.<br />
<br />
====Road Properties====<br />
<br />
Below the address properties on the General Tab are the road segment properties.<br />
<br />
=====Road Type=====<br />
<br />
The road type is changed by selecting the appropriate road type from the drop down box.<br />
[[Image:RoadTypeCB1.png]]<br />
<br />
See the [[Road types and names]] for your country for further guidance on selecting the correct road type.<br />
<br />
=====Toll Road=====<br />
<br />
Select the box for toll road if the segment meets the requirements as outlined under [[Best_map_editing_practice#Toll_roads|toll roads]].<br />
<br />
=====Road Direction=====<br />
<br />
The direction of the road is changed by selecting the appropriate direction from the drop down box.<br />
<br />
[[Image:RoadDirectionCB1.png]]<br />
<br />
If traffic may travel both ways on the road, select "Two way." If traffic may travel only one-way on the road in the direction from the [[image:ACB.png]] toward the [[image:BCB.png]] select "One way (A&rarr;B)." If traffic may travel only one-way on the road in the direction from the [[image:BCB.png]] toward the [[image:ACB.png]] select "One way (B&rarr;A)." <br />
<br />
After the road properties are saved, the direction is indicated by blue chevrons on the road.<br />
<br />
[[Image:OneWaySavedCB.png]]<br />
<br />
<br />
Base mapped roads are originally assigned the direction of unknown. When the direction is set to "Unknown", Waze automatically adjusts the directionality of the road as Wazers drive it. When editing, make every effort to determine the correct direction of the road and choose either "Two-way" or the appropriate "One-way" direction.<br />
<br />
See the article [[determining one-way streets]] for more information on determining the direction of a road as being one way or two way.<br />
<br />
=====Road elevation=====<br />
{{Anchor|Elevation}}<br />
The Road Elevation should be changed where one road passes over another. By default, the Elevation of a segment is '''Ground''' (zero). When two segments overlap but do not actually connect in the real world, the value of Elevation for each segment must be different. This ensures that the Waze problem detection system doesn't flag the spot where two segments overlap as a location where a junction might be needed. <br />
<br />
The visual representation of the relative Road Elevation is different when viewed in the Waze Map Editor (WME) and the Client application.<br />
<br />
1. The Client App displays segment elevation based on the road type only, meaning Freeways are always on top, Major Highways are next, followed by Minor Highways, Ramps next, Primary Streets below all those, and finally Streets are at the bottom. This is the same order seen when setting the road type in the editor.<br />
<br />
2. The WME uses the Road Elevation setting to display the relative elevation of the road. It displays the road with the highest "elevation" number at the top of the visual stack and works its way down as would be expected.<br />
<br />
Although the client application does not benefit from the Road Elevation setting, it is recommended to set the Road Elevation relative to the physical mapping in the real world to enable possible future Client application updates to show the same visual representation as the WME.<br />
<br />
3. Elevation -5 is used for non-drivable roads to help ensure that the routing engine does not try to connect or route drivers from roads onto non-roads by mistake. It acts to prevent false system reporting that the roads should be connected.<br />
<br />
<br />
See [[Overpasses,_Underpasses_and_Bridges|Bridges]] for more information on elevation.<br />
<br />
See [[Editing_rank#Locked_segments|Locked Segments]] for information on road ranks.<br />
<br />
====Locked Box====<br />
<br />
The segment is locked by checking the locked check box which is associated with the segments lock rank. For information on the effect of checking the locked box see [[FAQ#What is a locked road?|Locked Roads]].<br />
<br />
====Changing turn restrictions====<br />
<br />
Each intersection of two or more segments keeps track of the allowed directions you can turn from one segment to another. Changing these turn restrictions follows the same procedure as outlined above in the section on [[Creating and editing road segments#Set allowed turns .28connections.29|Set allowed turns]].<br />
<br />
====Separator line (disabled)====<br />
<br />
[[Image:SeparatorLine.png|right|150px]]The original map editor before the Waze Map Editor had the ability to add a black separator line down the middle of a road segment. It caused difficulty with map editing and was removed as a feature from the updated WME. There was a time when the line appeared in the WME, but could not be removed. It has since been disabled and no longer appears.{{clear}}<br />
<br />
==Roundabouts==<br />
See [[Roundabouts/USA]] for guidance on roundabouts or traffic circles.<br />
<br />
<br />
{{ReturnTo | Editing manual | the editing manual}}<br />
<br />
[[Category:Waze Map Editor]]<br />
[[Category:Convert to Subpages]]</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=New_York/Notice/Main&diff=129259New York/Notice/Main2015-12-03T09:00:50Z<p>Qwaletee: Validator localization - easier read</p>
<hr />
<div><!-- This page is only transcluded into (displayed on) the main page for this state. See more detailed instructions below. --><noinclude>{{:USA/CommonState/ReturnPurge|{{SubPage2}}}}<br/></noinclude><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
{{Mbox|image=[[File:Validator NY Icon.png]]|text=The ''Validator'' script has special support for New York. It customizes Validator with our unique rules and needs, and adds three map resource buttons (for NYS Orthos GIS maps, NY DOT FC Viewer, and NYCityMap). Please install the localization script (along with WME Validator). Instructions are on the [[New York/Validator]] page.}}<br />
{{mbox|image=none|text=We are now including GHO avatars and displayed names in the [[#Area Managers|editor tables below]], please add your details ([[Template:AM/Editor|instructions are here]]) or ask someone to do it for you.<br><br />
[[User:PesachZ|PesachZ]] ([[User talk:PesachZ|talk]]) 07:04, 1 October 2015 (UTC)}}<br />
{{Mbox|image=none|text=If you edit in New York, please make sure you are listed in the [[#Area Managers|table below]].}}<br />
<!--<br />
-->See [[{{BasePage2}}/Notice]] for the archives of previous notices.<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Notice|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Notice]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=Highway_naming&diff=126287Highway naming2015-11-17T01:01:11Z<p>Qwaletee: Correct NJ state routes</p>
<hr />
<div>This table identifies the specific naming conventions used for the various highway types for each state in the Unites States. Details of the naming convention is on the [[Road names/USA|road naming]] page.<br />
<br />
All [[Road names/USA#United States Interstate Highway System|interstate highways (freeways)]] are named the same across all states, so they are not included in the table below.<br />
<br />
The state names are linked to the respective wiki page that provides specific editing guidelines (and other information) for that state. If the state link is red, there are no specific guidelines for that state yet. If you actively edit in that state consider creating that page and providing information to other editors in your state.<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
! State<br />
! [[Road names/USA#State highways|State Highway/Route<br/>(TTS=....)]]<br />
! [[Road names/USA#County highways and county roads|County Highway/Road]]<br />
! [[Road names/USA#Township highways and township roads|Township Highway/Road]]<br />
|-<br />
| [[Alabama]]<br />
| SR-xxx<br />
| CR-xxx<br />
|<br />
|-<br />
| [[Alaska]]<br />
| State Hwy xxx<br />
| County Hwy xxx<br />
|<br />
|-<br />
| [[Arizona]]<br />
| SR-xxx<br />
| CR-xxx<br />
|<br />
|-<br />
| [[Arkansas]]<br />
| State Hwy xxx<br />
| County Hwy xxx<br />
|<br />
|-<br />
| [[California]]<br />
| SR-xxx <br><small>(currently under discussion)</small><br />
| CR-xxx<br />
|<br />
|-<br />
| [[Colorado]]<br />
| SH-xxx<br><small>[http://www.waze.com/forum/viewtopic.php?f=566&t=49337 (SW Forum)] &<br>[http://www.waze.com/forum/viewtopic.php?f=654&t=55969 (CO Forum)]&<br>[https://www.waze.com/forum/viewtopic.php?f=654&t=114290 (CO Forum)]</small><br />
| CR-xxx<br />
|<br />
|-<br />
| [[Connecticut]]<br />
| SR-xxx<br />
| ''N/A'' <small>[http://en.wikipedia.org/wiki/County_highway#United_States (Wikipedia)] </small><br />
<br />
|<br />
|-<br />
| [[Delaware]]<br />
| SR-xxx <small>[http://www.waze.com/forum/viewtopic.php?f=575&t=54067 (Forum)] </small><br />
<br />
<br />
| ''N/A'' <small>[http://en.wikipedia.org/wiki/List_of_numbered_routes_in_Delaware (Wikipedia)] </small><br />
<br />
|<br />
|-<br />
| [[District of Columbia]]<br />
| DC-295<br/>(TTS="DC 295")<br />
| N/A<br />
|<br />
|-<br />
| [[Florida]]<br />
| SR-xxx<br />
| CR-xxx<br />
|<br />
|-<br />
| [[Georgia]]<br />
| SR-xxx<br />
| CR-xxx<br />
|<br />
|-<br />
| [[Hawaii]]<br />
| SR-xxx<br />
| CR-xxx<br />
|<br />
|-<br />
| [[Idaho]]<br />
| State Hwy xxx<br />
| County Hwy xxx<br />
|<br />
|-<br />
| [[Illinois]]<br />
| SR-xxx<br />
| CR-xxx<br />
|<br />
|-<br />
| [[Indiana]]<br />
| IN-xxx<br/>(TTS="Indiana xxx")<br />
| CR-xxx<br/>When signed "County Road xxx"<br />
|<br />
|-<br />
| [[Iowa]]<br />
| IA-xxx<br />(TTS="Iowa xxx")<br />
| CR-xxx<br />
|<br />
|-<br />
| [[Kansas]]<br />
| K-xxx<br/>(TTS="''kay'' xxx")<br />
| County Hwy xxx<br />
|<br />
|-<br />
| [[Kentucky]]<br />
| KY-xxx<br/>(TTS="Kentucky xxx")<br />
| <br />
|<br />
|-<br />
| [[Louisiana]]<br />
| LA-xxx<br/>(TTS="Louisiana xxx")<br />
| Parish Rd xxx<br />
|<br />
|-<br />
| [[Maine]]<br />
| State Rte xxx<br />
| County Rte xxx<br />
|<br />
|-<br />
| [[Maryland]]<br />
| MD-xxx<br/> (TTS="Maryland xxx")<br />
| N/A<br />
| <br />
|-<br />
| [[Massachusetts]]<br />
| SR-xxx<br />
| ''N/A''<br />
|<br />
|-<br />
| [[Michigan]]<br />
| M-xxx<br/>(TTS="''emm'' xxx")<br />
| CR-xxx<br />
|<br />
|-<br />
| [[Minnesota]]<br />
| MN-xxx<br />
(TTS="Minnesota xxx")<br />
| CH-xxx (Blue signs)<br/>CR-xxx (White signs)<br />
|<br />
|-<br />
| [[Mississippi]]<br />
| MS-xxx<br/>(TTS="Mississippi xxx")<br />
| CR-xxx<br />
|<br />
|-<br />
| [[Missouri]]<br />
| MO-xxx (Primary numbered)<br/>(TTS="Missouri xxx")<br/>State Hwy xxx (Sec lettered)<br/>cnsd. SH-xxx<br />
| CR-xxx<br />
|<br />
|-<br />
| [[Montana]]<br />
| State Hwy xxx<br />
| County Hwy xxx<br />
|<br />
|-<br />
| [[Nebraska]]<br />
| N-xxx<br />(TTS="Nebraska xxx")<br />L-xxx<br />(TTS="Nebraska Link xxx")<br />S-xxx<br />(TTS="Nebraska Spur xxx")<br />R-xxx<br />(TTS="Nebraska Recreation Road xxx")<br />
| CR-xxx<br />
|<br />
|-<br />
| [[Nevada]]<br />
| NV-xxx<br>(TTS="Nevada xxx")<br />
| CR-xxx<br />
|<br />
|-<br />
| [[New Hampshire]]<br />
| SR-xxx<br />
| County Hwy xxx<br />
|<br />
|-<br />
| [[New Jersey]]<br />
| SR-xxx<br>(TTS="State Route xxx")<br />
| CR-xxx<br />
|<br />
|-<br />
| [[New Mexico]]<br />
| SR-xxx<br />
| CR-xxx<br />
|<br />
|-<br />
| [[New York]]<br />
| NY-xxx<br>(TTS="New York xxx")<br />
| CR-xxx<br>(TTS="County Road xxx")<br />
|<br />
|-<br />
| [[North Carolina]]<br />
| NC-xxx<br>(TTS="North Carolina xxx")<br />
| ''N/A'' <small>[http://en.wikipedia.org/wiki/County_highway#United_States (Wikipedia)]</small><br />
|<br />
|-<br />
| [[North Dakota]]<br />
| ND-xxx<br>(TTS="North Dakota xxx")<br />
| County Hwy xxx<br />
|<br />
|-<br />
| [[Ohio]]<br />
| SR-xxx<br />
| CH-xxx (limited use) & CR-xxx<br />
| TH-xxx (limited use) & TR-xxx<br />
|-<br />
| [[Oklahoma]]<br />
| SH-xxx<br />
| CR-xxx<br />
|<br />
|-<br />
| [[Oregon]]<br />
| State Hwy xxx<br />
| County Hwy xxx<br />
|<br />
|-<br />
| [[Pennsylvania]]<br />
| SR-xxx<br />
| na<br />
|<br />
|-<br />
| [[Rhode Island]]<br />
| RI-xxx<br />
| N/A<br />
|<br />
|-<br />
| [[South Carolina]]<br />
| SC-xxx<br/>(TTS="South Carolina xxx")<br />
| S-##-xxx (secondary roads)<br>CR-xxx# (county routes)<br />
|<br />
|-<br />
| [[South Dakota]]<br />
| SD-xxx<br/>(TTS="South Dakota xxx")<br />
| CR-xxx<br />
|<br />
|-<br />
| [[Tennessee]]<br />
| TN-xxx<br/>(TTS="Tennessee xxx")<br />
| CR-xxx<br />
|<br />
|-<br />
| [[Texas]]<br />
| SH-xxx<br />
| CR-xxx<br />
|<br />
|-<br />
| [[Utah]]<br />
| SR-xxx<br />
| CR-xxx<br />
|<br />
|-<br />
| [[Vermont]]<br />
| VT-xxx<br/>(TTS="Vermont xxx")<br />
| CR-xxx<br />
|<br />
|-<br />
| [[Virginia]]<br />
| SR-xxx < 600 & 785 & 895, VA-xxx > 600<br/>(TTS="Virginia xxx")<br />
| N/A<br />
|<br />
|-<br />
| [[Washington]]<br />
| SR-xxx<br />
| CR-xxx<br />
|<br />
|-<br />
| [[West Virginia]]<br />
| WV-xxx<br>(TTS="West Virginia xxx")<br />
| CR-xxx<br />
|<br />
|-<br />
| [[Wisconsin]]<br />
| WIS-xxx<br/>(TTS="Wisconsin xxx")<br />
| CH-xxx<br />
|<br />
|-<br />
| [[Wyoming]]<br />
| State Hwy xxx<br />
| County Hwy xxx<br />
|<br />
|}<br />
<br />
<small>Note: Some states are in the process of considering a change and may be designated with '''cnsd'''.</small><br />
<br />
If you are an editor for a particular state that feels your state should consider a different format than you see above, please come to the [http://world.waze.com/forum/viewforum.php?f=129 US forums] and select the sub-forum region for your state. In that sub-forum start a discussion around making a change to the naming convention for your state and tell the reasons why you think it should be done. Once consensus is reached the change can be made here.<br />
<br />
General discussions on this page can be found in [http://world.waze.com/forum/viewtopic.php?f=276&t=42135 this thread].<br />
<br />
[[Category:USA]]</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=Template:Lock_Standard_State&diff=125600Template:Lock Standard State2015-11-11T19:14:53Z<p>Qwaletee: PR as synonym for AZ</p>
<hr />
<div><noinclude><br />
{{Documentation}}<br />
</noinclude><br />
<includeonly>{{#switch: {{uc:{{{1|}}}{{{st|}}}{{{ST|}}}{{{St|}}}{{{sT|}}}}}<br />
| CA = {{Locking Standard<br />
<!-- https://www.waze.com/forum/viewtopic.php?f=566&t=92230&hilit=lock+standard&start=10 --><br />
|title=Major Areas<br />
|title2=Remote Areas<br />
|title3=Northern Urban (per DwarfLord)<br />
|Fwy=5|Fwy2=4|PS=2|mH3=3}}<br />
| NM = {{Locking Standard | Fwy=5 | Ramp=5 | MH = 4 | mH = 3|PS=2}} <!--same link + state page--><br />
| NH<br />
| VT<br />
| MA<br />
| RI<br />
| CT<br />
| ME<br />
| NEW ENGLAND = {{Locking Standard<br />
<!-- per HO discussion with OrbitC same as NORTHEAST with special guidance --><br />
|title=Statewide<br />
|Fwy=5|Ramp=Highest rank of connected segment|MH=4|mH=3|PS=2<br />
|note=Exception: At the request of an AM (or other trusted local editor) a [[State Manager/USA | State Manager]] (SM) may optionally lower an entire area to facilitate local editing. Requests must be formally recorded in the [https://www.waze.com/forum/viewforum.php?f=622 US Unlock Forum], but can be discussed and pre-approved by an SM beforehand. The AM should request the locks be raised again to standard when the area has stabilized; the request should be made in the same thread where the unlock was originally requested. SMs should use caution when uplocking an area to standard: If the area is consistently locked below standard, it might have been granted such an exception, and should not be uplocked without verification.}}<br />
| NJ<br />
| DE<br />
| NORTHEAST = {{Locking Standard<br />
<!-- per forum discussion with OrbitC and old template --><br />
|title=Statewide<br />
|Fwy=5|Ramp=Highest rank of connected segment|MH=4|mH=3|PS=2}}<br />
<br />
| NY = {{Locking Standard<br />
|title=NYC Only<br />
|Fwy=5|Ramp=Highest rank of connected segment|MH=5|mH=4|PS=3|Street=1<br />
|title2=Everywhere Else<br />
|MH2=4|mH2=3|PS2=2}}<!--A/p wiki--><br />
| PA = {{Locking Standard<br />
<!--per HO discussion with OrbitC and PA state managers--><br />
|title=Statewide|Fwy=5|Ramp=Highest rank of connected segment|MH=3|mH=3|PS=2|Street=1|PLR=2{{ref|PLR}}|append={{note|PLR|1}}This rule should primarily apply to LARGE parking lots such as shopping malls/centers/plazas, tourist attractions/sports/music venues, large office buildings and schools/colleges.}}<!--A/p wiki--><br />
| TX = {{Locking Standard<br />
|lede=In Texas we have a set minimum standard for locking roads based on segment type. Any road of a certain segment type must be locked '''at least''' to the rank (level) in the chart below. Roads may be locked higher for protection and special situations (areas with construction, tricky design, frequent mistakes, imaging inaccuracies, and the like), but should not be locked lower. If you find a road locked to a higher level than its minimum, please leave it locked no lower than that level when you have finished editing.<br />
|title=Lock Level<br />
|Fwy=5<br />
|Ramp=Highest Rank of Connected Segment<br />
|MH=5<br />
|mH=4<br />
|PS=3<br />
|Street=Automatic (1)<br />
|Private=Inquire with RC or SM}}<br />
<br />
| UT<br />
| NV = {{Locking Standard <!-- As per State Forum discussions, SuperDave1426, 2015-01-28 --><br />
|title=Urban Areas<br />
|title2=Rural Areas<br />
|Fwy=5|Fwy2=4<br />
|Ramp=5|Ramp2=4<br />
|MH=3<br />
|mH=2<br />
|PS=2<br />
|Street=Automatic (1)<br />
|Private=Automatic (1)<br />
|PLR=Automatic (1)<br />
}}<br />
<br />
| MO = {{Locking Standard <!-- a/p BlueTiger68 MO SM --><br />
|title=Statewide|Fwy=5|Ramp=4|MH=3|mH=3|PS=2|Street=1}}<br />
<br />
| KS = {{Locking Standard <!-- autenil KS AM --><br />
|title=Statewide|Fwy=5|Ramp=4|MH=3|mH=3|PS=2|Street=Automatic (1)}}<br />
<br />
| MN = {{Locking Standard<br />
|title=Urban<ref>This includes any city over [http://www.city-data.com/city/Minnesota.html 6,000 people]</ref>|Fwy=5|Ramp=Highest rank of connected segments|MH=4|mH=3|PS=2<ref>Increase lock level to 3 if [[House_numbers|House Numbering]] is correct</ref>|Street=1<ref>Increase lock level to 2 if [[House_numbers|House Numbering]] is correct</ref><br />
|title2=Rural<ref>This includes any area considered a township or a small town</ref>|Fwy2=5|Ramp2=Highest rank of connected segments|MH2=3|mH2=2|PS2=2|Street2=1<ref>Increase lock level to 2 if [[House_numbers|House Numbering]] is correct</ref><br />
|lede=In {{RootPage2}} we have a set minimum standard for [[Best_map_editing_practice#Locking_Segments|locking roads]] based on the segment type. Any road of a certain segment type must be locked to '''at least''' the [[Your_Rank_and_Points#Map_Editing_Rank|rank (level)]] in the chart below. Roads may be locked higher for protection and special situations (areas with construction, tricky design, frequent mistakes, imaging inaccuracies, and the like), but should not be locked lower.<br />
<br />
A great time to implement these locks is while performing the [[Functional_Classification|FC Upgrade]] of an area. Lock the roads based on the type after they've been set to [[Road_types/USA#Quick_reference_chart|FC standards]].<br />
}}<br />
<br />
| WV = {{Locking Standard <!-- 2015-07-06, stephenr1966, as discussed within state --><br />
|caption=West Virginia Locking Rank Standard Guideline<br />
|Fwy=5|Ramp=4|MH=3|mH=2|PS=1<br />
|lede=Actual locks used may be more or less than values in the table below, depending on area circumstance<br />
Please consult RC, SM, or appropriate AM for guidance<br />
}}<br />
| VA = {{Locking Standard<br />
|caption=Virginia Locking Rank Standard Guideline<br />
|title=Urban|Fwy=5|MH=4|mH=3|PS=2<br />
|title2=Rural|MH2=3|mH2=2|PS2=1<br />
|lede=Actual locks used may be more or less than values in the table below, depending on area circumstance<br />
Please consult RC, SM, or appropriate AM for guidance<br />
}}<br />
| WASHDC = {{Locking Standard<br />
|caption=Washington, DC Locking Rank Standard Guideline<br />
|Fwy=5|MH=4|mH=3|PS=2<br />
|lede=Actual locks used may be more or less than values in the table below, depending on area circumstance<br />
Please consult RC, SM, or appropriate AM for guidance<br />
}}<br />
| SOUTHERN = {{Locking Standard<br />
|caption=Standard for locking roads in the southeast region:<br />
|Fwy=5|Ramp=5|MH=5|mH=4|PS=3<br />
|lede=<br />
There are some cases that do not adhere to this standard, such as military base gates (6), and any theme park type areas in Orlando (5/6).<br />
}}<br />
| PR<br />
| AZ = {{Locking Standard|title=Statewide|Fwy=5|Ramp=4|MH=4|mH=3|PS=2|Street=1}}<!-- a/p Fredo_p AZ SM--><br />
| OK = {{Locking Standard|title=Statewide|Fwy=5|Ramp=Highest rank of connected segment|MH=4|mH=3|PS=2|Street=1}}<br />
| MD = {{Locking Standard <!-- a/p Kodi, nzahn1 SMs --><br />
|title=Urban<br />
|title2=Rural<br />
|Fwy=5|Fwy2=4<br />
|Ramp=5|Ramp2=4<br />
|MH=3|MH2=2<br />
|mH=2<br />
|PS=2<br />
}}<br />
<br />
| MI = {{Locking Standard <br />
|caption=Michigan locking standard<br />
|title=Urban<br />
|title2=Rural<br />
|Fwy=5<br />
|Ramp=Highest rank of connected segment<br />
|MH=3<br />
|mH=2|mH2=3<br />
|PS=2<br />
}}<br />
<br />
| WI = {{Locking Standard<br />
|title=Statewide<br />
|Fwy=5|Ramp=Highest rank of connected segment|MH=3|mH=2|PS=2|Street=1<br />
|note=Exception: At the request of an AM (or other trusted local editor) a [[State Manager/USA | State Manager]] (SM) may optionally lower an entire area to facilitate local editing. Requests must be formally recorded in the [https://www.waze.com/forum/viewforum.php?f=622 US Unlock Forum], but can be discussed and pre-approved by an SM beforehand. The AM should request the locks be raised again to standard when the area has stabilized; the request should be made in the same thread where the unlock was originally requested. SMs should use caution when uplocking an area to standard: If the area is consistently locked below standard, it might have been granted such an exception, and should not be uplocked without verification.}}<br />
<br />
| SC = {{Locking Standard<br />
|title=Statewide|Fwy=5|PS=2<br />
|title2=Coastal|MH2=4|mH2=3<br />
|note=Certain areas may be locked higher than the above minimums. Please do not lower locks unless approved by the RC or a {{RootPage2}} SM.}} <!-- a/p crazycaveman SC SM --><br />
| ND = {{Locking Standard <!-- As per RC --><br />
|title=Statewide<br />
|Fwy=5<br />
|Ramp=4<br />
|MH=3<br />
|mH=3<br />
|PS=2<br />
|Street=1}}<br />
| = {{Mbox|type=critical|text={{Red|Error: The Lock Standard State template requires a state/province abbreviation or other equivalent; none was supplied, so no locking scheme can be generated}}}}<br />
| {{Mbox|type=critical|text={{Red|The Lock Standard State template cannot display the locking scheme because it does not recognize the state/province/region specified: {{{1|}}}{{{st|}}}{{{ST|}}}{{{St|}}}{{{sT|}}}}}}}<br />
}}</includeonly></div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=User:Ply8808/USA_Local_Champ_Activity_Status&diff=125537User:Ply8808/USA Local Champ Activity Status2015-11-11T16:41:34Z<p>Qwaletee: Rationalize the three background sections (lede, description, introduction), title case, and maybe a few other minor tweaks</p>
<hr />
<div>This page defines the commitments expected of a [Roles_and_responsibilities#Local_Champs|Local Champ]] in the United States. To retain the status of Local Champ, with its rights and privileges, Local Champs must continue to meet these commitments, or request a leave of absence.<br />
<br />
Champs requires a high level of commitment, leadership and staying informed/engaged in the waze community. They are expected to participate actively in the US Champ forum and voting process, in the US Champs Google Hangout, be well-informed on current policies and best practices, and actively engaged with the broad editor community. Champs also act as Waze ambassadors to that community, and should maintain a certain level of polish and finesse in their interactions.<br />
<br />
== Introduction ==<br />
<br />
The role of a USA Local Champ is hard earned and the title should be retained unless the champ chooses to step down or it has been determined that a champ can no longer serve in the role due to improper conduct of a champ, or an inability to remain engaged at the level described in this document.<br />
<br />
It is necessary to create two separate groups of USA Local Champs to achieve retaining the title and showing accountability of an active status, these two groups will be explained in detail below.<br />
*Local Champ Group (active)<br />
*Local Champ Emeritus Group (inactive)<br />
<br />
== Disclaimer ==<br />
<br />
The guidelines on this page are specific to the United States Local Champs and do not reflect any guidelines or expectations of other countries' Local Champs or the Global Champ Group.<br />
<br />
== Activity factors ==<br />
<br />
These factors will be used to determine active/inactive status:<br />
*Date of last wiki edit<br />
*Date of last forum post<br />
*Date of last forum visit<br />
<br />
== Process for Determination of Active/Inactive Status ==<br />
<br />
A spreadsheet will be available for USA Local Champs to review and monitor as to the status of the group and their own current status.<br />
<br />
The spreadsheet will be formulated to present the active/inactive status of each champ.<br />
<br />
The formulation will use the 3 factors above, will eliminate the factor of the longest inactivity and average the remaining 2 factors.<br />
<br />
Upon an average of 90 days of inactivity the champ will be moved to the Emeritus Group.<br />
<br />
Upon an average of 180 days of inactivity the champ will be removed from both groups, this will be considered a voluntary resignation.<br />
<br />
A USA Local Champ will be assigned as the moderator of the spreadsheet for a determined time frame (TBD), the moderator will be responsible for gathering the necessary factor information to input on spreadsheet on a (TBD) basis. The moderator assignment will rotate through the champ group as a champ project.<br />
<br />
== Spreadsheet moderator responsibilities ==<br />
<br />
The moderator will be responsible for input of the data of the factors above and adjusting for new or removed champs on the spreadsheet.<br />
<br />
Upon an average of 60 days of inactivity, the moderator will attempt contact of the inactive champ via PM and email and inquire about the champs inactivity, this will include an email to staff so they may attempt contact also.<br />
<br />
If no contact can be established, the moderator will inquire via topic post in the champ forum for information regarding the champ.<br />
<br />
Upon an average of 90 days of inactivity and no response from communication attempts the champ will be moved into the Emeritus Group and retain title, the moderator will inform champ group of loss of voting rights.<br />
<br />
Upon an average of 180 days of inactivity a champ will inform staff that the champ be removed from all champ groups and rank lowered to R5.<br />
<br />
== Champ Groups Defined ==<br />
<br />
*USA Local Champ Group:<br />
<br />
This is the group of USA Local Champs that are currently listed as active on the spreadsheet, average of factors being less than 90 days, and has full voting rights and access to champ forum.<br />
<br />
*USA Local Champ Emeritus Group:<br />
<br />
This is the group of USA Local Champs that are currently listed as inactive on the spreadsheet, average of factors being greater than 90 days, the voting rights are restricted and reestablishment to the active group only requires current activity in the determining factors.<br />
<br />
<br />
== USA Local Champ loss of title ==<br />
<br />
This guideline is specific to the activity of a champ.<br />
<br />
Upon an average of 180 days of inactivity a champ will be removed from all champ groups and rank lowered to R5, reestablishment will be the same as if the individual was starting the process of champ request from the beginning but should be recognized as holding the title previously.</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=User:CBenson/ParkingLot&diff=123942User:CBenson/ParkingLot2015-10-28T06:59:19Z<p>Qwaletee: Minor corrections and add a section for places (parking/gas)</p>
<hr />
<div>=== Parking Lots ===<br />
<br />
Mapping a [[Road types/USA#Parking Lot Road|parking lot road]] serves three purposes:<br />
<br />
*it allows Waze to provide door-to-door directions within the lot;<br />
*it allows the Waze to recognize that the client is off the main road, avoiding erroneous traffic reports.<br />
*using the special type prevents Waze from routing traffic through the parking lot.<br />
<br />
Parking lot segments are not related to the [[Places/Parking lot|Parking Lot Place type]], though they are sometimes used together.<br />
<br />
The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for through navigation. Waze applies a [[Routing penalties|transition penalty]] for leaving a Parking Lot Road segment to enter another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. It is advised not to mix road types within a parking lot to avoid triggering the transition penalty unnecessarily.<br />
<br />
==== Shopping Centers ====<br />
<br />
When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following:<br />
<br />
*Main entrances from the roads outside the parking lot<br />
*Lanes that run along storefronts<br />
*Lanes at the edge of the lot which run alongside public roads (prevents Wazers in the parking area from "snapping" to the public road, and then sending incorrect speed information it)<br />
*Primary travel lanes that serve to get people from one area of the lot to another<br />
<br />
Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[Shortcut key]] Shift-G) to see where traffic is concentrated to get a sense of what needs mapping.<br/>[[File:ParkingLotRoad ShoppingCenter.png|714px]]<br />
<br />
In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map.<br />
<br />
==== Small Parking Lots ====<br />
<br />
Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with one entrance and one exit could even be represented by a single segment running through the parking area (either a diagonal across the lot if it connects to roads on each side, or a single, flattened curve for strip mall-style lots with entrances and exit along the same road).<br />
<br />
To permit a route to be given to exit a small parking lot from the same point the parking lot was entered, u-turns may be enabled at the ends of the parking lot road. This is particularly relevant where a single parking lot segment connects two different street segments such as is common for many corner gas stations.<br />
<br />
==== Drive-Through Lots ====<br />
<br />
Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction Style Guide#Loops|loop using three segments]].''<br />
<br />
==== Two parking lots connected to the same street ====<br />
<br />
Bad routing can occur when two parking lots connect to the same street. This can happen, for example, where two lots face each other. If you connect both parking lots to the street using ''the same junction'' as the connection point for both, Waze will treat them as one parking lot. <br />
<br />
If there are no turn restrictions preventing routing across the street, Waze may route the driver through one parking lot to reach a destination in the other parking lot. Waze is designed to avoid such routes, but in this configuration, Waze does not apply the expected penalty - because crossing through the junction from one parking lot segment to the other is not considered a transition, even though there is also a street running through the junction. This may be most easily understood by looking at the example image below.<br />
<br />
If it is not legal to cross from one lot to the other, [[turn restrictions]] will prevent any sort of routing between the lots. However, if it is possible to route from one lot to the other, then a different method is required to prevent routing through one lot to reach the other. <br />
<br />
To be sure that Waze will apply the transition penalty when routing through one parking lot from another, the two parking lots must be isolated from the each other such that passing from one to the other requires driving over a standard road segment (not a parking lot road or [[Private road|private road]]). You should map a very short "stub" segment (5m/17ft) of a standard road segment. This segment will run from the junction to the entry/exit segment of one of the lots. With this configuration, exiting the parking lot will have a consistent penalty, whether the route exits the first parking lot to the street or the route leads to another parking lot at the same junction.<br />
<br />
Parking lots do not have to be across the street from each other. In a strip mall, if the exit segment of one business is joined to the entrance segment of the next business, the same problem can occur.<br />
<br />
===== Illustration =====<br />
<br />
For example, in the configuration shown below if routing from the west parking lot, there is no transition penalty to route through the gas station parking lot on the east side of the street if routing east on Riva Rd. Conversely, if routing to the west parking lot from Riva Rd. there is no transition penalty to use the gas station. <br />
<br />
[[File:PLA.png|center]] {{clear}}<br />
<br />
<br />
[[File:PLB.png|right]]This potential problem arises when two parking lots on opposite sides of a street connect at the same junction node on the street.{{clear}}<br />
[[File:PLC.png|right]]If this configuration causes routing problems it can be solved by changing the road type of one (or both) of the parking lot roads that intersect with the street.{{clear}}<br />
[[File:PLD.png|right]]A five meter or longer stub of a different road type will accomplish the same result.{{clear}}<br />
[[File:PLE.png|left]]If the street is a divided highway, then the road type of the crossover segment may be changed (this may also allow U-turns at the crossover segment).<br />
<br />
==== Parking lot places and gas stations====<br />
A parking lot road (PLR) is used for the purposes described above. A parking lot place is used to help drivers locate a destination to route to. In some cases, for large parking lots, it may also be used for visual identification on the map.<br />
<br />
Using one does not require using the other. Our policy, with a number of exceptions, is that most parking lots are not mapped as parking lot places. Unless the parking lot you are mapping falls into one of those exceptions, you may map its roadways as PLRs but not create a parking lot place. If you do create a parking lot place, it may be a place point or an area place (using the rules for Places). If it is a point place, it may or may not have any PLRs mapped for it, depending on whether Waze should provide drivers with useful directions within the lot. If it is an area place, you will probably map PLRs within it.<br />
<br />
Gas stations are always mapped, and are always an area place. You should map PLRs through them, using the rules described above for small parking lots.</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=User:CBenson/ParkingLot&diff=123696User:CBenson/ParkingLot2015-10-25T23:33:52Z<p>Qwaletee: </p>
<hr />
<div>=== Parking Lots ===<br />
<br />
Mapping a [[Road types/USA#Parking Lot Road|parking lot road]] serves three purposes:<br />
<br />
*it allows Waze to provide door-to-door directions within the lot;<br />
*it allows the Waze to recognize that the client is off the main road, avoiding erroneous traffic reports.<br />
*using the special type prevents Waze from routing traffic through the parking lot.<br />
<br />
Parking lot segments are not related to the .[[Places/Parking lot|Parking Lot Place type]].<br />
<br />
The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for through navigation. Waze applies a [[Routing penalties|transition penalty]] for leaving a Parking Lot Road segment to enter another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. It is advised not to mix road types within a parking lot to avoid triggering the transition penalty unnecessarily.<br />
<br />
==== Shopping Centers ====<br />
<br />
When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following:<br />
<br />
*Main entrances from the roads outside the parking lot<br />
*Lanes that run along storefronts<br />
*Lanes at the edge of the lot which run alongside public roads (prevents Wazers in the parking area from "snapping" to the public road, and then sending incorrect speed information it)<br />
*Primary travel lanes that serve to get people from one area of the lot to another<br />
<br />
Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[Shortcut key]] Shift-G) to see where traffic is concentrated to get a sense of what needs mapping.<br/>[[File:ParkingLotRoad ShoppingCenter.png|714px]]<br />
<br />
In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map.<br />
<br />
==== Small Parking Lots ====<br />
<br />
Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with one entrance and one exit could even be represented by a single segment running through the parking area (either a diagonal across the lot if it connects to roads on each side, or a single, flattened curve for strip mall-style lots with entrances and exit along the same road).<br />
<br />
Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn.<br />
<br />
==== Drive-Through Lots ====<br />
<br />
Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction Style Guide#Loops|loop using three segments]].''<br />
<br />
==== Two parking lots connected to the same street ====<br />
<br />
Bad routing can occur when two parking lots connect to the same street. This can happen, for example, where two lots face each other. If you connect both parking lots to the public road using ''the same junction'' as the connection point for both, Waze will treat them as one parking lot, and could route the driver from public roads through one parking lot to reach a destination in the other parking lot. Waze is designed to avoid such routes, but in this configuration, Waze does not apply the expected penalty - because crossing through the junction from one parking lot segment to the other is not considered a transition, even though there is also a public road running through the junction. This may be most easily understood by looking at the example image below.<br />
<br />
To be sure that Waze will apply the transition penalty when routing through one parking lot from another, the two parking lots must be isolated from the each other such that passing from one to the other requires driving over a standard road segment (not a parking lot road or [[Private road|private road]]). You should map a very short "stub" segment (5m/17ft) of the same type as the public road. This segment will run from teh junction to the entry/exit segment of one of the lots. With this configuration, exiting the parking lot will have a consistent penalty, whether the exit leads to the public road or to another parking lot.<br />
<br />
Parking lots do not have to be across the street from each other. In a strip mall, if the exit segment of one business is joined to the entrance segment of the next business, the same problem can occur.<br />
<br />
If it is not legal to cross from one lot to the other, the stub segment is not necessary, as you can put in [[turn restrictions]] to prevent any sort of routing between the lots.<br />
<br />
===== Illustration =====<br />
<br />
For example, in the configuration shown below if routing from the west parking lot, there is no transition penalty to route through the gas station parking lot on the east side of the street if routing east on Riva Rd. Conversely, if routing to the west parking lot from Riva Rd. there is no transition penalty to use the gas station. <br />
<br />
[[File:PLA.png|center]] {{clear}}<br />
<br />
<br />
[[File:PLB.png|right]]This potential problem arises when two parking lots on opposite sides of a street connect at the same junction node on the street.{{clear}}<br />
[[File:PLC.png|right]]If this configuration causes routing problems it can be solved by changing the road type of one (or both) of the parking lot roads that intersect with the street.{{clear}}<br />
[[File:PLD.png|right]]A five meter or longer stub of a different road type will accomplish the same result.{{clear}}<br />
[[File:PLE.png|left]]If the street is a divided highway, then the road type of the crossover segment may be changed (this may also allow U-turns at the crossover segment).</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=Edits_to_avoid/Do_not_panic&diff=123599Edits to avoid/Do not panic2015-10-25T02:21:57Z<p>Qwaletee: Note usage as template in comment, and restore lost line break</p>
<hr />
<div><!-- For transclusion in parent page--><br />
<br />
''It may be intimidating to see all the things that can be done wrong. Don't panic! This article includes a [[<noinclude>{{ROOTPAGENAME}}</noinclude>#OK|list of things that are generally safe and easy]] to edit for beginners.''</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=Edits_to_avoid/Do_not_panic&diff=123598Edits to avoid/Do not panic2015-10-25T02:20:10Z<p>Qwaletee: And make it compatible with transclusion in parent</p>
<hr />
<div>''It may be intimidating to see all the things that can be done wrong. Don't panic! This article includes a [[<noinclude>{{ROOTPAGENAME}}</noinclude>#OK|list of things that are generally safe and easy]] to edit for beginners.''</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=Edits_to_avoid/Do_not_panic&diff=123597Edits to avoid/Do not panic2015-10-25T02:12:00Z<p>Qwaletee: Remove Global wiki comment, fixed #OK link to point to parent</p>
<hr />
<div>''It may be intimidating to see all the things that can be done wrong. Don't panic! This article includes a [[../#OK|list of things that are generally safe and easy]] to edit for beginners.''</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=Junction_Style_Guide/Intersections&diff=122435Junction Style Guide/Intersections2015-10-15T15:57:04Z<p>Qwaletee: /* Avoiding U turns in box and partial box intersections */ Missing dash, old text in anchor</p>
<hr />
<div><!--if the section parameter is defined, do not place the visible banner, only as the code block for the top of a section-->{{GlobalMark/visible}}<br />
<!--<br />
#####-----#####-----#####-----#####-----#####-----#####-----#####-----#####-----<br />
#### This page has been curated ####<br />
#### to be included in the new ####<br />
#### Wazeopedia - GLOBAL Wiki. ####<br />
#### Please do not make any ####<br />
#### edits on this page without ####<br />
#### PRIOR CONSENSUS in the Wiki ####<br />
#### Updates and Discussions ####<br />
#### forum thread for this page. ####<br />
#### If a specific forum thread ####<br />
#### for this page doesn't exist ####<br />
#### please start one. ####<br />
#### www.waze.com/forum/ ####<br />
#### viewforum.php?f=276 ####<br />
#####-----#####-----#####-----#####-----#####-----#####-----#####-----#####--><br />
<br />
{{construction<br />
| contact = http://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7009939<br />
| contacttype = user<br />
| draft = yes<br />
| open = no<br />
| revision = yes<br />
| section = yes<br />
| talk = yes<br />
}}<br />
<br />
{{ReturnTo | Junction_Style_Guide | the Junction Style Guide}}<br />
<br />
== Three-way ==<br />
<br />
=== Right angles ===<br />
{| class="Wikitable floatright"<br />
| [[Image:Jct_3_90_ex.png|border]]<br />
| [[Image:Jct_3_90.png|border|x199px]]<br />
|}<br />
The simplest junctions often resemble a "T" and are considered diverging or branch roads. The branch road will normally meet the main road at nearly a 90 degree angle. This is the simplest situation to map, as the physical and logical views of the roads match up well.<br />
{{clear}}<br />
<br />
=== Odd angles ===<br />
{| class="Wikitable floatright"<br />
| [[Image:Jct_3_45_ex1.png|border]]<br />
| [[Image:Jct_3_45.png|border|x200px]]<br />
|}<br />
Some roads meet at odd angles. The initial urge will be to represent the junction as it is in the physical world - two lines running into each other at a sharp angle. But there are issues with this method.<br />
* Depending on the angle, the client may give a "Keep Right" instruction to the driver when a "Turn Right" instruction is more appropriate. If Minor Highways or above are involved, you will actually get an "''Exit'' Right" which can be confusing in many situations.<br />
* In some cases, no instruction will be given at all. In the worst case, the [[routing server]] may determine that it isn't possible to make a very sharp turn angle and not suggest the turn at all (in the example image, heading south, then turning left, to head east).<br />
* Automatic map errors may appear with turns from one direction as the path of the turning traffic is "too far" away from the actual junction (in this example, traveling south, then turning left to head east).<br />
{{clear}}<br />
<br />
{| class="Wikitable floatright"<br />
| [[Image:Jct_3_45_curve.png|border]]<br />
|}<br />
To eliminate ambiguity, map the junction from a logical point of view. Since basic "Turn Left" and "Turn Right" instructions are desired, tweak the intersecting angle so it resembles a basic 90 degree intersection. Add [[Glossary#Geometry node|geometry nodes]] to make the branch road leave the main road at close to 90 degrees, then gradually curve the road to match the true departure angle. This will produce a junction that logically works like a basic 90 degree junction, but it also fits the reality of the physical world.<br />
{{clear}}<br />
<br />
{| class="Wikitable floatleft"<br />
| [[Image:Jct_3_45_ex.png|200px|border]]<br />
|}<br />
Here is a completed real world example which provides the expected turn instructions and "catches" turns from all directions avoiding automatic problems for [[Map_Problems_in_Waze_Map_Editor#Missing_road|missing road]] when they are "too far apart."<br />
{{clear}}<br />
<br />
=== Name changes on straight path ===<br />
For conditions where the straight through route changes road names, it is important to identify which segment is drawn as the straight route and which is shown as the right turn from the main road. As the [[How_Waze_determines_turn_/_keep_/_exit_maneuvers|How Waze Determines turn/keep/exit maneuvers]] page explains, segment names and geometry are very important in determining what navigation instructions are given.<br />
<br />
[[Image:Jct_Y_ex_aerial.png|200px|right|border]]<br />
In this example to the right, the multi-lane surface street is known as Main Street to the west and Atlantic Ave. to the east. The name change occurs when Main St. branches off as a regular surface street. That is the human description, but a more technical description would be that Main St. travels in a perfectly straight line and Atlantic Ave. branches off of it. But if we map it that way in the editor, we create a major problem.<br />
{{clear}}<br />
<br />
[[Image:Jct_Y_ex_map_bad.png|200px|left|border]]<br />
Since the multi-lane segment of Main St. and the regular street segment of Main St. have the same name, the routing engine automatically considers that to be "straight". If the two sections line up in a straight line the way they appear from the sky, then we are reinforcing the idea that "straight" is Main St. to Main St. But as a typical driver would want, "straight" should be the path that remains on the multi-lane roadway, regardless of what name it uses.<br />
{{clear}}<br />
<br />
[[Image:Jct_Y_ex_map.png|200px|right|border]]<br />
To make sure the routing engine understands the proper treatment of the junction, we have to be deliberate with the segment geometry of all three involved segments. We end up with something like the image on the right. Now the geometric definition of straight is the multi-lane portion of Main St. onto Atlantic Ave., since we have made that transition as close to zero degrees as possible. The regular street portion of Main St. now branches off at an angle close to 90 degrees. The routing engine should recognize that a turn is required. So the result is that Main St. to Atlantic Ave. has no announced turn, and multi-lane Main St. to surface road Main St. has a turn announced. Exactly what most drivers would expect in the real world.<br />
<br />
=== Steep angles with exits and keep right or left ===<br />
{|<br />
|-<br />
| [[File:Jct ramp no geo.png|border|Jct ramp no geo.png]]<br />
| [[File:Jct ramp no geo arrow.png|border|Jct ramp no geo arrow.png]]<br />
|}<br />
<br />
A ramp from a highway is another good example where additional geometry nodes are helpful. Especially since most ramps diverge at a very small angle from the road. The drawback in this case is it may be hard to see and click on the turn restriction arrows in the editor.<br />
<br />
{|<br />
|-<br />
| [[File:Jct ramp w geo.png|border|Jct ramp w geo.png]]<br />
| [[File:Jct ramp w geo arrow.png|border|Jct ramp w geo arrow.png]]<br />
|}<br />
<br />
Therefore add one more geometry node to make the departure angle at the junction closer to 10 or 20 degrees. (dogleg) See the discussion on [[Junction Style Guide#Controlling Turn Instructions|controlling turn instructions]] for details on those angles. Now the arrows are visible and accessible. Note that also pressing '''s''' in the editor will '''s'''pread or '''s'''eparate the arrows at a junction, if a arrow is still difficult to reach. See the [[Keyboard shortcut|keyboard shortcuts]] article for more tips on other keys.<br />
<br />
With this adjusted angle, this junction now behaves as expected and the turn restrictions can be easily accessed. {{clear}}<br />
<br />
== Four-way ==<br />
<br />
=== Right angles ===<br />
{| class="Wikitable floatright"<br />
| [[Image:Jct_4_90_ex.png|border]]<br />
| [[Image:Jct_4_90.png|border|x200px]]<br />
|}<br />
The second simplest junction category is a "+" or "cross" four-way junction that intersects at 90 degrees. These roads are simple to map as the logical and physical views of the roads match up well. These instructions follow the similar guidelines and solve the same problems as [[Junction Style Guide/Diverging roads|diverging roads]].<br />
{{clear}}<br />
<br />
=== Odd angles ===<br />
{| class="Wikitable floatright"<br />
| [[Image:Jct_4_45_ex1.png|border]]<br />
| [[Image:Jct_4_45.png|border|x200px]]<br />
|}<br />
Similar to diverging roads that intersect at odd angles, crossing roads can do the same thing. When these intersections are mapped as seen here with these odd angles, complications can occur.<br />
{{clear}}<br />
<br />
{| class="Wikitable floatright"<br />
| [[Image:Jct_4_45_curve.png|border|x200px]]<br />
|}<br />
[[Glossary#Geometry_node|Geometry nodes]] bring the actual junction close to 90 degrees. [[Map_Editor_Interface_and_Controls#Zoom_Control|Zoom]] in to the intersection and add a single geometry node on each side as close to the junction point as possible. This will give the more desirable 90 degree angle, and it will still be virtually invisible to client app users making it look like the physical world. This image is what is seen when zoomed in as close as possible. Zoomed back out, it looks just like the map image showing the junction without any geometry nodes.<br />
{{clear}}<br />
<br />
{| class="Wikitable floatleft"<br />
| [[Image:Jct_4_45_ex.png|border]]<br />
|}<br />
Here is a real world example at a close zoom level where you can still see the geometry adjustment. With that adjustment in place, the junction will produce predictable turn left and right navigation instructions while the roads still appear to meet at the real-world angle in the client app.<br />
{{clear}}<br />
<br />
== {{anchor|Split road intersections}}Divided road intersections==<br />
Many of the principles stated above apply to intersections between divided roads. Usually, divided road intersections should look like the traffic lanes they represent. "Box" shaped intersections are easiest to draw, maintain, and to explain to other editors. Only use variations when they are needed.<br />
<br />
Read through the pros and cons of the intersection types below and select the best suited.<br />
<br />
{{NeedInfo|Insert examples of a divided road intersecting a two-way road, two divided roads intersecting each other, 3-way intersections involving divided roads, intersections where one road changes between divided/2-way at the intersection...}}<br />
<br />
=== Box and partial box intersections ===<br />
<br />
This type of intersection is most useful in intersections where the traffic queues in a median segment that is long enough to justify being mapped, especially if the one-way roads would have to deviate greatly from their physical location to meet in a single point for a bow tie. This also allows the map to route correctly while representing the actual geometry of the roads in real life, which is more intuitive to users.<br />
<br />
Do not use this type of junction if the crossbar will be less than {{:Segment length/Minimum}}. Waze has difficulty in capturing average speeds for short segments, especially in wide intersections where traffic travels a fairly curved path rather than sticking close to the segment. Add in the inaccuracy of many phone GPS units, and you may have a situation where the reported positions of some of the vehicles are never on the segment during the maneuver.<br />
<br />
When creating three way and four way intersections, if the cross street changes names at the junction, make sure that the segment(s) have no name. This will cause the segment to inherit the appropriate name depending on the direction of travel. This center segment will not be included when you choose "Select entire street".<br />
<br />
Three way divided road intersections are easier to edit accurately than four way intersections.<br />
<br />
{{NeedInfo|Insert examples: divided road ends at 2-way road (single point if both lefts are allowed and u turns are not); divided road ends at divided road ("triangle" in median if both lefts are allowed and u turns are not); 2-way road ends at divided road (easy).}}<br />
<br />
[[Image:3wayunsplitsplit.png]]<br />
<br />
If possible, lay out the intersection to resemble reality. When all divided-road U turns are allowed at an intersection, or when disallowed U turns are effectively restricted in Waze by existing restricted left turns already, use the guidance in this section.<br />
<br />
When a U turn must be restricted, but both of the left turns that make up that U turn are allowed on their own, follow the guidance in [[#Avoiding U turns|Avoiding U turns]] below.<br />
<br />
{{NeedInfo|Insert examples: divided road intersects a 2-way road (≠); two divided roads intersect (#); intersection where one road changes between divided/2-way at the intersection...}}<br />
<br />
{| class="wikitable"<br />
|-<br />
! Intersection style !! Example<br />
|-<br />
| A divided road intersecting a divided road. || [[Image:4waysplitsplit.png|300px]]<br />
|-<br />
| A divided road intersecting a 2-way road. || [[Image:4waysplitunsplit.png|300px]]<br />
|-<br />
| A transitioning (divided-2-way) road intersecting a 2-way road. || [[Image:Split_road_to_sinlge_road.png|300px]]<br />
|-<br />
| A transitioning (divided-2-way) road intersecting a divided road. || (image)<br />
|-<br />
| Be careful with your geometry – following the center of the actual road too closely can lead to rather high turn angles, and therefore possibly unwanted turn instructions. Keep it smooth. || [[Image:Transition.png|300px]]<br />
|}<br />
<br />
=== Bow tie ===<br />
{{Anchor|Bowtie}}<br />
<br />
[[File:Jct_bowtie.png|300px|thumbnail|right|Gaining control of turns by reducing the intersection to a single point.]]The "bow tie" intersection method makes it easy to take separate control of left turns and u-turns at divided-road intersections. It also allows Waze to correctly draw conclusions about where traffic queuing occurs.<br />
Use it only<br />
* at 4-way divided road intersections (between two divided roads, or between a divided road and a two-way road).<br />
* only when necessary to prevent u-turns while allowing left-hand turns.<br />
* The angles at the single bow tie intersection can reasonably be made 45 degrees or less. Otherwise, drivers going straight through will get an instruction to turn or stay right in [[right-hand traffic]] countries (turn or stay left in [[left-hand traffic]] countries)<br />
* Because of the awkward appearance of the bowtie, consider using other methods, such as the U-turn prevention mechanism immediately below. It is common for drivers to report map errors due to the appearance.<br />
<br />
=== Avoiding U-turns in box and partial box intersections ===<br />
{{anchor|Avoiding U turns|Avoiding U turns in box and partial box intersections}}<br />
{{:Routing penalties/Controlling U-turn penalties}}<br />
<br />
{{clear}}<br />
{{ReturnTo | Junction_Style_Guide | the Junction Style Guide}}<br />
[[Category:Style Guides]]</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=New_Jersey/Area_Managers/Main&diff=121440New Jersey/Area Managers/Main2015-10-08T04:46:09Z<p>Qwaletee: /*Area_Managers/Main*/ Add GHO labeling to first column</p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE -------------------------------<br />
------------------------------------------------------------------------------------<br />
--><noinclude>{{:USA/CommonState/ReturnPurge|{{#titleparts:{{PAGENAME}}|-1|-2}}}}</noinclude><includeonly><!--<br />
------------------------------------------------------------------------------------<br />
---- Area Managers: Cancel edit and use link on table next to "Area Managers". -----<br />
---- Other Area Editors: Cancel edit and use link on table next to "Other Area<br />
---- Editors". If does not exist, that section can be added from talk page.<br />
---- Country/State Managers: Continue.<br />
------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this <br />
---- state. When first setting up this page, remove the example users for Country<br />
---- and State managers. Area Managers are changed in a different section as noted<br />
---- above. When adding a new user, use the following template: <br />
{{AM/Editor|Username|Area Managed|Other Comment|badge1=x|badge2=x|badge3=x}}<br />
---- If any fields are skipped, ensure the first three pipe "|" characters are<br />
---- present. Note the badge1, badge2, badge3 entries are optional, and the "x"<br />
---- is replaced only by what is defined under: {{AM/Badge}}<br />
---- This link can be reached from http://wiki.waze.com/wiki/Template:AM/Badge or<br />
---- search the Wiki for: "Template:AM/Badge"<br />
<br />
----<br />
---- When adding a new user, place the new template based on Rank (highest first)<br />
---- and then alphabetical order in that rank.<br />
------------------------------------------------------------------------------------<br />
--------------------- AREA MANAGER TABLE BEGINS BELOW ------------------------------<br />
---------------------------- EDIT BELOW LINE ---------------------------------------<br />
-----------------------------------------------------------------------------------><br />
{{AM/Top|gho=yes}}<!-- Top of the table --><br />
{{AM/Country}}<!-- Defines the start of the country manager section --><br />
{{AM/Editor|orbitc|6|States of NJ, NY, DE, PA, CT, ME, MA, NH, RI, VT |Region 9 Northeast & 8 New England|badge1=RC|badge2=GC|badge3=MGC}}<br />
{{AM/Editor|Kobes1878|5|NJ, parts of NY|Resident of State|badge1=M|badge2=CM}}<br />
{{AM/Editor|PhantomSoul|5|NJ, NY|Resident of NJ|badge1=M|badge2=CM}}<br />
{{User:Qwaletee/AM}}<br />
{{AM/State}}<!-- Defines the start of the state manager section --><br />
{{AM/Editor|Fredo-p|5|Union County|AZ|badge1=SM}}<br />
{{AM/Editor|PleaseDriveFast|5|NJ|Resident of State|badge1=M|badge2=SM|badge3=mr}}<br />
{{AM/Editor|LeoKantus|4|NJ|Resident of State|badge1=SM}}<br />
{{AM/AreaLink}}<!-- Defines the start of the area manager section --><br />
{{#ifexist: {{BasePage2}}/AM/Editor/Area |<!--<br />
-->{{:{{BasePage2}}/AM/Editor/Area}}<!-- Area managers are edited through the main page link accessed from within the table itself. Do not add them here.--><br />
}}<!-- End ifexist --><br />
{{AM/Bottom}}<!-- Bottom of the table; must be the last line of table. -------------<br />
------------------------------------------------------------------------------------<br />
-->{{#ifexist: {{BasePage2}}/AM/Area2Link <!-- If other table exists --><br />
| {{:{{BasePage2}}/AM/Area2Link}}<!--then display Other Table, or skip --><br />
}}<!-- End ifexist --></includeonly><br />
<!-----------------------------------------------------------------------------------><br />
<!------------------------ DO NOT ADD CODE BELOW THE TABLE --------------------------></div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=User:Qwaletee/AM&diff=120509User:Qwaletee/AM2015-10-02T15:35:17Z<p>Qwaletee: Preview stuff</p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE -------------------------------<br />
------------------------------------------------------------------------------------<br />
--><noinclude>{{:USA/CommonState/ReturnPurge|{{#titleparts:{{PAGENAME}}|-1|-2}}}}</noinclude><xincludeonly><!--<br />
------------------------------------------------------------------------------------<br />
---- Area Managers: Cancel edit and use link on table next to "Area Managers". -----<br />
---- Other Area Editors: Cancel edit and use link on table next to "Other Area<br />
---- Editors". If does not exist, that section can be added from talk page.<br />
---- Country/State Managers: Continue.<br />
------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this <br />
---- state. When first setting up this page, remove the example users for Country<br />
---- and State managers. Area Managers are changed in a different section as noted<br />
---- above. When adding a new user, use the following template: <br />
{{AM/Editor|Username|Area Managed|Other Comment|badge1=x|badge2=x|badge3=x}}<br />
---- If any fields are skipped, ensure the first three pipe "|" characters are<br />
---- present. Note the badge1, badge2, badge3 entries are optional, and the "x"<br />
---- is replaced only by what is defined under: {{AM/Badge}}<br />
---- This link can be reached from http://wiki.waze.com/wiki/Template:AM/Badge or<br />
---- search the Wiki for: "Template:AM/Badge"<br />
<br />
----<br />
---- When adding a new user, place the new template based on Rank (highest first)<br />
---- and then alphabetical order in that rank.<br />
------------------------------------------------------------------------------------<br />
--------------------- AREA MANAGER TABLE BEGINS BELOW ------------------------------<br />
---------------------------- EDIT BELOW LINE ---------------------------------------<br />
-----------------------------------------------------------------------------------><br />
{{AM/Top|gho=yes}}<!-- Top of the table --><br />
{{AM/Country}}<!-- Defines the start of the country manager section --><br />
{{AM/Editor|orbitc|6|Entire State of VT, also DE, NY, NJ, PA. CT, ME, NH, RI, MA|Region 9 Northeast & 8 New England|gho=Orbit C|pic=File:Avatar OrbitC.jpg|badge1=RC|badge2=mr|badge3=GC|badge4=MGC}}<br />
<!--{{User:Qwaletee/AM|6}}--><onlyinclude>{{AM/Editor|Qwaletee|6|Very active in NJ and Metro NYC. SM for all of Northeast and New England regions.|Local Champ. Resident of NJ. SM NJ,NY,PA,New England. |badge1=M|badge2=LC|badge3=mr|badge4=CM|badge5=SM|gho=Dovid}}</onlyinclude><br />
{{AM/Editor|davielde|5|Statewide|Vermont State Manager (Michigan-based editor)|badge1=m|badge2=SM}}<br />
{{AM/Editor|Dmcrandall|5|Statewide|US CM, AZ & MA State Mgr.|gho=David|pic=File:Avatar Dmcrandall.jpg|badge1=m|badge2=cm|badge3=mr}}<br />
{{AM/Editor|MojaveCactusMonkey|5|Country Manager USA|SM of CT/RI & NV}}<br />
{{AM/State}}<!-- Defines the start of the state manager section --><br />
{{AM/Editor|davielde|5|Statewide|Vermont State Manager (Michigan-based editor)|badge1=m|badge2=SM}}<br />
{{AM/AreaLink}}<!-- Defines the start of the area manager section --><br />
{{#ifexist: {{BasePage2}}/AM/Editor/Area |<!--<br />
-->{{:{{BasePage2}}/AM/Editor/Area}}<!-- Area managers are edited through the main page link accessed from within the table itself. Do not add them here.--><br />
}}<!-- End ifexist --><br />
{{AM/Bottom}}<!-- Bottom of the table; must be the last line of table. -------------<br />
------------------------------------------------------------------------------------<br />
-->{{#ifexist: {{BasePage2}}/AM/Area2Link <!-- If other table exists --><br />
| {{:{{BasePage2}}/AM/Area2Link}}<!--then display Other Table, or skip --><br />
}}<!-- End ifexist --></xincludeonly><br />
<!-----------------------------------------------------------------------------------><br />
<!------------------------ DO NOT ADD CODE BELOW THE TABLE --------------------------></div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=Vermont/Area_Managers/Main&diff=120508Vermont/Area Managers/Main2015-10-02T15:13:38Z<p>Qwaletee: */Area manager table update*/</p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE -------------------------------<br />
------------------------------------------------------------------------------------<br />
--><noinclude>{{:USA/CommonState/ReturnPurge|{{#titleparts:{{PAGENAME}}|-1|-2}}}}</noinclude><includeonly><!--<br />
------------------------------------------------------------------------------------<br />
---- Area Managers: Cancel edit and use link on table next to "Area Managers". -----<br />
---- Other Area Editors: Cancel edit and use link on table next to "Other Area<br />
---- Editors". If does not exist, that section can be added from talk page.<br />
---- Country/State Managers: Continue.<br />
------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this <br />
---- state. When first setting up this page, remove the example users for Country<br />
---- and State managers. Area Managers are changed in a different section as noted<br />
---- above. When adding a new user, use the following template: <br />
{{AM/Editor|Username|Area Managed|Other Comment|badge1=x|badge2=x|badge3=x}}<br />
---- If any fields are skipped, ensure the first three pipe "|" characters are<br />
---- present. Note the badge1, badge2, badge3 entries are optional, and the "x"<br />
---- is replaced only by what is defined under: {{AM/Badge}}<br />
---- This link can be reached from http://wiki.waze.com/wiki/Template:AM/Badge or<br />
---- search the Wiki for: "Template:AM/Badge"<br />
<br />
----<br />
---- When adding a new user, place the new template based on Rank (highest first)<br />
---- and then alphabetical order in that rank.<br />
------------------------------------------------------------------------------------<br />
--------------------- AREA MANAGER TABLE BEGINS BELOW ------------------------------<br />
---------------------------- EDIT BELOW LINE ---------------------------------------<br />
-----------------------------------------------------------------------------------><br />
{{AM/Top|gho=yes}}<!-- Top of the table --><br />
{{AM/Country}}<!-- Defines the start of the country manager section --><br />
{{AM/Editor|orbitc|6|Entire State of VT, also DE, NY, NJ, PA. CT, ME, NH, RI, MA|Region 9 Northeast & 8 New England|gho=Orbit C|pic=File:Avatar OrbitC.jpg|badge1=RC|badge2=mr|badge3=GC|badge4=MGC}}<br />
{{User:Qwaletee/AM|6}}<br />
{{AM/Editor|davielde|5|Statewide|Vermont State Manager (Michigan-based editor)|badge1=m|badge2=SM}}<br />
{{AM/Editor|Dmcrandall|5|Statewide|US CM, AZ & MA State Mgr.|gho=David|pic=File:Avatar Dmcrandall.jpg|badge1=m|badge2=cm|badge3=mr}}<br />
{{AM/Editor|MojaveCactusMonkey|5|Country Manager USA|SM of CT/RI & NV}}<br />
{{AM/State}}<!-- Defines the start of the state manager section --><br />
{{AM/Editor|davielde|5|Statewide|Vermont State Manager (Michigan-based editor)|badge1=m|badge2=SM}}<br />
{{AM/AreaLink}}<!-- Defines the start of the area manager section --><br />
{{#ifexist: {{BasePage2}}/AM/Editor/Area |<!--<br />
-->{{:{{BasePage2}}/AM/Editor/Area}}<!-- Area managers are edited through the main page link accessed from within the table itself. Do not add them here.--><br />
}}<!-- End ifexist --><br />
{{AM/Bottom}}<!-- Bottom of the table; must be the last line of table. -------------<br />
------------------------------------------------------------------------------------<br />
-->{{#ifexist: {{BasePage2}}/AM/Area2Link <!-- If other table exists --><br />
| {{:{{BasePage2}}/AM/Area2Link}}<!--then display Other Table, or skip --><br />
}}<!-- End ifexist --></includeonly><br />
<!-----------------------------------------------------------------------------------><br />
<!------------------------ DO NOT ADD CODE BELOW THE TABLE --------------------------></div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=Rhode_Island/Area_Managers/Main&diff=120494Rhode Island/Area Managers/Main2015-10-02T06:27:18Z<p>Qwaletee: */Area manager table update*/</p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE -------------------------------<br />
------------------------------------------------------------------------------------<br />
--><noinclude>{{:USA/CommonState/ReturnPurge|{{#titleparts:{{PAGENAME}}|-1|-2}}}}</noinclude><includeonly><!--<br />
------------------------------------------------------------------------------------<br />
---- Area Managers: Cancel edit and use link on table next to "Area Managers". -----<br />
---- Other Area Editors: Cancel edit and use link on table next to "Other Area<br />
---- Editors". If does not exist, that section can be added from talk page.<br />
---- Country/State Managers: Continue.<br />
------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this <br />
---- state. When first setting up this page, remove the example users for Country<br />
---- and State managers. Area Managers are changed in a different section as noted<br />
---- above. When adding a new user, use the following template: <br />
{{AM/Editor|Username|Area Managed|Other Comment|badge1=x|badge2=x|badge3=x}}<br />
---- If any fields are skipped, ensure the first three pipe "|" characters are<br />
---- present. Note the badge1, badge2, badge3 entries are optional, and the "x"<br />
---- is replaced only by what is defined under: {{AM/Badge}}<br />
---- This link can be reached from http://wiki.waze.com/wiki/Template:AM/Badge or<br />
---- search the Wiki for: "Template:AM/Badge"<br />
<br />
----<br />
---- When adding a new user, place the new template based on Rank (highest first)<br />
---- and then alphabetical order in that rank.<br />
------------------------------------------------------------------------------------<br />
--------------------- AREA MANAGER TABLE BEGINS BELOW ------------------------------<br />
---------------------------- EDIT BELOW LINE ---------------------------------------<br />
-----------------------------------------------------------------------------------><br />
{{AM/Top}}<!-- Top of the table --><br />
{{AM/Country}}<!-- Defines the start of the country manager section --><br />
{{AM/Editor|AndyPoms|6|Statewide|Connecticut based USA Country Manager, covers Rhode Island as well|badge1=cm}}<br />
{{User:Qwaletee/AM|6}}<br />
{{AM/Editor|Dmcrandall|5|Statewide|US CM, AZ & MA State Mgr.|gho=David|pic=File:Avatar Dmcrandall.jpg|badge1=m|badge2=cm|badge3=mr}}<br />
{{AM/Editor|MojaveCactusMonkey|5|Statewide|Resident of NV, SM of CT/RI & NV|badge1=cm}}<br />
{{AM/State}}<!-- Defines the start of the state manager section --><br />
{{AM/Editor|GooberKing|4|Statewide|RI born and bred!|badge1=sm}}<br />
{{AM/Editor|TheLastTatertot|4|Statewide||badge1=sm|badge2=mr}}<br />
{{AM/AreaLink}}<!-- Defines the start of the area manager section --><br />
{{#ifexist: {{BasePage2}}/AM/Editor/Area |<!--<br />
-->{{:{{BasePage2}}/AM/Editor/Area}}<!-- Area managers are edited through the main page link accessed from within the table itself. Do not add them here.--><br />
}}<!-- End ifexist --><br />
{{AM/Bottom}}<!-- Bottom of the table; must be the last line of table. -------------<br />
------------------------------------------------------------------------------------<br />
-->{{#ifexist: {{BasePage2}}/AM/Area2Link <!-- If other table exists --><br />
| {{:{{BasePage2}}/AM/Area2Link}}<!--then display Other Table, or skip --><br />
}}<!-- End ifexist --></includeonly><br />
<!-----------------------------------------------------------------------------------><br />
<!------------------------ DO NOT ADD CODE BELOW THE TABLE --------------------------></div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=New_Hampshire/Area_Managers/Main&diff=120493New Hampshire/Area Managers/Main2015-10-02T06:25:58Z<p>Qwaletee: */Area manager table update*/</p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE -------------------------------<br />
------------------------------------------------------------------------------------<br />
--><noinclude>{{:USA/CommonState/ReturnPurge|{{#titleparts:{{PAGENAME}}|-1|-2}}}}</noinclude><includeonly><!--<br />
------------------------------------------------------------------------------------<br />
---- Area Managers: Cancel edit and use link on table next to "Area Managers". -----<br />
---- Other Area Editors: Cancel edit and use link on table next to "Other Area<br />
---- Editors". If does not exist, that section can be added from talk page.<br />
---- Country/State Managers: Continue.<br />
------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this <br />
---- state. When first setting up this page, remove the example users for Country<br />
---- and State managers. Area Managers are changed in a different section as noted<br />
---- above. When adding a new user, use the following template: <br />
{{AM/Editor|Username|Area Managed|Other Comment|gho=y|pic=File:Avatar z.png|badge1=x|badge2=x|badge3=x}}<br />
---- If any fields are skipped, ensure the first three pipe "|" characters are<br />
---- present. Note the badge1, badge2, badge3 entries are optional, and the "x"<br />
---- is replaced only by what is defined under: {{AM/Badge}}. The gho, and pic fields<br />
---- are optional, they can be used to display your Google Hangouts avatar and display<br />
---- name under your username. If you only use the gho field without the pic field,<br />
---- a generic color tile will be generated for you in Google style.<br />
---- The y in the gho field should be replaced with you GHO display name.<br />
---- The z in the pic field should be replaced with the link (not including brackets)<br />
---- to your avatar image on this wiki.<br />
---- This link can be reached from http://wiki.waze.com/wiki/Template:AM/Badge or<br />
---- search the Wiki for: "Template:AM/Badge"<br />
<br />
----<br />
---- When adding a new user, place the new template based on Rank (highest first)<br />
---- and then alphabetical order in that rank.<br />
------------------------------------------------------------------------------------<br />
--------------------- AREA MANAGER TABLE BEGINS BELOW ------------------------------<br />
---------------------------- EDIT BELOW LINE ---------------------------------------<br />
-----------------------------------------------------------------------------------><br />
{{AM/Top|gho=yes}}<!-- Top of the table --><br />
{{AM/Country}}<!-- Defines the start of the country manager section --><br />
{{AM/Editor|orbitc|6|New England Region|Region 9 Northeast & 8 New England|gho=Orbit C|pic=File:Avatar OrbitC.jpg|badge1=RC|badge2=mr|badge3=GC|badge4=MGC}}<br />
{{AM/Editor|karlcr9911|6|Statewide|SM of NH & TX / AM NYC / US Champ & WME Mentor|gho=karlcr9911|pic=File:Avatar karlcr9911.jpg|badge1=MLC|badge2=CM|badge3=MR}}<br />
{{User:Qwaletee/AM|6}}<br />
{{AM/Editor|Dmcrandall|5|Statewide|US CM, AZ & MA State Mgr.|gho=David|pic=File:Avatar Dmcrandall.jpg|badge1=m|badge2=cm|badge3=mr}}<br />
{{AM/Editor|MojaveCactusMonkey|5|Statewide|M of CT/RI & NV, Country Manager USA|gho=Martin|badge1=m|badge2=cm}}<br />
{{AM/State}}<!-- Defines the start of the state manager section --><br />
{{AM/Editor|karlcr9911|6|Statewide|SM of NH & TX / AM NYC / CM USA & WME Mentor|gho=karlcr9911|pic=File:Avatar karlcr9911.jpg|badge1=m|badge2=cm|}}<br />
{{AM/AreaLink}}<!-- Defines the start of the area manager section --><br />
{{#ifexist: {{BasePage2}}/AM/Editor/Area |<!--<br />
-->{{:{{BasePage2}}/AM/Editor/Area}}<!-- Area managers are edited through the main page link accessed from within the table itself. Do not add them here.--><br />
}}<!-- End ifexist --><br />
{{AM/Bottom}}<!-- Bottom of the table; must be the last line of table. -------------<br />
------------------------------------------------------------------------------------<br />
-->{{#ifexist: {{BasePage2}}/AM/Area2Link <!-- If other table exists --><br />
| {{:{{BasePage2}}/AM/Area2Link}}<!--then display Other Table, or skip --><br />
}}<!-- End ifexist --></includeonly><br />
<!-----------------------------------------------------------------------------------><br />
<!------------------------ DO NOT ADD CODE BELOW THE TABLE --------------------------></div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=Maine/Area_Managers/Main&diff=120491Maine/Area Managers/Main2015-10-02T05:53:01Z<p>Qwaletee: */Area manager table update*/</p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE -------------------------------<br />
------------------------------------------------------------------------------------<br />
--><noinclude>{{:USA/CommonState/ReturnPurge|{{#titleparts:{{PAGENAME}}|-1|-2}}}}</noinclude><includeonly><!--<br />
------------------------------------------------------------------------------------<br />
---- Area Managers: Cancel edit and use link on table next to "Area Managers". -----<br />
---- Other Area Editors: Cancel edit and use link on table next to "Other Area<br />
---- Editors". If does not exist, that section can be added from talk page.<br />
---- Country/State Managers: Continue.<br />
------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this <br />
---- state. When first setting up this page, remove the example users for Country<br />
---- and State managers. Area Managers are changed in a different section as noted<br />
---- above. When adding a new user, use the following template: <br />
{{AM/Editor|Username|Area Managed|Other Comment|badge1=x|badge2=x|badge3=x}}<br />
---- If any fields are skipped, ensure the first three pipe "|" characters are<br />
---- present. Note the badge1, badge2, badge3 entries are optional, and the "x"<br />
---- is replaced only by what is defined under: {{AM/Badge}}<br />
---- This link can be reached from http://wiki.waze.com/wiki/Template:AM/Badge or<br />
---- search the Wiki for: "Template:AM/Badge"<br />
<br />
----<br />
---- When adding a new user, place the new template based on Rank (highest first)<br />
---- and then alphabetical order in that rank.<br />
------------------------------------------------------------------------------------<br />
--------------------- AREA MANAGER TABLE BEGINS BELOW ------------------------------<br />
---------------------------- EDIT BELOW LINE ---------------------------------------<br />
-----------------------------------------------------------------------------------><br />
{{AM/Top}}<!-- Top of the table --><br />
{{AM/Country}}<!-- Defines the start of the country manager section --><br />
{{AM/Editor|Orbitc|6|Statewide|Regional Coordinator|badge1=rc|badge2=gc|badge3=mgc}}<br />
{{User:Qwaletee/AM|6}}<br />
{{AM/Editor|Dmcrandall|5|Statewide|US CM, AZ & MA State Mgr.|gho=David|pic=File:Avatar Dmcrandall.jpg|badge1=m|badge2=cm|badge3=mr}}<br />
{{AM/Editor|MojaveCactusMonkey|5|Country Manager USA|Available in ME. Also SM in CT/RI |badge1=sm|badge2=m}}<br />
{{AM/State}}<!-- Defines the start of the state manager section --><br />
{{AM/Editor|SkiDooGuy|6|Statewide|Non-Resident|badge1=rc|badge2=mlc|badge3=sm}}<br />
{{AM/AreaLink}}<!-- Defines the start of the area manager section --><br />
{{#ifexist: {{BasePage2}}/AM/Editor/Area |<!--<br />
-->{{:{{BasePage2}}/AM/Editor/Area}}<!-- Area managers are edited through the main page link accessed from within the table itself. Do not add them here.--><br />
}}<!-- End ifexist --><br />
{{AM/Bottom}}<!-- Bottom of the table; must be the last line of table. -------------<br />
------------------------------------------------------------------------------------<br />
-->{{#ifexist: {{BasePage2}}/AM/Area2Link <!-- If other table exists --><br />
| {{:{{BasePage2}}/AM/Area2Link}}<!--then display Other Table, or skip --><br />
}}<!-- End ifexist --></includeonly><br />
<!-----------------------------------------------------------------------------------><br />
<!------------------------ DO NOT ADD CODE BELOW THE TABLE --------------------------></div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=Massachusetts/Area_Managers/Main&diff=120490Massachusetts/Area Managers/Main2015-10-02T05:22:12Z<p>Qwaletee: */Area manager table update*/</p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE -------------------------------<br />
------------------------------------------------------------------------------------<br />
--><noinclude>{{:USA/CommonState/ReturnPurge|{{#titleparts:{{PAGENAME}}|-1|-2}}}}</noinclude><includeonly><!--<br />
------------------------------------------------------------------------------------<br />
---- Area Managers: Cancel edit and use link on table next to "Area Managers". -----<br />
---- Other Area Editors: Cancel edit and use link on table next to "Other Area<br />
---- Editors". If does not exist, that section can be added from talk page.<br />
---- Country/State Managers: Continue.<br />
------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this <br />
---- state. When first setting up this page, remove the example users for Country<br />
---- and State managers. Area Managers are changed in a different section as noted<br />
---- above. When adding a new user, use the following template: <br />
{{AM/Editor|Username|Area Managed|Other Comment|gho=y|pic=File:Avatar z.png|badge1=x|badge2=x|badge3=x}}<br />
---- If any fields are skipped, ensure the first three pipe "|" characters are<br />
---- present. Note the badge1, badge2, badge3 entries are optional, and the "x"<br />
---- is replaced only by what is defined under: {{AM/Badge}}. The gho, and pic fields<br />
---- are optional, they can be used to display your Google Hangouts avatar and display<br />
---- name under your username. If you only use the gho field without the pic field,<br />
---- a generic color tile will be generated for you in Google style.<br />
---- The y in the gho field should be replaced with you GHO display name.<br />
---- The z in the pic field should be replaced with the link (not including brackets)<br />
---- to your avatar image on this wiki.<br />
---- This link can be reached from http://wiki.waze.com/wiki/Template:AM/Badge or<br />
---- search the Wiki for: "Template:AM/Badge"<br />
<br />
----<br />
---- When adding a new user, place the new template based on Rank (highest first)<br />
---- and then alphabetical order in that rank.<br />
------------------------------------------------------------------------------------<br />
--------------------- AREA MANAGER TABLE BEGINS BELOW ------------------------------<br />
---------------------------- EDIT BELOW LINE ---------------------------------------<br />
-----------------------------------------------------------------------------------><br />
{{AM/Top|gho=yes}}<!-- Top of the table --><br />
{{AM/Country}}<!-- Defines the start of the country manager section --><br />
{{AM/Editor|orbitc|6|Entire State of MA, also DE, NY, NJ, PA. CT, ME, NH, RI, VT|Region 9 Northeast & 8 New England|gho=Orbit C|pic=File:Avatar OrbitC.jpg|badge1=RC|badge2=mr|badge3=GC|badge4=MGC}}<br />
{{User:Qwaletee/AM|6}}<br />
{{AM/Editor|Dmcrandall|5|Statewide|US CM, AZ & MA State Mgr.|gho=David|pic=File:Avatar Dmcrandall.jpg|badge1=m|badge2=cm|badge3=mr}}<br />
{{AM/Editor|MojaveCactusMonkey|5|Statewide|Also SM of CT/RI & Resident SM of NV}}<br />
{{AM/State}}<!-- Defines the start of the state manager section --><br />
{{AM/Editor|Dmcrandall|5|Statewide|US CM, AZ & MA State Mgr.|gho=David|pic=File:Avatar Dmcrandall.jpg|badge1=m|badge2=cm|badge3=mr}}<br />
{{AM/AreaLink}}<!-- Defines the start of the area manager section --><br />
{{#ifexist: {{BasePage2}}/AM/Editor/Area |<!--<br />
-->{{:{{BasePage2}}/AM/Editor/Area}}<!-- Area managers are edited through the main page link accessed from within the table itself. Do not add them here.--><br />
}}<!-- End ifexist --><br />
{{AM/Bottom}}<!-- Bottom of the table; must be the last line of table. -------------<br />
------------------------------------------------------------------------------------<br />
-->{{#ifexist: {{BasePage2}}/AM/Area2Link <!-- If other table exists --><br />
| {{:{{BasePage2}}/AM/Area2Link}}<!--then display Other Table, or skip --><br />
}}<!-- End ifexist --></includeonly><br />
<!-----------------------------------------------------------------------------------><br />
<!------------------------ DO NOT ADD CODE BELOW THE TABLE --------------------------></div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=Connecticut/Area_Managers/Main&diff=120489Connecticut/Area Managers/Main2015-10-02T05:21:17Z<p>Qwaletee: */Area manager table update*/</p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE -------------------------------<br />
------------------------------------------------------------------------------------<br />
--><noinclude>{{:USA/CommonState/ReturnPurge|{{#titleparts:{{PAGENAME}}|-1|-2}}}}</noinclude><includeonly><!--<br />
------------------------------------------------------------------------------------<br />
---- Area Managers: Cancel edit and use link on table next to "Area Managers". -----<br />
---- Other Area Editors: Cancel edit and use link on table next to "Other Area<br />
---- Editors". If does not exist, that section can be added from talk page.---- Country/State Managers: Continue.<br />
------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this <br />
---- state. When first setting up this page, remove the example users for Country<br />
---- and State managers. Area Managers are changed in a different section as noted<br />
---- above. When adding a new user, use the following template: <br />
{{AM/Editor|Username|Area Managed|Other Comment}}<br />
---- If any fields are skipped, ensure all three the pipe "|" characters are present.<br />
---- Note the badge1, badge2, badge3 entries are only what is defined under {{AM/Badge}}<br />
---- When adding a new user, place the new template based on Rank (highest first)<br />
---- and then alphabetical order in that rank.<br />
------------------------------------------------------------------------------------<br />
--------------------- AREA MANAGER TABLE BEGINS BELOW ------------------------------<br />
---------------------------- EDIT BELOW LINE ---------------------------------------<br />
-----------------------------------------------------------------------------------><br />
{{AM/Top}}<!-- Top of the table --><br />
{{AM/Country}}<!-- Defines the start of the country manager section --><br />
{{AM/Editor|orbitc|6|Region 8 New England Regional Coordinator||badge1=rc|badge2=mgc|badge3=gc}}<br />
{{User:Qwaletee/AM|6}}<br />
{{AM/Editor|Dmcrandall|5|Statewide|US CM, AZ & MA State Mgr.|gho=David|pic=File:Avatar Dmcrandall.jpg|badge1=m|badge2=cm|badge3=mr}}<br />
{{AM/Editor|MojaveCactusMonkey|5|Country Manager USA|Also SM in RI & NV}}<br />
{{AM/State}}<!-- Defines the start of the state manager section --><br />
{{AM/Editor|pumrum|5|Statewide|Also covers NYC}}<br />
{{AM/Editor|Jallen|4|Statewide|Also covers I-684 & Saw Mill River Parkway corridor in New York}}<br />
{{AM/AreaLink}}<!-- Defines the start of the area manager section --><br />
{{#ifexist: {{BasePage2}}/AM/Editor/Area |<!--<br />
-->{{:{{BasePage2}}/AM/Editor/Area}}<!-- Area managers are edited through the main page link accessed from within the table itself. Do not add them here.--><br />
}}<!-- End ifexist --><br />
{{AM/Bottom}}<!-- Bottom of the table; must be the last line of table. -------------<br />
------------------------------------------------------------------------------------<br />
-->{{#ifexist: {{BasePage2}}/AM/Area2Link <!-- If other table exists --><br />
| {{:{{BasePage2}}/AM/Area2Link}}<!--then display Other Table, or skip --><br />
}}<!-- End ifexist --></includeonly><br />
<!-----------------------------------------------------------------------------------><br />
<!------------------------ DO NOT ADD CODE BELOW THE TABLE --------------------------></div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=Pennsylvania/Area_Managers/Main&diff=120488Pennsylvania/Area Managers/Main2015-10-02T05:18:29Z<p>Qwaletee: */Area manager table update*/ Sort</p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE -------------------------------<br />
------------------------------------------------------------------------------------<br />
--><noinclude>{{:USA/CommonState/ReturnPurge|{{#titleparts:{{PAGENAME}}|-1|-2}}}}</noinclude><includeonly><!--<br />
------------------------------------------------------------------------------------<br />
---- Area Managers: Cancel edit and use link on table next to "Area Managers". -----<br />
---- Other Area Editors: Cancel edit and use link on table next to "Other Area<br />
---- Editors". If does not exist, that section can be added from talk page.<br />
---- Country/State Managers: Continue.<br />
------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this <br />
---- state. When first setting up this page, remove the example users for Country<br />
---- and State managers. Area Managers are changed in a different section as noted<br />
---- above. When adding a new user, use the following template: <br />
{{AM/Editor|Username|Area Managed|Other Comment|badge1=x|badge2=x|badge3=x}}<br />
---- If any fields are skipped, ensure the first three pipe "|" characters are<br />
---- present. Note the badge1, badge2, badge3 entries are optional, and the "x"<br />
---- is replaced only by what is defined under: {{AM/Badge}}<br />
---- This link can be reached from http://wiki.waze.com/wiki/Template:AM/Badge or<br />
---- search the Wiki for: "Template:AM/Badge"<br />
<br />
----<br />
---- When adding a new user, place the new template based on Rank (highest first)<br />
---- and then alphabetical order in that rank.<br />
------------------------------------------------------------------------------------<br />
--------------------- AREA MANAGER TABLE BEGINS BELOW ------------------------------<br />
---------------------------- EDIT BELOW LINE ---------------------------------------<br />
-----------------------------------------------------------------------------------><br />
{{AM/Top}}<!-- Top of the table --><br />
{{AM/Country}}<!-- Defines the start of the country manager section --><br />
{{AM/Editor|jondrush|6|USA|Resident of state|badge1=cm}}<br />
{{AM/Editor|MGODLEW|6|All of Pennsylvania||badge1=cm|badge2=M|badge3=lc}}<br />
{{User:Qwaletee/AM}}<br />
{{AM/Editor|attheyard|5|Chester County|mainly in Maryland|badge1=cm}}<br />
{{AM/Editor|mpawlicki|5|||badge1=cm}}<br />
{{AM/Editor|svance92|5|||badge1=cm}}<br />
{{AM/State}}<!-- Defines the start of the state manager section --><br />
{{AM/Editor|no1uknow|5|All of Pennsylvania||badge1=SM|badge2=M}}<br />
{{AM/Editor|DrNeubie|4|All of Pennsylvania|badge1=SM}}<br />
{{AM/Editor|voludu2|4|All of Pennsylvania|badge1=SM}}<br />
{{AM/AreaLink}}<!-- Defines the start of the area manager section --><br />
{{#ifexist: {{BasePage2}}/AM/Editor/Area |<!--<br />
-->{{:{{BasePage2}}/AM/Editor/Area}}<!-- Area managers are edited through the main page link accessed from within the table itself. Do not add them here.--><br />
}}<!-- End ifexist --><br />
{{AM/Bottom}}<!-- Bottom of the table; must be the last line of table. -------------<br />
------------------------------------------------------------------------------------<br />
-->{{#ifexist: {{BasePage2}}/AM/Area2Link <!-- If other table exists --><br />
| {{:{{BasePage2}}/AM/Area2Link}}<!--then display Other Table, or skip --><br />
}}<!-- End ifexist --></includeonly><br />
<!-----------------------------------------------------------------------------------><br />
<!------------------------ DO NOT ADD CODE BELOW THE TABLE --------------------------></div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=User:Qwaletee/AM&diff=120487User:Qwaletee/AM2015-10-02T05:16:33Z<p>Qwaletee: Rank, too</p>
<hr />
<div>{{AM/Editor|Qwaletee|6|NJ, Metro NYC; Fairly active through Northeast and New England|LC. SM NJ,NY,PA,New England. Resident of NJ. |badge1=M|badge2=LC|badge3=mr|badge4=CM|badge5=SM|gho=Dovid}}</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=Pennsylvania/Area_Managers/Main&diff=120486Pennsylvania/Area Managers/Main2015-10-02T05:16:12Z<p>Qwaletee: */Area manager table update*/</p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE -------------------------------<br />
------------------------------------------------------------------------------------<br />
--><noinclude>{{:USA/CommonState/ReturnPurge|{{#titleparts:{{PAGENAME}}|-1|-2}}}}</noinclude><includeonly><!--<br />
------------------------------------------------------------------------------------<br />
---- Area Managers: Cancel edit and use link on table next to "Area Managers". -----<br />
---- Other Area Editors: Cancel edit and use link on table next to "Other Area<br />
---- Editors". If does not exist, that section can be added from talk page.<br />
---- Country/State Managers: Continue.<br />
------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this <br />
---- state. When first setting up this page, remove the example users for Country<br />
---- and State managers. Area Managers are changed in a different section as noted<br />
---- above. When adding a new user, use the following template: <br />
{{AM/Editor|Username|Area Managed|Other Comment|badge1=x|badge2=x|badge3=x}}<br />
---- If any fields are skipped, ensure the first three pipe "|" characters are<br />
---- present. Note the badge1, badge2, badge3 entries are optional, and the "x"<br />
---- is replaced only by what is defined under: {{AM/Badge}}<br />
---- This link can be reached from http://wiki.waze.com/wiki/Template:AM/Badge or<br />
---- search the Wiki for: "Template:AM/Badge"<br />
<br />
----<br />
---- When adding a new user, place the new template based on Rank (highest first)<br />
---- and then alphabetical order in that rank.<br />
------------------------------------------------------------------------------------<br />
--------------------- AREA MANAGER TABLE BEGINS BELOW ------------------------------<br />
---------------------------- EDIT BELOW LINE ---------------------------------------<br />
-----------------------------------------------------------------------------------><br />
{{AM/Top}}<!-- Top of the table --><br />
{{AM/Country}}<!-- Defines the start of the country manager section --><br />
{{AM/Editor|jondrush|6|USA|Resident of state|badge1=cm}}<br />
{{User:Qwaletee/AM}}<br />
{{AM/Editor|Qwaletee|5|Metro NY|NY, NJ|badge1=m|badge2=SM|badge3=mr|badge4=cm|gho=Dovid}}<br />
{{AM/Editor|attheyard|5|Chester County|mainly in Maryland|badge1=cm}}<br />
{{AM/Editor|MGODLEW|6|All of Pennsylvania||badge1=cm|badge2=M|badge3=lc}}<br />
{{AM/Editor|mpawlicki|5|||badge1=cm}}<br />
{{AM/Editor|svance92|5|||badge1=cm}}<br />
{{AM/State}}<!-- Defines the start of the state manager section --><br />
{{AM/Editor|no1uknow|5|All of Pennsylvania||badge1=SM|badge2=M}}<br />
{{AM/Editor|voludu2|4|All of Pennsylvania|badge1=SM}}<br />
{{AM/Editor|DrNeubie|4|All of Pennsylvania|badge1=SM}}<br />
{{AM/AreaLink}}<!-- Defines the start of the area manager section --><br />
{{#ifexist: {{BasePage2}}/AM/Editor/Area |<!--<br />
-->{{:{{BasePage2}}/AM/Editor/Area}}<!-- Area managers are edited through the main page link accessed from within the table itself. Do not add them here.--><br />
}}<!-- End ifexist --><br />
{{AM/Bottom}}<!-- Bottom of the table; must be the last line of table. -------------<br />
------------------------------------------------------------------------------------<br />
-->{{#ifexist: {{BasePage2}}/AM/Area2Link <!-- If other table exists --><br />
| {{:{{BasePage2}}/AM/Area2Link}}<!--then display Other Table, or skip --><br />
}}<!-- End ifexist --></includeonly><br />
<!-----------------------------------------------------------------------------------><br />
<!------------------------ DO NOT ADD CODE BELOW THE TABLE --------------------------></div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=New_York/Area_Managers/Main&diff=120485New York/Area Managers/Main2015-10-02T05:13:57Z<p>Qwaletee: Templatized name entry</p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE -------------------------------<br />
------------------------------------------------------------------------------------<br />
--><noinclude>{{:USA/CommonState/ReturnPurge|{{#titleparts:{{PAGENAME}}|-1|-2}}}}</noinclude><includeonly><!--<br />
------------------------------------------------------------------------------------<br />
---- Area Managers: Cancel edit and use link on table next to "Area Managers". -----<br />
---- Other Area Editors: Cancel edit and use link on table next to "Other Area<br />
---- Editors". If does not exist, that section can be added from talk page.<br />
---- Country/State Managers: Continue.<br />
------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this <br />
---- state. When first setting up this page, remove the example users for Country<br />
---- and State managers. Area Managers are changed in a different section as noted<br />
---- above. When adding a new user, use the following template: <br />
{{AM/Editor|Username|Area Managed|Other Comment|gho=y|pic=File:Avatar z.png|badge1=x|badge2=x|badge3=x}}<br />
---- If any fields are skipped, ensure the first three pipe "|" characters are<br />
---- present. Note the badge1, badge2, badge3 entries are optional, and the "x"<br />
---- is replaced only by what is defined under: {{AM/Badge}}. The gho, and pic fields<br />
---- are optional, they can be used to display your Google Hangouts avatar and display<br />
---- name under your username. If you only use the gho field without the pic field,<br />
---- a generic color tile will be generated for you in Google style.<br />
---- The y in the gho field should be replaced with you GHO display name.<br />
---- The z in the pic field should be replaced with the link (not including brackets)<br />
---- to your avatar image on this wiki.<br />
---- This link can be reached from http://wiki.waze.com/wiki/Template:AM/Badge or<br />
---- search the Wiki for: "Template:AM/Badge"<br />
<br />
----<br />
---- When adding a new user, place the new template based on Rank (highest first)<br />
---- and then alphabetical order in that rank.<br />
------------------------------------------------------------------------------------<br />
--------------------- AREA MANAGER TABLE BEGINS BELOW ------------------------------<br />
---------------------------- EDIT BELOW LINE ---------------------------------------<br />
-----------------------------------------------------------------------------------><br />
{{AM/Top|gho=yes}}<!-- Top of the table --><br />
{{AM/Country}}<!-- Defines the start of the country manager section --><br />
{{AM/Editor|orbitc|6|Entire State of NY, also DE, NJ, PA. CT, ME, MA, NH, RI, VT|Region 9 Northeast & 8 New England|gho=Orbit C|pic=File:Avatar OrbitC.jpg|badge1=RC|badge2=mr|badge3=GC|badge4=MGC}}<br />
{{AM/Editor|PesachZ|6|Bronx, Brooklyn, Manhattan, also active in some parts of NJ|NY|gho=PesachZ|pic=File:Avatar PesachZ.jpg|badge1=mr|badge2=lc|badge3=mlc|badge4=sm}}<br />
{{User:Qwaletee/AM}}<br />
{{AM/Editor|PhantomSoul|5|Hudson Valley and the Catskills|NJ|badge1=M|badge2=cm|badge3=SM|gho=George|pic=File:Avatar PhantomSoul.jpg}}<br />
{{AM/Editor|karlcr9911|6|Statewide|AM NYC / SM TX & NH / US Champ, CM, & WME Mentor|gho=karlcr9911|pic=File:Avatar karlcr9911.jpg|badge1=MLC|badge2=cm|badge3=MR}}<br />
{{AM/State}}<!-- Defines the start of the state manager section --><br />
{{AM/Editor|Fredo-p|5|Staten Island|AZ|badge1=SM}}<br />
{{AM/Editor|ialangford|5|NYC|SC and Los Angeles|badge1=SM}}<br />
{{AM/Editor|MojaveCactusMonkey|5|Manhattan & 5 boroughs area|NV,CT,RI|badge1=M|badge2=SM}}<br />
{{AM/Editor|Pumrum|5|Bronx, Manhattan, Queens|CT|badge1=M|badge2=SM}}<br />
{{AM/Editor|Joyriding|4|Statewide|NY|badge1=mr|badge2=sm}}<br />
{{AM/Editor|Shaq23|4|Brooklyn and parts of NJ|NY|badge1=SM}}<br />
{{AM/AreaLink}}<!-- Defines the start of the area manager section --><br />
{{#ifexist: {{BasePage2}}/AM/Editor/Area |<!--<br />
-->{{:{{BasePage2}}/AM/Editor/Area}}<!-- Area managers are edited through the main page link accessed from within the table itself. Do not add them here.--><br />
}}<!-- End ifexist --><br />
{{AM/Bottom}}<!-- Bottom of the table; must be the last line of table. -------------<br />
------------------------------------------------------------------------------------<br />
-->{{#ifexist: {{BasePage2}}/AM/Area2Link <!-- If other table exists --><br />
| {{:{{BasePage2}}/AM/Area2Link}}<!--then display Other Table, or skip --><br />
}}<!-- End ifexist --></includeonly><br />
<!-----------------------------------------------------------------------------------><br />
<!------------------------ DO NOT ADD CODE BELOW THE TABLE --------------------------></div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=User:Qwaletee/AM&diff=120484User:Qwaletee/AM2015-10-02T05:12:35Z<p>Qwaletee: Add badges and GHO</p>
<hr />
<div>{{AM/Editor|Qwaletee|5|NJ, Metro NYC; Fairly active through Northeast and New England|LC. SM NJ,NY,PA,New England. Resident of NJ. |badge1=M|badge2=LC|badge3=mr|badge4=CM|badge5=SM|gho=Dovid}}</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=New_Jersey/Area_Managers/Main&diff=120483New Jersey/Area Managers/Main2015-10-02T05:07:08Z<p>Qwaletee: Templatized name entry</p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE -------------------------------<br />
------------------------------------------------------------------------------------<br />
--><noinclude>{{:USA/CommonState/ReturnPurge|{{#titleparts:{{PAGENAME}}|-1|-2}}}}</noinclude><includeonly><!--<br />
------------------------------------------------------------------------------------<br />
---- Area Managers: Cancel edit and use link on table next to "Area Managers". -----<br />
---- Other Area Editors: Cancel edit and use link on table next to "Other Area<br />
---- Editors". If does not exist, that section can be added from talk page.<br />
---- Country/State Managers: Continue.<br />
------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this <br />
---- state. When first setting up this page, remove the example users for Country<br />
---- and State managers. Area Managers are changed in a different section as noted<br />
---- above. When adding a new user, use the following template: <br />
{{AM/Editor|Username|Area Managed|Other Comment|badge1=x|badge2=x|badge3=x}}<br />
---- If any fields are skipped, ensure the first three pipe "|" characters are<br />
---- present. Note the badge1, badge2, badge3 entries are optional, and the "x"<br />
---- is replaced only by what is defined under: {{AM/Badge}}<br />
---- This link can be reached from http://wiki.waze.com/wiki/Template:AM/Badge or<br />
---- search the Wiki for: "Template:AM/Badge"<br />
<br />
----<br />
---- When adding a new user, place the new template based on Rank (highest first)<br />
---- and then alphabetical order in that rank.<br />
------------------------------------------------------------------------------------<br />
--------------------- AREA MANAGER TABLE BEGINS BELOW ------------------------------<br />
---------------------------- EDIT BELOW LINE ---------------------------------------<br />
-----------------------------------------------------------------------------------><br />
{{AM/Top}}<!-- Top of the table --><br />
{{AM/Country}}<!-- Defines the start of the country manager section --><br />
{{AM/Editor|orbitc|6|States of NJ, NY, DE, PA, CT, ME, MA, NH, RI, VT |Region 9 Northeast & 8 New England|badge1=RC|badge2=GC|badge3=MGC}}<br />
{{AM/Editor|Kobes1878|5|NJ, parts of NY|Resident of State|badge1=M|badge2=CM}}<br />
{{AM/Editor|PhantomSoul|5|NJ, NY|Resident of NJ|badge1=M|badge2=CM}}<br />
{{User:Qwaletee/AM}}<br />
{{AM/State}}<!-- Defines the start of the state manager section --><br />
{{AM/Editor|Fredo-p|5|Union County|AZ|badge1=SM}}<br />
{{AM/Editor|PleaseDriveFast|5|NJ|Resident of State|badge1=M|badge2=SM|badge3=mr}}<br />
{{AM/Editor|LeoKantus|4|NJ|Resident of State|badge1=SM}}<br />
{{AM/AreaLink}}<!-- Defines the start of the area manager section --><br />
{{#ifexist: {{BasePage2}}/AM/Editor/Area |<!--<br />
-->{{:{{BasePage2}}/AM/Editor/Area}}<!-- Area managers are edited through the main page link accessed from within the table itself. Do not add them here.--><br />
}}<!-- End ifexist --><br />
{{AM/Bottom}}<!-- Bottom of the table; must be the last line of table. -------------<br />
------------------------------------------------------------------------------------<br />
-->{{#ifexist: {{BasePage2}}/AM/Area2Link <!-- If other table exists --><br />
| {{:{{BasePage2}}/AM/Area2Link}}<!--then display Other Table, or skip --><br />
}}<!-- End ifexist --></includeonly><br />
<!-----------------------------------------------------------------------------------><br />
<!------------------------ DO NOT ADD CODE BELOW THE TABLE --------------------------></div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=User:Qwaletee/AM&diff=120482User:Qwaletee/AM2015-10-02T05:05:45Z<p>Qwaletee: Initial create. Table entry for state page AM list.</p>
<hr />
<div>{{AM/Editor|Qwaletee|5|NJ, Metro NYC|LC. SM NJ,NY,PA,New Engalnd. Resident of NJ.|badge1=M|badge2=LC|badge3=mr}}</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=New_Jersey/Area_Managers/Main&diff=120481New Jersey/Area Managers/Main2015-10-02T05:03:19Z<p>Qwaletee: */Area manager table update*/</p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE -------------------------------<br />
------------------------------------------------------------------------------------<br />
--><noinclude>{{:USA/CommonState/ReturnPurge|{{#titleparts:{{PAGENAME}}|-1|-2}}}}</noinclude><includeonly><!--<br />
------------------------------------------------------------------------------------<br />
---- Area Managers: Cancel edit and use link on table next to "Area Managers". -----<br />
---- Other Area Editors: Cancel edit and use link on table next to "Other Area<br />
---- Editors". If does not exist, that section can be added from talk page.<br />
---- Country/State Managers: Continue.<br />
------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this <br />
---- state. When first setting up this page, remove the example users for Country<br />
---- and State managers. Area Managers are changed in a different section as noted<br />
---- above. When adding a new user, use the following template: <br />
{{AM/Editor|Username|Area Managed|Other Comment|badge1=x|badge2=x|badge3=x}}<br />
---- If any fields are skipped, ensure the first three pipe "|" characters are<br />
---- present. Note the badge1, badge2, badge3 entries are optional, and the "x"<br />
---- is replaced only by what is defined under: {{AM/Badge}}<br />
---- This link can be reached from http://wiki.waze.com/wiki/Template:AM/Badge or<br />
---- search the Wiki for: "Template:AM/Badge"<br />
<br />
----<br />
---- When adding a new user, place the new template based on Rank (highest first)<br />
---- and then alphabetical order in that rank.<br />
------------------------------------------------------------------------------------<br />
--------------------- AREA MANAGER TABLE BEGINS BELOW ------------------------------<br />
---------------------------- EDIT BELOW LINE ---------------------------------------<br />
-----------------------------------------------------------------------------------><br />
{{AM/Top}}<!-- Top of the table --><br />
{{AM/Country}}<!-- Defines the start of the country manager section --><br />
{{AM/Editor|orbitc|6|States of NJ, NY, DE, PA, CT, ME, MA, NH, RI, VT |Region 9 Northeast & 8 New England|badge1=RC|badge2=GC|badge3=MGC}}<br />
{{AM/Editor|Kobes1878|5|NJ, parts of NY|Resident of State|badge1=M|badge2=CM}}<br />
{{AM/Editor|PhantomSoul|5|NJ, NY|Resident of NJ|badge1=M|badge2=CM}}<br />
{{AM/Editor|Qwaletee|5|NJ, Metro NYC|LC. SM NJ,NY,PA,New Engalnd. Resident of NJ.|badge1=M|badge2=LC|badge3=mr}}<br />
{{AM/State}}<!-- Defines the start of the state manager section --><br />
{{AM/Editor|Fredo-p|5|Union County|AZ|badge1=SM}}<br />
{{AM/Editor|PleaseDriveFast|5|NJ|Resident of State|badge1=M|badge2=SM|badge3=mr}}<br />
{{AM/Editor|LeoKantus|4|NJ|Resident of State|badge1=SM}}<br />
{{AM/AreaLink}}<!-- Defines the start of the area manager section --><br />
{{#ifexist: {{BasePage2}}/AM/Editor/Area |<!--<br />
-->{{:{{BasePage2}}/AM/Editor/Area}}<!-- Area managers are edited through the main page link accessed from within the table itself. Do not add them here.--><br />
}}<!-- End ifexist --><br />
{{AM/Bottom}}<!-- Bottom of the table; must be the last line of table. -------------<br />
------------------------------------------------------------------------------------<br />
-->{{#ifexist: {{BasePage2}}/AM/Area2Link <!-- If other table exists --><br />
| {{:{{BasePage2}}/AM/Area2Link}}<!--then display Other Table, or skip --><br />
}}<!-- End ifexist --></includeonly><br />
<!-----------------------------------------------------------------------------------><br />
<!------------------------ DO NOT ADD CODE BELOW THE TABLE --------------------------></div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=New_Jersey/Area_Managers/Main&diff=120480New Jersey/Area Managers/Main2015-10-02T05:02:11Z<p>Qwaletee: LC upgrade</p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE -------------------------------<br />
------------------------------------------------------------------------------------<br />
--><noinclude>{{:USA/CommonState/ReturnPurge|{{#titleparts:{{PAGENAME}}|-1|-2}}}}</noinclude><includeonly><!--<br />
------------------------------------------------------------------------------------<br />
---- Area Managers: Cancel edit and use link on table next to "Area Managers". -----<br />
---- Other Area Editors: Cancel edit and use link on table next to "Other Area<br />
---- Editors". If does not exist, that section can be added from talk page.<br />
---- Country/State Managers: Continue.<br />
------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this <br />
---- state. When first setting up this page, remove the example users for Country<br />
---- and State managers. Area Managers are changed in a different section as noted<br />
---- above. When adding a new user, use the following template: <br />
{{AM/Editor|Username|Area Managed|Other Comment|badge1=x|badge2=x|badge3=x}}<br />
---- If any fields are skipped, ensure the first three pipe "|" characters are<br />
---- present. Note the badge1, badge2, badge3 entries are optional, and the "x"<br />
---- is replaced only by what is defined under: {{AM/Badge}}<br />
---- This link can be reached from http://wiki.waze.com/wiki/Template:AM/Badge or<br />
---- search the Wiki for: "Template:AM/Badge"<br />
<br />
----<br />
---- When adding a new user, place the new template based on Rank (highest first)<br />
---- and then alphabetical order in that rank.<br />
------------------------------------------------------------------------------------<br />
--------------------- AREA MANAGER TABLE BEGINS BELOW ------------------------------<br />
---------------------------- EDIT BELOW LINE ---------------------------------------<br />
-----------------------------------------------------------------------------------><br />
{{AM/Top}}<!-- Top of the table --><br />
{{AM/Country}}<!-- Defines the start of the country manager section --><br />
{{AM/Editor|orbitc|6|States of NJ, NY, DE, PA, CT, ME, MA, NH, RI, VT |Region 9 Northeast & 8 New England|badge1=RC|badge2=GC|badge3=MGC}}<br />
{{AM/Editor|Kobes1878|5|NJ, parts of NY|Resident of State|badge1=M|badge2=CM}}<br />
{{AM/Editor|PhantomSoul|5|NJ, NY|Resident of NJ|badge1=M|badge2=CM}}<br />
{{AM/Editor|Qwaletee|5|NJ, Metro NYC|SM NJ,NY. Resident of NJ.|badge1=M|badge2=LC|badge3=mr}}<br />
{{AM/State}}<!-- Defines the start of the state manager section --><br />
{{AM/Editor|Fredo-p|5|Union County|AZ|badge1=SM}}<br />
{{AM/Editor|PleaseDriveFast|5|NJ|Resident of State|badge1=M|badge2=SM|badge3=mr}}<br />
{{AM/Editor|LeoKantus|4|NJ|Resident of State|badge1=SM}}<br />
{{AM/AreaLink}}<!-- Defines the start of the area manager section --><br />
{{#ifexist: {{BasePage2}}/AM/Editor/Area |<!--<br />
-->{{:{{BasePage2}}/AM/Editor/Area}}<!-- Area managers are edited through the main page link accessed from within the table itself. Do not add them here.--><br />
}}<!-- End ifexist --><br />
{{AM/Bottom}}<!-- Bottom of the table; must be the last line of table. -------------<br />
------------------------------------------------------------------------------------<br />
-->{{#ifexist: {{BasePage2}}/AM/Area2Link <!-- If other table exists --><br />
| {{:{{BasePage2}}/AM/Area2Link}}<!--then display Other Table, or skip --><br />
}}<!-- End ifexist --></includeonly><br />
<!-----------------------------------------------------------------------------------><br />
<!------------------------ DO NOT ADD CODE BELOW THE TABLE --------------------------></div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=File:Jug_BDP_alt.jpg&diff=119166File:Jug BDP alt.jpg2015-09-17T17:42:46Z<p>Qwaletee: PL</p>
<hr />
<div>Jug BDP.jpg after changes to eliminate false positive BDP. [https://www.waze.com/editor/?env=usa&lon=-75.04419&lat=39.76680&zoom=9 Sandbox (should be removed soon)]</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=File:Jug_BDP_alt.jpg&diff=119164File:Jug BDP alt.jpg2015-09-17T17:39:36Z<p>Qwaletee: Jug BDP.jpg after changes to eliminate false positive BDP.</p>
<hr />
<div>Jug BDP.jpg after changes to eliminate false positive BDP.</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=New_Jersey/Special_roads/Main&diff=119163New Jersey/Special roads/Main2015-09-17T17:38:48Z<p>Qwaletee: */Special_roads/Main*/ Illustrate jug BDP issue</p>
<hr />
<div><!-- This page is only transcluded into (displayed on) the main page for this state. See more detailed instructions below. --><noinclude>{{:USA/CommonState/ReturnPurge|{{SubPage2}}}}<br/></noinclude><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
<br />
=== Special Road Guidelines ===<br />
The following special roads are managed slightly uniquely in some states and territories.<br />
<br />
====Jughandles====<br />
{{construction<br />
| contact = http://www.waze.com/forum/viewtopic.php?f=249&t=106629<br />
| contacttype = forum<br />
| draft = yes<br />
| section = yes<br />
| open = no<br />
}}<br />
Jughandles are a special type of exit used to make left turns or U-turns. They promote overall traffic flow and often improve safety.<br />
<br />
====Background====<br />
New Jersey is especially known for using jughandles - some people call them a "New Jersey Left," and even engineering societies call them NJJI, for New Jersey Jughandle Interchange.<br />
<br />
Jughandles typically occur on busy roadways where left turns or U-turns would be slow, dangerous and/or disruptive to traffic. Rather than have a left turn lane at such an intersection, a right-side exit is used. The exit, in various configurations, allows the driver to come back to the same intersection, but perpendicular (crossing) the originally roadway. This typically creates a safer, faster intersection. Usually there is a traffic light at the intersection, though some jughandles do not have them.<br />
<br />
Jughandles do not exist on freeways. Since freeways are controlled-access highways, you don't find cross-streets connecting to them at-grade. They exist on highways that are not fully controlled-access, and on particularly busy local streets that may not be highways at all. (Note that the terms highways and streets above reflects real-world road configuration, not the Waze segment type.)<br />
<br />
There are 3 kind of Jughandles in New Jersey per the [http://www.nj.gov/transportation/eng/documents/RDM/sec6.shtm#jughandles| NJ-DOT]. They are:<br />
<br />
* '''Type A - Forward:''' [[File:JugA.JPG|450px|thumbnail|right|Type A jughandle with some non-standard features. Click to see full size.]]The exit is on the right hand side prior to the intersection, and can accommodate traffic turning either right and left to the cross street. The exit segment connects to the cross street ''away'' from the intersection. Left or U-turn maneuver requires taking the exit, making a left onto the cross street, approaching the intersection, and then turning left (effectively a U-turn from the original roadway) or continuing straight through (effectively a left from original roadway).<br />
<br />
* '''Type B - U-Turn:''' The exit is on the right side prior to the intersection, and loops directly into the intersection. Usually the intersection must be a T-intersection (aside from the jughandle), with a cross street only on the other side of the original roadway.<br />
<br />
* '''Type C - Reverse:''' The exit is on the right, but ''after'' the intersection. It loops "backwards" to the cross street, similar to type A but from the other side of the cross street. Can be used to complete a left turn (continue straight after exiting jughandle to cross street). Can also be used to complete a u-turn (turn left after reaching intersection on cross-street), though they may be difficult or illegal if there are multiple lanes of traffic on the cross street.<br />
<br />
* '''''Pseudo-jughandles:''' Sometimes, the exit is directly onto a short normal street instead of a dedicated ramp. The street may function as a Type A jughandle, by connecting immediately to the cross street of the original roadway. NJ-DOT does not classify these as jughandles, though for the purpose of mapping, we may have to make naming and typing considerations that are similar to the mapping considerations of jughandles.''<br />
<br />
<br />
=====Editing guidance=====<br />
{{Anchor|Guidance}}<br />
{{Mbox|type=warning|text=Special consideration must be given to Waze's [[detour prevention]] feature when jughandles are used for U-turns. The [[#Detour prevention errors|text below notes]] some of these considerations. If you don't follow that guidance, Waze may not want to use the jughandle for a U-turn.}}<br />
<br />
This section explains how to name jughandle segments, and what segment type to apply to them. {{Mbox|text=Some of the guidance below calls for following [[at-grade connector]] rules (AGCs), since many jughandles function exactly like AGCs. For the discussion below, here is a simplified set of AGC rules:<br />
* AGCs are unnamed, and Waze simply "inherits" the name of the next segment in the route that they connect to.<br />
* An AGC should have the same type as the cross road it leads to, or the type of the road it leads from if that type is "lower." AGCs should not be of type ramp.<br />
* If for some reason an AGC must have a special name in order to give more detailed instructions, then the type should be changed to ramp.}}<br />
<br />
Name and segment-typing of jughandles does not depend on jughandle type. A, B, and C jughandles are set up similarly to each other in Waze. Instead, when determining the name and segment type of a jughandle, you will primarily examine the signage leading to the jughandle exit. You may find:<br />
# Destination signage that only indicates the name of the cross street (''"SIMPLE"'')<br />
# Destination signage that is similar to a regular exit sign ("[[BGS]]" or "[[LGS]]"), listing one or more street/highway names or a city or landmark name (''"STANDARD"'')<br />
# No destination signage, but directional signage exists (e.g., U-Turn, Left turns). These are usually black lettered on a white background (''"DIRECTIONAL"'')<br />
# No signage (''"UNSIGNED"'')<br />
<br />
To properly set up the jughandle based on signage:<br />
<br />
# For ''SIMPLE'' signed jughandles, you can typically use the AGC rules described above (unnamed, lower connection type). Waze will give the appropriate exit instruction, using the name of the cross street. Instructions will be usable even for U-turns, because we are using a series of exit/turn instructions with the name of the road at each maneuver; there is no instruction to make a U-turn, even though the effect is to create a U-turn. However, if there is any segment at the end of the jughandle which has a name that does ''not'' match the sign, the instructions may be confusing, and you may have to use exit-style naming (see ''STANDARD'' instructions immediately below). The Type A example diagram above shows a ''SIMPLE''-signed jughandle. It is labeled Old Mill Road, the same name as the cross street. It would be a candidate for being unnamed, with a type of Primary Street (the same type as Old Mill Rd), except for the unusual feature of having a differently named segment, Low Rd, included in the end junction. For that reason, it will be treated as ''STANDARD'' instead of ''SIMPLE.''<br />
# For ''STANDARD'' signed jughandles, use normal [[Road names/USA#Exit|exit naming guidance]]. The exit segment type will be ramp, to prevent Waze form displaying the complex road name, which will follow the signage closely. If there are extra colored signs (e.g., a brown "State Park" sign mounted adjacent to the exit name sign), you may add them to the end of the jughandle name, but only if they provide a destination. Do not add signage about vehicle restrictions or directionals (no trucks, U-turn, etc.). In the case of the Type A diagram above, the exit sign reads "Old Mill Road," with a directional white sign, "All Turns" also attached. Our normal exit guidance calls for naming the exit "to Old Mill Rd," ignoring the directional sign. The type is ramp because we do not want to display "to Old Mill Rd" on the map. However, because of the confusion that may arise for a route that brings the driver onto Low Rd instead of Old Mill Rd, a better name is "to Old Mill Rd / Low Rd."<br />
# For jughandles with ''DIRECTIONAL'' signage only, typically treat the same as ''UNSIGNED'' (below). However, if for some reason it is necessary to provide a name, you may use the ''DIRECTIONAL'' sign's language, and make the segment of type Ramp. Examples: a) Where there are two adjacent exits, and it would be confusing to have Waze announce the turn without any name or with the name of the connecting road (which doesn't appear on any sign), then it may be appropriate to name the jughandle using the wording on the ''DIRECTIONAL'' sign, since that will best orient the driver and allow him or her to select the proper turn. b) The jughandle's end connects directly back to the original highway, typical of a Type B jughandle. It may confuse the driver to hear an instruction to exit to the highway they are already on, even for the opposite compass direction.<br />
# For ''UNSIGNED'' jughandles, typically leave unnamed. Use [[AGC]] rules as described for ''SIMPLE'' signage (above). However, you may need to seek local guidance or senior editor guidance in some situations to create an effective set of exit instructions. For example, if the jughandle might be easily confused with another nearby junction, or where the name of the connecting street may create an ambiguity, we may need to invent a unique name for the jughandle so that it gives better instructions. In such situations, use ramp segment type, to prevent display of the invented name.<br />
# For ''UNSIGNED pseudo-jughandles,'' you will typically leave the street name as-is, matching the true street name. However, if more complex instructions are required, you may need to insert a stub ramp between the highway and the start of the regular street type, to accommodate the longer naming and to avoid giving a real street a false name (especially problematic if there are houses, businesses, or any other location that has an [[House numbers|address number]] along the segment).<br />
<br />
=====Detour prevention errors=====<br />
''Special handling to avoid incorrect Waze Detour Prevention:''<br />
<br />
Waze has a special routing rule designed to prevent Waze from leading a driver off a highway and then immediately re-enter the same highway (the exit/entrance may be measured by Waze as slightly faster, but is confusing, awkward, and may not be legal). The way Waze does this is by examining the names of the next several segments in a route. If one of them is a mismatch, and then some segments later a match appears again, Waze will make some effort to avoid that route.<br />
<br />
When a jughandle creates a U-turn, Waze may inappropriately detect it as exactly such a detour. For example, consider an undivided highway ("Highway 99"), with jughandle used for a U-turn. For our example, the jughandle is an unsigned Type A, leading to cross street ("Plain St"). If Waze is going to lead the driver through this jughandle U-turn, the segment name sequence would be:<br />
<br />
[[File:Jug BDP.jpg|450px|thumbnail|right|Illustration of the example]]<br />
[[File:Jug BDP path.jpg|450px|thumbnail|right|Route that may be impossible due to BDP logic]]<br />
# Highway 99<br />
# Unnamed jughandle segment<br />
# Plain St<br />
# Highway 99<br />
<br />
Segments 1 and 4 have the same name, but the two middle segments do not. Waze sees this as a detour, and will try for a different route, even if somewhat longer and slower.<br />
<br />
To prevent Waze from falsely considering this to be a detour, you must provide Highway 99 as an alternate name to the jughandle and to any cross street segment(s) between the jughandle and the intersection. This will cause Waze to see all four segments as having the same name (even though two ''primary'' names are different).<br />
<br />
[[File:Jug BDP alt.jpg|450px|thumbnail|right|Changed jug attributes to prevent false positive BDP and allow route - now ramp, named "to Plaint St" and alt name matching highway. Same alt should be applied to intervening segment of Plain St.]]Since the jughandle is unnamed, it is somewhat awkward to provide an alternate name. You may elect to name the jughandle "to Plain St" so that it has a primary name, before you add Highway 99 as the alternate. If you do so, make the jughandle of type ramp, so the exit/entrance-style naming does not display.<br />
<br />
Note that if Highway 99 was a divided highway with separate one-way north and south segments, the sequence above would normally change to:<br />
<br />
# Highway 99 W<br />
# Unnamed jughandle segment<br />
# Plain St ''(between jughandle and intersection)''<br />
# Plain St ''(between 99 W and 99 E)''<br />
# Highway 99 E<br />
<br />
In that case, the first and last segments no longer have the same name. You would not need to provide the highway name as an alternate to the middle segments, since detour prevention would never be considered by Waze anyway. In the same scenario, if the north and south segments did not include the N and S cardinals, you would have to go back to alternate names. Another options would be to bring naming of the entire highway up to standard by adding the cardinal N and S along the entire highway.<br />
<br />
Another situation where alternate naming is not required is where the U-turn is not permitted anyway. This occurs where no left turn is allowed from the cross street into the reverse lanes of the original roadway.<br />
<br />
====Parking Lot Roads====<br />
This state uses the following national standard guidelines found in the Wiki for [[Road_types/USA#Parking_Lot_Road|Parking Lot Roads]].<br />
<br />
====Alleys====<br />
This state uses the following unique guidelines for mapping alleys.<br />
<br />
*Alleys should always be mapped if they have a name.<br />
*Alleys should always be mapped if they are the sole access to a home or business.<br />
*Alleys should always be set to "Parking Lot Road" type.<br />
*Alleys are normally mapped if they are acknowledged by the municipality.<br />
If an alley does not meet the above criteria, mapping is optional. Leave the name field blank.<br />
<br />
'''{{Red|Note:}}''' Be careful adding alleys which will be closer to the destination pins for house numbers, as this can cause navigation to addresses on that block to route onto the alley instead of the main road. It may be better not to map these alleys, or you may have to adjust all the address pins to be closer to the actual roads.<br />
<br />
==== Dirt Roads ====<br />
This state uses the following national standard guidelines found in the Wiki for [[Road_types/USA#Dirt|Dirt Roads]].<br />
<br />
'''{{Red|Note:}}''' In other Regions/Countries, the usage of Dirt Roads-4x4 Trails may vary greatly.<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=File:Jug_BDP_path.jpg&diff=119161File:Jug BDP path.jpg2015-09-17T17:27:04Z<p>Qwaletee: Path of route with BDP problem associated with Jug_BDP.jpg</p>
<hr />
<div>Path of route with BDP problem associated with Jug_BDP.jpg</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=File:Jug_BDP.jpg&diff=119160File:Jug BDP.jpg2015-09-17T17:26:23Z<p>Qwaletee: Fictional example of jughandle with BDP problem</p>
<hr />
<div>Fictional example of jughandle with BDP problem</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=User:Qwaletee/Chart&diff=117626User:Qwaletee/Chart2015-08-27T15:00:44Z<p>Qwaletee: Exit RIGHT correct to Haledon</p>
<hr />
<div>{| class="wikitable <!--sortable-->"<br />
|-<br />
! ..........to>>>><br />
From&nbsp;vvv<br />
! Valley !! Central S !! Central N<br />
|-<br />
| Valley || - || Right to Central then Right; Right to Central || ''(2 continues then)'' Left to Central<br />
|-<br />
| Central S || Exit right (exit! I hate those! ''then 2 continations'') || - || n/a - blocked<br />
|-<br />
| Central N || Left to Valley ''(then 2 continues)'' || n/a (blocked by red arrows) || -<br />
|}</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=User:Qwaletee/Chart&diff=117624User:Qwaletee/Chart2015-08-27T14:59:42Z<p>Qwaletee: Correct N/S for Haledon</p>
<hr />
<div>{| class="wikitable <!--sortable-->"<br />
|-<br />
! ..........to>>>><br />
From&nbsp;vvv<br />
! Valley !! Central S !! Central N<br />
|-<br />
| Valley || - || Right to Central then Right; Right to Central || ''(2 continues then)'' Left to Central<br />
|-<br />
| Central S || Exit left (exit! I hate those! ''then 2 continations'') || - || n/a - blocked<br />
|-<br />
| Central N || Left to Valley ''(then 2 continues)'' || n/a (blocked by red arrows) || -<br />
|}</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=User:Qwaletee/Chart&diff=117623User:Qwaletee/Chart2015-08-27T14:55:55Z<p>Qwaletee: Haledon - Valleyview rd & Central</p>
<hr />
<div>{| class="wikitable <!--sortable-->"<br />
|-<br />
! ..........to>>>><br />
From&nbsp;vvv<br />
! Valley !! Central N !! Central S<br />
|-<br />
| Valley || - || Right to Central then Right; Right to Central || ''(2 continues then)'' Left to Central<br />
|-<br />
| Central N || Left to Valley ''(then 2 continues)'' || - || n/a (blocked by red arrows) <br />
|-<br />
| Central S || Exit left (exit! I hate those! ''then 2 continations'') || n/a - blocked || - <br />
|}</div>Qwaleteehttps://www.waze.com/wiki/USA/index.php?title=User:Qwaletee/Wazeopedia&diff=110657User:Qwaletee/Wazeopedia2015-06-19T03:14:28Z<p>Qwaletee: </p>
<hr />
<div>'''Wazeopedia''' is an upcoming project for the Waze community. It will contain the updated editing manual. Wazeopedia will support both ''global'' and ''local'' content. Wazeopedia will adopt most of the content of the existing wiki. It can be edited just like the existing wiki. However, it will have a better structure for supporting many local communities plus a set of global pages. The global pages are those that apply to all communities.<br />
<br />
''Global content'' is selected content that is useful for all the Waze editing communities around the world. Each community is free to adopt Wazeopedia lobal content into its own pages. This can be done in the original English, or translated. <br />
<br />
''Local content'' is managed community content (regional) in multiple carefully <br />
The Wazeopedia wiki site is not yet available. However, the team that is building Wazeopedia examined the pages in the existing Waze wiki. Many of those are already global in nature. We are currently editing them to the standards of the global Wazeopedia. This is a slow process, as there is a great deal of content to work on.<br />
<br />
The existing function of those selected pages, in the past, was mostly to support the Waze United States community, and sometimes other English-speaking countries. Those pages will continue serving those communities until they are moved. At that time, the United States and other English communities will do the same as any other community - either adopt the global pages, or recreate their own versions of them.<br />
<br />
If you have a question about the global page nomination process that applies to existing pages, pease visit [http://forums.waze.com/hhkjhkjhkhkjhkjh this forum thread]. You can pose questions there, and alert the global wiki team to any concerns you have.<br />
<br />
The complete list of current nominated pages for global Wazeopedia is here LINK CATEGORY PAGE.</div>Qwaletee