Bob McCormick
My feedback
101 results found
-
89 votes
Hey!
This request is currently under consideration.
An error occurred while saving the comment -
26 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
-
14 votes
-
13 votes
-
14 votes
-
18 votes
An error occurred while saving the comment This is a good idea. In some places in Vermont, E911 EMT services are provided by organisations separate from local fire departments. We currently don't have a good category to assign these EMT locations which are staffed typically 24x7.
-
26 votes
An error occurred while saving the comment We have quite a bit of this in Vermont US - one editor has a spreadsheet of segments and we also put map comments over segments that are closed in the winter time. This takes a significant amount of time each year to maintain - it would be ideal if something could be integral in WME to manage this, and beyond just the ability to put recurring closures on segments. (For example, sometimes opening dates may have to be extended if snow has not been removed - we need to see a list of these types of closures.)
-
26 votes
-
19 votes
-
20 votes
-
24 votes
An error occurred while saving the comment In the US we use the WME Cities Overlay script, which I find invaluable. As Vermont US state manager I obtained very accurate polygons from VT GIS and had the script author load those into a database that the script uses to draw the polygons.
Note: many states appear to have US Census Bureau TIGER polygons in that database. My experience is that much of that data: 1) contains inaccurate polygons, and 2) is missing a significant amount of cities and towns.
The ideal situation would be the functionality of the WME Cities Overlay script was native to WME, and the database(s) of polygons would be something coming from the editing community and submitted to and maintained by Waze.
-
23 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 Not all the road type classifications are for US / North America - there are ones that we are told not to use in the US.
Maybe a better approach would be to have each country have the ability to choose which classifications are used / available to editors in in WME.
-
25 votes
-
29 votes
An error occurred while saving the comment I do not believe that URs should be owned by any single editor; the editing community as a whole should take responsibility for the management and response to URs. Most communities have standards for responding to URs (how many days after initial UR, days after Waze response, and when to close).
Therefore, if an editor who first responds to a UR is subsequently unable to respond in the future (for whatever reason, including loss of EA, on vacation, quits editing, etc.) then other editors should respond to the URs.
-
80 votes
-
42 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 I disagree with the suggestion. I think the problem is combining these two attributes together: "off-road" and "not maintained" probably should be separate attributes.
I would agree that off-road should imply unpaved - should be easy enough to set the unpaved attribute automatically.
In some jurisdictions "not maintained" could also mean that in the winter time the road is not plowed - that is a form of maintenance. It does not have to mean that the road is unpaved - it could be paved.
-
53 votes
Don't we have this now in WME? upper right hand side, icon with circular arrow?