The new Waze Wiki, aka Wazeopedia, is now live at Wazeopedia.waze.com! While this legacy wiki will remain accessible for the time being, it is no longer updated by the community. For the most up-to-date guidance, please visit your local Wazeopedia.

Please do not make any more updates to these legacy wiki pages, all future updates should be made in your country's local Wazeopedia.

Clock over a larger globe

User:Mudge42

From waze
Jump to: navigation, search

Mudge42's Compendium of Mostly Useful Information

Technical Info

Priority of house number searches (info from a forum post by taco909 and also here)

In order of preference by the routing server/search engine:

  1. Waze Private Residential Place Points (Private Residential only, not "public")
  2. Waze House Number if and only if it has been "confirmed" (moved, even one pixel, by an editor in WME)
  3. Google database

The distinction between Private and non-private Waze places is important.
Non-Private Waze places search ONLY on the name (or alt-name) of the place. The address is simply there for the user to confirm
Private Residential Places search only on the address, EXCEPT that the person who added the place, and possibly his "friends" (unconfirmed) may search on the name.

Links I Like

A Favorite Street

DwarfLord's Boilerplate UR Responses

Voludu's Welcoming New Editors

Community Plugins, Extensions and Tools

USA Road Functional classification

MA Road Inventory
OLIVER (Statewide GIS)
Massachusetts Interactive Property Map

Massachusetts Information

Massachusetts/Major roads
Massachusetts/Cities and towns

Massachusetts Unlock Requests

Places

MapRaid Boston Place Browser

Real time closures

Editing manual

And my own boilerplate:

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/Wrong Driving Direction:

Volunteer map editor responding. Waze did not provide enough information to determine the problem. Would you please describe what went wrong, and 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)? 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? Thanks!

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 are the street names at the junction, and what is wrong? Thanks!

Other:

Volunteer map editor responding. The map issue report does not tell me your destination. What was it, as you entered it into Waze's search? Thanks!

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? Thanks!

Volunteer map editor responding. The route trace provided by Waze indicates that your GPS signal was off and Waze did not know where you were. Does this explain the problem? Thanks!

Map editors don't work for Waze, we are just volunteer users of the app. For privacy reasons, a map issue report does not include your complete route, your start or destination point, or your Waze user ID. So we have to ask for extra information to figure out what the problem might be.

Fixes

The problem is that Waze was getting the location of that address from Google Maps, where it is wrong. I've added the address to Waze; it will take 2-3 days for the map to update. Delete any favorites or saved searches you have in the Waze app for that address before trying again.

I have moved the navigation point for that address to the correct spot. It normally takes Waze's map and routing 2-3 days to update. Delete any favorites or saved searches you have in the Waze app for that address before trying again.

Waze was getting the location (map coordinates) of that address from Google Maps. Waze then directed you to the road closest to Google's location pin, which is <>. This has been fixed in Waze's map. Please allow 2-3 days for the map and routing to update, and delete any favorites or saved searches you have in the Waze app for that address before trying again.

Volunteer map editor responding. I've corrected the location of <> in Waze. Please allow at least 2-3 days for the map and routing to update, and then delete any favorites or saved searches you have in the Waze app for that address before trying again. Thanks!

I've made a change to improve navigation to that address. Please allow at least 2-3 days for the map and routing to update, and then delete any favorites or saved searches you have in the Waze app for that address before trying again.

I've made some changes to improve directions at that intersection. Please allow at least 2-3 days for the map and routing to update. Thanks for reporting!

Waze gets its search results from both its own internal database and from Google Maps. Depending on which result you select, you may get a location from either source. In this case, the Waze location ("<>") is correct, but the Google Maps pin ("<>") is in the wrong place. I've requested a correction in Google Maps, but have no control over when or if it will be made. Meanwhile, you can try deleting any favorites or saved searches you have in the Waze app for that address, performing a new search, and selecting the abbreviated form of the street address: "2 Burlington Woods Dr". Thanks!

OK, I can see the problem. Waze is getting the location (map coordinates) of that place from Google Maps. Waze then directs you to the road closest to Google's location pin, which is <>. To fix this, I've added a parking lot road in front of the building, so Waze will route using that. Please allow 2-3 days for the map and routing to update.

The partial route trace shows a "turn right" instruction. There have been sporadic reports of Waze's text-to-speech giving the wrong turn direction (opposite of turn shown on screen). Nothing we map editors can do, I'm sorry to say.

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. 4) As an absolute last resort (this will blow away ALL settings): reset the app by going to the navigation screen, typing ##@resetapp in the search field, and tapping search. 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

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.

Volunteer map editor responding. It appears that Waze was trying to route you via a detour. Waze may route detours to save a small amount of time. We map editors have no control over this. Sorry!

