Main Page Waze Map Editor WME errors

WME errors: Difference between revisions View history

Waze Map Editor
VisualWikitext
imported>Kentsmith9
(→‎Collector/distributor cloverleaf: clarified why ramps may look different from this and can be fixed to look this way.)
imported>Kentsmith9
(Added category)
Line 1: Line 1:
<!-- To Do - Add protection from ramp to ramp return to freeway for split highways. https://www.waze.com/forum/viewtopic.php?f=276&t=23294&view=unread#p222769 -->
The [[Waze Map Editor]] (WME) will periodically run into problems when trying to save information. Depending upon the error message you may need to do one of the following: 1) change what you last edited, 2) undo some number of prior edits, or 3) just reload the page and ignore the error.


When two roads meet in a limited access interchange (any situation where travel between grade separated roads is facilitated by ramps or slip roads alone), extra care must be taken.
Generally it is best to save before you exceed 10 changes. This minimizes the problems you run into when one of the early changes in your edit sequence has a problem and you have to undo everything else after that in order to determine what out of all your edits is causing the problem.


If an exit ramp lines up with an entrance ramp, care must be taken to restrict the straight through direction to prevent "ramp-to-ramp routing" where the routing engine may try to take a shortcut from the Freeway, to the exit ramp, to the entrance ramp, and back to the Freeway instead of staying on the Freeway. That motion is inefficient and may be illegal in certain jurisdictions.
The alphabetical list of errors below will explain the reason for the error and provide suggested steps to rectify the issue.


'''Care must be taken to not enable all turns in any situation where ramps meet unless all possible flows of traffic have been considered!'''
== An error occurred while saving ==


We also have to pay attention to the '''elevation''' of the road segments since there will typically be many bridges and overpasses for any limited access interchange. If two roads cross without connecting, their elevations must be different.
This is a general purpose error message that can occur for many reasons. Sometimes it is hard to identify specifically the problem. Here are some of the reasons you may run into this.


The following sections discuss some of the common Interchange designs. Note that some Interchanges may be a hybrid of these basic designs where one side or quadrant of the interchange may differ from the others.
=== Corrupt Roundabout ===


Before reading through this article, be sure to fully understand the information in the [[Junction Style Guide]].
'''Explanation:''' Sometimes roundabouts get corrupted from prior edits making further changes very difficult.


