DwarfLord
My feedback
-
28 votesAdded to backlog · 0 comments · Map Editor Suggestions » General · Flag idea as inappropriate… · Admin →DwarfLord
supported this idea
·
-
41 votesDwarfLord
supported this idea
·
-
12 votesDwarfLord
shared this idea
·
-
60 votes
Thank you to all who submitted and voted for this suggestion, however it is currently not planned due to PII issues associated with tracking URs in this manner. Please make sure to include the UR ID when reporting abusers on the map so that Staff can properly track the case. Often times we are unable to investigate due to no longer having the UR ID once the UR is closed and deleted.
DwarfLord
shared this idea
·
-
21 votesLooking into the suggestion · 0 comments · Map Editor Suggestions » General · Flag idea as inappropriate… · Admin →DwarfLord
supported this idea
·
-
15 votesLooking into the suggestion · 1 comment · Map Editor Suggestions » General · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment -
12 votesDwarfLord
supported this idea
·
-
18 votesDwarfLord
supported this idea
·
-
12 votesLooking into the suggestion · 1 comment · Map Editor Suggestions · Flag idea as inappropriate… · Admin →DwarfLord
shared this idea
·
-
16 votesLooking into the suggestion · 1 comment · Map Editor Suggestions » General · Flag idea as inappropriate… · Admin →
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
·
-
3 votesDwarfLord
shared this idea
·
-
14 votesLooking into the suggestion · 0 comments · Map Editor Suggestions · Flag idea as inappropriate… · Admin →DwarfLord
supported this idea
·
-
106 votesAdded to backlog · 6 comments · Map Editor Suggestions » General · Flag idea as inappropriate… · Admin →DwarfLord
supported this idea
·
-
213 votes
Hi all,
Thanks for voting on this suggestion!
We’re updating to let you know we’re working on this, but we don’t yet have a timeline. We will update once more info is available.
Best,
-StaffDwarfLord
supported this idea
·
-
91 votes
Hi all,
Thanks for voting for this suggestion!
It will be integrated into the new Waze Chat feature, and is currently on the roadmap for a later phase.
We’ll be sure to update when we have a clearer picture of the timeline.
DwarfLord
shared this idea
·
-
14 votesLooking into the suggestion · 0 comments · Map Editor Suggestions » General · Flag idea as inappropriate… · Admin →DwarfLord
supported this idea
·
-
82 votes
Hey!
Thank you for this great suggestion.
We currently have an internal process in place to address this issue, and therefore won’t be developed as a feature in the WME.
If you encounter any issue with advertised location. Please let your coordinators know about it, and they will inform the SCM, so we will be able to check this.
Best,
HeziDwarfLord
supported this idea
·
-
17 votesLooking into the suggestion · 0 comments · Map Editor Suggestions · Flag idea as inappropriate… · Admin →DwarfLord
supported this idea
·
-
39 votesLooking into the suggestion · 1 comment · Map Editor Suggestions » General · Flag idea as inappropriate… · Admin →DwarfLord
supported this idea
·
-
6 votesDwarfLord
shared 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.