Volunteer map editor responding. Although not the obvious route, the route Waze suggested was a possible alternative. Waze tries to find the fastest route, even if the time difference is less than a minute. Thanks!

Thanks for the additional information. I can't find any map errors that would cause this. Waze is fairly averse to u-turns, and if the app believed that you were already pointed <direction> on <street> at the start, it could have routed you as described to get you back to <location> without a u-turn. Not anything that we map editors can fix, I'm sorry to say.

My guess is this: Waze tends to avoid u-turns, so if it thinks you are starting pointed away from the destination, it will route you into a loop instead of telling you to turn the other way. As it's not a problem with the map itself, nothing we map editors can fix. Sorry!

When you first request a route, Waze guesses at the direction you'll be travelling, and there's a good chance it will guess wrong. Waze also tends to avoid u-turns, and so will route you into a loop rather than telling you to turn around (some call this the "Waze 180"). As it's not a problem with the map itself, nothing we map editors can fix. Sorry!

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!

By default, the Waze routing engine tries to find the fastest route to your destination based on average speeds and current conditions, even if the route is longer and the time difference is less than a minute. If you always want the shortest route, you can change the Navigation settings in the app (Settings > Navigation > Routing styles) from "Fastest" to "Shortest", and see if this works better for you. As this isn't an issue with the map itself, I'm closing this report, but please continue to report any map issues you encounter.

Volunteer responding. I can't find anything on the map to explain the route Waze gave you. Waze will sometimes route odd detours to save a few seconds, and map editors can't do anything to fix this. Sorry!

Volunteer responding. There are no map issues that would explain the route Waze gave you, but historical speed data suggests occasional long waits to turn at that intersection. Waze will sometimes route detours to save a few seconds. Unfortunately, there is nothing that map editing would fix. Sorry!

Construction: For temporary road closures, it's best to use the "Closure" button in the Waze app. That will force the app to re-route you, avoiding the closed road. A "map issue" report may not be looked at by a map editor until some time has passed. (And map editors can't really do anything unless we have advance notice of the closure.)

We mark road closures in Waze if we can get advance notice from MassDOT. For temporary road closures, it's best to use the "Closure" button in the Waze app. That will force the app to re-route you, avoiding the closed road. By the time a "map issue" report is looked at by a map editor, it's generally too late to do anything.

Volunteer map editor responding. We try to mark road closures, if there is advance notice. This is not always possible. For temporary road closures, it's best to use the "Closure" button in the Waze app. That will force the app to re-route you, avoiding the closed road. A "map issue" report may not be looked at by a map editor until some time has passed. Thanks!

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!

Volunteer map editor responding. I've reviewed the issue and did not find any map errors. It looks like Waze provided you with a valid route. By default (unless you've changed settings in the app), Waze will pick the fastest route - even if the difference vs. the shortest route is minimal.

This sounds like a network issue (possibly bad cell signal) or an app issue. Problems with the Waze app can often be fixed by turning your phone off, and then on again. Beyond that, we map editors aren't able to help. As this isn't a problem with the map itself, I'm closing this report.

Private / Not a Through Way: Volunteer map editor responding. In Massachusetts, unless a road is on privately-owned land, or travel is restricted by town ordinance (unable to find any <> ordinance), "private way" and "not a through way" signs do not prevent the public from using a street. We can't restrict travel on <> without evidence of a legally-enforceable restriction. Thanks!

Volunteer map editor responding. The odd "Lake St detour" is a consequence of existing turn restrictions along Lake Street (Wilson, Little John, and Homestead only, when heading east on Lake). All turns suggested by Waze are legal, according to current Arlington traffic regulations. We can't change the Waze routing engine's behavior, so just ignore and continue driving straight on Lake St. Thanks!

For unknown reasons, Waze was using the place location from Google Maps (which was incorrect) instead of its own location for that address. I've submitted a correction to GMaps, but have no control over when it might be updated. Please delete any favorites or saved searches you have in the Waze app for that address before trying again.

Volunteer map editor responding. Apologies, this report did not show up until now. If still possible, would you please describe what went wrong, and tell us your destination as you entered it into Waze? Thanks!

I have seen occasional problems with the location of places that are advertised in Waze. Please try deleting any favorites or saved searches you have in the Waze app for that place, and try again with a fresh search. If you are still directed incorrectly, then it is a problem with the location as provided by the ad, and there is nothing that we map editors can do.

I have seen occasional problems with the location of places that are advertised in Waze (as Marshall's is). It is a problem with the location as provided by the ad, and all we map editors can do is report the problem to Waze staff (which I've done). Sorry!

