DwarfLord
My feedback
85 results found
-
95 votesDwarfLord supported this idea ·
-
1 vote
An error occurred while saving the comment -
12 votesDwarfLord supported this idea ·
-
33 votesDwarfLord shared this idea ·
-
8 votesDwarfLord supported this idea ·
-
49 votesDwarfLord supported this idea ·
-
70 votesDwarfLord supported this idea ·
-
40 votes
Hey,
Please note we're changing the status of this suggestion to Currently Not Planned, since we finalized our plans for 2024 and this idea won't be implemented this year.
We hope to include it in our plans for later down the line.
Thanks!
DwarfLord supported this idea · -
29 votesDwarfLord supported this idea ·
-
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.
DwarfLord supported this idea · -
36 votes
Hey!
Thank you for the suggestion.
In order to check this suggestion, we would like you to share some more examples with us.
We aim to get the understanding of how often this is an issue.Best,
Hezi.DwarfLord supported this idea · -
106 votes
Thank you for submitting this suggestion!
At the moment, when you hover over a place, it shows its complete address. Is this something that solves the original issue you mentioned?
If not, we would love to hear from you on how it can be improved.
Thank you!
DwarfLord supported this idea · -
92 votesDwarfLord supported this idea ·
-
24 votes
Hi all,
Thanks for this suggestion. We currently have other features which can account for this, like Roadshields and the towards option.
Editors should continue to avoid creating short segments where they aren't necessary, however this issue will be resolved by other future feature releases.
Many thanks,
Waze Communities Team
An error occurred while saving the comment DwarfLord commentedIt does appear that the team missed the suggestion's intent. The suggestion was extremely simple. At present, WME allows any editor, of any experience, for ANY purpose (including as a byproduct of other work or even by accident), to create very short segments with lengths as little as 1 m. Should WME really allow creation of such extremely short segments, when they are said to cause routing problems?
The suggestion had nothing to do with giving advanced editors better ways of adjusting instructions (e.g. with informational short segments).
DwarfLord shared this idea · -
49 votes
An error occurred while saving the comment DwarfLord commented> Maybe also critical map comments shouldn't be able to be hidden via the layers menu?
That is a GREAT idea! As long as it only applies to comment points, not comment areas, as editors need to be able to hide comment areas in order to work efficiently underneath them.
DwarfLord shared this idea · -
90 votes
Hey!
This request is currently under consideration.
DwarfLord supported this idea · -
85 votes
Hey,
We have looked at this suggestion, and in order to make some decisions about it, would like to kindly ask you to provide us with more data about it.
Please share some examples for when and where this restrictions apply? (use cases)
And any country you know relevant for it.
Thanks!
DwarfLord supported this idea · -
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,
HeziDwarfLord supported this idea · -
15 votesDwarfLord supported this idea ·
-
46 votesDwarfLord supported this idea ·
The significant technical obstacle to what you describe is that Waze is, at its core, about speed and "beating traffic". It works by measuring the speed of Wazing traffic at different times of day.
If bicyclists were to use Waze, they would severely pollute these speed data. This could foul the very reason Waze exists in the first place.
Consequently, in the US we do everything we can to *discourage* bicyclists from using Waze. It's important that the speed data that Waze acquires be representative of motor-vehicle traffic, not a mix of motor vehicle and bicycle speeds.
It seems unlikely Waze would go for this, as it could harm the foundational algorithms underlying the app (all IMHO, of course).