Bob McCormick
My feedback
101 results found
-
80 votes
-
14 votes
-
52 votes
-
104 votes
An error occurred while saving the comment 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.
-
201 votes
Great timing! We’re currently working on having the history of closures. Keep an eye out for updates on the WME.
An error occurred while saving the comment This is a great feature - now that we have the ability to have closure history I've found that really helpful in solving URs.
As part of this - we shouldn't be able to delete closures now - the delete functionality should be changed into an expire instead. What I do when a closure needs to be removed is edit it, changing the time to 2 minutes into the future, and save. That guarantees the history is maintained (versus a delete).
-
67 votes
-
354 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.
-
48 votes
Thank you for this suggestion.
This is currently not planned to be implemented, and therefore we. won’t move forward with it
We encourage you to keep on suggesting great ideas.
Best,
Hezi -
162 votes
Great timing! We’re currently working on allowing Junction Boxes and Paths to exist together. Keep an eye out for updates on the WME.
An error occurred while saving the comment What John said :)
I think the majority of where this combination exists is where a JB is used to restrict a U-Turn. The other alternative is to come up with a method of having a U-Turn restriction with something other than the JB.
-
39 votes
An error occurred while saving the comment As an EV driver the Waze charging station places are not of a level of quality that I could rely on - we need to be able to clean up the map and the feed to really make this of value to Wazers.
-
66 votes
An error occurred while saving the comment Luke warm to this idea.
In some places like NZ I can see maybe value where there are things like one-lane bridges. For visitors who are not accustomed to driving there the warnings for signs like this may be helpful:
https://www.nzta.govt.nz/assets/resources/roadcode/gfx/one-lane-bridge-giveway-1.gif
(means you need to give way to oncoming traffic)Or in places where the road narrows, like in Pete's first few examples. In the UK and elsewhere you typically see a sign like this:
https://www.highwaycodeuk.co.uk/uploads/3/2/9/2/3292309/editor/road-narrows-on-both-sides.jpg
(Often the centre line goes missing and you only have paint on the edges of the road.) Many narrow roads have hedges, or worse yet, stone walls, right at the edge of the road. While I'm not sure I'd want to flag every narrow road, I think ones where there are particular challenges would make sense.Not in favor of the two lane street where one side can be used for parking - reality of high density urban areas - and hopefully Waze isn't regularly routing people down streets like that.
-
28 votes
An error occurred while saving the comment Wow - never tried to add a home address to the map - that's crazy amount of steps, and is confusing. And now that you've shared the process, as an editor it make a lot more sense what we are seeing in WME. Yes - this could be improved in the Waze client for the sake of Wazers, and it also benefits the editing community as well.
For RPP for residences, would make a lot of sense to require at least a house number and street, as often I find these kinds of things actually distant from where they should actually be located. Saves editors time where otherwise the only thing we can do is look at a photo (if provided) and if there's street view, try to figure out which dwelling it is - otherwise do that from comparison with aerial imagery.
-
67 votes
-
40 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 agree that the current color scheme doesn't really convey info that is very useful to me.
Age of GPS traces would be paramount in my mind. I would accept that being done with color coding, though I would much rather have a filter that could choose an age.
And maybe could be part of a revamp in this area. Please! Get rid of all the outliers with GPS traces that are just scattered about. Happens mostly in areas with possibly marginal mobile Internet connectivity, but could also be related to GPS quality as well. In many areas this "noise" just clutters the map, especially when it is close to legitimate traces.
-
8 votes
AdminElla (Waze Team) (Admin, Waze) responded
-
29 votes
Great timing! We're currently working on the ability to close places permanently or temporarily. Keep an eye out for updates on the WME.
-
267 votes
Hey jangliss,
Thank you very much for this detailed suggestion.
Currently there is a lot of work around communication between the WME and the client (the app), to find how best should be handled.We will do our best to share some more details about it in the near future.
At this point this is currently not planned, and therefore won’t move to our back log.
If any thing in this direction will be changed, we will update accordingly.
Best,
HeziAn error occurred while saving the comment Anything we can do to improve Wazer - editor communications should be considered. My success rate in communicating with Wazers is under 20% and far too many URs are closed due to a lack of interaction with the reporter. The number of URs that I typically close based solely on the information provided to us in WME is almost nil.
-
90 votes
-
93 votes
-
9 votes
This was also discussed in one of the roundtable discussions at the mega meetup Atlanta GA US 2024