You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have 2 layers of different types, the sort keys won't be taken into consideration, meaning that fill layers could be rendered on top of a symbol even though they have sort keys that suggest that the symbol should be on top.
Steps to Trigger Behavior
Create a symbol layer with a single item, have a sort key of 100
Create a fill layer of a single polygon that contains the symbol location, make it have a sort key of 90
The fill layer will be above the symbol
Expected Behavior
Sort key will be calculated among all layer types and be global
Actual Behavior
Sort keys only work on same layer types
The text was updated successfully, but these errors were encountered:
-sort-key properties only reorder features within a layer — they are not designed to control rendering order across layers. We might need to clarify this in the docs, but that's how they work, and it's technically not possible to implement them differently.
-sort-key properties only reorder features within a layer — they are not designed to control rendering order across layers. We might need to clarify this in the docs, but that's how they work, and it's technically not possible to implement them differently.
So there's no way for me to declare a layer that is above other layers? If my app loads rasters dynamically then the raster that is loaded latest is above all my other layers (symbols, fills etc)
If you have 2 layers of different types, the sort keys won't be taken into consideration, meaning that fill layers could be rendered on top of a symbol even though they have sort keys that suggest that the symbol should be on top.
Steps to Trigger Behavior
Expected Behavior
Sort key will be calculated among all layer types and be global
Actual Behavior
Sort keys only work on same layer types
The text was updated successfully, but these errors were encountered: