Bob McCormick
My feedback
96 results found
-
48 votes
-
74 votes
-
18 votes
An error occurred while saving the comment -
12 votes
An error occurred while saving the comment I'll have to look around - I think this has been suggested before. With over 50% of the roads in Vermont unpaved, would love to see this. (Plus - would love to have all of them appropriately coded in WME.) Have you ever experienced mud season?! :)
-
297 votes
-
78 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
56 votes
Great timing! We’re currently working on being able to select long streches of road. Keep an eye out for updates on the WME.
-
78 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
An error occurred while saving the comment Another example:
Closure is put in for planned roadwords. Then, for one of the days, the construction is postponed for another day.
-
85 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
99 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
3,179 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
63 votes
-
10 votes
-
40 votes
-
89 votes
Hey!
This request is currently under consideration.
An error occurred while saving the comment Don't we have this now in WME? upper right hand side, icon with circular arrow?
-
278 votes
Hi all,
Thanks for voting for this suggestion!
It will be integrated into the new Waze Chat feature, and is currently on the roadmap for a later phase.
We’ll be sure to update when we have a clearer picture of the timeline.
-
23 votes
An error occurred while saving the comment I think this may be better described as a search issue and not really something to do with routing.
Also know that the rural address guidance is a somewhat regional issue in the US. For example, in New England we don't really have unincorporated areas that would follow guidance where the primary city may be blank and the alternate city is the USPS name.
We do have situations though where the USPS name may be different than the city, and USPS names do not necessarily align with municipal boundaries. In VT a lot of USPS names bleed over town lines.
I believe the real issue at hand is how Waze search is working. I would hope that whenever Waze finds a Waze address (that was placed by an editor and not some automated process) it would take priority over everything else -- and that should include searches against all pri and alt streets and cities.
As for the accuracy of Google Maps addresses, in VT we do have lots of scenarios where the GM address locations (passed back to Waze) are incorrect. In some cases it is apparent that the locations are the centroids of property parcels, which may be significantly different than the start of a driveway. This sometimes results in Waze routing to a location that's on the other side of a stream or even hill from where the destination should be, especially for larger parcels.
Google Maps also has a lot of erroneous street info in VT - incorrect names, incorrect placement, etc. We are nearing the end of a project to ensure Waze has every E911 street in VT correctly mapped in WME - when that's done Waze will more accurately reflect the state's roads than Google Maps. I'm sure that's the exception and probably GM for most places has a better representation of accuracy (especially in rural areas) than WME.
W1QA
-
8 votes
-
21 votes
-
11 votes
Would also cut down on various aspects of troubleshooting URs if we could find out from Wazers what kind of result they obtained. And it needs to be easy to distinguish what it is, too.