The sysadmins don’t maintain that page. We keep the Servers/Tile Rendering page up to date since we use it.
Wiki pages with outdated information added by well-intended users is an ongoing problem, and how to solve it is a larger discussion. Projects like osm2pgsql have moved away from the OSM wiki for these reasons, among others.
It’s worth noting that Tilekiln exports all sorts of prometheus metrics about tile size that aren’t yet on a dashboard.
I redirected it in Tile disk usage: Difference between revisions - OpenStreetMap Wiki if sysadmins are not maintaining it anymore
I would redirect them to maintained pages covering the same topic or point at external resources
I would - even with the outdated data - keep that page (tile disk usage) as it mentions the date and by that show it’s outdated state.
It would have just been nice to see how that usage (e.g. size of meta tile cache at one of the rendering servers per zoom level) would have evolved over time.
The other data from that table (tiles viewed per zoom level) could probably be digested from the published tile logs but not the (meta)tiles on disk per zoom level.
well, it also generates support requests directed at sysadmins
That was not really my intention, but you are right.
So for the moment I self-assigned the job of getting some useful statistics for 2025 towards myself (using the already available public data like e.g. the tile_logs published at planet.osm.org) to update that wiki page in the next days.
Are you ok on not-redirecting it (as somewhat useful - while even outdated - data gets hidden at the moment by redirecting it)? When I first started diving into tile rendering servers several years ago that information was useful and still could be for newbies (and would be even more useful with more up-to-date data)…
Maybe then it would be better to include that information into switch2osm.org into the serving tiles section but for the time being and until that happens I still find that wiki page useful - even with outdated data (e.g. % of world viewed in higher zoom levels, etc.).
yes, I do not feel strongly about it, though maybe I would try to purge outdated info or more clearly indicate its historic status and that it is not supported anymore by sysadmins and they should not be bothered about updates
I’m a bit puzzled by the tile rendering stats. The “tile served by zoom” plot tops out as expected at zoom 19, but the other displays show zoom 20 - is this is a display issue?
Either way, it’s interesting that the current stats for “effort per zoom” appear objectively different to the 2015 figures (now gone?) in which the “effort per zoom” seem to tail off after zoom 17.
Currently, the effort is steadily increasing with zoom level, albeit ~linearly rather than quadratically.
Perhaps there is still some systematic tile scraping going on where zoom 19 tiles are being requested in a bot-like fashion rather than because somebody is seriously interested in zooming all the way in?
Obviously this would be a major argument against increasing the maximum zoom level rendered.
OpenHistoricalMap would also benefit from the fresher tiles. There seems to be a consensus among mappers there that the Standard tiles are useful as a locator tool for finding one’s way around blanker parts of the map, as well as to compare and contrast the two projects. That said, the cached tiles aren’t an urgent problem, as most mappers know how to use OSM too.
Support requests are part of the problem, but the other is that people might use the information. The information on the page is outdated, but even if we updated it the numbers would be specific to the OSMF setup and would require knowledge of our even/odd backend split, pre-rendering, and automated tile cleanup.
For anyone who is curious, this is the current data for one of the vector tile servers.
| zoom | bytes | count |
|---|---|---|
| 0 | 53281 | 1 |
| 1 | 116249 | 4 |
| 2 | 685298 | 16 |
| 3 | 1454278 | 64 |
| 4 | 2495873 | 256 |
| 5 | 58333218 | 1024 |
| 6 | 156780519 | 4096 |
| 7 | 535594846 | 16384 |
| 8 | 1069647741 | 65536 |
| 9 | 2152974634 | 262144 |
| 10 | 2564640105 | 176280 |
| 11 | 3203532584 | 470408 |
| 12 | 4515519811 | 1436660 |
| 13 | 5771042740 | 4605588 |
| 14 | 12692907474 | 16154156 |
It changes over time on the high zooms as more editing is done
Hello, I didn’t know how to add it when using it before © I apologize for the inconvenience caused by the inability to access attribution information such as contributors to OpenStreetMap! Afterwards, we have followed the Tile usage policy, but still cannot restore access. Is there any way to reply? Please
We need to know your site address to unblock it (this is done manually). Can you share it?
Can’t see anything, not even a demo, without first creating an account?
Not a good start!
Here is why you have been blocked: tracksolidpro.com · Issue #60 · openstreetmap/tile-attribution · GitHub
You were using OpenStreetMap tiles without attributing us. This is against our tile usage policy.
Let us know when you correctly show our attribution, and we will then look at removing the block.
