Bob McCormick
My feedback
107 results found
-
20 votes
-
69 votes
An error occurred while saving the comment -
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.
-
84 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.
-
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
-
32 votes
-
98 votes
-
92 votes
-
175 votes
-
125 votes
-
190 votes
Thanks all! We're researching this further and will come back with follow up questions shortly.
-
304 votes
-
237 votes
Since bilingual support is a bigger issue affecting not just the WME, this is a company-wide decision that we will bring to the relevant teams.
-
278 votes
At the moment, this is not planned. That said, we introduced more user settings in URs that hopefully have improved the overall experience.
-
384 votes
-
432 votes
-
111 votes
This idea currently isn't planned, but we will update if it becomes feasible in the future.
Thanks to all who pushed for this idea!
An error occurred while saving the comment I concur
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.