-
Notifications
You must be signed in to change notification settings - Fork 120
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
Disk space needed for .mapbox tiles? #76
Comments
Good question. I personally don't have a strong sense for that. If we assume all tiles from zoom level 0 -> 20, that's about 1.466 trillion tiles. Even though many of those will be mostly empty, I'd expect the total size to be in the ballpark that you mention. @bcamper: any thoughts? |
Both for computation and space, it would probably not be advisable to ever try render the whole world at a high zoom level. We are pursuing an approach of pre-seeding commonly requested areas, such as those in our Metro Extracts. We're moving to a new production architecture for these tiles soon. When we do, we could post some stats on space for the pre-seed areas, in case it's a useful guideline. cc @rmarianski |
Apparently, you can do the entire planet in vector tiles in about 50-100GB (z15ish, which is sufficient for z19 raster tiles). |
I have some numbers for our mapbox vector tiles at zoom level 10: number of tiles: 1,048,576 |
Do you have a sense for how much space is used by mapbox tiles for the planet?
I'm sure you're not pre-rendering for an area that large, but it would be interesting to know how this compares to raster tiles for the planet (which I believe, in theory, would be 50+ TB).
The text was updated successfully, but these errors were encountered: