< Utilisateur:Deeploz | WIP
WIP #006 (WORK IN PROGRESS)
Revision of Best map editing practice in order to Globalize it (removing reference or content peculiar to US community
Best map editing practices
{{ReturnTo | Editing manual | the editing manual}}
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.
{{LocalGuidance}}
<br/>
{{TOC}}
== Overall Goals ==
=== Usability ===
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.
=== Simplicity ===
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.
=== Retention ===
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".
== In Practice ==
=== Dividing and un-dividing divided highways ===
==== When to divide a two-way road (and when not to) ====
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:
# 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.
# If a road is currently working with no problem reports, consider leaving it as is.
# 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 [[Discussion Forums | editing forums]] to get additional feedback from other editors in your area.
# 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/>
'''A road may be divided when <u>any</u> of the following conditions are met:'''
* It is a National Highway or other Limited Access Highway using the "Freeway" road type,
* 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]],
* 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,
* U-turns are required to properly make turns from public drivable road types that are blocked by a median.
'''A road should <u>not</u> be divided when:'''
* There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above).
* The non-drivable median is interrupted by a cross segment at most intersections.
* 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.
* It is possible and legal to make a left turn/u-turn everywhere along the road
* The objective is solely for visual appearance or to make the road match another visual source like Google Maps.
{{clear}}
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.
==== How to un-divide two one-way roads ====
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.
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.
{{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.}}
The steps below show how to properly merge two one-way roads and preserve the underlying house numbers.
This is our example road segment. For the entire length of the road you need to:
[[File:undivideRd1.jpg]]
1. Select the two segments to be merged and set them both to two-way.
[[File:undivideRd2.jpg]]
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.
[[File:undivideRd3.jpg]]
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.
[[File:undivideRd4.jpg]]
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.
{{#ev:youtube|6blRMtGwaYA}}
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.
# With the street/road selected, click ‘Edit house numbers’.
# From the house number editing view, you need to select each house number one-by-one.
# With the house number selected, you see the dashed line is attached to a circle on the street.
# Select the circle and move it along the road closest to the entrance of the driveway to the building.
Also be sure to check the following:
# Remove all "orphaned" junctions.
# Change the direction of the preserved segments to two-way.
# Check/fix the connectivity of all the roads already connect to the side you kept.
# Connect (and set connectivity) of all the roads that used to be connected to the other side.
# Make sure all the new two-way segments are connected.
# Adjust the geometry to move the two-way road segments to the middle of the road.
Now repeat the entire process for the remaining segments matching the two opposite from each other.
It isn't difficult once you have gone through the process a couple of times.
'''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 could find that all the road segments have reverted to Streets in another country/state and any alternate road names are lost.
=== Highways and Ramps ===
Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways & Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important.
==== Roads ====
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.
==== Ramps ====
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".
Remember to check connectivity and turn restrictions while you're there.
Be sure to understand the difference between ramps and [[at-grade connectors]].
==== Overpasses & Underpasses ====
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.
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.
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.
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.
==== Caveat re. Elevation ====
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.
See also [[Creating and editing road segments#Road elevation|Road Elevation]].
==== Bridging Roads ====
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.
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.
==== Handling Restricted Lanes ====
At this time, Waze does not have a facility to handle restricted lanes; e.g. lanes that are available only for a particular type of vehicule (taxi, trucks, high-occupancy vehicules,...). 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.
So far, the best partial solution the community has come up with is described in detail by the US community 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.
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.
=== Toll roads ===
:''For other uses see [[Toll (disambiguation)]].''
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:
*there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment
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.
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.
* ''see advanced topic on [[Time-based Tolls]] for mapping tolls that do not charge all the time.''
=== Time Restricted Turns ===
The Waze Map Editor and routing engine supports scheduled restrictions (time of day, day of week, turns, traffic flow direction, vehicle type, etc.).
Please see the [[Partial restrictions]] page for full documentation on this feature.
=== When to Use Ramps in an Intersection ===
Please see the discussion on [[at-grade connectors]].
=== When to Create a Roundabout ===
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.
'''''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]]''
=== Locking Segments ===
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.
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.
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.
'''Locking should be used sparingly and carefully.'''
=== Junction Style Guide ===
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.
== New Roads ==
=== Parking Lots ===
Mapping a parking lot road serves three purposes:
*it allows Waze to provide door-to-door directions within the lot;
*it allows the Waze client to get off the main road, avoiding erroneous traffic reports.
*it prevents the Waze client from routing thru-traffic along the parking lot segments.
'''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]].
==== Shopping Centers ====
When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following:
*Main entrances from the roads outside the parking lot
*Lanes that run along storefronts
*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)
*Primary lanes that serve to get people from one area of the lot to another
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]]
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.
==== Small Parking Lots ====
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).
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.
==== Drive-Through/Drive-in Lots ====
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]].''
==== Use of the Parking Lot Road Type ====
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.
=== Recorded via Client ===
Once you start editing a road, it changes from red (a new road) to the color 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.
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.
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.
# 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]]
# Enter the correct name and road type for your road, following the standards for your country
# Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way.
# 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.
=== Roundabouts ===
*A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME.
*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.
*Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections.
== Classification of crossings ==
Different types of crossings have [[Classification of crossings|standard ways to handle them]].
{{ReturnTo | Editing manual | the editing manual}}
[[Category:Waze Map Editor]]
[[Category:Convert to Subpages]]
[[Category:Add Wikilinks]]