Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

L.geoJson.setZIndex doesn't seem to work

See original GitHub issue

Trying to control layer order with L.geoJson but it seems that map.addLayer(layer) always adds the layer on top, if the layer was created with L.geoJson.

I’ve tried layer.setZIndex(foo) and this doesn’t affect it, and also creating the layer with L.geoJson(data, {zIndex: foo}).

Issue Analytics

State:
Created 8 years ago
Comments:7 (2 by maintainers)

Top GitHub Comments

3reactions

SuberFucommented, Jun 8, 2016

@neothemachine I would go for a warning instead of exceptions. Since L.geojson inherits from L.LayerGroup, and L.layerGroup has setZIndex, it’s not unreasonable for user to expect that calling setZIndex on any object that inherits from L.layerGroup will not throw an error.

As for sort layers, I would love to have that. It would be nice to have a way to disable that functionality (like setZIndex to null) so that maps with many geojson layers do not pay the cost of sorting them if the user don’t care about their order.

0reactions

letmaikcommented, Jun 8, 2016

I just stumbled over the same issue in 1.0rc1 and found it very confusing. If setZIndex has no effect in a geojson layer then it should throw an exception as it is clearly a programmer error. Of course, it would be nice to actually get setZIndex working since it is possible to sort layers with the bringToBack and bringToFront methods. Can’t the geoJson (or other suitable) class not override setZIndex and implement such logic?