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
I've seen this mentioned a few times, but have not seen an actual request or feature for it. So here it is!
Client-side generated tiles
Client-side generated grids
Anything where the vector tile generation can be offloaded to the client on a tile-by-tile basis
Alternative caching mechanism or logic that needs to be maintained outside of Mapbox
Providing an alternative to the delay/lag of loading large datasets that may be much larger than the current viewport, instead it could be generated & rendered tile-by-tile client-side
Similarly, a changing dataset could be more performant if more use-case specific tile-generating & caching strategies could be employed, and the vector tiles results just fed to mapbox
I could really use this too; ideally just provide the blob rather than having to pass it as a data/object url.
Ideally it would be possible to use something like the buckets directly and leave out the HTTP, HTML, GeoJSON, vector tile/PBF stuff; it serves no purpose when editing client-side in a data driven web app.
Motivation
I've seen this mentioned a few times, but have not seen an actual request or feature for it. So here it is!
Similar Issues:
Design Alternatives
Unknown
Design
Prove the ability to pass a function as a vector tile source for a layer. Instead of just a URL.
For instance a function
getTile(x,y,z)
could return the appropriate map tiles for mapbox to use for some layer.Mock-Up
Unknown
Concepts
Unknown
Implementation
Unknown
The text was updated successfully, but these errors were encountered: