Skip to content
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

Support bounds in TileJSON #1775

Closed
steinbachr opened this issue Dec 1, 2015 · 4 comments · Fixed by #4556
Closed

Support bounds in TileJSON #1775

steinbachr opened this issue Dec 1, 2015 · 4 comments · Fixed by #4556
Assignees

Comments

@steinbachr
Copy link

the combination of documentation here which states, "Tiled sources (vector and raster) must specify their details in terms of the TileJSON specification" and the TileJSON documentation here leads me think it's possible to add a raster source that only adds tiles within certain bounds. However, when I try to do so, the entire map is tiled, rather than just the portion of map contained within bounds. For instance, this code tiles the entire map without respect to bounds whereas I would expect it to tile only within the bounds given ([-10, -10, 10, 10]):

"raster-layer": {
      "type": "raster",
      "tiles": [
           "https://some-tile-source/{z}/{x}_{y}.jpg"
       ],
      "bounds": [-10, -10, 10, 10],
      "tileSize": 256,
      "minzoom": 0,
      "maxzoom": 5
}
@jfirebaugh
Copy link
Contributor

You're right, TileJSON bounds is something that should be supported, but isn't currently.

@steinbachr
Copy link
Author

ah okay, thanks for the clarification @jfirebaugh

@lucaswoj lucaswoj changed the title Bounds for individual raster source Support bounds in TileJSON Jul 29, 2016
@lucaswoj
Copy link
Contributor

ref #1404

@Scarysize
Copy link

We are using something like this to avoid requests to tiles which are located outside of a given bounding box:

https://gist.github.com/Scarysize/abcf22c514d64125111a5b130cf66fb3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants