tilemaker

Unfortunately, Tilemaker hasn't planned or cannot plan to support MLT in the medium-term. That will leave a significant part of the community out of this transition. See this interesting (and quite heated) discussion : https://github.com/systemed/tilemaker/issues/856

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

> Static or infrequently updated vector tiles can be generated from OSM data by a number of tools, but those most popular right now are https://github.com/systemed/tilemaker and https://github.com/onthegomap/planetiler this is the first I've seen of these alternative tools compared to using Tippecanoe(https://github.com/felt/tippecanoe). Are they considered to be higher performance?

No, because you've been able to self host (or have somebody host them for you) vector tiles for a long time with very little effort, and yes that will somewhat offload processing to clients, and, more importantly allow many styling decisions to be made by the client (but not all). Static or infrequently updated vector tiles can be generated from OSM data by a number of tools, but those most popular right now are https://github.com/systemed/tilemaker and https://github.com/onthegomap/planetiler The actual -new- thing is that the work Paul has done for the OSMF allows on the fly (aka in minutes) updates of the vector tiles. This is important for OSM contributors as a feedback mechanism and the main reason the OSMF operates the current raster tile service. What is currently a bit out in the open is which usage restrictions will apply to to

You can download an extract of your country from Geofabrik, run it through Tilemaker (https://github.com/systemed/tilemaker) to get a nice mbtiles file, and then use the built-in Ruby server to give you something you can load in your web-browser locally.

Two C++ projects I’m involved in that you might enjoy: https://github.com/systemed/tilemaker https://github.com/Project-OSRM/osrm-backend

Fully open: - https://github.com/systemed/tilemaker (for generating tiles) - https://github.com/systemed/mod_mbtiles (for serving them) tilemaker is similar to planetiler which OP is using (it's more configurable but also more memory-hungry).

Thanks! Tilemaker is a great tool and probably the closest alternative (no intermediate db). The most recent benchmarks I saw though were around a day for the planet, so roughly 10x longer than flatmap. If Edit: benchmark link https://github.com/systemed/tilemaker/issues/315#issue-99432...

https://github.com/systemed/tilemaker can generate vector tiles directly from *.osm.pbf files. Then serve the vector tiles with leaflet+mapbox-gl-leaflet, mapbox gl js, openlayers 3 or similar. https://github.com/mapbox/awesome-vector-tiles

The submitter of this issue [1] reported that 64GB of RAM was insufficient to load an 18GB PBF. Considering the planet PBF is 58GB, you're going to need a lot of RAM (and time). I tried the example tilemaker config (4 layers, zoom 11-14) on the 519MB Australia PBF. My 24 thread PC took a little under 20 minutes to finish generating 773,576 tiles, using about 10GB of RAM. 1. https://github.com/systemed/tilemaker/issues/238

The tile generation from PBF (actually OSMX) is not one of the parts that is open source; for that task I would look at https://github.com/systemed/tilemaker or https://github.com/openmaptiles/openmaptiles

Depending on your needs, tilemaker (https://github.com/systemed/tilemaker) may be the least painful way for generating tiles from OSM data with modifications to it. Or at least it seems to be the least painful way of doing that that I've found so far. The input data is manipulated by Lua code that you provide, and some reasonable default configuration for it exists. Your custom Lua code could pull additional information from other information sources should you wish to do so.

https://github.com/systemed/tilemaker generates mapbox vector tiles from OSM, which you can serve static. I saved an example config and usage to help get going https://github.com/ogre/tilemaker_config

Open-source vector renderers don't yet have the cartographic chops that raster renderers do. The most glaring difference is that label placement in common vector renderers is generally "try once, fail if no room", whereas in Mapnik (standard raster renderer), for example, you can supply a list of positions to try in order of preference. There's a lot to like about client-side rendering (which is why I wrote https://github.com/systemed/tilemaker/ to generate vector tiles) but it's not up to feature parity with raster rendering yet, and for some of us those features are important.

Looks interesting. I've recently released a C++ project that embeds Lua (https://github.com/systemed/tilemaker, a utility to make 'vector tiles' directly from OpenStreetMap data dumps) but installation of Luabind is pretty much the pain point for everyone who's tried it. (bjam? I mean, why?) A header-only library is really tempting.