User:Triage685/UR

VA specific

RIC Airport

There is a problem with routing to many airports in Waze. What happens is that you search for the Richmond airport, and Waze may pick-up multiple search results by default. The CORRECT destination is "Richmond International (RIC)" with a Sandston address on Terminal Drive. Unfortunately, that is not clear to users. If you select the Google Maps result, you end up in a neighborhood behind the airport, closest to the runways. Waze editors have notified Google and Waze to fix this problem for RIC. Not a great solution for your error, but the volunteer editors can't do much else to resolve the issue.

264-64 left vs right

There is both a left and a right side exit leading to I-64 E from I-264 E. Waze will try to route you to whichever it thinks is fastest at the moment.

Military bases

Waze is limited on what they can and can not map with regards to military bases by what is released to the public. Naturally this is somewhat limited for OPSEC purposes.

15th View St ramp to I-64 W

There is no set schedule for this on-ramp closure. It is closed whenever traffic is backed up at the HRBT to prevent people short-cutting the traffic through the neighborhood. It is currently set as closed M-F 3pm-7pm in the map as that is the typical heavy traffic time. I wish I could be more help, but we can’t keep up with these unscheduled closures.

NOVA HOV

Thanks for the report, the southern entrance to the Express Lanes are mapped.  The problem is that the speeders in the regular lanes during nonrush hours have made the time difference only 10-20 sec.  Waze needs at least 30 sec of time savings to change the route.

No response on UR

As there's been no response for some time, I'm closing this one. If there is still a problem, please submit a new map issue report. There's been no activity on this report for some time, so I'm taking the liberty of closing it. If there is still a problem, please submit a new map issue report.

More info needed

General Error:

Volunteer map editor responding. You reported a "general error". Waze didn't provide enough information to determine the problem, so please provide as much detail as possible - what was your route, and what was the error?

Volunteer map editor responding. Waze did not provide enough information to determine the problem. Would you please let us know what went wrong? Would you tell us your destination as you entered it into Waze? Thanks!

Turn Not Allowed:

Volunteer map editor responding. You reported a "turn not allowed" issue. Waze didn't provide enough information to determine the problem, so please provide as much detail as possible - which turn wasn't allowed? Was this a temporary restriction (due to construction)?

Wrong Driving Direction:

Volunteer map editor responding. You reported a "wrong driving direction" issue. Waze didn't provide enough information to determine the problem, so please provide as much detail as possible - what were your start and end points, and where was the routing wrong?

Volunteer map editor responding. Waze did not provide enough information to determine the problem. Would you please let us know what went wrong with the route Waze gave you? Would you tell us your destination as you entered it into Waze? Thanks!

Missing Road:

Volunteer map editor responding. You reported a "missing road" issue. Waze didn't provide enough information to determine the problem, so please provide as much detail as possible - what road is missing?

Incorrect Junction:

Volunteer map editor responding. You reported an "incorrect junction" issue. Waze didn't provide enough information to determine the problem, so please provide as much detail as possible - what is wrong with the junction?

Other:

Volunteer map editor responding. Waze doesn't provide enough information to determine the problem. Which address/location was incorrect?

Volunteer map editor responding. The Waze app doesn't necessarily display overpasses correctly, but this should not affect routing. Was this the issue, or is there another problem?

Fixes

The drop-down list of places that appears as you start to enter your desired destination is from 3rd party sources (typically Google maps). They generally put the stop point pin near the middle of the building which often causes Waze to route you to the street behind the destination. Type out enough of the name, hit the search button, and make sure you've slected the Waze results for more accurate routing.

I can't reproduce the problem, and get routings direct to the correct location of <>. Please try: 1) Delete any favorites or saved searches you have in the Waze app for that address and try again with a fresh search. 2) Tap the Wazer icon > Settings > Advanced > Data transfer > Refresh Map Of My Area. This forces a reload of maps to your device. 3) Clear Waze's app cache in your phone’s app manager. Let us know if any of these help!

Undivided Highway:

It's a common problem with the way Waze treats roads where there is a barrier, but the road doesn't fit Waze's definition of a divided highway. You will often be directed to the wrong side. You can read more about the issue here, if interested: https://www.waze.com/forum/viewtopic.php?f=618&t=89218