Volunteer map editor responding. There's no <> on Waze's map at that location. Waze may get search results from another source (Google Maps), or there may be incorrect info coming from an ad feed. In either case, we map editors have no way to fix that problem. Sorry!

American Legion Hwy, Revere: Volunteer map editor responding. If you are reporting being sent around the rotary, instead of straight through: Waze tries to find the fastest route, even if it saves only a few seconds. Another editor, who drives through there, has confirmed that it's often faster to go around the circle than to go straight through. As such, Waze is doing what it's supposed to do. At other times of day, you might be directed straight through. This isn't a map error. Thanks!

Pleasant St, Framingham: Volunteer map editor responding. Although Waze's route may not agree with the road signs, Waze has determined that, on average, the fastest way to continue west to Pleasant St / Rt 30 is to take Rt 9 past Edgell to a right turn on Maynard Rd, then turn left on Pleasant from Maynard. This is not a map error. Thanks!

Quinobequin Rd, Newton: Volunteer map editor responding. Waze was providing a valid alternate route to enter I-95 S. By default, the Waze routing engine tries to find the fastest route to your destination based on average speeds and current conditions, even if the route is longer and the time difference is less than a minute. Thanks!

Volunteer map editor responding. There is a lot of GPS signal scatter in the vicinity of the Weston State Police barracks. This is confusing Waze as to your location. Right now, there's nothing that editing the map would fix. Thanks!

Volunteer map editor responding. Based on the limited route and GPS traces included with your report, Waze was routing you along the main portion of Comm Ave, but you were actually driving along the service road. Consumer GPS is not accurate enough for Waze to have determined that you were on a different, parallel road. This explains the incorrect turn instruction. It's not a problem with the map itself, so I'm closing this report. Thanks!

Sparhawk St, Boston: Volunteer map editor responding. By default, the Waze routing engine tries to find the fastest route to your destination based on average speeds and current conditions, even if the route is longer and the time difference is less than a minute. In this case, historical travel times give a slight edge to the detour around that triangle, at most times of day - must typically be long wait times at Sparhawk and Cambridge. As this isn't an issue with the map itself, I'm closing this report, but please continue to report any map issues you encounter. Thanks!

This is a recurring problem, for which we don't have a good fix. Waze's route was actually along the Exit 23 ramp from I-93 S (where a left to Oliver St is allowed), while your GPS trace indicates that you were actually driving on Purchase St (no left turn). Consumer GPS accuracy is often not good enough for Waze to determine that you were on a different, parallel road - leading to incorrect instructions. Sorry!

Volunteer map editor responding. By default, the Waze routing engine tries to find the fastest route to your destination based on average speeds and current conditions, even if the route is longer and the time difference is less than a minute. I cannot see your starting point or destination, so I have no way of determining if there is some problem that prevents Waze from suggesting a shorter route. If you are willing to share that information, I can check. Thanks!

Each place in Waze has only one navigation point, usually placed close to the entrance. When a large store has multiple entrances (and a big parking lot), you may not pass close enough to the navigation point for Waze to recognize that you've arrived. If that happens, just tap the Stop button to prevent Waze from trying to direct you back to the navigation point.

Difficult Route: We currently can't disable legal routes only because they are difficult (although Waze has promised a way to mark difficult intersections in the future). The wait time should contribute to Waze’s database, thus helping to discourage the routing server from suggesting the route. If you do not feel comfortable with the suggested route, you can always go another route and let Waze recalculate.

Speed Limits

Missing or invalid speed limit: Volunteer map editor responding. You reported a "missing or invalid speed limit" issue. What is the correct speed limit at the place where you made your report? Thanks!

Temporary Speed Limits: Speed limits in Waze are set to normal statutory limits (official black and while Speed Limit signs) - the driver is still responsible for obeying any temporary or variable (e.g. school zone) limits. Thanks!

Updated: I've updated the speed limit in Waze. Please allow at least 2-3 days for the map to update. Thanks!

SL missing or incorrect: Thank you for your report. The speed limit here was previously added to the map. Speed limits only display in the client when you are speeding, unless you change the speedometer settings to show them all the time. There can be delay of several seconds in the client app to show the correct speed limit after a speed limit change (after a ramp, limit change, or turning onto a new road). Please wait a few seconds on a new road to see if the correct limit shows up before reporting. This request will now be closed. Thanks!

Volunteer map editor responding. We cannot independently verify speed limits within parking lot roads (and they are not legally enforceable by the town or state) and so do not set them on Waze's map. Thanks!

Volunteer map editor responding. We do not generally set speed limits within parking lot roads (they are not legally enforceable by the town or state). This report (and duplicates) will be closed. Thanks!

Volunteer map editor responding. We are unable to independently verify the speed limit on that road, and so cannot set it on Waze's map. Thanks!