Skip to content
This repository has been archived by the owner on Apr 24, 2024. It is now read-only.

tilejson issues #196

Closed
tmcw opened this issue Feb 18, 2013 · 4 comments
Closed

tilejson issues #196

tmcw opened this issue Feb 18, 2013 · 4 comments

Comments

@tmcw
Copy link
Contributor

tmcw commented Feb 18, 2013

Right now the approach does well with being minimal - no special code required for it to work with native attribution and mapbox.legend. But this needs some work:

Most importantly, there's a real race condition with layer addition - layers will not stay in the order in which they are added
@jfirebaugh
Copy link
Contributor

Not sure how to fix the race condition. L.TileLayer constructed without a URL throws errors if added to a map, and Leaflet's support for manually ordering layers is limited to bringToFront/Back.

@tmcw
Copy link
Contributor Author

tmcw commented Feb 19, 2013

Leaflet's support for manually ordering layers is limited to bringToFront/Back.

We should improve this - the modestmaps layer api is much more complete

@jfirebaugh
Copy link
Contributor

Leaflet itself doesn't even correctly preserve order: Leaflet/Leaflet#1422.

jfirebaugh added a commit that referenced this issue Feb 19, 2013
@jfirebaugh
Preserve z-order for TileJSON tile layers (#196)
fefc58b 
However, the opacity example still does not work correctly due
to a Leaflet bug (Leaflet/Leaflet#1422).
@jfirebaugh
Copy link
Contributor

Fixed upstream, opacity example now has correct z-order.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tmcw @jfirebaugh