== Diamond Interchange ==
'''Solution:''' For simple parking lot roundabouts, it is usually fastest to delete the roundabout and recreate it with the changes you require. If it is part of a highway, deleting it will lose traffic flow history, so you may need to go to the forums for some troubleshooting assistance on the issue from more experienced editors.
: [[Image:Jct_diamond.png]]
''See also: [http://en.wikipedia.org/wiki/Diamond_interchange Diamond Interchange article on Wikipedia]''


Common in wide open spaces where land acquisition and geography are not concerns, this Interchange design has ramps equally distributed across all 4 quadrants.
=== {{anchor|Landmarks}}Places ===


In the simplest form, this can be represented as single connections from the ramps to the surface street.  
'''Explanation #1:''' If editing a Place, there may be a problem with the address fields.


Note: Be sure to restrict the straight through motion from the exit ramp onto the entrance ramp on the other side of the road. This will prevent the routing server from trying to route someone off the freeway just to get back on it. Even though it may be a legal direction for a vehicle, turn restrictions are only for controlling routing directions.
'''Solution #1:''' Highlight the Place again and check the address with the Edit button. Look to be sure the Country, State, and City are all three set correctly. In some countries there may be less or different fields, but ensure they are correct. Sometimes the name can be misspelled and it is hard to notice. If the fields (like city name) exist in another area too far away from the Place, you will get this error. If you enter a location that does not exist anywhere, it will accept it, but that will not help when trying to search for that Place in the client app.


: [[Image:Jct_diamond_simple_turns.png]]
'''Explanation #2:''' A Place cannot overlap any part of another place with the same name.


If the ramps connect to the surface street at multiple points, ramp-to-ramp routing should be avoided as well as illegal turns which should use another ramp. Review the section [[Junction_Style_Guide#How_complex_should_ramps_be?|How complex should ramps be?]] in the Junction Style Guide for more details on this topic.  
'''Solution #2:''' Either change the name of the Place to not be exactly the same as the Place it overlaps, or adjust them to not overlap.  


First we see the turns that must be restricted for the exit ramps:
=== Too many edits ===


: [[Image:Jct_diamond_cplx_turns_off_L.png]]  [[Image:Jct_diamond_cplx_turns_off_R.png]]
'''Explanation:''' If you are saving a large number of edits at one time, sometimes the server is unable to respond back to your browser before it times out. This is common when using a script to make global changes to an area.  


Then we see what must be restricted for the entrance ramps:
'''Solution:''' Generally for this problem, the saves will likely go through, but you have to use the [[Waze Map Editor#Permalink|permalink]] button or reload the page with your browser. Check the area after the reload is complete to confirm the changes were saved, otherwise make them again in a smaller quantity of changes between saves.


: [[Image:Jct_diamond_cplx_turns_on.png]]
== The highlighted angle is not allowed in a road ==


'''Note on elevations:'''
'''Explanation:''' There is an extremely sharp angle or "kink" in a new or changed segment. This can happen from you moving a junction or geometry node such that the segment doubles back on itself, or there is a bug in WME which can create this kink when a new junction is created.
The single surface street segment between the inner most ramps should be either raised or lowered in relation to the freeway segments depending on the actual geography at the interchange.


== Cloverleaf Interchange ==
'''Solution:''' Delete any geometry nodes at the kink and/or adjust the junction so that there is no extremely sharp angle in any segment.
: [[Image:Jct_cloverleaf.png]]


''See also: [http://en.wikipedia.org/wiki/Cloverleaf_interchange Cloverleaf Interchange article on Wikipedia]''
'''Detailed examples:''' The following shows situations where you will encounter this error caused by the WME junction bug and by the user. Click on the thumbnail images to view them in full size if necessary.


In a Cloverleaf Interchange, left turns are eliminated from all movements between the Freeway and the surface street. First check the exit ramps.
=== Junction Error ===
<gallery widths="250px" heights="250px">
Image:Highlighted_angle_junction1.jpg|Error on a junction
Image:Highlighted_angle_junction2.jpg|Close-up on the error
</gallery>
This most often happens when you end drawing a new segment onto an existing segment: double-clicking to shift+click to end the segment drawing mode sometimes adds a geometry node extremely close to the ending junction node.
{{clear}}


: [[Image:Jct_cloverleaf_off_outer_turns.png]] [[Image:Jct_cloverleaf_off_inner_turns.png]]
=== Roundabout Error ===
<gallery widths="250px" heights="250px">
Image:Highlighted_angle_roundabout1.jpg|Error on a roundabout
Image:Highlighted_angle_roundabout2.jpg|Close-up on the roundabout error
</gallery>


Then check the entrance ramps for illegal turns.
This also happens when connecting a segment onto an existing roundabout. WME has a bug which will junction onto the roundabout on the other side of an existing geometry node on the roundabout, which creates a kink in one of the roundabout segments. This occurs especially when connecting to an existing roundabout at [[Map_Editor_Interface_and_Controls#Scale|zoom level]] 6 or lower (higher elevation).
{{clear}}


: [[Image:Jct_cloverleaf_on_turns.png]]
=== Mid-segment Error ===
 
<gallery widths="250px" heights="250px">
The connections to the Freeway segments may be treated in two ways:
Image:Highlighted_angle_segment1.jpg|Error in the middle of a segment
 
Image:Highlighted_angle_segment2.jpg|Close-up doesn't quite show the problem yet
:[[Image:Jct_cloverleaf_options.png]]
Image:Highlighted_angle_segment3.jpg|Dragging a geometry node shows the error clearly
 
Image:Highlighted_angle_segment4.jpg|Deleting one geometry node fixes this error
# (top) we can have the inner entrance and exit ramps have their own junction nodes with the Freeway. Do '''NOT''' use this approach if there are [[#Collector.2FDistributor_Lanes|Collector/Distributor Lanes]] (or a similar situation) involved.
</gallery>
# (bottom) we can have the entrance and exit ramps share a single junction node with the Freeway. This allows us to eliminate the very short Freeway segment that may exist between the inner entrance and exit ramps.<br />It is best to offset this shared junction onto the Entrance ramp side of the surface street. This prevents the junction from accidentally being connected to the surface street or looking like it does. We favor the Entrance ramp side, because this would result in a slightly earlier exit instruction which is of course preferred over a late exit instruction.
{{clear}}
 
The determining factor of which design to use will partly depend on the actual size and scale of the specific interchange and if there is a [[#Collector.2FDistributor_Lanes|Collector/Distributor]] involved.
 
'''Note on Elevation:'''
The single surface street segment between the inner most ramps should be either raised or lowered in relation to the freeway segments depending on the actual geography at the interchange.
 
== Folded Diamond ==
: [[Image:Jct_folded_diamond.png]]
''See also: Discussion of Folded Diamonds and A2/B2 Partial Cloverleafs on the [http://en.wikipedia.org/wiki/Partial_cloverleaf_interchange Partial Cloverleaf Interchange article on Wikipedia]''
 
Geography or property ownership may prevent the ability for an interchange to be constructed with all ramps evenly distributed across the 4 quadrants of the interchange. When only two quadrants are used, it is typically called a Folded Diamond (basically a sub-type of a Partial Cloverleaf Interchange). The ramps may be all on one side (as in the examples in this section) or they may be located in diagonally opposed quadrants.


The unique situation presented by the Folded Diamond arrangement is having both Entrance and Exit ramps terminating on the same side of the surface street. Ideally both ramps should terminate on the same junction node to permit us to easily restrict the illegal and usually impossible ramp-to-ramp movement.
== The highlighted element was moved beyond the allowed distance ==


: [[Image:Jct_folded_diamond_u-turn.png]]'
'''Explanation:''' When stretching or extending an already existing segment by dragging an endpoint, it cannot be extended more than about 3600 feet (1100 meters) at a time.


Like with a basic Diamond Interchange, often it will be necessary to represent the ramps making multiple connections to the surface street. Be sure to read the article [[Junction_Style_Guide#How_complex_should_ramps_be?|How complex should ramps be?]] in the Junction Style Guide.  
'''Solution:''' If the segment must be extended, try extending it a shorter distance and save between each stretch.


Restrict all non-permitted turns.
== The highlighted road is too far from the city it was added to ==


: [[Image:Jct_folded_diamond_off_turns_L.png]] [[Image:Jct_folded_diamond_off_turns_R.png]] [[Image:Jct_folded_diamond_on_turns.png]]
This can happen for two reasons.  


'''Note on Elevation:''' Similar to a basic Diamond interchange, in most cases only the segment of the surface street that crosses the Freeway segments will need to be adjusted up or down.
'''Explanation #1:''' You may have just named a road with a city that already exists in the database, but is not anywhere near the location of the road.  


== Single Point Urban Interchange (SPUI) ==
'''Solution #1:''' Go back and edit the road name or mark it as NONE. Save again.
: [[Image:Jct_SPUI.png]]
''See also: [http://en.wikipedia.org/wiki/Single-point_urban_interchange Single Point Urban Interchange article on Wikipedia]''


A SPUI is a very space and flow efficient design, but it takes extra attention to ensure the turns are correct. And as the name indicates, ideally there should be a single junction in the center. You may need to tweak the geometry of segments a bit off of alignment from the real physical world, but it should be minor if the interchange is a true SPUI.
'''Explanation #2:''' You may not have edited the name of a road, but you edited one of its properties and the road was originally imported into the database incorrectly.


The outer branches of the exit ramps are very much like in the case of a diamond interchange:
'''Solution #2:''' Edit the segment highlighted and fix the name of the city or state as necessary.


: [[Image:Jct_SPUI_off_outer_turn.png]]
== The highlighted segments are not connected by a node ==


Where things get complicated is the inner branches leading to the Single Point.  You need to avoid ramp-to-ramp in two directions and a reverse flow turn. '''Note:''' The ramp-to-ramp motion to facilitate a U-Turn (the top left arrow in the image below) may or may not be allowed depending on the specific interchange.  Please validate this turn.
'''Explanation:''' WME has identified two segments ends that are very close to one another, but are not actually joined.


: [[Image:Jct_SPUI_off_inner_turn.png]]
'''Solution:''' Move one or the other segment end get it to "snap" to the other segment end. Save again. You may need to move the segment which isn't connecting away from the junction, save, then move it back and save again.


Luckily the entrance ramp restrictions are similar to the diamond interchange:
== While you were editing, the elements you're trying to save have been modified and/or deleted ==


: [[Image:Jct_SPUI_on_turn.png]]
'''Explanation:''' If you are saving a large number of edits at one time, sometimes the server is unable to respond back to your browser before it times out. This is common when using a script to make global changes to an area.  


If you were to look at all the restricted turns at once, you may get the false impression that something is very wrong. But as you now know, a SPUI has almost as many restricted turns as allowed ones.
'''Solution:''' Generally for this problem, the saves will likely go through, but you have to use the [[Waze Map Editor#Permalink|permalink]] button or reload the page with your browser. Check the area after the reload is complete to confirm the changes were saved, otherwise make them again in a smaller quantity of changes between saves.
R


: [[Image:Jct_SPUI_all_turns.png]]
== You have no permissions to make some of the changes ==


'''Note on Elevation:'''
'''Explanation #1:''' An area will be highlighted that reflects changes you are trying to make that are outside of your allowed [[Waze_Map_Editor#Editable_Area|Editable Area]]. There is a time limit for areas that you have driven. See the Editable Area link for more information.
The two surface street segments (between the outer ramps and connected to the Single Point) and the 4 ramp segments connected to the single point should all be the same level, either one higher or one lower than the elevation of the freeway segments above/below the single point.


== Collector/distributor lanes ==
'''Solution #1.a:''' Turn on the [[Map_Editor_Interface_and_Controls#Editable_areas|layer for Editable Areas]] to check if you have permission to edit all of the segment in question. Sometimes segments can stretch outside of your reach. The layer highlight will help you see when that happens. If your driven area has expired you will need to drive there again, or consider applying to be an [[Area Manager]].


These are lanes parallel to, but physically separated from, the lanes of a Freeway that serve to keep merging traffic out of the flow of through traffic on the mainline Freeway.
For Area Managers, you may be trying to edit outside of your allocated area as well. Use the above techniques to solve the problem.


Collector/distributor lanes serve as either:
'''Solution #1.b:''' If an object needs to be edited outside of your area, you can always go to the [[Discussion Forums]] to post a request for assistance by a higher level editor who has permissions for the object.
* some of the ramps in an '''exit or group of exits''', or
* local lanes in configurations with '''[[wikipedia:local-express lanes|local-express lanes]]'''.


'''Explanation #2:''' Your login credentials have expired and must be reloaded by logging back in again. This typically happens when you have a browser tab open with the Waze Map Editor and your login expires after about a 24 hour period.


=== Collector/distributor exits ===
'''Solution #2:''' Note the changes you made to the map. Press the [[Waze Map Editor#Permalink|Permalink]] button on the Waze Map Editor screen. You will receive a warning you will lose all information. At this point you have no choice and must accept leaving the page. After that the system will ask for you to log in again. Then you can make the changes again.
 
Some exit configurations make use of collector/distributor lanes to separate lower-speed merging traffic from high-speed through traffic. This is often used in cloverleaf interchanges and in groups of nearby exits.
 
==== Collector/distributor cloverleaf ====
 
This is a cloverleaf interchange that is connected to a collector/distributor instead of directly to the main roadway. Map collector-distributor cloverleaf ramps as you would any other ramp.
 
[[Image:Jct_fc_cloverleaf_bad.png]]
 
The [[Detour Prevention Mechanisms|detour prevention mechanism]] will prevent Waze from routing users onto the collector-distributor and back onto the freeway. Previously this feature was not available and the ramps were set up to restrict the through route. Some of these ramp configurations may still be set up that way, so they can now be configured as pictured above with the through route enabled.
 
==== Complex collector/distributor exit systems ====
 
[[Image:Collector-distributor-exit.png|thumb|right|450px|Collector-distributor lanes used in a group of exits on I-81 in Christiansburg, Virginia (Exits 118A-B-C)]]
 
Where collector/distributor lanes are used as part of an exit or group of exits, use the {{Ramp}} type for the collector/distributor lanes. Name the ramp segments as you would any other ramp segment.
 
{{clear}}
 
=== Local-express lanes ===
 
[[Image:Local-express.png|thumb|right|450px|A local-express lane configuration on I-96 in Livonia, Michigan]]
 
Local-express lanes are similar to collector/distributor exits, but on a larger scale. While collector/distributor exits typically have an exit number or numbers, local-express names typically share the same name, differentiated by "Local" for the collector/distributor lanes and "Express" for the thru lanes.
 
Where collector/distributor lanes are used as part of a local-express lane configuration,
*use the same type (most likely {{Freeway}}) for the Local lanes as is used for the Express lanes, and
*name the road as it is signed: typically "[Name] Local [Direction]": for example, "I-96 Local W" (and "I-96 Express W" for the Express lanes).
 
{{clear}}
 
== See also ==


Review the [http://en.wikipedia.org/wiki/Interchange_(road) Wikipedia article on Road Interchanges] for further information on this topic.
[[Category:Waze Map Editor]]

Revision as of 01:28, 25 April 2014

The Waze Map Editor (WME) will periodically run into problems when trying to save information. Depending upon the error message you may need to do one of the following: 1) change what you last edited, 2) undo some number of prior edits, or 3) just reload the page and ignore the error.

Generally it is best to save before you exceed 10 changes. This minimizes the problems you run into when one of the early changes in your edit sequence has a problem and you have to undo everything else after that in order to determine what out of all your edits is causing the problem.

The alphabetical list of errors below will explain the reason for the error and provide suggested steps to rectify the issue.

An error occurred while saving

This is a general purpose error message that can occur for many reasons. Sometimes it is hard to identify specifically the problem. Here are some of the reasons you may run into this.

Corrupt Roundabout

Explanation: Sometimes roundabouts get corrupted from prior edits making further changes very difficult.

Solution: For simple parking lot roundabouts, it is usually fastest to delete the roundabout and recreate it with the changes you require. If it is part of a highway, deleting it will lose traffic flow history, so you may need to go to the forums for some troubleshooting assistance on the issue from more experienced editors.

Places

Explanation #1: If editing a Place, there may be a problem with the address fields.

Solution #1: Highlight the Place again and check the address with the Edit button. Look to be sure the Country, State, and City are all three set correctly. In some countries there may be less or different fields, but ensure they are correct. Sometimes the name can be misspelled and it is hard to notice. If the fields (like city name) exist in another area too far away from the Place, you will get this error. If you enter a location that does not exist anywhere, it will accept it, but that will not help when trying to search for that Place in the client app.

Explanation #2: A Place cannot overlap any part of another place with the same name.

Solution #2: Either change the name of the Place to not be exactly the same as the Place it overlaps, or adjust them to not overlap.

Too many edits

Explanation: If you are saving a large number of edits at one time, sometimes the server is unable to respond back to your browser before it times out. This is common when using a script to make global changes to an area.

Solution: Generally for this problem, the saves will likely go through, but you have to use the permalink button or reload the page with your browser. Check the area after the reload is complete to confirm the changes were saved, otherwise make them again in a smaller quantity of changes between saves.

The highlighted angle is not allowed in a road

Explanation: There is an extremely sharp angle or "kink" in a new or changed segment. This can happen from you moving a junction or geometry node such that the segment doubles back on itself, or there is a bug in WME which can create this kink when a new junction is created.

Solution: Delete any geometry nodes at the kink and/or adjust the junction so that there is no extremely sharp angle in any segment.

Detailed examples: The following shows situations where you will encounter this error caused by the WME junction bug and by the user. Click on the thumbnail images to view them in full size if necessary.

Junction Error

  • Error on a junction

    Error on a junction

  • Close-up on the error

    Close-up on the error

This most often happens when you end drawing a new segment onto an existing segment: double-clicking to shift+click to end the segment drawing mode sometimes adds a geometry node extremely close to the ending junction node.

Roundabout Error

  • Error on a roundabout

    Error on a roundabout

  • Close-up on the roundabout error

    Close-up on the roundabout error

This also happens when connecting a segment onto an existing roundabout. WME has a bug which will junction onto the roundabout on the other side of an existing geometry node on the roundabout, which creates a kink in one of the roundabout segments. This occurs especially when connecting to an existing roundabout at zoom level 6 or lower (higher elevation).

Mid-segment Error

  • Error in the middle of a segment

    Error in the middle of a segment

  • Close-up doesn't quite show the problem yet

    Close-up doesn't quite show the problem yet

  • Dragging a geometry node shows the error clearly

    Dragging a geometry node shows the error clearly

  • Deleting one geometry node fixes this error

    Deleting one geometry node fixes this error

The highlighted element was moved beyond the allowed distance

Explanation: When stretching or extending an already existing segment by dragging an endpoint, it cannot be extended more than about 3600 feet (1100 meters) at a time.

Solution: If the segment must be extended, try extending it a shorter distance and save between each stretch.

The highlighted road is too far from the city it was added to

This can happen for two reasons.

Explanation #1: You may have just named a road with a city that already exists in the database, but is not anywhere near the location of the road.

Solution #1: Go back and edit the road name or mark it as NONE. Save again.

Explanation #2: You may not have edited the name of a road, but you edited one of its properties and the road was originally imported into the database incorrectly.

Solution #2: Edit the segment highlighted and fix the name of the city or state as necessary.

The highlighted segments are not connected by a node

Explanation: WME has identified two segments ends that are very close to one another, but are not actually joined.

Solution: Move one or the other segment end get it to "snap" to the other segment end. Save again. You may need to move the segment which isn't connecting away from the junction, save, then move it back and save again.

While you were editing, the elements you're trying to save have been modified and/or deleted

Explanation: If you are saving a large number of edits at one time, sometimes the server is unable to respond back to your browser before it times out. This is common when using a script to make global changes to an area.

Solution: Generally for this problem, the saves will likely go through, but you have to use the permalink button or reload the page with your browser. Check the area after the reload is complete to confirm the changes were saved, otherwise make them again in a smaller quantity of changes between saves. R

You have no permissions to make some of the changes

Explanation #1: An area will be highlighted that reflects changes you are trying to make that are outside of your allowed Editable Area. There is a time limit for areas that you have driven. See the Editable Area link for more information.

Solution #1.a: Turn on the layer for Editable Areas to check if you have permission to edit all of the segment in question. Sometimes segments can stretch outside of your reach. The layer highlight will help you see when that happens. If your driven area has expired you will need to drive there again, or consider applying to be an Area Manager.

For Area Managers, you may be trying to edit outside of your allocated area as well. Use the above techniques to solve the problem.

Solution #1.b: If an object needs to be edited outside of your area, you can always go to the Discussion Forums to post a request for assistance by a higher level editor who has permissions for the object.

Explanation #2: Your login credentials have expired and must be reloaded by logging back in again. This typically happens when you have a browser tab open with the Waze Map Editor and your login expires after about a 24 hour period.

Solution #2: Note the changes you made to the map. Press the Permalink button on the Waze Map Editor screen. You will receive a warning you will lose all information. At this point you have no choice and must accept leaving the page. After that the system will ask for you to log in again. Then you can make the changes again.

Retrieved from "https://www.waze.com/wiki/CommunityHub/index.php?title=WME_errors&oldid=32386"