Allow editors to override default order in which area polygons are rendered.
Often times we find that area places intersect on the map and do not render in a way that makes sense. As an example, under the current scheme, a large water body will be drawn behind a smaller park polygon where these two types of objects are drawn together. To combat this, editors are required to either draw complex coastlines twice, or break up water objects to create smaller polygons that will be drawn on top. We could improve the appearance of the map significantly if we had some control over which objects appear in front of others. This could also improve the appearance of edits from junior editors who do not have an understanding of the current prioritization scheme.
We would like to get some examples with permalinks in order to be able to check this suggestions.
Any example will be highly appreciated.
Sure: PL for the example I gave originally: https://www.waze.com/editor/?env=usa&lon=-119.47970&lat=49.87797&zoom=6&venues=157614579.1576276860.468041
The classic use case is where a park meets a water body. Usually the park is small compared to the water body and renders on top, when we'd almost always prefer the water body to remain visible.
Some others that come to mind: https://www.waze.com/editor/?env=usa&lon=-101.38732&lat=50.96689&zoom=2&venues=169476606.1695028201.3988981
Hope that helps.
Based on your demonstration, it appears that what you're really requesting is that the Live Map web site and the Waze app render consistently with each other? If so I'd agree. When there is a difference in rendering, such as for water vs. land Area Places, I *always* edit for best display on the app (and I would hope all editors would). But it sure would be better this wasn't a question in the first place.
I saved a demonstration of what I am describing here: https://imgur.com/a/Fu9B9eH