Talk:Tile disk usage
This page could do with a bit more explanation.
Are we talking "generated tiles" here (i.e. .pngs) or meta tiles (or even something else entirely like MBTiles)?
I'm guessing that the "Pre-rendering all tiles would use around 54000GB of storage" statement assumes one kind of tile storage (e.g. generated .pngs) and a maximum zoom level of 18 (no longer accurate)? Also, with small files (e.g. .png rendered tiles) the storage required can be very dependant on the filesystem used, because the files are individually very small.
I'm guessing that "Tile view count" is "the number of tiles at this zoom level that were actually viewed and "Maximum (4^zoom)" is "the maximum number of potential tiles" at this zoom level. "% viewed on tile (March 2011)" is presumably based on the two previous figures, but what is "Newer value % viewed on tile" supposed to be? --SomeoneElse (talk) 11:33, 7 November 2014 (UTC)
It would be great to update this information from 2011. I would be curious to see how the smaller tiles (higher zoom levels) utilization has increased with the rise of mobile applications on multi-screen devices. I would be willing to help the originator of this content curate this update. -- 2015-11-17T13:36:19 Chardy709
Disk Use Per Level
If it's not too much work, is there any chance we could get a column with disk space consumed per zoom level? You give "(z0 to z15: 252GB, z16 to z18: 1020GB)" which is great, but per individual zoom level would be even more helpful. Just to get a vague guideline to help with guessing what levels make sense to prerender. Thanks for considering. Xenotropic (talk) 16:50, 21 March 2017 (UTC)
I don't know where to put this information, but this may be of use here:
Average tile size for an variant of osm-bright, along with hillshading and contour lines is 17.9kB in png-24bits, to be compared with the average 633B of OSM's png-256 in march 2011. --Yvecai (talk) 06:06, 27 August 2016 (UTC)