Problems, bugs and limitations: Difference between revisions View history

No edit summary
(All pages about Waze App have been obsoleted - wikilinks removal accordingly.)
 
(26 intermediate revisions by 2 users not shown)
Line 1: Line 1:
* [Currently working] Routing server unavailable on 15 September. Client routing and [[Live Map]] routing fails with a message that the routing server could not be contacted. This has been an intermittent problem for nearly a week. On 9 September the [[How Waze calculates routes|routing server]] was unavailable for over 12 hours. It was also unavailable for an hour on 13 September.
Waze is a fun and sophisticated navigation app. In most developed countries Waze provides superior navigation information over commercial GPS applications. Like any developing application, there are issues and complications that are being worked to resolve. Many of them are cosmetic and do not prevent a fully gratifying experience when using Waze.
* [[Wandering cities]]
 
* 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.
Temporary issues are tracked in the official [http://status.waze.com/ Waze server status and issues] page.
* Aerial images are missing for USA and Canada in [[Cartouche]]. Aerial images previously present have reportedly been missing for months. Rumour is the USGS servers may be down. Waze is looking into it.
 
* If you have the "No Name Roads" layer selected in [[Cartouche]] you cannot select any roads
Note that Waze Bugzilla, a tool previously used for bug reporting, is no longer in use. The Waze community used to report and tracks bugs and problems in the Bugzilla application. At the time, it was the best place to identify any currently known issues. There is no official replacement for Bugzilla.
* 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.
 
* [[Known issues]] with [[Cartouche]] - needs updating
Some of the more common issues include:
* Newly plotted (unknown, red-line) roads are not showing in [[Cartouche]] at the 3 minimum zoom levels. Waze is aware of this and are working to fix it
* Routing distance is limited to about 1,000 miles (1600 km) distance. To route to longer distances, select a point between your origin and destination less than this limit.
* Anyone can create a landmark, but only [[Area Managers]] can edit landmarks once they have been created
 
* Some roads are reverting back to an unconfirmed state (back to Pacman roads with dots on them). Waze is investigating this. Please report any observed examples in [http://www.waze.com/forum/viewtopic.php?f=3&t=5495&p=40586#p40586 this forum thread]
* When you request a route the client device app assumes you are continuing in the same direction you last traveled. This is often desirable, but can lead to unnecessarily longer routes when you have a choice of direction from your starting position. If you start driving the other direction, it will recalculate the route.
* [http://www.waze.com/forum/viewtopic.php?f=18&t=4789 Known Waze service issues]
 
* [[Client device problems]]
* Issues and limitations on your supported model smartphone
 
* Odd routing: Waze has been known to make short detours. In these situation, Waze instructs the driver to turn off a road, only to have the driver immediately return to it. Ostensibly, this shortens the route, but it produces routes that many drivers consider unreasonable, and the time savings are often dubious. Editors can often work around this using the [[Detour prevention]] mechanisms.
 
 
<!-- do not include this template when transcluded -->
<noinclude>[[Category:Review Purpose]]</noinclude>

Latest revision as of 09:14, 1 April 2015

Waze is a fun and sophisticated navigation app. In most developed countries Waze provides superior navigation information over commercial GPS applications. Like any developing application, there are issues and complications that are being worked to resolve. Many of them are cosmetic and do not prevent a fully gratifying experience when using Waze.

Temporary issues are tracked in the official Waze server status and issues page.

Note that Waze Bugzilla, a tool previously used for bug reporting, is no longer in use. The Waze community used to report and tracks bugs and problems in the Bugzilla application. At the time, it was the best place to identify any currently known issues. There is no official replacement for Bugzilla.

Some of the more common issues include:

  • Routing distance is limited to about 1,000 miles (1600 km) distance. To route to longer distances, select a point between your origin and destination less than this limit.
  • When you request a route the client device app assumes you are continuing in the same direction you last traveled. This is often desirable, but can lead to unnecessarily longer routes when you have a choice of direction from your starting position. If you start driving the other direction, it will recalculate the route.
  • Issues and limitations on your supported model smartphone
  • Odd routing: Waze has been known to make short detours. In these situation, Waze instructs the driver to turn off a road, only to have the driver immediately return to it. Ostensibly, this shortens the route, but it produces routes that many drivers consider unreasonable, and the time savings are often dubious. Editors can often work around this using the Detour prevention mechanisms.