Changes

From Wazeopedia

Best map editing practice

3,212 bytes added, 10 months ago
Toll roads: updated per https://www.waze.com/forum/viewtopic.php?t=287774
{{construction
| contact = https://www.waze.com/forum/viewtopic.php?f=1636&t=273406
| contacttype = forum
| draft = yes
| open = yes
| section = no
| talk = no
}}
 
{{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 requestsRequests]], set standards for [[Road types and names|labeling roads]], and a general [[Frequently Asked Questions (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.
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].
=== 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 an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type,
* GPS tracks show a clearly definable and continuous gap (blank area) between the [[colourcolor-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, or
* U-turns are required to properly make turns from public drivable road types that are blocked by a median.
{{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.
==== {{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 ====
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.
This is our example road segment. For the entire length of the road you need to:
[[File:undivideRd1DivideRoads 2018 00001.jpgpng]]
1. Select the two segments to be merged and set them both to two-way.
[[File:undivideRd2DivideRoads 2018 00002.jpgpng]]
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:undivideRd3DivideRoads 2018 00003.jpgpng]]
3. Bring the two disconnected ends together in the middle (and realign the roads as necessary, removing the unnecessary segments as shown). You can remove the junction point you just created by selecting it and clicking the trash can icon or using the Delete key(Fn + Delete on Mac). Please note that the 2 aligned sections must have matching road information (name, type, direction, speed limit, elevation , and lock) or the junction point will not allow removal!
[[File:undivideRd4DivideRoads 2018 00004.jpgpng]]<br />{{clear}}[[File:DivideRoads 2018 00005.png]]
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}}
[https://www.youtube.com/watch?v=6blRMtGwaYA Un-Dividing Roads and Preserve HN - Video Reference]<br /><br />[https://youtu.be/rkrxrz-gIC0 Un-Dividing Roads WME 2018 - Video Reference]<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.
==== Handling Restricted Lanes ====
At this time, Waze does not have a facility to handle restricted lanes{{mbox| type = cleanup| textstyle = color: red; font-weight: bold; e.g., highfont-occupancy/"car pool" lanes. This is important because these lanes sometimes style: italic;| text = There have their own ramps that the regular lanes do not have, and they often run alongside been major changes to the main road, so that GPS has a hard time discriminating between way [[Partial restrictions]] are handled in the twoWME. The result text below is driving instructions that can range from incorrect to deadly.out of date and should not be utilized when editing the map}}
The most direct solution might appear <span style="text-decoration: line-through;">At this time, Waze does not have a facility to be omittinghandle restricted lanes; e.g., high-occupancy/deleting "carpool" lanes. This is important because these lanes from sometimes have their own ramps that the map. Please '''regular lanes do not''' delete these lanes. As Waze implements more featureshave, it helps (in terms of testing and making they often run alongside the feature available) if these lanes are already mappedmain 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></span>
The best partial most direct solution might appear to be omitting/deleting these lanes from the community has come up with is described in detail on the [[Carpool, HOV, Transit map. Please '''do not''' delete these lanes]] page. The lanes should be set with the appropriate road type for the road they are part ofAs Waze implements more features, and the entrance it helps (in terms of testing and in some cases exit) ramps set with making the appropriate restrictions for vehicle type (and timefeature available). If the if these lanes are reversible then they will have to be set with separate timed restrictions for each direction on the lanes themselves as wellalready mapped.<br>
<span style="text-decoration: line-through;">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 separately timed restrictions for each direction on the lanes themselves as well.<br></span> <span style="text-decoration: line-through;">This "solution" gives routing onto these special lanes a very high [[Routing penalties|penalty]] when they are 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.</span>
{{details|Carpool, HOV, Transit lanes}}
==== High Occupancy Toll (HOT) Roads/Lanes (USA) ====
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.
[[Image:I-15-express-lanes.jpg]]
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.
The entrances {{mbox| type = cleanup| textstyle = color: red; font-weight: bold; font-style: italic;| text = There have been major changes to HOT the way [[Carpool,_HOV,_Transit_lanes|HOV lanes ]] are handled in the WME. The text below is out of date and should not be marked with utilized when editing 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.map}}
<span style="text-decoration: line-through;">The entrances to HOT lanes of the HOT itself should not be flagged as a marked with the toll roadflag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, to prevent while allowing Waze from trying to route HOV users out of use the HOT lanes if they have for routing for those willing to pay a toll avoidance active in the clientfor a faster commute.</span>
Because Waze does not currently support HOV <span style="text-decoration: line-through;">The lanes, HOV users with toll avoidance turned on are not routed onto of the HOT lanes. Just itself should not be flagged as with the current HOV best practicesa toll road, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves prevent Waze from trying to route HOV users out of the HOT lanes; if they are not be routed onto them by have toll avoidance active in the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane.</span>
<span style="text-decoration: line-through;">Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes are still considered "experimental" there may be some variation in local implementation. If Just as with the HOT lane does not current HOV best practices, those that meet all the HOV requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on and wish to use the HOT lanes need to navigate themselves to the forumHOT lanes; a change to they are not be routed onto them by the guidelines or an exception may Waze client. As with standard HOV lanes, HOV users need to be made recalculate the route for Waze to snap them to the local variationHOT lane.</span>
<span style="text-decoration: line-through;">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.</span>
=== Toll roads ===
:''For other uses see [[Toll (disambiguation)]].''
Roads with tolls can be indicated by checking using the checkbox '''Toll road''' box in the Add Restrictions menu 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 set segments as toll box setting for segments that lead roads if they are leading 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.
* ''For more information, see advanced topic on the [[Time-based Tollstoll]] for mapping tolls that do not charge all the timepage.''
=== Time Restricted Turns ===
The Waze Map Editor and routing engine supports support 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.
=== 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.
=== Parking Lots ===
{{mbox | type=important | text = {{As of | 2018 | 10}}, guidance changed to recommend more detailed mapping of Parking Lot roads, in those lots which should be mapped. There is no priority to adapt existing lots to the new standards unless working on or near the lot for other reasons or there is guidance from a senior editor to pursue it.}}
Mapping a the roads inside parking lots serves the following purposes:# It allows Waze to provide door-to-door directions to Places within the lot.# It allows Waze to recognize that the client is off the main road, avoiding erroneous traffic reports.# The '''[[Road types/USARoad_types#Parking_lot_road|Parking Lot Road|]]''' road type prevents routes from transiting the lots to other destinations.# It allows Waze to calculate estimated times for walking from the parking lot road]] serves three purposes:to destinations, and to calculate walking times for users leaving Places near the lot.
*it allows Waze For information on how to provide door-to-door directions within map '''Parking Lot Area (PLA) Places''', see the [[Places/Parking_lot]] page. Parking lot;*it allows Waze roads are not limited to recognize that the client is off the main roaduse with PLAs, avoiding erroneous traffic reports.*using the special type prevents Waze from routing traffic through the parking lotthough they are best used in combination.
For marking The '''Parking Lot Road''' type exists to allow proper navigation into and out of parking lots with places see the information on the [[Places/Parking lot|while discouraging routes through parking lots. Waze applies a penalty to routes which transition from Parking Lot Place type]]Road to other road types. Parking This transition penalty decreases the chances that Waze will route through a parking lot roads are not limited as a shortcut but doesn't interfere with navigation to use with the or from points within parking lots. Avoid mixing road types within a parking lot place so as to avoid triggering the transition penalty unnecessarily. See [[Road_types#Parking_lot_roads]] for more information on this road type, though they are often used together.
The Parking Lot Road {{mbox | type exists to allow the mapping of = neweditor | text = All roads, including parking lotslot roads, while discouraging [[Creating_and_editing_road_segments#Confirm_the_road_by_updating_details|must be verified]] by having a street and city name applied or by utilizing the routing server from using them for through navigation‘None’ checkboxes. Waze applies a <br /><br />If [[Routing penaltiesPlaces#Residential_point_place|transition penaltyResidential Point Places (RPPs)]] for leaving a Parking Lot Road segment to enter another road type. This penalty decreases are used along the chance that Waze will route through a parking lot as a shortcut but allows better navigation , adding alternate street/city names could be required if the RPP is some distance from the named road. If an RPP fails to save near an unnamed PLR, or if in and out of a parking lot. It is advised not -app routing fails to mix road types within a parking lot navigate to avoid triggering the transition penalty unnecessarilyPLR, add the street & city names as an alternate on the PLR. One or more tile updates may be required before RPPs function near PLRs with alternate street/city names.}}
==== Shopping Centers Large Parking Lots ====When mapping large parking lots, map each aisle of the parking lot. Add any appropriate turn restrictions, one-way segments, etc., as you would with any road.
When mapping a large On any two-way segment which travels directly along perpendicular parking lot (espaces, set the U-turns at either end of the segment to Allowed.gThis enables the routing server to implicitly direct the user to exit their parking spot in the optimal direction.Typically aisles for angled parking are one-way, at a shopping center) consider mapping only the following:and U-turns are not available. In rare cases, angled two-way parking may occur, and in this case, u-turns should be Prohibited.
*Main entrances from the roads outside the parking lot{| class="wikitable" style="margin: auto;"|-| [[File:AngleParking.jpg]] || [[File:PerpendicularParking.jpg]]*Lanes that run along storefronts|-*Lanes at the edge of the lot which run alongside public roads (prevents Wazers in the | PLR aisles with angled parking || PLR aisles with perpendicular parking area from "snapping" to the public road, and then sending it incorrect speed information)*Primary travel lanes that serve to get people from one area of the lot to another|}
Remember, the goals here are usability and simplicity==== Parking Garages ==== [[File:ParkingGaragePLRs. When in doubt, imagine yourself in jpg|thumb|right|PLRs for a car in Parking Garage]] Parking garages should not have each lane visible on the lot at various pointsuppermost parking level mapped. Instead, each entry 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 should be mapped as few convolutions one-way or two-way as possibleappropriate. The lanes that are used the most in this thought experiment should be mapped {{As of | 2018 | 10}}, with the rest being omitted. You can turn on the GPS points layer ([[Shortcut key]] Shift-G) to see where traffic is concentrated to get a sense of what needs mapping.<brPlaces/>[[File:ParkingLotRoad ShoppingCenter.pngParking_lot|714pxParking Lot Areas (“PLA”)]] In particular, '''do not''' map every single lanesupport multiple entries. For this reason, connect the entry and especially not every exit road segments to a single parking space (it has been done!)segment, with the PLA’s entry point set along that segment. This serves no purpose but allows Waze to choose the best entry to clutter the map, confuse directions, and put an unnecessary burden garage depending 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 maproute’s starting location.
==== Small Parking Lots ====
[[File:OneWayPairPLR.jpg|right|frame|Using a single two-way segment to approximate two one-way aisles]] For small lots, if there is only one entrance and one exit, or if there are multiple entrances/exits near to each other on the same road, then it may not be necessary to add PLRs at all, especially if the entrances and exits are on a divided or one-way road (so there's effectively only one way in and one way out). Small parking lots should be mapped if:
# there are entrances/exits to the lot on more than one street;
# there are nearby PLRs that might cause a user to be snapped to the wrong lot;
# the Place served is a gas station or has a drive-thru.
Parking lots that serve a If the small number lot is on at the corner of businesses should be minimal: enough to give two or more non-PLR roads, the driver correct directions into and out value of the lot, and navigate should be carefully weighed against the damage to a particular business(turn timing) done by adding nodes near an intersection. Very small lots with one entrance and one exit could even be represented by a single segment running through Consider if the parking area (either addition of a diagonal across the lot if it connects [[Junction Box]] is needed to roads on each side, or a single, flattened curve for strip mall-style lots with entrances and exit along the same road)resolve data collection concerns.
To permit a route to be given to exit If it is determined that PLRs are desirable in a small parking lot from , then follow the same point the instructions as when mapping a large lot. However, in cases where a small store-front parking lot was enteredhas a pair of one-way aisles, such as at a ‘strip mall’, [[Turn_restrictions#Uit is acceptable to use a single two-turns|way road segment that approximates the location of both aisles. In this case, enable the u-turns]] may be enabled at the ends on either end of the parking lot road. This is particularly relevant where a single parking lot segment connects two different street segments such as is common for many corner [[Places/Gas_Station|gas stations]], so users traveling in either aisle will get efficient routes.
==== Drive-Through Lots ====
===== Illustration =====
For example, in the configuration shown below , if routing from the west parking lot, there is no transition penalty to route through the gas station parking lot on the east side of the street if routing east on Riva Rd. Conversely, if routing to the west parking lot from Riva Rd. there is no transition penalty to use the gas station.
[[File:PLA.png|center]] {{clear}}
[[File:PLB.png|right]]This potential problem arises when two parking lots on opposite sides of a street connect at the same junction node on the street.{{clear}}
[[File:PLC.png|right]]If this configuration causes routing problems it can be solved by changing the road type of one (or both) of the parking lot roads that intersect with the street.{{clear}}
[[File:PLD.png|right]]A five meter {{:Segment length/Minimum}} or longer stub of a different road type will accomplish the same result.{{clear}}
[[File:PLE.png|left]]If the street is a divided highway, then the road type of the crossover segment may be changed (this may also allow [[U-turn_prevention#Avoiding_U_turns|U-turns]] at the crossover segment).
{{clear}}
== New Roads ==
=== Recorded via Client ===
Once you start editing a road, it changes from red (a new road) to the colour 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.
# 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.
*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}}
1,270
edits