Recent submissions

Comment · 4 years ago
Comment · 4 years ago
Comment · 4 years ago
Both arguments of yours are quite true, I also don't think that going beyond zoom level 20 or 21 is advisible within a raster tile stack (and I just checked that the UK map I mentioned earlier goes up to zoom 24 and not 28 as I stated, while the software stack (in this case mod_tile&renderd) is prepared for up to zoom 28).

I also don't intend to argue against a vector tile stack - both vector and raster have their use cases and pro's and con's. Vector tiles bring much more flexibility but less support in some use cases, raster normally loads/displays much faster (if served pre-rendered) and has universal support on the client side.

Comment · 4 years ago
But with vector tiles you (normally) start overzooming at level 15, resulting in either much less detail or really large file sizes for a zoom 14 vector tile that would have to carry all the data to be used in overzooming.

So raster tiles load much faster and OpenStreetMap retina tiles help against pixelation.

And you can - though not advisable for large areas - render raster tiles at much higher zoom levels, e.g. SomeOneElse renders his raster style up to level 28 for the UK.

Comment · 4 years ago
It actually is possible with raster tiles as well - see e.g. the local chapter work in France ( https://www.openstreetmap.fr ) or Germany ( https://www.openstreetmap.de ) or the osMap project with 10 different language versions ( https://wiki.openstreetmap.org/wiki/osMap ). All those are produced with raster tiles.

But you are right as this approach does not scale well in regard to using it for all languages out there. So a vector tile stack is a better approach for just switching languages.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton