Hi Paul,
It’s beautiful 
If someone has already put together a docker-compose based setup that only requires specifying a small BBOX of interest, which automatically updates the data and generates tiles within it, I would be happy to focus on testing, multilingual support, and possibly even operating a small test server similar to this. So, if anyone has a setup like this already configured, could you please share it?
Is there a straightforward way to tell which changeset triggered the latest update of a particular tile, or its timestamp? Is this something one can query in Prometheus as well? That could be useful for when, say, someone drains one of the Great Lakes by accident, since the changeset bbox could technically be elsewhere.
There seems to be a rendering problem with roads and other linear features at the border of two tiles:
This change is now showing properly, could the cache be lasting up to two hours, or is there a rendering delay as well at the moment?
Thanks. This is a problem with insufficient buffer.
Another find:
A (curved) way with many nodes close to each other produces rendering artifacts:
https://pnorman.github.io/tilekiln-shortbread-demo/#19/49.5879206/11.0348144
https://pnorman.github.io/tilekiln-shortbread-demo/#19/49.5837502/11.0252494
That’s a great debugging feature, helps us find those grandiosely over-noded ways 
Thanks. If you could give a link to the url for the demo it would help to find the location and zoom you’re seeing the problems on. This problem is a bit trickier. Any map layer starts to exhibit problems if you zoom in enough, and if you have a very finely noded curved way it will always experience jumps like this if you zoom in enough because there is coordinate rounding. It looks like this is happening on z19, which is equivalent in scale to z20 on a typical raster map. I’ll look at what scale we’re targeting and increasing the extent.
There shouldn’t have been - everything was working fine when I checked it. Fastly is set to a 5 minute TTL and Varnish to 5m, so the most there should be is about 15 minutes.
There’s a few possibilities
Added the links to my post.
No. Changesets objects aren’t in the minutely data diffs and the last remains of them are stripped out early in the processing.
I will be adding last-modified headers for cache reasons, but this is not the same as when the changes were made.
No. Per-tile metrics are not possible to store in Prometheus.
My usual issue with vector tiles is geometry simplification being too aggressive, but since that doesn’t seem to be the case here, that’s something going right
There’s no true simplification going on here at all. There is a resolution reduction and de-duplicating step (ST_AsMVT) but that is adjusted by the resolution used and should hold up well till the scale of z19 raster tiles.
If you try zooming in quickly on a slow connection you will see very simplified lines but this is better than rasters where you see a blur.
I also find many tile sets oversimplify. I understand why because it’s an easy way to reduce tile size but it is frequently overdone. This is best seen at a zoom like 13.99 where the tiles are 1024 pixels wide.
I do expect to need to introduce some simplification but because I’m aiming at mappers it adjusts the priority of reproducing the original geometries compared to performance and tile size.
I call that quite ambitious; I guess the interests of mappers – though less in numbers – in the minutes presented vary much more than the interests of consumers. I might be wrong though.
I’m not aiming to meet the needs of every mapping-related use case that mappers have. No one service can do that. But minutely updates are really only of use to mappers so the biggest single feature is for them.
Indeed this is showing that more nodes for rounded ways is not always better.
There seems to be some issue with rendering railways, service roads et cetera (which I assume is because of those tags not being covered in the style yet). Here’s an instance of that in Sealdah, India.
I tried opening it by using QGIS
Neat. It appears that it actually includes every OSM object instead of limiting it to a select few.
Back then, I struggled because some OSM objects were missing from the vector tile server :
Update : I can’t find healthcare=midwife on poi layer. Is there any documentation regarding which OSM tag is included for each data layer?
Just made my own custom map style by consulting this documentation and directly modifying the “colorful.json”.
https://altilunium.github.io/vmap-osm/
I have to modify the sprite configuration ( "sprite": "http://localhost/vtile/sprites/sprites" | https://github.com/versatiles-org/versatiles-style/releases/download/v4.3.0/styles.tar.gz) as the original demo’s sprites seem to be missing.
Requests :
Just here to say this is exciting and cool!
