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
Use the mapbox vector tile api to fetch all the needed tiles for a subset of basemaps and cache those in the client's browser.
How many tiles would this take and what would it cost?
Could we cache detailed zoom levels near shorelines, but less detail over sparse ocean space? How would mapbox-gl handle that if a tile isn't cached but one at a "parent" zoom level is?
Instead, we could create our own mbtiles files specifically for offline use. This would require dedicated "offline basemaps" complete with tile packages and styles to be uploaded. This would be less ideal as it would require a lot more work for each project.
We could have truly global basemaps with very sparse data in the worst case scenario so we could build just 1 "offline basemap" once.
Other questions...
How to handle satellite imagery. Is it much different?
The text was updated successfully, but these errors were encountered:
This thread has some useful discussion about how mapbox-gl-js overzooms "sparse" tilesets. It appears we may be able to get away with caching different areas at different zoom levels but there may be some issues.
I have a partial answer to how many tiles would take and what it would cost, per-basemap.
Tiling French Polynesia at zoom levels 16-10 would generate something around 35k tiles and cost around $9.00 to download from MapBox. Unfortunately, it is explicitly against their terms of service to download and redistribute tiles for offline use, so each time a survey facilitator downloads a map it would incur this cost. We may need to look at discounts through their community program.
Imagery is handled via the raster tile API, which actually has a more generous free tier.
There a few different options for doing this:
Other questions...
The text was updated successfully, but these errors were encountered: