From Wazeopedia

Best map editing practice

2,214 bytes added, 9 months ago
Toll roads: updated per
| contact =
| 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 [ 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 ===
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.
[ Un-Dividing Roads and Preserve HN - Video Reference]<br /><br />[ 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.
<span style="text-decoration: line-through;">At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car poolcarpool" 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></span>
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>
<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 separate 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.
=== 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 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 typesRoad_types#Parking_lot_road|Parking Lot Road|parking lot roads]] in a ''' road type prevents routes from transiting the lots to other destinations.# It allows Waze to calculate estimated times for walking from the parking lot 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 road type 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}}
# 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}}