fvwazing
My feedback
8 results found
-
56 votes
-
1,545 votes
AdminElla (Waze Team) (Admin, Waze) responded
An error occurred while saving the comment fvwazing
supported this idea
·
-
204 votes
An error occurred while saving the comment fvwazing
commented
...and in countries where there is a reasonable detailed basemap it is so rarely needed, take that bulldozer off the map alltogether! Question: why is the bulldozer removed from the map in Germany, but not in the Netherlands?
fvwazing
supported this idea
·
-
3,178 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 fvwazing
commented
I am very curious how this "pause" works when Waze runs in the background ;^)
My opinion: have Waze distinguish between "pause" and traffic by looking at the movements of the last 2 minutes.... if a car does not move at all, it has stopped for a pause; if it still moves 20-100m per minute, it is in traffic.
-
15 votesfvwazing
shared this idea
·
-
359 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 fvwazing
commented
We need a way to distinguish between various vehicle-types; this would do all the things asked for now as taxis, motorcycles, walking, bicycling.
Check this suggestion:
http://waze.uservoice.com/forums/59223-client-how-can-we-improve-waze-on-your-phone-/suggestions/825243-use-vehicle-type?ref=title -
2,824 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 fvwazing
commented
We need a way to distinguish between various vehicle-types; this would do all the things asked for now as taxis, motorcycles, walking, bicycling.
Check this suggestion:
http://waze.uservoice.com/forums/59225-cartouche-map-editor-and-waze-com-website/suggestions/825175-use-vehicle-type?ref=title -
418 votes
An error occurred while saving the comment fvwazing
commented
The ability of Waze to calculate alternative routes is a strong one. But it can be made better.
Currently, Waze offers a few parameters that influence the calculation of routes. "Fastest", "Shortest", "Avoid Highways", "Minimize Turns", and "Prefer cookie-munching". Offcourse the routes that are calculated always are a trade-off: often a route without highways is not entirely possible or impractical; some turns always must be made and nobody expects "prefer cookie munching" to route through ALL roads with cookies.
By calculating alternative routes you get 3 routes of different length and duration. You can compare the different length and duration, and select whatever is best for you. But if you are interested in cookie munching, you can not see how many cookies the different routes bring**. If you prefer to minimize turns you can not see which route has the fewest.
Suggestion: Show a few more values for these alternative routes, and show them sorted by one of these values.
Also, a preference for different road-types could go in. Avoid highways, freeways and dirt-roads. Avoid ferries (we do not have them yet in Waze, but...) Prefer non-toll-roads. Have all of these prioritized.
**) Currently, if you have "prefer cookie munching"on, you do not get alternatives at all. I consider that to be a bug and hope Waze will work more consistent in a future release.
fvwazing
supported this idea
·
Make those buffers BIG! From what I can see, storing a driven route (1 sample per second) takes less then 30-40KB per hour driving - so there could be stored 20 hours of driving in a MB. I have 1000's of MB free for Waze! To show a small Waze-Icon on the map it would be sufficient to send 1 (one) sample every few minutes.
Also, a complete map costs between 0.1KB (in the desert) and maybe 30KB (in a city) per square kilometer, so there could be 30 to 1000 square kilometers in a MB. Again, I have 1000's of MB available for that.
Trafficinformation is very dense - a set of 20 events may take only a few KB. If I am driving in a foreign country, with dataroaming on, I could get maybe 500 trafficevents in 1 MB for €2. I guess that generating a message on the client does cost a comparable volume. There is an option to block trafficinformation - but from a costperspective that does not make much sense.
All that Waze has to do is:
1. Make those recording- and mapbuffers BIGGER. At best make their limits set by the user.
2. For each set of data - recording, position, mapdata, trafficevents - make it possible to block transmission when not in WiFi. That way users can choose for mapdata and recordingdata could be swapped/updated at home, positioninfo (1 per 5 minutes) trafficinfo on the way. That is how I would use it, probably.