(→Fixes) |
No edit summary |
||
| Line 285: | Line 285: | ||
[[User:Mudge42/Proposed MA Changes|Proposed MA Changes]] | [[User:Mudge42/Proposed MA Changes|Proposed MA Changes]] | ||
[[User:Mudge42/Wazume|WIP]] | |||
Revision as of 22:52, 14 July 2022
Mudge42's Compendium of Mostly Useful Information
Technical Info
Priority of house number searches (see here for details)
In order of preference by the routing server/search engine:
- Waze Private Residential Place Points (Private Residential only, not "public")
- Waze House Number - reportedly whether confirmed or not (moved, even one pixel, by an editor in WME)
- Google database
- Google interpolation
- Waze interpolation
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
And my own boilerplate:
No response on UR
Just a reminder: We have not received any additional information on your report. (Email notifications come from an unmonitored address, and sending a reply directly will not work. You need to reply to the message in the app inbox or by clicking the web link in the email message.) If we don't hear back from you soon, we will infer everything is okay and close the report. Thanks!
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 the name or address of 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.
I haven't been able to reproduce that problem - please delete the previous search from your search history and try again. Instructions: Saved Places: https://goo.gl/hd74Uq History: https://goo.gl/1PMxL4 If the destination pin is still in the wrong location, please take a screenshot, showing the pin, and send it to masswazers@gmail.com, attn: mudge42. Thanks.
Volunteer map editor responding. I have just tested in the app and am routed to the correct location for that address. Please delete any Saved Places or search history you have for the address, and try a fresh search. Instructions: Saved Places: https://goo.gl/hd74Uq History: https://goo.gl/1PMxL4 If the problem persists, please take a screenshot of the search result, showing the destination pin, and send to masswazers@gmail.com attn: mudge42. Thanks!
Volunteer map editor responding. I have just tested in the Waze app and am routed to the correct location for <>. If delivery people are using the Waze app at all (it isn't licensed for commercial use), they may also be using another app that actually looks up the address in its own database, and then sends map coordinates (not the actual address) to Waze. There's nothing we can do to fix the driving directions, if those coordinates point to the wrong location. If you can reproduce the problem with a direct search in the Waze app, please take a screenshot of the search result, and send to masswazers@gmail.com attn: mudge42. Thanks!
Without getting into excess detail - Waze can get locations from multiple sources (its own database, Google Maps, other apps, etc.). When you search for an address or place, Waze takes the location coordinates and navigates to the nearest drivable road segment. The best you can do is look at the pin location of the search result / destination to see if it makes sense. (We try to make sure the locations in Waze's database are as correct as possible.) Once a location (right or wrong) is in your history, the app will continue to offer it when you next search - so we recommend clearing your history. How to do this: Saved Places: https://goo.gl/hd74Uq History: https://goo.gl/1PMxL4
Fixes
Exit Re-numbering Volunteer map editor responding. Exit x is being renumbered as Exit y. MassDOT began the renumbering of <road> exits recently (https://newmassexits.com/), and we have updated Waze to show both new and old exit numbers. Thanks!
That exit number was updated to xx on Waze's map nearly a year ago, and currently Waze is still showing both the new number and the old one (at the end of the instruction). Did you see only the old number on the display, or was it in the voice instructions? Thanks!
If this is a route you travel often, the app may be using cached data. You can try these instructions: https://www.techjunkie.com/waze-clear-cache-data/ to clear the cache.
Volunteer map editor responding. This address was previously fixed. Please delete any saved places or search history you have for the address, and try a fresh search. Instructions: Saved Places: https://goo.gl/hd74Uq History: https://goo.gl/1PMxL4
If you are still having a problem please submit a new report. Thanks!
If the problem persists, please take a screenshot of the search result, and send to masswazers@gmail.com attn: mudge42. Thanks!
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 Saved Places or search history 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 can take up to a week for Waze's map and routing to update. After that, delete any Saved Places or search history 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 Saved Places or search history 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 a week for the map and routing to update, and then delete any Saved Places or search history you have in the Waze app for that address before trying again. Thanks!
I've made a change to improve navigation to that address. It can take over a week for the map and routing to update, so please allow some time. Previous searches for that address may be cached in the app and don't update automatically. After allowing time for the update, delete any Saved Places or search history you have in the Waze app for that address before trying again.
I've made a change to improve navigation to that place. It can take 2-3 days for updates to reach your phone, so please allow some time. Previous searches for that place may be cached in the app and don't update automatically. After allowing time for the update, delete any Saved Places or search history you have in the Waze app for that place 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 Saved Places 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 Saved Places 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 (we editors suspect that there is a bias to continue in the direction you were travelling when last using Waze). 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"). The best thing to do is start driving in the direction you know to be correct, and force the app to recalculate the route. As it's not a problem with the map itself, there's 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. Sometimes, it will 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, if you are able. 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 of the schedule from MassDOT. This is not always possible. For temporary road closures, it's best to use the "Closure" button in the Waze app, if you are able. 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, if you are able. 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!
Volunteer map editor responding. Closures on the exit ramp are being set by Waze staff based on information provided the Massachusetts State Police. If the schedule changes, the map editors do not get notified, and are unable to help. 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 hardware in your phone 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.
Slowdown at Light: Volunteer map editor responding. This is a known issue, but is unrelated to the map itself. The Waze routing engine appears to have "forgotten" that slowdowns are normal at certain intersections. We map editors aren't able to help - we can only fix problems with the map itself, and these reports are not read by anyone at Waze. You can contact Waze support by going to Settings > Help Center in the app, or here: https://goo.gl/rgkE6m . As this isn't a problem with the map itself, I'm closing this report. Thanks!
App Problem: Volunteer map editor responding. This could be 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. In extreme cases, you might need to delete and re-install the app. Beyond that, we map editors aren't able to help - we can only fix problems with the map itself, and these reports are not read by anyone at Waze. You can contact Waze support by going to Settings > Help Center in the app, or here: https://goo.gl/rgkE6m . As this isn't a problem with the map itself, I'm closing this report. Thanks!
This problem is possibly due to bad cell signal or poor GPS signal reception in you phone. We map editors aren't able to help with that - we can only fix problems with the map itself, and these reports are not read by anyone at Waze. If you believe it's a problem with the app, you can contact Waze support by going to Settings > Help Center in the app, or here: https://goo.gl/rgkE6m . As this isn't a problem with the map itself, I'm closing this report. Thanks!
I've examined the map carefully in that area, and I'm unable to find any map errors that would explain the odd routing. I can only guess that there was a temporary issue with GPS signal reception on your phone or car device, and Waze did not know your correct location. As there's no apparent map error, I'm closing this report. Should something similar happen again, please submit a new report. Thanks!
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. Massachusetts law regarding public use of "ways" (whether classified as public or private) is a complex subject. In many cases, "private" means "unaccepted by the city/town", but not privately-owned. Unless a road is on privately-owned land, or travel is restricted by town 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!
Private (longer): Volunteer map editor responding. Massachusetts law regarding public use of "ways" (whether classified as public or private) is a complex subject. The section of <> that is completely within the <> parcel is clearly on privately-owned land, and I have set it to Private Road in Waze. Subdivisions add another level of complexity, and a restriction on public access to roads may or may not be enforceable. I'm not a lawyer, and can't comment on the rights conveyed (or not conveyed) by the deeds you cite. (This article has some comments from the Medford city solicitor that provide a simplified explanation: http://archive.boston.com/news/local/articles/2008/02/10/private_ways_public_access/?page=full . A much longer discussion of the issues is here: http://cainhibbard.com/wp-content/uploads/2011/03/Streets-Ways-May-2011.pdf) We can't restrict travel on roads without evidence of a legally-enforceable restriction, based on an official Town of <> source. If you have some information that would support a restriction (an opinion from the town solicitor has been useful in the past), please send it to masswazers@gmail.com. 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 Saved Places 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 Saved Places 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!
Volunteer map editor responding. Based on the limited route and GPS traces included with your report, Waze was routing you along the Exit 17 ramp, where a left turn on Oliver Street is possible. You appear to have been driving in the tunnel, on the Exit 16A ramp. 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!
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. 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.
Although Waze has introduced a way to mark difficult turns, we can't time-limit it, so marking the turn as difficult would cause routing problems for drivers at other times of day. The only solution right now is to ignore the turn and force the Waze app to recalculate. Sorry!
Rideshare / Delivery: Are you a rideshare driver? The rideshare apps send a set of map coordinates to Waze, not an address or name of a place. There's nothing we can do to fix the driving directions, if those coordinates point to the wrong location.
If you are a delivery driver and using another app together with Waze, be aware that other apps often send a set of map coordinates to Waze, not an address or name of a place. There's nothing we can do to fix the driving directions, if those coordinates point to the wrong location.
Volunteer map editor responding. I have just tested in the app and am routed to the correct location for <>. Please delete any Saved Places (including "Home") or search history you have for the address, and try a fresh search. Instructions: Saved Places: https://goo.gl/hd74Uq History: https://goo.gl/1PMxL4 If the problem persists, please take a screenshot of the search result, showing the destination pin, and send to masswazers@gmail.com attn: mudge42. Waze is not the only navigation app, and we can't fix anything related to Google Maps, Apple Maps, or commercial GPS devices. Also, some delivery services use their own app together with Waze. These other apps often send a set of map coordinates to Waze, not an address or name of a place. There's nothing we can do to fix the driving directions, if those coordinates point to the wrong location. Thanks!
Marriott: I've seen this problem before. Although the hotel location is correct in Waze's database, the Marriott app sends a set of map coordinates (which are apparently wrong), not an address or name of the hotel. There's nothing we can do to fix the driving directions, if those coordinates point to the wrong location. All I can suggest is that you report this to Marriott - it's not a problem Waze can fix. Thanks.
Restrictions: Volunteer map editor responding. The turn restriction goes into effect at X am, which is right at the time of your report. Waze calculates routes based on your estimated time of arriving at intersections that have restrictions. If you arrive slightly later than estimated, the app may not have a chance to calculate a new route. Thanks!
RRC: Waze recently imported railroad crossing locations, based on Federal Railroad Administration data. The local editors have been cleaning up the errors and outdated info. Those crossing markings should disappear from the app within a few days. Thanks.
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!
Thank you for your report. The speed limit here is currently correct. 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!