Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

multi-level mosaicJSON #6

Closed
vincentsarago opened this issue Jul 17, 2019 · 2 comments
Closed

multi-level mosaicJSON #6

vincentsarago opened this issue Jul 17, 2019 · 2 comments

Comments

@vincentsarago
Copy link
Member

extension to create multiple zoom range mosaicJSON

{
  "bounds": [ 34.8046875, -20.3034175184893, 35.5078125, -19.31114335506464 ],
  "center": [ 35.15625, -19.80728043677697, 10 ],
  {minzoom: 0, maxzoom: 9, : ["links to mosaicJSON"]},
  {minzoom: 10, maxzoom: 14, : ["links to mosaicJSON"]},
  {minzoom: 15, maxzoom: 18, : ["links to mosaicJSON"]},
}
@sharkinsspatial
Copy link
Member

👍 I literally typed up this exact issue before looking and then saw this when I went to post it. 😄

@kylebarron
Copy link
Member

Do you enforce that no minzoom-maxzoom pairs overlap? It seems like it would be tricky to try to combine overlapping mosaic JSONs at an intermediate zoom.

Right now my workaround for multiple zoom ranges in a mosaicJSON is to have separate Mapbox GL layers that each point to an individual mosaicJSON. One downside of that is that Mapbox only overzooms within a layer. So in my project, if you start at zoom 7, initial Landsat tiles are loaded, and those tiles are overzoomed at layers 7-12 while higher resolution tiles are generated at the higher zooms. But once you cross zoom 12, everything is blank while the NAIP tiles are generated, since it's a separate Mapbox layer.

@developmentseed developmentseed locked and limited conversation to collaborators May 31, 2023
@vincentsarago vincentsarago converted this issue into discussion #22 May 31, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants