Bob McCormick
My feedback
115 results found
-
35 votes
An error occurred while saving the comment -
20 votes
-
91 votes
-
41 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.
-
92 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'd give this 100 votes if I can. Scripts like Junction Angle should just be part of the native WME. Waze functionality depends on our mapping angles. If this script didn't exist, how would we know?
Every Waze editor in every country benefits from this.HN NavPoints does a much better job than the WME provided House Numbers layer.
As OP noted LaneTools and Road Shield Assistant are also worthy of being included in native WME. Surely there are other scripts as well.
Without scrips the quality of what I have been able to map would be significantly impacted.
Editors and Wazers owe a lot of thanks to the script authors and maintainers. Alas, it is only normal over time for some of these contributors to move on, and that may leave scripts unfunctional, or even worse, exploited as recently happened.
Moving script functionality into WME will ensure the longevity of core editing tools, for the benefit of everyone.
-
240 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.
-
130 votes
An error occurred while saving the comment Additionally:
Using script functionality, there was great value in seeing the location of the Google Maps place in WME. This adds confidence that a GM place being linked in WME is correct. Further - when I typically found the ping for a GM place to be off, I would go into Google Maps and suggest a correction.
What we really need is a harmonious POI database between both products, Waze and Google Maps. Crazy that we have a lot of duplicate places in each map, and maintaining all that duplicate meta data as well.
-
547 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.
-
30 votes
-
9 votes
-
93 votes
Great timing! We're currently working on making your preferences accessible when logging in on a different device. Keep an eye out for updates on the WME.
-
130 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 Way too easy to have the new RRC PH snap to a RR segment. While this may be amusing for someone using Waze on a train, seems like this should be something simple to implement that would help ensure the proper placement of RRC PH.
-
20 votes
-
75 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.
-
13 votes
An error occurred while saving the comment https://www.mass.gov/info-details/cooling-centers-guidance
I support this. While the demographic for people affected by extreme heat / lack of heating may not be Waze users, in many areas volunteers and possibly even ride-share drivers could be providing transportation and would benefit by this.
Above is a link for Massachusetts guidance on cooling centers. There is also a central database of this information albeit I don't believe accessible to the public. It may be possible to establish a partner relationship to get this info into Waze.
-
83 votes
-
91 votes
-
16 votes
-
92 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.
-
107 votes
An error occurred while saving the comment This was also discussed in one of the roundtable discussions at the mega meetup Atlanta GA US 2024
An error occurred while saving the comment Now that we have closure history - there shouldn't be any reason to delete closures, which has been typically what we do when a closure needs to be terminated early.
What I have typically been doing is editing the closure and setting the time 2 minutes into the future. This effectively expires it. Change the delete button / functionality to expire would be a large benefit to maintaining closure history - which has become great for researching URs as well as adding future closures in areas of construction, etc.
Many places where shields don't work - because for any given street name / city combination a route number (shield) may not exist for the entire length of the road.
In many places any given segment may have multiple route numbers, hence multiple shields. This is currently not supported in Waze - practically every other navigation solution can do this.
In many locales surface streets (e.g., non-freeway road types) have both a street name and one or more route numbers / shields. Ideally Waze would better support this on the editor, back end and client.