Known issues
From waze
Revision as of 19:04, 11 April 2012 by Alanoftheberg (Talk | contribs)
Contents |
Service Issues
Check for current known service issues on the Waze Status webpage.
Recent Fixes
-
Known Issues
Waze App
Please see the Waze App Bugs and Issues page for bugs and issues with the Waze app.
Website (Dashboard, Community)
| Date | Issue Description | Workaround | Status |
|---|---|---|---|
| 2011-08-01 | Foursquare integration is broken. | Foursquare turned off their APIv1 functions, which Waze uses. Until Waze updates to use the new API, checking in via Waze will not be available.
The new API is available in Waze v3 and up. |
Resolved |
Waze Map Editor
- Always check waze status for the latest issues and information.
- Papyrus is the internal name used for the next generation Waze map editor.
- Papyrus uses the same live database as Cartouche, and therefore also has a separate instance for North America and World.
- Even though they access the same database, Waze Map Editor has a small buffer database or tables between it and the real data so there are occasional lapses in proper road display and potential for different display between Waze Map Editor and Cartouche
In the table below, "Region" values are as follows:
- All
- NA (North America)
- INTL (Global except for North America)
| Date | Region | Issue Description | Example Image/Link | Workaround | Status |
|---|---|---|---|---|---|
| 2012-03-21 | All | "My places | Drives" archive is often displaying some drives incorrectly marked as "Yesterday" or "Today". | http://www.waze.com/forum/viewtopic.php?f=10&t=15409&start=210#p145399 + http://www.waze.com/forum/viewtopic.php?f=22&t=16204&start=30#p149788 | Open | |
| 2012-03-21 | INTL | If a lower-ranking editor (no AM) creates all segments, joined in a junction and a higher-ranking editor locks all of them, the segments' former author can still modify their connectivity arrows through the junction. | Open | ||
| 2012-03-05 | All | City layer does not update when city/state/country attributes are changed on segments. | Open | ||
| 2012-02-12 | All | Cannot delete an unlocked segment last edited by a higher-ranking editor.
Location: Outside AM area, inside Editable Area Object: Unlocked segment Previous edit by: Higher-ranking editor Action not allowed: Deletion Actions allowed: all others |
Modify segment geometry. The segment can then be deleted. | Open | |
| 2011-11-13 | INTL | Sometime, when saving edits (not necessarily to a roundabout), it will result in an error and the highlight will show the error on a roundabout in another country. | http://www.waze.com/forum/viewtopic.php?f=186&t=13280 + http://www.waze.com/forum/viewtopic.php?f=10&t=15409&p=143027#p142916 | Undo some of the changes and try edits again. Possibly the undo is not necessary at all! | Open |
| 2011-09-07 | All | Very large landmarks "flip" their area covered at certain zoom levels. |  becomes  |
Waze Map Editor was supposed to hide very large landmarks which are more than 2 degrees in width or height. This may or may not be happening, but as of 2011-10-13, examples of this are still visible. | Resolved |
| 2011-10-10 | All | Locked status and possibly other attributes do not appear to save. Locked status particularly, does not save. | In general, this is resolved. There can still by sync errors which will cause this to happen sometimes, but it is not a systemic issue just related to the locked checkbox. | Resolved | |
| 2011-09-22 | All | All save errors are generic, without specific guidance or spotlight on the error. | Must progressively undo changes until the save goes through or undo all and do incremental changes and saves. | Resolved | |
| All | Separating line checkbox is unavailable. | Separating line will be not be added to the Waze Map Editor, and the display of the separating line on Primary Street road type will be removed. There is no use for this option. | Pending | ||
| INTL | Very few map problems appear. | Map problem detection is being rewritten and very few map problems are currently available. As the new editor matures, more automated detection will be added. | Resolved | ||
| INTL | Map error "Missing Road" shows way too often and in places where there are very few GPS tracks. | There is a flaw in the detection algorithm for this error which has been identified. A fix is supposed to go in by early November 2011. | Resolved | ||
| INTL | No map problems appear. | Map problems have not yet been implemented on the World server. Use Cartouche. | Resolved | ||
| All | Cannot see Update Requests. | Use Cartouche. | Resolved | ||
| All | Window space usage is not optimal. Too much wasted space and left details sidebar is too large. | Current maximum viewable map area is set to maximize browser performance using Waze Map Editor, which utilizes the browser for more functionality that previous editor versions. This is not likely to be changed. | Resolved | ||
| All | NEW:2011/12/12: Allow all connections creates routing server connectivity the wrong direction on one-way or no entrance roads. This is called "reverse connectivity." |  |
This function in Papyrus allows connectivity in all directions for all roads at the junction, regardless of the specified directionality of the roads. Use cartouche to disable then enable turns in the junction to set the correct connectivity. |
Resolved | |
| All | Disallow all connections doesn't actually do that. | This function in Papyrus disallows all connections for road directionality currently available. However, if any reverse-allowed connections are enabled, they are not disabled. To truly disable all connections, use Cartouche. | Resolved | ||
| All | Reverse connectivity is enabled when one-way roads are split in Waze Map Editor. | http://www.waze.com/forum/viewtopic.php?p=92528#p92528 | Select the new junction and use the "Disallow all connections" function or keyboard shortcut, then individually all correct connections.
UPDATE 2012-02-27: Waze Map Editor beta now properly allows all connections according to connected segment directionality. |
Pending | |
| All | When adding a segment which connects to the same segment twice (creates a loop), the first connection point does not split the first segment and create a junction node. | Working as designed. NOT AN ISSUE. Before saving, move the first node of the new segment, and then move it back to where you want to first junction to be created. Papyrus will now split the original segment. | Resolved | ||
| All | Cannot add alternate names. | Use Cartouche. Will be added to Waze Map Editor in the future. | Open | ||
| All | Yellow "add intersection" sign for crossing segments doesn't appear reliably. | Segments must be set to the same level, country, state (where applicable) and city. For recently drawn or modified segments which now cross each other at the same level, you may need to use the Permalink to reload the current view. The Add Intersection icon should appear above the intersection when both segments are selected. | Open | ||
| All | Moving the free end of dead-end street while it is selected will disconnect it from its terminal junction. This causes routing to fail on this road. | Move the end of a dead-end road by selecting the junction node at that end and moving it. | Open | ||
| All | A dead end road with no junction at the end will cause routing problems for the road as a departure point. When creating a new dead-end road in the editor, a junction is not automatically applied. | Open |
Cartouche (Map Editing)
- While server upgrades have markedly increased the speed of Cartouche there are times of day when it is still very slow. This may be because the servers are performing other tasks or because there are many map editors working at the same time. If you find the map editing to be painfully slow, we don't want you to become discouraged. The best advice is to wait and try again at a different time of day
- If you have the GPS Points layer selected it can be difficult or impossible to select a road because you are always selecting a GPS point. This can happen even if the GPS points are not visible at your current zoom level
- Newly plotted (unknown, red-line) roads are not showing in Cartouche at the 3 minimum zoom levels
- Bugs can occur when deleting junctions
In the table below, "Region" values are as follows:
- All
- NA (North America)
- World (Global except for North America)
| Date | Region | Issue Description | Example Image/Link | Workaround | Status |
|---|---|---|---|---|---|
| All | House numbers location changes slightly after saving an update. This is because the house number re-centers to the precise location of the mouse click which selected it. This will cause house numbers to drift. | Recommended to stop creating and updating house numbers. | Open | ||
| NA | House numbers repeatedly fail to permanently save (turn blue) due to various reasons. | Recommended to stop creating and updating house numbers. | Open | ||
| All | Changes in street names for house numbers are not saved. | Recommended to stop creating and updating house numbers. | Open | ||
| NA | House numbers street name turns blank immediately after creating and saving. | Recommended to stop creating and updating house numbers. | Open | ||
| All | House numbers cannot contain any characters other than numbers. | This is currently working as designed. | Open | ||
| NA | Cannot update geometry of new (red) roads until the road is given a type, state and name. | This is working as designed. You must first Edit the street, set the State if not set, and save before attempting to update geometry. | Open | ||
| ALL | Orphan nodes are hidden and are sometimes selected even when you cannot see them. | Delete them when you find them. When deleting road segments, remove them in such a way as to be able to remove road-end segments before deleting the road segment. | Open | ||
| All | Editing roads of multiple types will change all roads to type 'Street' upon saving. | Only edit roads of the same type per edit. | Open | ||
| All | Alt. Steet (Alias) road names can only be saved for a single segment at a time. Multiple segment selections will result in no changes (add/change/remove) to the Alt names. | Only make changes to Alt Names on single segment edits. | Open | ||
| All | English City Name field cannot be cleared/deleted. | If it is incorrect, set it to be the same as the City name. | Open | ||
| All | Alt street names are deleted when changing road geometry. | Open | |||
| All | Some segments have alt street names that cannot be removed (they remain after blanking the field and saving). | Delete ALL names (primary and alt) for the segment and save it, then add the correct names back. | Open | ||
| All | Segments cannot be selected with the "No Name Roads" layer enabled. | Find a no-name road with the layer enabled, then disable it to select the road. | Open | ||
| All | Safari on Windows does not display borders of controls (checkboxes, select menus, text boxes) with the Aerial Layer enabled. Checkboxes do not display their state at all. |
|
Open | ||
| ALL | GPS points are not selectable. | Working as designed. | Open | ||
| All | Highlight connectivity may not display correctly, especially for very recent changes. | This is due to database refresh and tile refresh timing. Deselect the segment(s), change zoom level, then select segment(s) again and connectivity highlighting should be correct. | Open | ||
| All | Restricted turn layer is not accurate. | Do not use the Restricted Turn layer | Open | ||
| NA | Only Area Managers can edit a Landmark. If you create a landmark and are an Area Manager, if any portion of the Landmark falls outside your managed area, you will not be able to edit it. |
|
Open | ||
| 2011-06-13 | NA | Landmark points cannot be added due to a bug. | Open | ||
| All | The prompt for speed camera speed asks for mp/h, but if your country uses km/h then the entered speed will be taken as km/h. | Open | |||
| All | Names containing single and double quotes (' and ") are not handled correctly | Avoid entering names using single and double quotation marks. | Open | ||
| All | Need to refresh browser to select roads after adding street | This behavior is working as designed in order to reduce the load on the server by batching certain types of updates. | Open | ||
| All | Autocomplete City and Street text boxes produces inaccurate suggestions. | Open | |||
| 2011-03-08 | All | Cartouche allows panels to be dragged vertically (accidentally) off the screen and they become unretrievable unless cache/cookies are deleted. Both Safari and Firefox allow the panels to be dragged up or left beyond the page and application window. At this point, the browser does not recognize or allow you to scroll up or left to retrieve the panel. Dragging right or down beyond the page does give scrollbars, but not panels dragged up or left. | Empty your browser cache. | Open | |
| All | When enabling the Map Problems layer, the View Panel defaults to showing problem Type 1, though the map itself seems to display all errors. | Change the Type selection to whatever you wish, typically 'All', 'Scan' or 'Merger' and you will then be able to select the problems which appear on the map. | Open | ||
| 2011-02-14 | All | The Map Problem drop-down menu for Type is dramatically different on different browsers.
|
Forum thread "Why? Browser differences in Map Problem Type dropdown menu" | Open | |
| 2011-05-01 | All | Enable All Turns on a node allows u-turns, and there is no way to restrict a u-turn. | Restrict all turns on the node, then enable turns manually one at a time. There is not a consensus that Waze actually utilizes segment-node-same segment routing at all. | Open | |
| 2011-05-04 | NA | Using the Select All Roads in Between function doesn't populate the State field when editing the multiple selections. Using the multi-select method does not have the same issue. | Multi-select each segment manually, or remember to populate the State field. | Open |
Routing
| Region | Issue Description | Example Image/Link | Workaround | Status |
|---|---|---|---|---|
| All | In general, there is a 650 mile/ 1047km restriction on navigation routes. | Some locations may still be restricted to 200 mile/322 km routes. The client will usually display that it cannot do routes over 1000 miles, but the real limit is around 650. | Open | |
| World | The icon display for roundabout directions are incorrect for countries that drive on the left. | Open | ||
| NA | The client does not display the name or give the proper verbal instruction for a ramp segment if the next segment is also a ramp segment. | The clients receive information for screen and speech prompts from the routing server. The current state is somewhat by design in an attempt to minimize "Exit to <blank>" prompts, but when a ramp segment does have a name, it should display it. That part is a bug. | Open | |
| When the client uses the "Prefer cookie munching" option, routing will ignore turn restrictions and road directionality. | Do not use the "Prefer cookie munching" option. | Open |
