Christoph Hormann

My idea was actually not to have any zoom level based selection in MSS code but to select per zoom level in SQL using the `Z(!scale_denominator!)` (https://github.com/imagico/osm-carto-alternative-colors/blob/master/z.sql). This way the...

@sommerluk - i don't see a fundamental problem here - as @jeisenbe illustrated you could have a kind of `startzoom` attribute assigned to the features, which can either be an...

You would do something like ``` SELECT ... FROM (SELECT ... CASE WHEN highway = 'mini_roundabout' THEN 17 WHEN railway = 'level_crossing' THEN 14 WHEN railway = 'crossing' THEN 15...

You need to run z.sql in postgis on the osm database to install the function.

Also related to #1026 and #964. The `building-text` layer is also part of this problem because it starts at z14 but has lower priority than the POI symbols - many...

Symbols vanishing as you zoom in can be a deliberate and useful choice but never the vanishing and reappearance later - which is a common effect with the non-consistent prioritization....

By the way - i found an impressive example demonstrating this problem: https://www.openstreetmap.org/#map=19/48.00981/7.90126 * at z17 the shelter vanishes because it is blocked by the newly appearing picnic table. *...

#4734 showed additional problems when dynamic line labeling is involved. Case example shown was https://www.openstreetmap.org/way/510921128. Any change to address this problem will need to be checked against such cases.

I have now demonstrated and discussed an example of how this issue can be addressed on https://imagico.de/blog/en/competing-priorities-symbols-and-labels-in-rule-based-map-rendering/ This deals with a lot of additional things and not only the prioritization...

To clarify - because that seems to be occasionally misunderstood: This issue is of high importance to fix, and it should be done in a way that scales well in...