Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Landcover and amenity-points drawing order and tag prioritization not in sync #4631

Open
imagico opened this issue Jul 30, 2022 · 1 comment

Comments

@imagico
Copy link
Collaborator

imagico commented Jul 30, 2022

Since #3441 we set the drawing order in the landcover layer by feature in addition to way_area to have a defined order in case of features with identical geometries.

However for features with multiple landcover tags the prioritization is done with COALESCE() - and the order there is not alphabetical:

COALESCE(aeroway, golf, amenity, wetland, power, landuse, leisure, man_made, "natural", shop, tourism, highway, railway) AS feature

That means a feature with two landcover tags will potentially render differently from the case with the same two landcover tags being applied to two identical geometries, potentially leading to confusion.

This is not a practically overly significant scenario - still it would be good to correct that and to document this better with a suitable comment in the code.

@imagico
Copy link
Collaborator Author

imagico commented Sep 14, 2022

Same problem applies to amenity-points by the way - there the COALESCE() order is more complex and partly deliberately chosen. The amenity-points case is actually practically more relevant. See also #4676 and #3880.

@imagico imagico changed the title Landcover drawing order and tag prioritization not in sync Landcover and amenity-points drawing order and tag prioritization not in sync Sep 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant