Bob McCormick
My feedback
84 results found
-
59 votes
-
16 votes
An error occurred while saving the comment -
5 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?! :)
-
250 votes
-
71 votes
-
52 votes
-
75 votes
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.
-
68 votes
-
81 votes
-
95 votes
-
2,925 votes
-
54 votes
-
10 votes
-
38 votes
-
86 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?
-
115 votes
-
146 votes
An error occurred while saving the comment I think the color scheme is just fine - what is more important is to understand when the GPS traces are from. How about a slider with a control point on each end, that you can use to select the oldest and newest to display? The GPS points displayed would then be indicative of the selected date range.
-
203 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.
-
150 votes
An error occurred while saving the comment This should be fairly easy to implement: for each type of individual feature we have in WME just have a flag that we can turn on and off to disable the display on the map.
I have a fairly high end system, high end graphics card and 2K (full screen) monitor. When encountering areas of the map that have large amounts of polygons (like for water objects) really can degrade the responsiveness of WME. Plus: being able to dynamically remove these objects reduces map clutter for the editor.
-
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
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.