DwarfLord
My feedback
97 results found
-
72 votesDwarfLord
supported this idea
·
-
98 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.
DwarfLord
supported this idea
·
-
16 votesDwarfLord
shared this idea
·
-
68 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.
DwarfLord
shared this idea
·
-
24 votesDwarfLord
supported this idea
·
-
79 votes
An error occurred while saving the comment -
73 votes
Great timing! We’re currently working on your suggestion about avoiding seasonal roads. Keep an eye out for updates on the WME.
DwarfLord
supported this idea
·
-
15 votesDwarfLord
shared this idea
·
-
18 votes
An error occurred while saving the comment DwarfLord
commented
If standardized alerts are offered, deer/wildlife zones should be included. Every year there are between 1 and 2 million deer collision insurance claims in the US alone. Drivers (and wildlife) would benefit from driver alerts when entering known wildlife hazard areas.
To avoid over-alerting, custom alerts should be programmable by season and time of day. For example, schools are only hazards during daylight on weekdays. Deer zones may be more dangerous in the autumn and at early, late, or nighttime hours. This would be critical, because hazard alerts that always sound, even when there is little or no hazard, teach drivers to ignore them or turn them off.
DwarfLord
supported this idea
·
-
38 votesDwarfLord
supported this idea
·
-
109 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.
DwarfLord
supported this idea
·
-
23 votesDwarfLord
supported this idea
·
-
9 votesDwarfLord
shared this idea
·
-
285 votesDwarfLord
supported this idea
·
-
74 votesDwarfLord
supported this idea
·
-
6 votesDwarfLord
supported this idea
·
-
15 votesDwarfLord
shared this idea
·
-
8 votes
An error occurred while saving the comment DwarfLord
commented
This would be extremely helpful during disasters (severe storms, earthquakes, wildfires, etc.) in remote areas. In particular, Wazers could note roads closed by the disaster. Even if the report isn't available immediately, if it could upload as soon as connectivity reappears it could help editors and Wazers alike understand road conditions.
DwarfLord
supported this idea
·
-
25 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.
DwarfLord
supported this idea
·
-
10 votesDwarfLord
supported this idea
·
Two thoughts:
1. The image is from WME, not the app. What matters is the app display, which at present doesn't show city boundaries at all. Rather it "floats" the city name above the other items on the display in a way it hopes is unobtrusive. Is there any complaint with how the app is doing this?
2. My understanding is that there are two "flavors" of city in Waze. One flavor consists of cities that were part of the original basemap import; they are "hard-coded" into the database and their display boundaries cannot be changed, regardless of anything editors do, without intervention by HQ (which can be requested, but can take some time). The other flavor consists of cities added by editors since the basemap import. The display boundaries for these are fluid, and can change as the primary city names on various segments change.
I believe your best shot at relief from Waze is to (a) demonstrate that the display on the app is messed up, not just the WME cities layer; AND (b) consequently request that HQ modify their hard-coded city boundary. In the US, this process generally implies RC involvement.