Replies: 1 comment 5 replies
-
Hello, thanks for reaching out! Flatmap and tilemaker are similar in that they are both single executables with no external dependencies that read shapefiles and osm.pbf files and emit an mbtiles file containing mapbox vector tiles. They both let you define custom schemas with attributes that drop out below certain zoom levels and that merge adjacent polygons/linestrings below zoom levels. They differ in that:
Tilemaker has been around for longer and lots of people have used it, no one has found the issues in flatmap yet 😉 |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello Michael @msbarry
recently I came across flatmap and this well documented github repo ... awesome efforts!!
Subsequently I added your project to my github watchlist where I have a lot of OSM related software etc.
So you mention https://github.com/systemed/tilemaker as a similar approach to produce OSM based MVT files.
Though I have not enough skills and hardware to run flatmap or tilemaker on my own, I ask myself:
What is the difference between tilemaker and flatmap?
So what features do they have in common, and where do they differ?
Of course I already read documentation and blogs for them both, but I am not able to put any answer in own words.
Maybe both projects can benefit from each other?
Or why are there some issues in one of them (mainly tilemaker) that seem to not occure in the other one?
(This text has been copied from a similar question in the tilemaker repo discussions section)
Beta Was this translation helpful? Give feedback.
All reactions