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 have just been working with some Esri vector tiles, which support a variable zoom depth. That is, tiles are generated to higher zoom levels in areas that contain more detail, and aren't generated in comparatively empty areas.
It has obvious benefits when statically generating large tilesets that cover both urban and rural areas. The downside is that you also need to communicate to the client where tiles are available. Esri does this through a hefty tilemap JSON file, but there probably more efficient ways.
Is it worth putting something like this in TileJSON? Or maybe it doesn't make sense if Mapbox isn't going to support it.
The text was updated successfully, but these errors were encountered:
I think the JSON tilemap approach is cumbersome. When I was working with terrain data, the available resolution of that would vary dramatically, especially offshore.
I have just been working with some Esri vector tiles, which support a variable zoom depth. That is, tiles are generated to higher zoom levels in areas that contain more detail, and aren't generated in comparatively empty areas.
https://developers.arcgis.com/rest/services-reference/vector-tilemap.htm
It has obvious benefits when statically generating large tilesets that cover both urban and rural areas. The downside is that you also need to communicate to the client where tiles are available. Esri does this through a hefty
tilemap
JSON file, but there probably more efficient ways.Is it worth putting something like this in TileJSON? Or maybe it doesn't make sense if Mapbox isn't going to support it.
The text was updated successfully, but these errors were encountered: