CuttySpark
My feedback
11 results found
-
75 votes
An error occurred while saving the comment -
1 vote
-
286 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,
Hezi -
9 votes
-
5 votes
-
31 votes
-
26 votes
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.
-
47 votes
Thanks for the suggestion!
We currently don't have plans to institute this change right now, but this may be included in future changes to SATmap options.
-
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,
Hezi -
90 votes
Hey!
This request is currently under consideration.
-
297 votes
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?