Vector Tiles are deployed on OpenStreetMap.org

(blog.openstreetmap.org)

42 points | by ikawe 19 hours ago

3 comments

  • maelito 5 hours ago
    In case you wonder how much time / resources it takes to generate vector tiles, I'm running benchmarks with Tilemaker here for https://cartes.app

    https://github.com/systemed/tilemaker/issues/839

  • davidkwast 16 hours ago
    Nice. I already use Vector Tiles on my backend. But it is nice to have other sources like this.
    • maxerickson 15 hours ago
      A feature goal for this deployment was that the tiles would update continuously, keeping up with changes that people are making to the OpenStreetMap database.

      Providing that feedback is one of the main purposes of the site.

  • eulgro 17 hours ago
    I had no idea what vector tiles were and the page doesn't explain it.

    https://en.wikipedia.org/wiki/Vector_tiles

    • kurtoid 17 hours ago
      Here's how I understand it: Previously, OpenStreetMap's tile endpoints would serve pre-rasterized PNG images, so zooming in on a tile could cause it to get blurry, until your client requests a new, zoomed in tile. Now, they can serve tiles in SVG format, which scale better
      • maelito 5 hours ago
        > so zooming in on a tile could cause it to get blurry, until your client requests a new, zoomed in tile. Now, they can serve tiles in SVG format, which scale better

        They still are blurry, because openstreetmap.org uses a JS library that does not seem to support vector tiles :/

      • rjh29 16 hours ago
        SVG tiles use less data too, and can be recoloured/restyled.
      • dbetteridge 15 hours ago
        Basically that + vector tiles can store information about the tile, styles, objects or buildings etc