Were you directed to take a turn through a barrier? Unfortunately, it's an ongoing problem with the way Waze treats roads where there is a barrier, but the road doesn't fit Waze's definition of a divided highway. You will often be directed to take turns through the barrier. You can read more about the issue here, if interested: https://www.waze.com/forum/viewtopic.php?f=618&t=89218

Improper Route

Thanks for that detailed information. Unfortunately, the Live Map is providing only the more direct route on (fill in) today. This looks like one of those cases where the Waze routing engine, possibly due to reported traffic conditions and average speeds, decided to send you the roundabout way. Nothing that map editing would fix, I'm sorry to say.

Thanks for that additional information.The Waze Live Map currently estimates a <> minute difference between the more direct route and the roundabout route suggested by the app. This is one of those cases where the Waze routing engine, possibly due to reported traffic conditions and average speeds on the direct route at the time, decided that the roundabout way would be faster. Nothing that map editing would fix, I'm sorry to say, but please continue to report any map issues you encounter!

For temporary road closures, use the "Closure" button in the Waze app. That will provide a more timely alert to other drivers. A "map issue" report may not be looked at by a map editor until a few days have passed. (And map editors can't really do anything unless the closure will be a month or more.)

Judging by your GPS trace, you lost signal and Waze really didn't know where you were. Unfortunately, that's a problem with the GPS in your device or your satellite reception. Nothing that map editing would fix, I'm sorry to say, but please continue to report any map issues you encounter!

Thanks for your reply. Waze will sometimes have you do U turns if it believes it can save you time over going the normal way. These can sometimes be odd routes, but they should save you time. If they don't, waze will learn and stop offering these.

Either Waze thinks there is traffic or an incident up ahead, and is trying to take you around it to save time. (This traffic/incident may have already cleared up, but Waze will only know once people start driving through that segment at average speed.) -OR- Based on historical traffic data for that time of day, Waze thinks that the other route will be faster. (The only way to fix this is by people driving both routes and teaching Waze what the correct average speeds on those roads are.)

Waze doesn't give you any navigation instructions at a merge, or where a road's name changes, or where you have to turn a corner because there is nowhere else to go. This is by design; Waze only gives you turn instructions when you have to make a choice. Also, Waze doesn't give you directions to stay on the road you are already on, even at complicated interchanges. Some of these may change in the future, but for now, map editors cannot change any of these behaviors.

Report->Map Issue goes to volunteer map editors. There is nothing we can adjust in the map to fix GPS Chip problems. Please see https://wiki.waze.com/wiki/FAQ#Waze_is_repeatedly_losing_GPS_signal.2C_What_can_I_do_about_this.3F

Due to the inherent error in GPS chips, Waze will keep you snapped to the directions given until it is really, really, really sure you have deviated.

Waze tracks stop-lights by way of the average speed entering and exiting. It does not and should not mark every light on the map, though. Thank you for the report and rest assured that Waze is tracking the average speed through this and every other light and routing you the fastest (or shortest depending on your settings) route.

Hi! I'm a wazer like you working on your report. I would hate it too if Waze asked me to make a left turn through heavy traffic! Unfortunately, there is nothing we can do to tell waze to recommend a different route. The good news is that Waze keeps track of how long it takes to make a turn. Thanks to your experience, other drivers are less likely to be routed this way during peak traffic hours. Thank you for your report!

HOV Lanes are very problematic for WAZE due to the close proximity to normal freeway + inherent errors in GPS chips. The app does not, yet, fully support HOV lanes, but it is a priority for WAZE staff and should be fully implemented soon. In the mean time, volunteer editors are doing all we can to support the HOV lanes with the tools we currently have.

App problems

Report->Map Issue goes to volunteer map editors. We can only adjust the map. There is nothing we can do to fix problems with the app. Please report this problem via https://www.waze.com/support/

You might need to force a refresh in your client app with Setting>Advanced>Data Transfer>Refresh map of my area.

Favorite Wiki pages

The most valuable Wiki pages that I wish I had found sooner:

Best Practices: Just what it sounds like. Editing community agreed best practices.

Junction Style Guide: Explains the often odd looking intersections.

Places: All you ever wanted to know about "places" in the map editor...and then some.

Parking Lots: All about parking lot places. When to add, when not to add, etc.

Incorrect Edits: List of common editor mistakes and how to fix them. I wish I had read this one on day one.

WME Errors: When you can't save an edit, this page will probably explain why.