drslump34
My feedback
12 results found
-
192 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.
An error occurred while saving the comment -
95 votes
An error occurred while saving the comment Re-up / +1. Adding AED/DAE (defibrillator) locations as a dedicated POI category (or searchable emergency place type) would be a true public-safety feature. In sudden cardiac arrest, minutes matter—helping users quickly find and navigate to the nearest AED can directly impact survival outcomes.
To address data quality concerns, this could be implemented with:
Official/open datasets where available (e.g., national registries), with a visible “last update” date.
Attributes such as public access hours (24/7 vs limited), indoor/outdoor, and access notes.
A review/verification workflow (trusted editors/partners) to avoid duplicates or outdated entries.
Even a first step—search + navigation to nearest AED within ~1 km—would already be extremely valuable. Please consider adding this category.
-
585 votes
Great timing! We’re currently working on allowing Junction Boxes and Paths to exist together. Keep an eye out for updates on the WME.
-
20 votes
-
141 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.
-
48 votes
-
2,496 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.
-
10 votes
-
10 votes
-
42 votes
-
63 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.
-
7,341 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 would really like Waze to reconsider this topic, even if it is currently marked as “not planned”.
This is not just a French-specific request or a nice-to-have feature. It addresses a real structural issue in countries where places are not always cleanly represented by a single “city” object.
In France, we have many hamlets, localities, former municipalities, attached municipalities and “communes de rattachement”. Today, without a proper sub-city mechanism, editors often have to choose between several bad options:
- creating or keeping artificial city names, which pollutes the city layer;
- forcing everything under the parent municipality, which hurts local relevance and address search;
- using alternate names or other workarounds, which are not designed to solve this problem cleanly;
- spending a lot of time maintaining address consistency manually, with no proper hierarchy.
This is especially painful when editing addresses. We need users to find the correct place, while also keeping the map clean, consistent and administratively accurate. The current model makes that unnecessarily difficult.
The need is also clearly not limited to France. Previous comments mention similar issues in the UK, Italy, the Philippines, and the US. Many countries have boroughs, districts, neighborhoods, hamlets, villages, former municipalities or local names that need to be searchable without being treated as independent full cities.
What makes this even more frustrating is that this does not feel like a purely new product idea. The concept of sub-cities has existed in Waze discussions for years, and the data structure appears to already have supported this kind of hierarchy, with city types and parent city relationships. So from a community perspective, this feels less like inventing a new feature from scratch, and more like finally making an existing or almost-existing capability usable in WME.
A proper sub-city implementation would bring several concrete benefits:
- cleaner city layers;
- better address and place search;
- fewer artificial or duplicated city objects;
- better handling of hamlets, districts and attached municipalities;
- less local workaround logic;
- more consistent editing rules across countries;
- better long-term map quality.
I understand that product priorities are difficult, but marking this as “not on the roadmap” feels disappointing because the issue has been known for a long time, affects several communities, and creates daily editing and search-quality problems.
This is not a cosmetic request. It is a data model and map quality issue. I really hope Waze can reopen the discussion and at least evaluate whether the existing city/sub-city structure could be exposed or operationalized in WME.