Creator here. I maintain <a href="https://onthegomap.com" rel="nofollow">https://onthegomap.com</a> as a side project. I originally used Google Maps API but after their price hike switched to OpenStreetMap data. I self-host GraphHopper for routing and tried to self-host OpenMapTiles but gave up and used Stadia Maps since it would have taken over 100 days [1] to generate a map of the world myself. Stadia Maps has been great and I highly recommend them, but the problem continued to nag me, so earlier this year I started prototyping a new way to generate vector tiles faster. The idea worked and ended up being able to generate a ~100GB planet.mbtiles file in as little as 59 minutes on a single c5ad.16xlarge instance with 64 cpus and 128GB RAM (although smaller machines appear to be more economical).<p>I’m open-sourcing Flatmap today. Let me know what you think, or if you have any suggestions!<p>[1] <a href="https://github.com/openmaptiles/openmaptiles/issues/654#issuecomment-724606293" rel="nofollow">https://github.com/openmaptiles/openmaptiles/issues/654#issu...</a>
Looks great! Potentially a game changer for projects that need a basemap for a smallish area (like one country), get a fair bit of traffic, but don't have budget for ongoing tile subscriptions to Mapbox or MapTiler.
This is really sweet, awesome work. I really love onthegomap too.<p>I maintain an openmaptiles pipeline, and we've got our planet runtimes down to about ~4 days on AWS.<p>Would be excited to see if we could use this tool, but we really heavily depend on PostGIS data manipulation to ensure that the data we want ends up in our output tiles. How difficult do you think migrating this SQL to your tool would be? It seems like you can support modifying the data fairly heavily, both before and after MBtile creation.
Nice :)<p>There's an ongoing effort to research vector tile solutions for openstreetmap.org. I wonder how your software stack compares to tilemaker, which has seen some optimization lately.<p><a href="https://github.com/openstreetmap/operations/issues/565" rel="nofollow">https://github.com/openstreetmap/operations/issues/565</a>
Nice tool OP, but I think we as a community should try to avoid creating tools that use already common names.<p>Googling "flatmap" gives a bunch of bad results. There is a value in having unique names.
This looks great!<p>I hacked around with OpenMapTiles to generate vector tiles in Arctic, Antarctic and WGS84 projections (the latter with 2×1 tiles at zoom 0) [1]. The time spent waiting for PostGIS to do reprojections etc made development very slow, and I've put off updating the tiles.<p>This tool is reprojects from WGS84 to Web Mercator while reading the tiles, so optimistically changing that would be much of what's needed.<p>[1] See the map at the bottom of gbif.org, there's a button to change the projection
A bit off-topic, but do people who host their own map tiles worry that other apps will use/abuse their tileserver? I would worry that I'd come in one Monday morning and discover that I've got a $20K bandwidth bill because someone else got popular.
We self-host OpenMapTiles, but are super lazy about replacing them with updated tiles (and we don’t love the watermark). I’m really glad that there are options for generating them ourselves! Starred, and will give it a try soon.
at that cost it almost feels like something internet archive or aws open data could provide on a regular basis. the cost of pre-made vector tiles is huge, and making them yourself has been a huge ordeal before this...
> at least 1.5x as much free RAM as the input .osm.pbf file size<p>Ouch! Is there any plan to reduce the amount of ram or it's impossible?<p>I'm currently building a tile server with Europe's map, the PBF is 28GB, I have 32GB ram.