WME errors: Difference between revisions View history

Revision as of 04:22, 2 August 2013

This page is under construction and is a work in progress. If you have comments or suggestions go to the forum on [error messages page].

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.

The alphabetical list of errors below will provide suggested steps to rectify the error.

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.

Landmarks

If editing a landmark, highlight the landmark 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 landmark, 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 landmark in the client app.

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

This can happen for two reasons.

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. Go back and edit the road name or mark it as NONE. Save again.

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. Edit the segment highlighted and fix the name of the city or state as necessary.

The highlighted segments are not connected by a node

WME has identified two segments ends that are very close to one another, but are not actually joined. Move one or the other segment end get it to "snap" to the other segment end. Save again.

You have no permissions to make some of the changes

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.

You can also 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.

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

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.

@@ 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 -->
+{{Red|This page is under construction and is a work in progress. If you have comments or suggestions go to the forum on [[http://www.waze.com/forum/viewtopic.php?f=276&t=56452|WME error messages page]].}}
-== Limited Access Interchanges ==
-''See also: [http://en.wikipedia.org/wiki/Interchange_(road) Wikipedia article on Road Interchanges]''
-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.
+-------------------
-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 [[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.
-'''Care must be taken to not enable all turns in any situation where ramps meet unless all possible flows of traffic have been considered!'''
+The alphabetical list of errors below will provide suggested steps to rectify the error.
-We also have to pay attention to the '''Level''' 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 levels must be different.
+== 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.
-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.
+=== Landmarks ===
+If editing a landmark, highlight the landmark 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 landmark, 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 landmark in the client app.
-=== Diamond Interchange ===
+== The highlighted road is too far from the city it was added to ==
-: [[Image:Jct_diamond.png]]
+This can happen for two reasons.
-''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.
+) 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. Go back and edit the road name or mark it as NONE. Save again.
-In the simplest form, this can be represented as single connections from the ramps to the surface street.
+) 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. Edit the segment highlighted and fix the name of the city or state as necessary.
-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.
+== The highlighted segments are not connected by a node ==
+WME has identified two segments ends that are very close to one another, but are not actually joined. Move one or the other segment end get it to "snap" to the other segment end. Save again.
-: [[Image:Jct_diamond_simple_turns.png]]
+== You have no permissions to make some of the changes ==
+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.
-If the ramps connect to the surface street at multiple points (be sure to read [[#How_complex_should_ramps_be?|How complex should ramps be?]], we have to avoid ramp-to-ramp routing as well as illegal turns which should use another ramp.  First we see the turns that must be restricted for the exit ramps:
+You can also 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.
-: [[Image:Jct_diamond_cplx_turns_off_L.png]]  [[Image:Jct_diamond_cplx_turns_off_R.png]]
+For [[Area Manager]]s, you may be trying to edit outside of your allocated area as well. Use the above techniques to determine the problem.
-Then we see what must be restricted for the entrance ramps:
+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.
-: [[Image:Jct_diamond_cplx_turns_on.png]]
-'''Note on Levels:'''
-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 ===
-: [[Image:Jct_cloverleaf.png]]
-''See also: [http://en.wikipedia.org/wiki/Cloverleaf_interchange Cloverleaf Interchange article on Wikipedia]''
-In a Cloverleaf Interchange, left turns are eliminated from all movements between the Freeway and the surface street. First check the exit ramps.
-: [[Image:Jct_cloverleaf_off_outer_turns.png]] [[Image:Jct_cloverleaf_off_inner_turns.png]]
-Then check the entrance ramps for illegal turns.
-: [[Image:Jct_cloverleaf_on_turns.png]]
-The connections to the Freeway segments may be treated in two ways:
-:[[Image:Jct_cloverleaf_options.png]]
-# (top) we can have the inner entrance and exit ramps have their own junction nodes with the Freeway.
-# (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.
-The determining factor of which design to use will partly depend on the actual size and scale of the specific interchange.
-'''Note on Levels:'''
-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.
-: [[Image:Jct_folded_diamond_u-turn.png]]'
-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 [[#How_complex_should_ramps_be?|How complex should ramps be?]].  Restrict all non-permitted turns.
-: [[Image:Jct_folded_diamond_off_turns_L.png]] [[Image:Jct_folded_diamond_off_turns_R.png]] [[Image:Jct_folded_diamond_on_turns.png]]
-'''Note on Levels:''' 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.
-=== Single Point Urban Interchange (SPUI) ===
-: [[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.
-The outer branches of the exit ramps are very much like in the case of a diamond interchange:
-: [[Image:Jct_SPUI_off_outer_turn.png]]
-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.
-: [[Image:Jct_SPUI_off_inner_turn.png]]
-Luckily the entrance ramp restrictions are similar to the diamond interchange:
-: [[Image:Jct_SPUI_on_turn.png]]
-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.
-: [[Image:Jct_SPUI_all_turns.png]]
-'''Note on Levels:'''
-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 level of the freeway segments above/below the single point.