Anonymous
My feedback
39 results found
-
89 votes
-
30 votes
-
33 votes
-
12 votes
-
69 votes
An error occurred while saving the comment -
957 votes
-
137 votes
-
26 votes
-
9 votes
-
98 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.
-
85 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.
-
31 votes
-
60 votes
Great timing! We’re currently working on the option to invert the filter. Keep an eye out for updates on the WME.
-
105 votes
-
48 votes
-
42 votes
-
51 votes
Great timing! We’re currently working on the option to disable automatic refresh. Keep an eye out for updates on the WME.
-
50 votes
-
267 votes
Hey,
Please note we're changing the status of this suggestion to Not right now, 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!
-
325 votes
I would like to bring this topic back up.
In the following we have 3 examples where the layer from a city a is over one from another city (mostly or complete)
Example 1:
"Siebengewald" (Netherland) is covered by german city "Goch"
https://ibb.co/ZHmMtVc // Permalink: https://waze.com/de/editor?env=row&lat=51.65641&lon=6.13457&zoomLevel=14
Example 2:
City "Markkleeberg" is mostly covered by city of "Leipzig"
https://ibb.co/dBNpVvP // Permalink: https://waze.com/de/editor?env=row&lat=51.30688&lon=12.43872&zoomLevel=12
Example 3:
City "Oberheldrungen" is complety covered by city "An der Schmücke"
https://ibb.co/cTy2Yf8 // Permalink: https://waze.com/de/editor?env=row&lat=51.29013&lon=11.26961&marker=true&zoomLevel=13
In all cases the segments have the correct citys there, the form of the citys is not correctly builded up by the waze city layers.
So an improvement is necessary.