Changes

From Wazeopedia

Best map editing practice

137 bytes removed, 1 year ago
m
Removed link to Classifications of Crossings page which was previously removed as unneeded; corrected numerous punctuation errors.
=== 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 ===
{{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.
[[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. 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: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}}
}}
<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.
[[Image:I-15-express-lanes.jpg]]
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 the 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 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:
For information on how to map '''Parking Lot Area (PLA) Places''', see the [[Places/Parking_lot]] page. Parking lot roads are not limited to use with PLAs, though they are best used in combination.
The '''Parking Lot Road''' type exists to allow proper navigation into and out of parking lots while discouraging routes through parking lots. Waze applies a penalty to routes which transition from Parking Lot Road to other road types. This transition penalty decreases the chances that Waze will route through a parking lot as a shortcut, but doesn't interfere with navigation to or from points within parking lots parking lots. Avoid mixing road types within a parking lot so as to avoid triggering the transition penalty unnecessarily. See [[Road_types#Parking_lot_roads]] for more information on this road type.
{{mbox | type = neweditor | text = All roads, including parking lot roads, [[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 ‘None’ checkboxes.<br />
<br />If [[Places#Residential_point_place|Residential Point Places (RPPs)]] are used along the parking lot, adding alternate street/city names could be required if the RPP is some distance from the named road. If a an RPP fails to save near a an unnamed PLR, or if in-app routing fails to navigate to the PLR, 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.}}
==== Large Parking Lots ====
# the Place served is a gas station or has a drive-thru.
If the small lot is on at the corner of two or more non-PLR roads, the value of the lot should be carefully weighed against the damage to (turn timing) done by adding nodes near an intersection. Consider if the addition of a [[Junction Box]] is needed to resolve data collection concerns..
If it is determined that PLRs are desirable in a small lot, then follow the same instructions as when mapping a large lot. However, in cases where a small store-front parking lot has a pair of one-way aisles, such at as at a ‘strip mall’, it is acceptable to use a single two-way road segment that approximates the location of both aisles. In this case, enable the u-turns on either end of the segment, 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}}
9,309
edits