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
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:
style2.json — between zooms 15 and 15.5, poi_r1 layer is covered by building-3d layer. There is no mention of zoom 15.5 in the style, so the reason buildings cover POI on on zoom and don't on others is unknown.
style2_old.json — same style without building and poi_r7 layers. While it should not have affected the outcome, instead extruded buildings cover POI on all zooms 15+.
When you remove any layers from the label group, suddenly extruded buildings stop covering POI symbols. That is the most baffling: why labels affect this, and why not "all labels".
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:
poi_r1
layer is covered bybuilding-3d
layer. There is no mention of zoom 15.5 in the style, so the reason buildings cover POI on on zoom and don't on others is unknown.building
andpoi_r7
layers. While it should not have affected the outcome, instead extruded buildings cover POI on all zooms 15+.When you remove any layers from the
label
group, suddenly extruded buildings stop covering POI symbols. That is the most baffling: why labels affect this, and why not "all labels".Versions:
A screenshot:
See also #2776.
The text was updated successfully, but these errors were encountered: