-
-
Notifications
You must be signed in to change notification settings - Fork 318
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
fill-extrude
layer is drawn above the next-above symbol layer
#2259
Comments
It looks like this is fixed with |
#2894 contains a reproduction From @Zverik: Sometimes extruded buildings cover symbols and labels. Which never happens with MapLibre GL JS (on web) — and that made debugging this quite hard. I was testing with Flutter package, which uses MapLibre Native for Android. We have also encountered this bug on a native Android application using the SDK. After some experimenting, I narrowed styles to replicate this to those two:
When you remove any layers from the Versions:
A screenshot: |
We have been testing, and the bug does not seem to completely go away with the Vulcan build. For POI — yes, it is fixed. But instead, landuse labels (e.g. park and pond names) get obscured by extruded buldings. Even on non-adjusted styles: osm-liberty shows this between zooms 14 and 15. I'm doing more tests (using modified flutter library, so not sure it does use vulkan), but our Android developer reports this. |
From what I tested so far it seems that this issue is happening only on OpenGL, not on Vulkan or Metal. |
Describe the bug
The icons shown in a
symbol
layer are drawn behind the geometries in afill-extrude
layer if the latter is immediately below the former in the layer list.To Reproduce
Steps to reproduce the behavior:
symbol
layer directly above (i.e. after, in the layer list) afill-extrude
layer in a style jsonfill-extrude
layerExpected behavior
fill-extrude
should respect the layer order or the documentation should be updated to explain this.Screenshots
Platform information (please complete the following information):
(Only tested with v11-pre04)
The text was updated successfully, but these errors were encountered: