CuttySpark
My feedback
13 results found
-
69 votes
-
100 votes
Hey,
This topic may not answered as part of the suggestion up until now, but it has been discussed multiple times across the relevant teams.
We will keep on updating with any news
Best,
HeziAn error occurred while saving the comment -
7 votes
An error occurred while saving the comment Roads that were originally bidirectional and later have grown into dual carriage way usually end up as a mix of A->B and B->A segments. Fixing by manually by turning them around will affect history etc. The benefit of making homogenous A->B roads is that creating closures, speed limits etc literally gets more straight forward.
This swap function would be a quite elegant solution.
-
94 votes
Thank you for your valuable feedback. We're pleased to confirm that this suggestion is planned and we appreciate your input as we continue to enhance our product.
An error occurred while saving the comment Searching for destinations is a central function of Waze. Waze searches both internal places in the Waze map and Google Maps places and present the results. In the Waze map the map editors can (and should) link Google Maps places to the Waze places so that they are treated as one. But people add Google Maps places (and duplicates) at a very high pace, making this task difficult to do manually. So Waze now has a bot adding these links. Waze should present "native" Waze map places higher than similarly distant Google Maps places because they are usually of higher quality and because errors in the waze map can be fixed by the editors. When the search term is not exactly matching the place name which is in Waze or Google, I guess a closer match (spelling wise) may be higher on the result list than a nearby place with slightly different spelling etc. If search results are really off, say you search for "Tiffany's" and the highest result is in New York and not a local venue - this could qualify as a bug report more than a request?
-
1 vote
-
325 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.
-
9 votes
-
5 votes
-
31 votes
-
73 votes
Great timing! We’re currently working on your suggestion about avoiding seasonal roads. Keep an eye out for updates on the WME.
An error occurred while saving the comment Good idea! Many mountain roads should display a warning in the app when they are included in a route in winter even if they are not closed. The probability of a closure is much higher than ordinary roads. The segments could be open in summer, display a warning spring and autumn and be closed in winter. Start and end of each period set with dates.
-
125 votes
Great timing! We’re currently working on displaying the date of the satellite image. Keep an eye out for updates on the WME.
-
96 votes
Hey!
This request is currently under consideration.
-
338 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.
I think this is a very good concept! Maintenance of a single segment road is far easier than dual one-way segments with #-shaped intersections etc. How to handle where there is a crossover? Just a junction with appropriate U-turns allowed. Longer crossovers are normal, undivided segments, i.e. where crossing the street is possible when arriving at a destination.