Show HN: Tilemaker – DIY vector tiles from OpenStreetMap data
tilemaker.org
tilemaker.org
And guess what? My next project is map related! I'm certainly going to take this for a test drive. Thanks for sharing.
tilemaker's default Lua script has had lots of great incremental improvements from contributors over the last few years, but half of the point, of course, is that you can write your own script which puts exactly what you want in the vector tiles.
The GitHub readme lists "You want the entire planet" as a reason not to use tilemaker. Why is that? Presumably it's excessive RAM/CPU usage during pbf conversion, or when serving tiles from the mbtiles sqlite file.
But how excessive are we talking? How big a machine would be needed to process a planet file? What tools work better with huge input files?
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.
For whole-planet scale, the traditional approach is to load the OSM data into a Postgres database, and then serve vector tiles from there.
- How would it compare to converting relevant layers to GeoJSON and then generating with tippecanoe? It seems to have very advanced options for tile size reduction.
In my case I use it to display roads that a person has walked/biked, so you can easily accumulate thousands of items to display.
> You can charge any amount of money you want for any service or data you provide. However, since the data (or service) that is derived from OSM data must be licensed as above, other people may then redistribute this without payment.
The work would be copyrighted "You And OSM Contributors" or something.
See also how to accurately attribute printed materials on the same link.
[0] https://wiki.osmfoundation.org/wiki/Licence/Licence_and_Lega...
"What exactly do I need to share?
ODbL draws a distinction between data, (geodata), and works produced from the data, (maps). You are probably distributing data if you are involved in searching, routing, geocoding. You are probably distributing maps if you print paper maps, have a website with map tiles, or are displaying a map as part of a larger work such as a television show, film, advertisement or book.
[...]
- If you correct or extend our data, you need to share your new data.
- If you make a map from our data, you may publish the map itself under any license you like, including commercial. You DO however, have to share the underlying data [...]"
I do not think there should be any problems.
If you make something I would be quite interested in what you created :)
In case of selling some produced artwork there will be no problem.
Cons: generating large areas require a lot of RAM; you can't just top it up with OSM diffs for the latest data; OMT has more corporate support; you don't get all the wizardry of PostGIS for geometry manipulation.
But sometimes making note with StreetComplete and editing with JOSM at home is more efficient.