Best map editing practices: Difference between revisions View history

Latest revision as of 05:07, 6 April 2020

The purpose of this page is to help all map editors design maps that work best for the end-user whilst 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 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.

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 permalink of the road to the map editing forums to get additional feedback from other editors
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.

A road may be divided when any of the following conditions are met:

It is a 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 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.

A road should not 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 driver side 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

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.

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:

1. Select the two segments to be merged and set them both to two-way.

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.

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.

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'll find that all the (alternate) road names are lost !

Freeways, Major Highways and Ramps

Useful long distance navigation is impossible with Waze if the highways structure is broken. For long distances the routing server typically prefers the use of FW, MH and Ramps. Because those limited-access roads offer more to think about (and more opportunities to mess them up) than typical surface-road work, it is important to lock them at the correct levels in order to protect the integrity of the map. Refer to the Road Types section for the advised lock levels.

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.

As stated elsewhere, off-ramps should be named correctly as per the UAE naming guidelines. Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality, as standard at L5.

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 deleting a junction for more information.

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 Railroads under Road Types for more information.

Toll roads

Roads with tolls can be indicated by checking the Toll road box on the road segment properties tab. Mark a segment as a toll road only if there is a toll gate ON the segment. Do NOT check the toll box setting for segments that lead up to the 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.

The routing server will add a 3 minute penalty to a route with TOLL (transition from non-toll segment to toll segment). So routes not using toll roads will have a slight preference over toll roads, even if they take slightly longer !

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

In our editing and driving experience, once you learn 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

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 Road Types for our 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 unlocking an object above your rank for more information.

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 Malls

When mapping a large parking lot (e.g. at a shopping mall) 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.

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 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 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 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.

Adding New Segments

Each segment that is added in WME must minimally have the Country, City, and Street information added to it. A segment which is missing any one of these will be OUTLINED IN RED to show it is unfinished. If there is no City and/or Street then the "None" box(es) must be selected.

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 usable.

Follow these simple steps, as best you can, and get it right the first time. Map Editing explains how to carry out these steps.

Align the geometry of the road to the aerial image unless that is not appropriate in your area
Enter the correct name and road type for your road. Please make sure to select the correct city name. When unsure enable the City Layer in WME to verify the correct City name, check adjacent segments or ask someone in order not to upset the city polygon
Make sure the road has the correct directionality. Most roads should be 2-way with ALL turns ALLOWED. As standard the setting in WME is 1-way with turns disabled! In order to avoid having to individually change direction and enable all turns we advise you check and change the WME settings. It is far more easy to disable just a few turns and there is less risk of forgetting to overlook any disabled turns. The Toolbox feature where you can easily display all red turns can be a great help
Do NOT enable the uturns at the end of segments. Those are only enabled in some particular situations
Add junctions where the road intersects with other roads. Restrict any turns that are not allowed. On a typical symmetrical junction all disabled red turns should also be symmetrical when displayed

