←back to thread

OpenStreetMap's New Vector Tiles

(tech.marksblogg.com)
479 points marklit | 1 comments | 19 Nov 24 12:03 UTC | HN request time: 0s | source
Show context
zawaideh ◴[19 Nov 24 15:27 UTC] No.42184496[source]▶
The other issue is that the arabic font is not rendering correctly in the vector version. It's rendering left to right (instead of right to left) with characters broken up instead of linked.
replies(3): >>42185056 #>>42185301 #>>42190246 #
sp8962 ◴[19 Nov 24 16:13 UTC] No.42185056[source]▶
The whole point of vector tiles is that the rendering is local and controlled by a style configuration (except for the tile schema) that can be changed. So the brokenness you are seeing is either in the style or the library that is rendering the contents locally.
replies(2): >>42185076 #>>42185878 #
SSLy ◴[19 Nov 24 16:15 UTC] No.42185076[source]▶
Indeed, but that is probably not going to help end users of apps.
replies(1): >>42185643 #
sp8962 ◴[19 Nov 24 17:04 UTC] No.42185643[source]▶
Well nobody claimed things are going to get simpler.

It is difficult to beat raster tiles in that respect. vector tiles split up responsibility for what you get visually over multiple moving pieces with different provenance and operators.

replies(2): >>42185815 #>>42186040 #
lxgr ◴[19 Nov 24 17:16 UTC] No.42185815[source]▶
> It is difficult to beat raster tiles in that respect.

Intuitively, why can't the local vector rasterizer do whatever the server-side tile rasterizer does, especially if both are fully custom?

replies(2): >>42185854 #>>42185938 #
1. maxerickson ◴[19 Nov 24 17:24 UTC] No.42185938{3}[source]▶
It can, it's just that they typically don't, because they use an off the shelf data schema for the tiles and a library to handle the rendering.

Having the data in tiles also complicates some things (where the renderer needs to consider merged tiles to get a similar result).