https://www.waze.com/wiki/USA/api.php?action=feedcontributions&user=KodakYarr&feedformat=atomWazeopedia - User contributions [en]2024-03-28T17:52:31ZUser contributionsMediaWiki 1.40.2https://www.waze.com/wiki/USA/index.php?title=Color-by-azimuth&diff=117464Color-by-azimuth2015-08-25T18:44:26Z<p>KodakYarr: KodakYarr moved page Color-by-azimuth to Colour-by-azimuth: Spelling error</p>
<hr />
<div>The colours of the arrows in the GPS points layer of the WME represents a different direction of travel as seen here.<ref>https://www.waze.com/forum/viewtopic.php?f=8&t=128248</ref><br />
[[File:GPStracks.jpg|framed]]<br />
To find out which colour represents which direction, check out the visualisation below:<br />
[[File:AzimuthColours.jpg|framed]]</div>KodakYarrhttps://www.waze.com/wiki/USA/index.php?title=Best_map_editing_practice&diff=117463Best map editing practice2015-08-25T18:43:51Z<p>KodakYarr: /* {{anchor|When (Not) to Split a Two-Way Road|When to Split a Two-Way Road (and when not to)|When to divide a TwoWay Road (and when not to)}}When to divide a two-way road (and when not to) */</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 />
The purpose of this page is to help all map editors design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Waze Map Editor]], identify and solve [[Map problems]] and [[Update requests]], set standards for [[Road types and names|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for newer editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits.<br />
<br />
If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [http://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum].<br />
<br />
{{LocalGuidance}}<br />
<br/><br />
{{TOC}}<br />
<br />
== Overall Goals ==<br />
<br />
=== Usability ===<br />
When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed.<br />
<br />
=== Simplicity ===<br />
It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance.<br />
<br />
=== Retention ===<br />
As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle".<br />
<br />
== In Practice ==<br />
<br />
=== Dividing and un-dividing divided highways ===<br />
==== {{anchor|When (Not) to Split a Two-Way Road|When to Split a Two-Way Road (and when not to)|When to divide a TwoWay Road (and when not to)}}When to divide a two-way road (and when not to) ====<br />
<!-- After this anchor is updated to the new term, update the glossary to link back here for the entry [[Glossary#Dual carriageway]] --><br />
Generally, a road should be un-divided unless it meets any of the requirements for dividing a road. When initially reviewing whether to divide or "un-divide" (merge back together) a roadway, consider these points first:<br />
<br />
# The default representation for any roadway is a single 2-way segment, even if the physical roadway is divided. Dividing a roadway carries with it the burden of proof that the change will improve the usability and/ or simplicity of the Waze map.<br />
# If a road is currently working with no problem reports, consider leaving it as is.<br />
# If the area has an Area Manager, consult with them before dividing/un-dividing. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors.<br />
# Try to avoid switching roads back and forth between being divided and 2-way. For example, if most of the road is clearly divided and only parts would be considered a single two-way road, consider leaving it all divided. If only a small portion seems better off divided, consider keeping it all 2-way.<br />
<br/> <br />
<br />
'''A road may be divided when <u>any</u> of the following conditions are met:'''<br />
<br />
* It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type,<br />
* GPS tracks show a clearly definable and continuous gap (blank area) between the [[colour-by-azimuth]] arrows at the 100m/500ft [[Map_Editor_Interface_and_Controls#Scale|zoom level]], <br />
* multiple houses or businesses with no off-street parking are located directly on the street but are not accessible from the opposite direction of travel due to lengthy median, obstruction, or traffic control signage, or<br />
* U-turns are required to properly make turns from public drivable road types that are blocked by a median.<br />
<br />
<br />
'''A road should <u>not</u> be divided when:'''<br />
* There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). <br />
* The non-drivable median is interrupted by a cross segment at most intersections.<br />
* There is a center turn lane (any width) between directions of travel. Dividing this type of road creates problems when people turn from the middle lane because there is no road for the navigation to follow.<br />
* It is possible and legal to make a driver side turn/u-turn everywhere along the road<br />
* The objective is solely for visual appearance or to make the road match another visual source like Google Maps.<br />
{{clear}}<br />
<br />
Remember that dividing and un-dividing roads each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a divided road. Consider every aspect of routing, and carefully examine each junction before dividing or un-dividing. Regardless of whether you're dividing or un-dividing, remember that you might cause more problems than you solve and you might have to put it back the way it was before. Also remember that dividing and un-dividing each cause loss of some traffic data, which can result in poor Waze routing.<br />
<br />
==== {{anchor|How to "Un-Split" two One-Way Roads|How to "Un-divide" two One-Way Roads}}How to un-divide two one-way roads ====<br />
Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before dividing a road in the first place. And then think some more.<br />
<br />
When you come across a road in your area that has been divided but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way roads UNLESS there are Update Requests related to the road caused by it being divided.<br />
<br />
{{Red|The process to un-divide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. They would have to be looked up and manually added back to the new road.}}<br />
<br />
The steps below show how to properly merge two one-way roads and preserve the underlying house numbers.<br />
<br />
This is our example road segment. For the entire length of the road you need to:<br />
<br />
[[File:undivideRd1.jpg]]<br />
<br />
1. Select the two segments to be merged and set them both to two-way.<br />
<br />
[[File:undivideRd2.jpg]]<br />
<br />
2. Disconnect both segments from one side of the section being un-divided. It is best to disconnect alternate ends of each segment as shown.<br />
<br />
[[File:undivideRd3.jpg]]<br />
<br />
3. Bring the two disconnected ends together in the middle (and realign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key.<br />
<br />
[[File:undivideRd4.jpg]]<br />
<br />
The following video was recorded by an editor merging two one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen.<br />
<br />
{{#ev:youtube|6blRMtGwaYA}}<br />
<br />
<br />
After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over.<br />
# With the street/road selected, click ‘Edit house numbers’. <br />
# From the house number editing view, you need to select each house number one-by-one.<br />
# With the house number selected, you see the dashed line is attached to a circle on the street.<br />
# Select the circle and move it along the road closest to the entrance of the driveway to the building.<br />
<br />
Also be sure to check the following:<br />
# Remove all "orphaned" junctions.<br />
# Change the direction of the preserved segments to two-way.<br />
# Check/fix the connectivity of all the roads already connect to the side you kept.<br />
# Connect (and set connectivity) of all the roads that used to be connected to the other side.<br />
# Make sure all the new two-way segments are connected.<br />
# Adjust the geometry to move the two-way road segments to the middle of the road.<br />
<br />
<br />
Now repeat the entire process for the remaining segments matching the two opposite from each other.<br />
<br />
It isn't difficult once you have gone through the process a couple of times.<br />
<br />
'''Caveat:''' If you decide to be clever and edit the road properties of multiple segments at a time, first familiarize yourself with the known problems with mass-editing. It can be done -- but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names are lost.<br />
<br />
=== Highways and Ramps ===<br />
<br />
Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways &amp; Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important.<br />
<br />
==== Roads ====<br />
<br />
The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered and exited solely by ramps. Such roads almost always should be mapped as separate one-way segments -- and other roads almost never should be.<br />
<br />
==== Ramps ====<br />
<br />
As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) --> <br />
<br />
Remember to check connectivity and turn restrictions while you're there.<br />
<br />
*There is a more detailed description of [[Road names/USA#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]].<br />
<br />
*Be sure to understand the difference between ramps and [[at-grade connectors]].<br />
<br />
==== Overpasses &amp; Underpasses ====<br />
<br />
Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road.<br />
<br />
Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned.<br />
<br />
In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment.<br />
<br />
Occasionally you run into a situation in which no set of values will work. For example, three segments named A, B, and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish.<br />
<br />
==== Caveat re. Elevation ====<br />
<br />
No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map Editing Quick-start Guide#Delete a Junction|deleting a junction]] for more information.<br />
<br />
See also [[Creating and editing road segments#Road elevation|Road Elevation]].<br />
<br />
==== Bridging Roads ====<br />
<br />
Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them.<br />
<br />
Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road types/USA#Railroad|Railroads]] under Road Types for more information.<br />
<br />
<br />
==== Handling Restricted Lanes ====<br />
At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly.<br />
<br />
The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it helps (in terms of testing and making the feature available) if these lanes are already mapped.<br />
<br />
The best partial solution the community has come up with is described in detail on the [[Carpool, HOV, Transit lanes]] page. The lanes should be set with the appropriate road type for the road they are part of, and the entrance (and in some cases exit) ramps set with the appropriate restrictions for vehicle type (and time). If the lanes are reversible then they will have to be set with separate timed restrictions for each direction on the lanes themselves as well.<br />
<br />
This "solution" gives routing onto these special lanes a very high [[Routing penalties|penalty]] when they being enforced, and reduce the likelihood that Waze will create a route over them. It does not prevent Waze from snapping a driver to the segments if it determines they are on such a lane, and any recalculation of the route from these segments is correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error.<br />
<br />
{{details|Carpool, HOV, Transit lanes}}<br />
<br />
==== High Occupancy Toll (HOT) Roads/Lanes (USA) ====<br />
The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway.<br />
<br />
[[Image:I-15-express-lanes.jpg]]<br />
<br />
HOT roadways have the following features:<br />
* These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes.<br />
* There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed.<br />
* Entrances and exits to the HOT lanes are limited to help maintain high speeds.<br />
* There are no entrance/exit combinations where the toll fare rules don't apply.<br />
* Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day.<br />
<br />
HOT lanes are often marketed as "Express Lanes"; however, the term "Express Lanes" is also used by various regional governments for non-HOT lanes. In order to be considered a HOT lane for Waze purposes, a road needs to meet all criteria listed above.<br />
<br />
The entrances to HOT lanes should be marked with the toll flag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute.<br />
<br />
The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client.<br />
<br />
Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves to the HOT lanes; they are not be routed onto them by the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane.<br />
<br />
Because HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation.<br />
<br />
<br />
=== Toll roads ===<br />
:''For other uses see [[Toll (disambiguation)]].''<br />
<br />
Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating and editing road segments#Road Properties|road segment properties]] tab. Mark a segment as a toll road only if:<br />
*there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment<br />
<br />
Do not check the toll box setting for segments that lead up to the final toll segment even if they have no other exit except the final toll segment.<br />
<br />
In the case of a bridge that is tolled in only one direction, divide the road where the toll is collected and mark only the segment with the toll booth as a toll road.<br />
<br />
* ''see advanced topic on [[Time-based Tolls]] for mapping tolls that do not charge all the time.''<br />
<br />
=== Time Restricted Turns ===<br />
The Waze Map Editor and routing engine supports scheduled restrictions (time of day, day of week, turns, traffic flow direction, vehicle type, etc.).<br />
<br />
Please see the [[Partial restrictions]] page for full documentation on this feature.<br />
<br />
<br />
=== When to Use Ramps in an Intersection ===<br />
Please see the discussion on [[at-grade connectors]].<br />
<br />
<br />
=== When to Create a Roundabout ===<br />
In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts.<br />
<br />
'''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]''<br />
<br />
<br />
=== Locking Segments ===<br />
In some regions there are locking rank standards applied based on road type. In these regions all roads of a certain type are locked to a minimum rank, and should be locked even in residential areas. Check [[Template:Countries|your local wiki]] for your local standards to see if these apply in your editing area. Locking should otherwise be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes.<br />
<br />
NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct.<br />
<br />
If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing restrictions#Unlocking an object above your rank|unlocking an object above your rank]] for more information.<br />
<br />
'''Locking should be used sparingly and carefully.'''<br />
<br />
<br />
=== Junction Style Guide ===<br />
When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] provides the best practices with the many different types of junctions.<br />
<br />
== New Roads ==<br />
<br />
=== 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 client to get off the main road, avoiding erroneous traffic reports.<br />
*it prevents the Waze client from routing thru-traffic along the parking lot segments.<br />
<br />
'''NOTE:''' Most parking lots should '''not''' be designated as a Waze "place," and especially not an Area Place (previously known as Landmarks). Landmark-worthy parking must be something of a destination in itself, either having a well-known and documented name, or serving multiple destinations. For information pertaining to using the Parking Lot Place please see: [[Places/Parking lot]].<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 that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information)<br />
*Primary 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 has been most recently to help determine what might be the best section to map.<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 a single entrance/exit could even be represented by a single segment running diagonally across the parking area (lots with entrances on both sides) or a single, flattened curve (lots that only have entrances/exits along a single road, such as for strip malls).<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 />
==== Use of the Parking Lot Road 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 navigation vs. the road network. As of June 2012, Waze applies a [[Routing penalties|transition penalty]] when transitioning from a Parking Lot Road to 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. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot.<br />
<br />
=== Recorded via Client ===<br />
Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which goes out to all Waze users.<br />
<br />
So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable.<br />
<br />
Follow these simple steps, as best you can, and get it right the first time. [[Waze Map Editor|Map Editing]] explains how to carry out these steps.<br />
<br />
# Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning on possible lack of accuracy in aerial images|not appropriate in your area]]<br />
# Enter the correct name and road type for your road, following the standards for your country<br />
# Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way.<br />
# Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads.<br />
<br />
<br />
=== Roundabouts ===<br />
*A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. <br />
*When it is first created, the segments are configured as new roads - they need to be edited as above before they become part of the live map.<br />
*Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections.<br />
<br />
<br />
== Classification of crossings ==<br />
Different types of crossings have [[Classification of crossings|standard ways to handle them]].<br />
<br />
{{ReturnTo | Editing manual | the editing manual}}<br />
<br />
[[Category:Waze Map Editor]]<br />
[[Category:Convert to Subpages]]<br />
[[Category:Add Wikilinks]]</div>KodakYarrhttps://www.waze.com/wiki/USA/index.php?title=Color-by-azimuth&diff=117462Color-by-azimuth2015-08-25T18:42:32Z<p>KodakYarr: Created page with "The colours of the arrows in the GPS points layer of the WME represents a different direction of travel as seen here.<ref>https://www.waze.com/forum/viewtopic.php?f=8&t=128248..."</p>
<hr />
<div>The colours of the arrows in the GPS points layer of the WME represents a different direction of travel as seen here.<ref>https://www.waze.com/forum/viewtopic.php?f=8&t=128248</ref><br />
[[File:GPStracks.jpg|framed]]<br />
To find out which colour represents which direction, check out the visualisation below:<br />
[[File:AzimuthColours.jpg|framed]]</div>KodakYarrhttps://www.waze.com/wiki/USA/index.php?title=File:AzimuthColours.jpg&diff=117461File:AzimuthColours.jpg2015-08-25T18:39:46Z<p>KodakYarr: A graphic showing which colour the direction of travel yields on GPS tracks in WME.</p>
<hr />
<div>A graphic showing which colour the direction of travel yields on GPS tracks in WME.</div>KodakYarrhttps://www.waze.com/wiki/USA/index.php?title=File:GPStracks.jpg&diff=117460File:GPStracks.jpg2015-08-25T18:36:56Z<p>KodakYarr: GPS tracks showing track colour depending on direction.</p>
<hr />
<div>GPS tracks showing track colour depending on direction.</div>KodakYarrhttps://www.waze.com/wiki/USA/index.php?title=Best_map_editing_practice&diff=117459Best map editing practice2015-08-25T18:26:27Z<p>KodakYarr: /* {{anchor|When (Not) to Split a Two-Way Road|When to Split a Two-Way Road (and when not to)|When to divide a TwoWay Road (and when not to)}}When to divide a two-way road (and when not to) */</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 />
The purpose of this page is to help all map editors design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Waze Map Editor]], identify and solve [[Map problems]] and [[Update requests]], set standards for [[Road types and names|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for newer editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits.<br />
<br />
If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [http://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum].<br />
<br />
{{LocalGuidance}}<br />
<br/><br />
{{TOC}}<br />
<br />
== Overall Goals ==<br />
<br />
=== Usability ===<br />
When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed.<br />
<br />
=== Simplicity ===<br />
It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance.<br />
<br />
=== Retention ===<br />
As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle".<br />
<br />
== In Practice ==<br />
<br />
=== Dividing and un-dividing divided highways ===<br />
==== {{anchor|When (Not) to Split a Two-Way Road|When to Split a Two-Way Road (and when not to)|When to divide a TwoWay Road (and when not to)}}When to divide a two-way road (and when not to) ====<br />
<!-- After this anchor is updated to the new term, update the glossary to link back here for the entry [[Glossary#Dual carriageway]] --><br />
Generally, a road should be un-divided unless it meets any of the requirements for dividing a road. When initially reviewing whether to divide or "un-divide" (merge back together) a roadway, consider these points first:<br />
<br />
# The default representation for any roadway is a single 2-way segment, even if the physical roadway is divided. Dividing a roadway carries with it the burden of proof that the change will improve the usability and/ or simplicity of the Waze map.<br />
# If a road is currently working with no problem reports, consider leaving it as is.<br />
# If the area has an Area Manager, consult with them before dividing/un-dividing. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors.<br />
# Try to avoid switching roads back and forth between being divided and 2-way. For example, if most of the road is clearly divided and only parts would be considered a single two-way road, consider leaving it all divided. If only a small portion seems better off divided, consider keeping it all 2-way.<br />
<br/> <br />
<br />
'''A road may be divided when <u>any</u> of the following conditions are met:'''<br />
<br />
* It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type,<br />
* GPS tracks show a clearly definable and continuous gap (blank area) between the [[color-by-azimuth]] arrows at the 100m/500ft [[Map_Editor_Interface_and_Controls#Scale|zoom level]], <br />
* multiple houses or businesses with no off-street parking are located directly on the street but are not accessible from the opposite direction of travel due to lengthy median, obstruction, or traffic control signage, or<br />
* U-turns are required to properly make turns from public drivable road types that are blocked by a median.<br />
<br />
<br />
'''A road should <u>not</u> be divided when:'''<br />
* There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). <br />
* The non-drivable median is interrupted by a cross segment at most intersections.<br />
* There is a center turn lane (any width) between directions of travel. Dividing this type of road creates problems when people turn from the middle lane because there is no road for the navigation to follow.<br />
* It is possible and legal to make a driver side turn/u-turn everywhere along the road<br />
* The objective is solely for visual appearance or to make the road match another visual source like Google Maps.<br />
{{clear}}<br />
<br />
Remember that dividing and un-dividing roads each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a divided road. Consider every aspect of routing, and carefully examine each junction before dividing or un-dividing. Regardless of whether you're dividing or un-dividing, remember that you might cause more problems than you solve and you might have to put it back the way it was before. Also remember that dividing and un-dividing each cause loss of some traffic data, which can result in poor Waze routing.<br />
<br />
==== {{anchor|How to "Un-Split" two One-Way Roads|How to "Un-divide" two One-Way Roads}}How to un-divide two one-way roads ====<br />
Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before dividing a road in the first place. And then think some more.<br />
<br />
When you come across a road in your area that has been divided but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way roads UNLESS there are Update Requests related to the road caused by it being divided.<br />
<br />
{{Red|The process to un-divide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. They would have to be looked up and manually added back to the new road.}}<br />
<br />
The steps below show how to properly merge two one-way roads and preserve the underlying house numbers.<br />
<br />
This is our example road segment. For the entire length of the road you need to:<br />
<br />
[[File:undivideRd1.jpg]]<br />
<br />
1. Select the two segments to be merged and set them both to two-way.<br />
<br />
[[File:undivideRd2.jpg]]<br />
<br />
2. Disconnect both segments from one side of the section being un-divided. It is best to disconnect alternate ends of each segment as shown.<br />
<br />
[[File:undivideRd3.jpg]]<br />
<br />
3. Bring the two disconnected ends together in the middle (and realign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key.<br />
<br />
[[File:undivideRd4.jpg]]<br />
<br />
The following video was recorded by an editor merging two one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen.<br />
<br />
{{#ev:youtube|6blRMtGwaYA}}<br />
<br />
<br />
After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over.<br />
# With the street/road selected, click ‘Edit house numbers’. <br />
# From the house number editing view, you need to select each house number one-by-one.<br />
# With the house number selected, you see the dashed line is attached to a circle on the street.<br />
# Select the circle and move it along the road closest to the entrance of the driveway to the building.<br />
<br />
Also be sure to check the following:<br />
# Remove all "orphaned" junctions.<br />
# Change the direction of the preserved segments to two-way.<br />
# Check/fix the connectivity of all the roads already connect to the side you kept.<br />
# Connect (and set connectivity) of all the roads that used to be connected to the other side.<br />
# Make sure all the new two-way segments are connected.<br />
# Adjust the geometry to move the two-way road segments to the middle of the road.<br />
<br />
<br />
Now repeat the entire process for the remaining segments matching the two opposite from each other.<br />
<br />
It isn't difficult once you have gone through the process a couple of times.<br />
<br />
'''Caveat:''' If you decide to be clever and edit the road properties of multiple segments at a time, first familiarize yourself with the known problems with mass-editing. It can be done -- but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names are lost.<br />
<br />
=== Highways and Ramps ===<br />
<br />
Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways &amp; Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important.<br />
<br />
==== Roads ====<br />
<br />
The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered and exited solely by ramps. Such roads almost always should be mapped as separate one-way segments -- and other roads almost never should be.<br />
<br />
==== Ramps ====<br />
<br />
As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) --> <br />
<br />
Remember to check connectivity and turn restrictions while you're there.<br />
<br />
*There is a more detailed description of [[Road names/USA#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]].<br />
<br />
*Be sure to understand the difference between ramps and [[at-grade connectors]].<br />
<br />
==== Overpasses &amp; Underpasses ====<br />
<br />
Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road.<br />
<br />
Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned.<br />
<br />
In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment.<br />
<br />
Occasionally you run into a situation in which no set of values will work. For example, three segments named A, B, and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish.<br />
<br />
==== Caveat re. Elevation ====<br />
<br />
No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map Editing Quick-start Guide#Delete a Junction|deleting a junction]] for more information.<br />
<br />
See also [[Creating and editing road segments#Road elevation|Road Elevation]].<br />
<br />
==== Bridging Roads ====<br />
<br />
Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them.<br />
<br />
Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road types/USA#Railroad|Railroads]] under Road Types for more information.<br />
<br />
<br />
==== Handling Restricted Lanes ====<br />
At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly.<br />
<br />
The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it helps (in terms of testing and making the feature available) if these lanes are already mapped.<br />
<br />
The best partial solution the community has come up with is described in detail on the [[Carpool, HOV, Transit lanes]] page. The lanes should be set with the appropriate road type for the road they are part of, and the entrance (and in some cases exit) ramps set with the appropriate restrictions for vehicle type (and time). If the lanes are reversible then they will have to be set with separate timed restrictions for each direction on the lanes themselves as well.<br />
<br />
This "solution" gives routing onto these special lanes a very high [[Routing penalties|penalty]] when they being enforced, and reduce the likelihood that Waze will create a route over them. It does not prevent Waze from snapping a driver to the segments if it determines they are on such a lane, and any recalculation of the route from these segments is correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error.<br />
<br />
{{details|Carpool, HOV, Transit lanes}}<br />
<br />
==== High Occupancy Toll (HOT) Roads/Lanes (USA) ====<br />
The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway.<br />
<br />
[[Image:I-15-express-lanes.jpg]]<br />
<br />
HOT roadways have the following features:<br />
* These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes.<br />
* There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed.<br />
* Entrances and exits to the HOT lanes are limited to help maintain high speeds.<br />
* There are no entrance/exit combinations where the toll fare rules don't apply.<br />
* Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day.<br />
<br />
HOT lanes are often marketed as "Express Lanes"; however, the term "Express Lanes" is also used by various regional governments for non-HOT lanes. In order to be considered a HOT lane for Waze purposes, a road needs to meet all criteria listed above.<br />
<br />
The entrances to HOT lanes should be marked with the toll flag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute.<br />
<br />
The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client.<br />
<br />
Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves to the HOT lanes; they are not be routed onto them by the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane.<br />
<br />
Because HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation.<br />
<br />
<br />
=== Toll roads ===<br />
:''For other uses see [[Toll (disambiguation)]].''<br />
<br />
Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating and editing road segments#Road Properties|road segment properties]] tab. Mark a segment as a toll road only if:<br />
*there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment<br />
<br />
Do not check the toll box setting for segments that lead up to the final toll segment even if they have no other exit except the final toll segment.<br />
<br />
In the case of a bridge that is tolled in only one direction, divide the road where the toll is collected and mark only the segment with the toll booth as a toll road.<br />
<br />
* ''see advanced topic on [[Time-based Tolls]] for mapping tolls that do not charge all the time.''<br />
<br />
=== Time Restricted Turns ===<br />
The Waze Map Editor and routing engine supports scheduled restrictions (time of day, day of week, turns, traffic flow direction, vehicle type, etc.).<br />
<br />
Please see the [[Partial restrictions]] page for full documentation on this feature.<br />
<br />
<br />
=== When to Use Ramps in an Intersection ===<br />
Please see the discussion on [[at-grade connectors]].<br />
<br />
<br />
=== When to Create a Roundabout ===<br />
In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts.<br />
<br />
'''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]''<br />
<br />
<br />
=== Locking Segments ===<br />
In some regions there are locking rank standards applied based on road type. In these regions all roads of a certain type are locked to a minimum rank, and should be locked even in residential areas. Check [[Template:Countries|your local wiki]] for your local standards to see if these apply in your editing area. Locking should otherwise be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes.<br />
<br />
NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct.<br />
<br />
If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing restrictions#Unlocking an object above your rank|unlocking an object above your rank]] for more information.<br />
<br />
'''Locking should be used sparingly and carefully.'''<br />
<br />
<br />
=== Junction Style Guide ===<br />
When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] provides the best practices with the many different types of junctions.<br />
<br />
== New Roads ==<br />
<br />
=== 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 client to get off the main road, avoiding erroneous traffic reports.<br />
*it prevents the Waze client from routing thru-traffic along the parking lot segments.<br />
<br />
'''NOTE:''' Most parking lots should '''not''' be designated as a Waze "place," and especially not an Area Place (previously known as Landmarks). Landmark-worthy parking must be something of a destination in itself, either having a well-known and documented name, or serving multiple destinations. For information pertaining to using the Parking Lot Place please see: [[Places/Parking lot]].<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 that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information)<br />
*Primary 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 has been most recently to help determine what might be the best section to map.<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 a single entrance/exit could even be represented by a single segment running diagonally across the parking area (lots with entrances on both sides) or a single, flattened curve (lots that only have entrances/exits along a single road, such as for strip malls).<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 />
==== Use of the Parking Lot Road 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 navigation vs. the road network. As of June 2012, Waze applies a [[Routing penalties|transition penalty]] when transitioning from a Parking Lot Road to 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. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot.<br />
<br />
=== Recorded via Client ===<br />
Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which goes out to all Waze users.<br />
<br />
So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable.<br />
<br />
Follow these simple steps, as best you can, and get it right the first time. [[Waze Map Editor|Map Editing]] explains how to carry out these steps.<br />
<br />
# Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning on possible lack of accuracy in aerial images|not appropriate in your area]]<br />
# Enter the correct name and road type for your road, following the standards for your country<br />
# Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way.<br />
# Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads.<br />
<br />
<br />
=== Roundabouts ===<br />
*A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. <br />
*When it is first created, the segments are configured as new roads - they need to be edited as above before they become part of the live map.<br />
*Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections.<br />
<br />
<br />
== Classification of crossings ==<br />
Different types of crossings have [[Classification of crossings|standard ways to handle them]].<br />
<br />
{{ReturnTo | Editing manual | the editing manual}}<br />
<br />
[[Category:Waze Map Editor]]<br />
[[Category:Convert to Subpages]]<br />
[[Category:Add Wikilinks]]</div>KodakYarrhttps://www.waze.com/wiki/USA/index.php?title=Routing_server&diff=117453Routing server2015-08-25T17:57:01Z<p>KodakYarr: /* Turn delays */</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 />
When using the Waze application, Waze servers use routing algorithms to determine the best path for a given route at that particular time. The specific details of the routing algorithms used by the Waze server are not publicly disclosed and the following is based on observation, speculation, and some information revealed by Waze staff. It is assumed that the operation of the routing server is considered to be proprietary and a competitive advantage to Waze. It is also assumed that it is subject to change, and that any information that has been revealed might be incomplete or out of date.<br />
<br />
== Client based routing ==<br />
Calculating an optimal route is a difficult task. While the client device app has a routing algorithm included, this is not used unless there is no connection to the Waze server.<br />
<br />
== Routing requests ==<br />
When you request a route calculation, the request is sent to the Waze server. That route is then transmitted back to your client device and displayed. <br />
<br />
The requests for routing vary according to the settings you have chosen on your client device. Under Navigation you can choose:<br />
* Fastest or shortest route<br />
* Whether to allow or avoid toll roads<br />
* Whether to allow dirt roads, never allow dirt roads, or to avoid long dirt roads<br />
* Whether to avoid major highways<br />
<br />
The shortest route refers to physical distance. Most people usually prefer the Fastest route option; 100km of freeway is better than 90km of country roads.<br />
<br />
== Missing roads and incorrect junction connections ==<br />
Waze tries to find the best route between you and your destination based on your navigation settings. Obviously it can only route based on roads that it knows about, so your route will not be optimal if a better route does not have all the roads with correct connections in the [[Waze Map Editor]]. Also if [[Segment length|segments are less than {{:Segment length/Minimum}}]] they can cause routing issues.<br />
<br />
== Real-time current road speeds ==<br />
The routing server uses real-time road speeds (from recent Waze app users if available) and combines the historical speed of the segment broken down into 10-15 minute chunks. The time to pass through a segment is tracked separately for each route out of a segment. For example if a segment ends with a left and right turn (no straight let's say), then the routing engine isolates the time through the segment to turn left and the time through the segment to turn right. This detailed speed information is proprietary & is part of the data Waze sells/plans to sell and won't be displayed through the editor.<br />
<br />
It is known that Waze uses real-time reports of current road speeds by preference over historical average road speeds. Waze also uses traffic congestion reports to reroute around slow traffic. <!-- Early versions of the client would also report when traffic speeds were good - this was removed due to map clutter. But Waze will still be receiving this information. -->It is assumed that the speed of any Wazer ahead of you on a stretch of road will be the speed used when your route is calculated.<br />
<br />
As the number and density of Wazers grows, this real-time data takes on a greater importance. This emphasis is partly a reflection of Waze's original goal to create optimal commutes. As Waze has grown to be used as a more general purpose GPS navigation device over roads less traveled, the historical average road speeds becomes more important.<br />
<br />
Since Waze uses the time you expect to be at a road segment to calculate the expected speed on that segment, it cannot use real time data when your trip time moves into a future time slot. So trips of more than 30 minutes (and on average more than 15 minutes) will include future time slots where current traffic data is not available when initially calculated. When you enter a new time slot, any real-time traffic data that is available causes your client to recalculate your ETA and reroute you at that point.<br />
<br />
== Fastest routing ==<br />
Waze knows the average speed of every confirmed road between you and your destination. The Waze server can calculate which list of roads to take to minimize the total travel time.<br />
<br />
While every request is processed in real-time, by observation it appears that Waze [[glossary|caches]] some requested routes or major points. This means if it already knows the best route from B to C, and you ask for a route from A to C, it might just calculate the best route from A to B, once it checks that there isn't a better route bypassing B altogether. This does mean that when there is a [[Timeline of updating process|Live map update]] some routes might be less than optimal for up to a day as routes are cached and recalculated.<br />
<br />
While a complex calculation, calculating the optimal route is possible. The complexity arises over the "average speed" of the roads.<br />
<br />
== Changes in route due to different origin ==<br />
Consider calculating a route from A to Z. The suggested route might be A to B to C to D to Z. Then calculate the route from B to Z. You might get a suggested route of B to C to E to Z. At first glance, this suggests one route is not optimal because the [[Glossary|origin]] changed.<br />
<br />
We can guess at what might be happening. There might be a problem associated with the possible caching of routes. Or there might be a "timing window" effect. The different arrival time at C might change the best route to Z. Or there might be a fine tuning effect in the route, perhaps to avoid too many turns. So by dropping the segment A to B, the segments C to E to Z no longer exceed some threshold.<br />
<br />
This effect can be observed while driving. If you recalculate a route to a destination while driving along an already calculated route to that same destination, the route can change.<br />
<br />
Waze sometimes offers a new route to bypass heavy traffic which raises the question as to when and how Waze considers rerouting.<br />
<br />
== Changes in routes due to different route lengths ==<br />
<br />
In addition, it is known that the Waze routing engine can't calculate every possible route for long distance routes, so it takes shortcuts for longer routes, potentially resulting in the route changing dramatically when lengthened slightly. According to Waze support ({{as of|July 2011|lc=y}}), the section of a route more than 10 km from each endpoint is heavily weighted towards non-streets (i.e. "Primary Streets" or the various Highway types). It is believed that Waze servers simply ignore streets outside of the 10 km radius from the endpoints when doing its calculations to speed up the process.<br />
<br />
== Problems with average road speeds ==<br />
If the average road speed is not correct, then the route will not be optimal. However, it is never recommended to delete segments in order to reset the average road speed for that segment. Waze uses the data from Wazers traveling through the segments to update the average speed. If you suspect Waze is not using certain segments along a route, there are a number of other reasons that can cause such a situation. Don't assume deleting the segment is the place to start.<br />
<br />
The following are reasons why the routing engine might not use the average road speed.<br />
<br />
=== Time of day variations ===<br />
Consider a road that most Wazers drive at 5pm when the average speed is 12 mph. You choose your route at 10am when the road is clear and the average speed is 60mph. It is the best road to take, but Waze chooses a different route because it has no information about the speed at 10am and assumes the speeds is 12mph all day.<br />
<br />
You can, of course, drive the road yourself, and Waze eventually learns the speed for that time. We do not know how long Waze holds the older data in computing the average speed. However, if Waze does discard old time information, you might not accumulate new time faster than it is discarded. It is also possible that your times are being ignored as being abnormal.<br />
<br />
More Waze users would help fix this. <br />
<br />
=== Turn delays ===<br />
On a segment of a road, your average speed can be very different depending on what you do at the end of the segment. Traffic going straight through a traffic light might go very fast while traffic turning left might wait a very long time. A freeway exit lane might go fast while traffic continuing hits congestion.<br />
<br />
[[Image:SegmentTraffic1.png|right|350px]]Waze has the ability to separately track the average speed of traffic that passes through a segment, but exits to different segments. The routing engine takes this into account. In the diagram, multiple times are tracked for traffic flowing through Seg4 based on the segments to which it exits. There are then two average drive times for:<br />
<br />
* Seg4 to Jnct2 to Seg5<br />
<br />
* Seg4 to Jnct2 to Seg6<br />
<br />
Traffic building up on Seg4 that turns right to Seg6 does not affect the route timing for the traffic also using Seg4, but instead turning left to Seg5.<br />
For this reason it is important to keep long segment lengths before junctions if traffic congestion at the junction might affect exits differently. <br />
<br />
To understand this problem better, consider if we add a short Seg8 between Seg7 and Jnct4. Let's say the traffic exiting Seg10 backs up all the way to Seg7 (easy enough, since Seg8 is short). Because Seg7 only has a single exiting segment (Seg8), the routing server is only able to collect a single average speed &mdash; it can no longer distinguish traffic by where it is going ''after'' Seg8. Now the through traffic going to Seg9 appears to Waze to slow down through Seg7, even though it doesn't in reality. At a minimum this causes an incorrect ETA for routing, and it might actually cause traffic to be rerouted unnecessarily, and less optimally, through another route. Hence if there is a chance that traffic that goes in different directions at a junction experiences different congestion, keep the segment before that junction long.<br />
<br />
Note this data is not presented to users through the Waze Map Editor, but is only visible to the routing server.<br />
<br />
== Traffic lights and stop signs ==<br />
Waze does not record the location of traffic lights. While some GPS navigation offers guidance like "turn right at the next traffic light" the information is frequently incomplete, incorrect or outdated. The consensus view is that Waze should not record the location of traffic lights.<br />
<br />
Waze does take traffic lights and stop signs into account by noting the effect they have on traffic speed. Consider a traffic light with long waiting times. The road segment leading to that traffic light will have a low average speed. If the average speed (based on the average waiting time) becomes low enough, a longer route that avoids the light becomes the preferred route. This has been observed in practice and is an example of ''emergent behaviour''. Waze isn't programmed to avoid traffic lights but it does avoid slow roads; if the traffic lights make the road slow then Waze avoids them.<br />
<br />
Some drivers regularly take longer routes — even winding through side streets — to avoid any stops or traffic lights. Waze has been known to suggest this, and also known to revert to waiting at lights when better average speed information is collected from the side streets. But note that this can be less than optimal due to the turn delays discussed above.<br />
<br />
== Outdated and abnormal road speeds ==<br />
Road conditions change, construction work comes and goes, and average road speeds can change dramatically. One day you might be stuck behind a truck, and another day you might be crawling along the roads at 2 a.m. transporting your pet goldfish. Or your GPS might have a glitch and show you travelling at 1,000 mph.<br />
<br />
In short, average speeds can change over time, and recorded times can be abnormal or just plain wrong—and can stay wrong for a very long time.<br />
<br />
We can assume Waze is aware of this. There is some evidence that abnormal road speeds and old road speeds are discarded, or at least not used in calculating the average speeds of roads.<br />
<br />
== Average road speed "shrinking window" ==<br />
If there are enough recorded speeds on a road, then Waze uses a shrinking window of speeds to better estimate the average speed at the time you are travelling on it. Waze uses the speed of each road segment (in both directions) in intervals as small as 30 minutes. So a two-way road might have up to 96 average road speeds. We can assume that when there are insufficient records for an individual time slot, a wider time range is takes up a full day. As the road is driven more, the time slot shrinks down to 30 minutes.<br />
<br />
We can speculate that there is additional information used that is based upon the day of the week. There is some observational evidence that a road that is busy on weekdays and not used for routing is chosen as the optimal route on weekends.<br />
<br />
At some point, Waze also needs to consider the months of the year as seasonal variations can affect the speed of the roads.<br />
<br />
Waze uses the average road segment speed for the time slot that applies at the time you are expected to arrive at that road segment.<br />
<br />
Because of this "time window", Waze suggests different routes at different times of day. This is dependent on how many times are recorded on the roads along the route. If they're all recorded at about the same time of day, then the time window does not help. If 1,000 times are recorded at about 5 p.m. and 2 times are recorded at 10 a.m., then your 10 a.m. average speed still is based mostly on times from around 5 p.m.<br />
<br />
== Routing algorithm refinements ==<br />
=== Routing options ===<br />
It's easy to see how routing options can be implemented. For example, to minimize turns we can add a time [[Routing_penalties|penalty]] for fastest routing or a distance penalty for shortest routing, when calculating the fastest or shortest route. <br />
<br />
=== Junction penalties ===<br />
For newly created roads, currently Waze applies a five-second time [[Routing_penalties|penalty]] for each junction through which a route passes. Once vehicles drive over that road and generate Waze traffic data, the penalty for these junctions is dropped.<br />
<br />
== What to do if you think the generated route is wrong ==<br />
Firstly, use the option to generate alternative routes. This might give you some clues as to why Waze is offering that route.<br />
<br />
Secondly, if you think there is a better route, check in WME that the roads are all connected along the route.<br />
<br />
Thirdly, post a message detailing the problem route - origin, destination and a WME permalink to the [http://www.waze.com/forum/viewforum.php?f=6&sid=2872533f5796ac39dc6747511398e907 Navigation forum]. Other eyes will check it, and you might indeed find a flaw in the Waze routing algorithm. Fixing it might make it better for everyone.<br />
<br />
== Change of routing ==<br />
When Waze receives notification of traffic conditions it uses the actual speed of roads on your route, rather than the average speed. This is based only on the automatic traffic condition reports - light, moderate, heavy traffic or complete standstill. Manual reports of traffic jams and accidents are for your information only and do not change routing.<br />
<br />
It might be that even with the traffic reports, there is no better route and Waze cannot offer you one.<br />
<br />
== You are the driver ==<br />
Waze can never see that the traffic light is green going straight, or know that today is a public holiday. It can offer you guidance as to what is the best route under average conditions. But you are the driver and you are in the best position to make the decision for today under today's conditions.<br />
<br />
If everyone followed Waze directions and never drove on a new route, Waze might never learn that route is better. When Waze is recording your travels, every trip helps make Waze better for everyone. That includes when you think you know better. Sometimes you will be right. And sometimes you will be wrong. But it is better to find out you are wrong so you can choose the better route. And when you are right, all Waze users benefits by sharing in your knowledge.<br />
<br />
[[Category:Review redirects]]<br />
[[Category:Waze operations]]</div>KodakYarrhttps://www.waze.com/wiki/USA/index.php?title=Roundabouts&diff=117262Roundabouts2015-08-23T23:12:18Z<p>KodakYarr: </p>
<hr />
<div>[[Image:roundabout_09.png|right|275px]]<br />
Roundabouts, rotaries, or traffic circles, are unique segments of roadway in the Waze router. When a driver approaches a roundabout, a specific icon is displayed in the turn direction area of the display with a number corresponding to the exit count from the driver's entry into the roundabout. Manually creating a circular road will not tell Waze to navigate the area as a roundabout.<br />
<br />
Countries around the world may use slightly different instructions for creating and editing roundabouts. Currently defined specific country instructions include:<br />
<br />
* [[Junctions and roundabouts/Australia#Roundabouts|Australia]]<br />
* [[Junctions and roundabouts/India|India]]<br />
* [[Veityper#Rundkj.C3.B8ringer|Norway]]<br />
* [[Sweden/Redigera#Rondeller|Sweden]]<br />
* [[Junctions and roundabouts/United Kingdom|United Kingdom]]<br />
* [[Roundabouts/USA|USA]]</div>KodakYarrhttps://www.waze.com/wiki/USA/index.php?title=Roundabouts&diff=117261Roundabouts2015-08-23T23:11:51Z<p>KodakYarr: </p>
<hr />
<div>[[Image:roundabout_09.png|right|275px]]<br />
Roundabouts, rotaries, or traffic circles, are unique segments of roadway in the Waze router. When a driver approaches a roundabout, a specific icon is displayed in the turn direction area of the display with a number corresponding to the exit count from the driver's entry into the roundabout. Manually creating a circular road will not tell Waze to navigate the area as a roundabout.<br />
<br />
Countries around the world may use slightly different instructions for creating and editing roundabouts. Currently defined specific country instructions include:<br />
<br />
* [[Junctions and roundabouts/Australia#Roundabouts|Australia]]<br />
* [[Junctions and roundabouts/India|India]]<br />
* [[Veityper#Rundkj.C3.B8ringer|Norway]]<br />
* [[Redigera#Rondeller|Sweden]]<br />
* [[Junctions and roundabouts/United Kingdom|United Kingdom]]<br />
* [[Roundabouts/USA|USA]]</div>KodakYarr