@@ Line 1: / Line 1: @@
-The purpose of this page is to help Area Managers & others 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 [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and  [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular 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.
+The purpose of this page is to help all map editors design maps that work best for the end-user whilst 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.
-If you find something missing from the 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 [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum].
+==Overall Goals==
-== 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.
-=== Usability ===
+===Simplicity===
-When it comes to the map, the first & 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.
+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.
-=== Simplicity ===
+===Retention===
-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.
+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"'''.
-=== Retention ===
+==In Practice==
-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:
-=== When (Not) to Split a Two-Way Road ===
+#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
-It is not always a good idea to split anything short of a freeway or major highway--which use nothing but ramps to enter/exit--into two one-way roads.
+#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 [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors
+#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.
-Some formal guidelines - '''A road should be split if:'''
+'''A road may be divided when <u>any</u> of the following conditions are met:'''
-* There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass.
+*It is a Highway or other Limited Access Highway using the "Freeway" road type,
-* GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level.
+*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]],
-* A road with a non-drivable surface (of any width) between the directions of travel where many left turns are physically impossible due to the median.
+*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
-* A road with a non-drivable surface (of any width) between the directions of travel where there are three or more lanes in each travel direction.
+*U-turns are required to properly make turns from public drivable road types that are blocked by a median.
-* U-Turns are required to properly make turns that are blocked by a median.
-* It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type.
-'''A road should not be split 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 every intersection.
-* There is a center turn lane, even a wide one, between directions of travel, does not count because it is drivable.
-* Google Maps or other mapping source show it as a split road.
-Remember that splitting and unsplitting 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 split road.  Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting.  Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before.  (I strongly believe that, for every mile of road that an AM wants to split into one-way roads, he should first merge a mile of split roads back into a two-way road. [[Best_map_editing_practice#How_to_.22Un-Split.22_two_One-Way_Roads|Check out what's involved]].  It builds character.)
+'''A road should <u>not</u> be divided when:'''
-=== How to "Un-Split" two One-Way Roads ===
+*There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above)
-Sorry to say it, but 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 splitting a road in the first place.  And then think some more.
+*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 driver side 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
-When you come across a road in your area that has been split but shouldn't have been--just look for the highest concentration of problem reports, and you'll find them!--you have some major map surgery ahead of you.  Basically, for the length of the road, you're going to:
+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.
-# delete road segments on one side or the other*, including segments that connect the two sides;
+====How to un-divide two one-way roads====
-# remove all "orphaned" junctions;
+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.
-# 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; and
-# adjust the geometry to move the two-way road segments to the middle of the road.
-'*' It usually saves time to preserve whichever side is already connected to more roads, so you may want to delete one side in some places, and the other side in other places.  Just remember to re-connect them later.
+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.
-It isn't difficult once you have gone through the process a couple times.
+{{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.}}
-'''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first.  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 will be lost.  I wish I were kidding.
+The steps below show how to properly merge two one-way roads and preserve the underlying house numbers.
-=== Highways and Ramps ===
+This is our example road segment.  For the entire length of the road you need to:
-Useful long-range navigation is impossible with Waze if the highways are broken.  Since 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.
+[[File:undivideRd1.jpg]]
-==== Roads ====
+. Select the two segments to be merged and set them both to two-way.
-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 & exited solely by ramps.  Such roads almost always should be mapped as separate one-way segments--and other roads almost never should be.
+[[File:undivideRd2.jpg]]
-==== Ramps ====
+. Disconnect both segments from one side of the section being un-divided. It is best to disconnect alternate ends of each segment as shown.
-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".  Ramps should always be locked to preserve directionality, since they often run especially close to other ramps that flow in the opposite direction.  (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.)  Remember to check connectivity and turn restrictions while you're there.
+[[File:undivideRd3.jpg]]
-*There is a more detailed descriptions of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]].
+. 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.
-*Be sure to understand the difference between ramps and [[At-Grade Connectors]].
+[[File:undivideRd4.jpg]]
-==== Overpasses & Underpasses ====
+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.
-Recent experience has changed my thinking regarding road levels.  Given the current editor limitations, I have found that it is more important to know that road level 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 level across multiple segments of the same road.
+#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.
-I use level 0 as a "sentinel value" that signifies that a segment has no overpasses or underpasses.  When editing an over/underpass, if either segment is at level 0, set it to a non-zero value that reflects its relative level.  If both levels 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.
+Also be sure to check the following:
-In many cases, the conflict can be resolved simply by adjusting one segment's level, or perhaps several segments will need to be adjusted.  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.  Or perhaps take a course in Topology at your local community college.
+#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.
-Occasionally you will 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 levels 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.)
+Now repeat the entire process for the remaining segments matching the two opposite from each other.
-==== Caveat re. Levels ====
+It isn't difficult once you have gone through the process a couple of times.
-No matter what levels 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 levels of the road segments are correct, and that all the other info. of each pair of road segments match.  At that point, deleting the junction will most likely work.  If not (perhaps because a ramp or another road segment prevents you from deleting it), you can try:
+'''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 (alternate) road names are lost !
-==== Bridging Roads ====
+===Freeways, Major Highways and Ramps===
-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 level increased by 1.  Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their levels are correct, and then re-connect them.
+Useful long distance navigation is impossible with Waze if the highways structure is broken. For long distances the routing server typically prefers the use of FW, MH and Ramps. Because those limited-access roads offer more to think about (and more opportunities to mess them up) than typical surface-road work, it is important to lock them at the correct levels in order to protect the integrity of the map. Refer to the [[Road types|Road Types]] section for the advised lock levels.
-==== Handling Restricted Lanes ====
+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.
-At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc..  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.
-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 will help (in terms of testing and making the feature available) if these lanes are already mapped.
+As stated elsewhere, off-ramps should be named correctly as per the [[Names|'''UAE naming guidelines''']]. Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality, as standard at '''L5'''.
-The best partial solution the community has come up with so far is to leave these segments' directionality as  whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''.
+Remember to check connectivity and turn restrictions while you're there.
-This "solution" will give routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It will 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 will then be 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.
+Be sure to understand the difference between ramps and [[at-grade connectors]].
-=== Toll roads ===
+===Overpasses &amp; Underpasses===
-Roads with tolls can be indicated by checking the '''Toll road''' box on the road segment properties tab. Only mark segments as toll roads if:
-*there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment
-*there is no way to drive on that segment without eventually paying a toll (such as at an exit)
-In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road.
-=== Time Restricted Turns ===
+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.
-Waze currently has no provision for handling this type of restriction, although it is planned for the future.  In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and allow the turn.  This way, waze will always give an optimal route and the driver can decide (based on local conditions) whether or not to use it.
-=== When to Use Ramps in an Intersection ===
+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.
-Please see the discussion on [[At-Grade Connectors]].
-=== When to Create a Roundabout ===
+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.
-In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]] in Cartouche, 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 that a roundabout should never be used in place of an end-node on dead-end or cul-de-sac streets.
+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.
-=== Locking Segments ===
+===Caveat re. Elevation===
-It is not recommended to lock segments in residential neighborhoods. Locking should only be used on high-value roads and complicated junctions to prevent inexperienced lower level editors from making changes.
-NEVER lock a segment unless are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct.
+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.
-If you run into a segment or junction that is locked by someone at a higher editing level than you, select the segment(s), copy the [[permalink]] of that location, and post it in the [http://www.waze.com/forum/viewforum.php?f=265 Unlock request forum].
+See also [[Creating and editing road segments#Road elevation|Road Elevation]].
-'''Locking should be used sparingly and carefully.'''
+===Bridging Roads===
-=== Junction Style Guide ===
+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.
-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]] will provide the best practices with the many different types of junctions.
-== New Roads ==
+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.
+===Toll roads===
-=== Parking Lots ===
+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 gate '''ON''' the segment. Do NOT check the toll box setting for segments that lead up to the  toll segment even if they have no other exit except the final toll segment.
-Mapping a parking lot serves two purposes:
-*it allows Waze to provide door-to-door directions within the lot
-*it allows the Waze client to get off the main road, avoidiing erroneous traffic reports
-==== Shopping Centers ====
+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.
-When mapping a large parking lot (e.g., at a shopping center), the main entrances should be mapped, along with any lanes that run along storefronts, and other 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 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; the rest should be 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.
+The routing server will add a '''3 minute penalty''' to a route with TOLL (transition from non-toll segment to toll segment). So routes not using toll roads will have a slight preference over toll roads, even if they take slightly longer !
-[[Image: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 & expertise can be better used elsewhere in the map.
+See advanced topic on [[Time-based Tolls]] for mapping tolls that do not charge all the time.
-==== Small Parking Lots ====
+===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.).
-Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into & 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.
+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===
+In our 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.
-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.
+'''''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 [[Road types|Road Types]] for our 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.
-==== Drive-Through Lots ====
+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.
-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 will be necessary to build the loop using two segments.''
+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.
+===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.
-==== Use of the Parking Lot Road Type ====
+==New Roads==
-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.  Waze has changed the way that Parking Lot roads route as of June 2012.  Parking Lot roads now have a transition penalty when transitioning from the Parking Lot road to another road type.  This penalty decreases the chance that Waze will route through a Parking Lot as a shortcut but allow better navigation in and out of the Parking Lot.  Every segment that is used to map a Parking Lot should be of the Parking Lot segment type.  It is no longer advisable to mix road types within the Parking Lot.
+===Parking Lots===
-=== Recorded via Client ===
+Mapping a [[Road types/USA#Parking Lot Road|parking lot road]] serves three purposes:
-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 will go 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 realise it is driveable.
+*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
-Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps.
+*it prevents the Waze client from routing thru-traffic along the parking lot segments
-# 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 ===
-Even though a proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in Cartouche, when it is first created, the segments are configured as new roads.  They will need to be edited as above before they will become part of the live map.
-== Classification of crossings ==
+'''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]].
-Different types of crossings will have [[classification_of_crossings|standard ways to handle them]]
-== Cartouche (old editor) Caveats ==
+====Shopping Malls====
-'''''Cartouche has been superseded by Waze Map Editor (WME) and should only be used by experienced map editors to access a few features that are not available in WME.  As of January 2012, Waze developers have expressed their intention of taking this editor offline, but they have not done so because of these few unavailable features in WME.  Many of the problems listed in this section have been solved with WME.'''''
-===Features only available in Cartouche (old editor)===
+When mapping a large parking lot (e.g. at a shopping mall) consider mapping only the following:
-*Alternate names for segments (currently not referenced, but may have future value)
-*Removal of separating line (obsolete feature, but useful for getting rid of the black line on the Primary Street segments, which may make it difficult to see arrows which indicate the directionality of the segment - also for the sanity of editors who can't stand the sight of that black line.  Has no effect on routing or client maps whatsoever.)
-*Viewing of Update Requests sent prior to February 2012, or URs that have been sent via LiveMap.
-*Entering/editing of house numbers (not referenced in basemapped countries).
-===Everything listed below refers specifically to Cartouche.===
+*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
-Every tool, however good, has its limitations, and Cartouche is no exception.  For general editing, what you see is usually what you get, and if you read the copious online documentation in advance, you will be able to make sense of (and extricate yourself from) most situations that you run into when editing the map.  But there are a few things to watch out for, that can result in a lot of extra work for you if you miss them.
+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.
-=== Road Geometry and Alternate Names ===
+<br />[[File:ParkingLotRoad ShoppingCenter.png]]
-Simply put: when you edit the geometry of a road, any Alternate names assigned to it are gone.  It makes no sense, people have been aware of this for ages and it has not been fixed.  Perhaps it will be addressed in the next incarnation of the editor.  Until then: Nothing to see here, move along.  (Just remember to go back and restore the Alt names after the geometry is set.  Copy & paste are your friends...)
-Note that this only affects the segment whose geometry is actually being modified, and ''not'' any roads that might be connected to it via junctions.  So if you have a road with an Alt name (e.g., a minor highway), you may be able to adjust its geometry without disturbing its Alt name assignment by editing the geometry of adjoining roads instead.
+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).
-=== Directionality & Locking ===
+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.
-If Waze sees enough people driving along a road in a certain direction, it will conclude that travel in that direction is allowed, and update the map accordingly.  The problem is, client GPS signals can be inaccurate, and Waze can mistakenly think that you are on one road when you are really on another.  When this happens, one-way roads suddenly become two-way.  When this happens on a highway or one of its ramps, it can have far-reaching effects on navigation.
-'''UPDATE:''' Waze has changed its heuristics to make it more difficult for road directionality to change as described above, once it has been set via the editor.  Therefore, in order to allow automatic geometry adjustments, it is now better to leave roads unlocked after assigned them to be one-way.
+====Drive-Through Lots====
-=== The Turn Restrictions Layer is Broken in the Cartouche editor ===
+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]].''
-Just leave this layer off and use the [[Cartouche_-_Update_map#Highlight_Connectivity:|Highlight Connectivity]] feature instead.
-=== Connectivity ===
+====Use of the Parking Lot Road Type====
-Just because two roads are touching where there is a junction, don't assume they are connected.  Because you have "Highlight Connectivity" turned on (see above), you should notice pretty quickly that a segment is not connected.  To fix, either:
-* Highlight the disconnected segment and the one to which it needs to connect, in from-to order where one-way roads are involved, and use "Connect roads in order of selection" (or the 'c' keyboard shortcut)
-or
-* add a junction on top of the existing junction.  The new one will replace the old one.  Most of the time you will want the "Allow all turns" mode on, but sometimes when working with one-way roads it is easier to turn that option off and enable turns individually.
-=== Reducing Junctions / Consolidating Segments ===
+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.
-You will often see junctions in the middle of roads, where there is no intersection.  These "extra" junctions are often the result of editing attempts gone awry, and seem to be a magnet for ill-connected and incorrectly-named roads.  They multiply the number of segments that you need to maintain, and I'm sure they're not helpful to the routing servers.  In short, unnecessary junctions indicate problems, and should almost always be eliminated.  (The only exceptions are when they mark a change of city, or when you know that you will be connecting a road there very soon.)
-When deleting a junction, remember that the segments on either side of the junction have to match road type, name, city, state, and have compatible directions.  If both segments are two-way, or one-way in the same directions, it will work.  If they are both "no entrance", it will fail.  IMO this is a bug; just remember to change them to two-way beforehand, and then change the consolidated segment back to "no entrance" afterward.
+===Adding New Segments===
+Each segment that is added in WME '''must''' minimally have the '''Country, City, and Street''' information added to it. A segment which is missing any one of these will be '''OUTLINED IN RED''' to show it is unfinished. If there is no City and/or Street then the "None" box(es) must be selected.
-After the junctions are removed, you may need to adjust the consolidated segment's geometry to account for the missing junctions.
+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 usable.
-Please note that there are currently [[bugs can occur when deleting junctions]].
+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.
-=== How to Remove Multiple Junctions ===
+#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]]
-During the interval after pressing the 'y' key (to confirm removing a junction) and before Cartouche returns control to the Edit Panel, it ''is'' possible to click on additional junctions and use the 'y' key to delete them as well.  This often results in faster deletions because Cartouche is effectively deleting them in parallel; '''However,''' there is one known bug and one suspected bug associated with this practice, so its use is highly discouraged:
+#Enter the correct '''name''' and road '''type''' for your road. Please make sure to select the correct city name. When unsure enable the City Layer in WME to verify the correct City name, check adjacent segments or ask someone in order not to upset the city polygon
+#Make sure the road has the correct [[glossary|directionality]]. Most roads should be '''2-way with ALL turns ALLOWED'''. As standard the setting in WME is '''1-way with turns disabled'''! In order to avoid having to individually change direction and enable all turns we advise you check and change the WME settings. It is far more easy to disable just a few turns and there is less risk of forgetting to overlook any disabled turns. The Toolbox feature where you can easily display all red turns can be a great help
+#Do NOT enable the uturns at the end of segments. Those are only enabled in some particular situations
+#Add junctions where the road intersects with other roads. Restrict any turns that are not allowed. On a typical symmetrical junction all disabled red turns should also be symmetrical when displayed
-#Deleting adjacent junctions in this manner often causes nearby road segments to vanish, and need to be re-created.  I suspect this is due to a race condition.  Deleting adjacent junctions means you are deleting the junctions at both ends of a segment.  If the first junction is deleted, and then before the segment can be merged with its neighbor, the second junction is deleted, the road segment between them ends up being deleted.
+[[Category:Waze Map Editor]]
-#:''The workaround for this bug is to make sure you never multi-delete adjacent junctions.  However, I have started to suspect another bug that has sworn me off of multi-deleting junctions at all, adjacent or not:''
+[[Category:Convert to Subpages]]
-#Also probably due to a race condition, I believe that using this technique may corrupt the segment IDs of the road segments involved, causing route highlighting problems when using the Waze client to navigate.
+[[Category:Add Wikilinks]]

Search