Vector tile generator about bolder HOT 4 CLOSED

I'm going to rule out tilemaker. Doing it for a regularly updating full-planet rich basemap is just too experimental.

from bolder.

tegola 0.4.0 appears to have the features required, but the experience will be the same as writing SQL for Mapnik: giant UNION ALLs, zoom conditionals, etc.

c.f. go-spatial/tegola#127

from bolder.

Having tried tegola, t-rex, and Mapzen's tileserver, I'm deciding on tileserver.

I'm not confident that either tegola or t-rex have all the features we will need, but know that tileserver does. My main concern was complexity, particularly with the new RAWR tiles. It turns out that we won't need to use any of that stuff.

The main remaining drawback is a unhealthy amount of intertwining with vector-datasource, Mapzen's vector definitions, which are an upstream component.

from bolder.

Re-opening this. Mapzen ending changes the landscape.

The options are

• tegola, with improved features including cache
• t-rex, as it was before
• tileserver, as it was before, but with iffy support going forwards

tm2source (node-mapnik) has new developments like https://github.com/rory/tileigi which remove the need for Mapnik, but they're a long way off.

Looking at development this year, tegola has plenty of commits on the v0.6.0 branch, t-rex has some development, and tileserver/tilequeue has nothing in the last month.

With tegola now having cache support, it's feature complete, and i'm leaning towards it much more.

from bolder.