3 ms·

Is this another one of those things like openmaptiles.com which is technically open but they don't really provide the tooling to generate new tiles and getting

Is this another one of those things like openmaptiles.com which is technically open but they don't really provide the tooling to generate new tiles and getting a copy of the tiles costs either thousands of dollars or you can only get versions that are 3+ years out of date? And also none of the tools are actually open source, or the ones that are go completely undocumented and don't actually work? /rant

alfman 6y ago
This is all wrong! 1.) you're mixing a routing service with a tile service (just view the map). A routing service needs always a tile service to display its result. 2.) the difference between openmaptiles and a traditional apache mod_tile is, that you don't need a ~600GB postgress to serve the entire planet. It's pre-rendered in vector tiles and the entire planet fits into a ~50GB mbtiles (sqlite3) file. 3.) Generating your own mbtiles file is documentated here: https://openmaptiles.org/docs/generate/generate-openmaptiles/ https://openmaptiles.org/docs/generate/generate-openmaptiles... and here is the belonging github repository https://github.com/openmaptiles/openmaptiles https://github.com/openmaptiles/openmaptiles But take care, rendering the entire planet took a lot of ressources. e.b. i7 sandy bridge with raid 0 ssd will take ~1 year for planet zoom level 0 to 14. And aws c5d.12xlarge will take 7 days only for zoom level 14.
- traverseda 6y ago
  > that you don't need a ~600GB postgress to serve the entire planet. That 600GB must surely include the full history? The xml dump of just the current openstreetmap data is only ~90GB, and generally XML dumps get smaller when you put them into a real database. That isn't a good comparison. I could have sworn the last time I checked this the docker image had dependencies that simply were not available, either in docker or on git but I guess I'm mis-remembering.
  - chippy 6y ago
    90GB is a bz2 compressed file not raw xml See the wiki: https://wiki.openstreetmap.org/wiki/Planet.osm/full https://wiki.openstreetmap.org/wiki/Planet.osm/full
    - traverseda 6y ago
      Well I suck. I'm honestly not sure how I got so wrong on this issue.
  - rmc 6y ago
    > That 600GB must surely include the full history? Nope! IME a regular `osm2pgsql` database for displaying maps which can be updated with changes needs about ~1TB of diskspace. There are many indexes needed.
chippy 6y ago
> Is this another one ... nope

alfman 6y ago

This is all wrong! 1.) you're mixing a routing service with a tile service (just view the map). A routing service needs always a tile service to display its result. 2.) the difference between openmaptiles and a traditional apache mod_tile is, that you don't need a ~600GB postgress to serve the entire planet. It's pre-rendered in vector tiles and the entire planet fits into a ~50GB mbtiles (sqlite3) file. 3.) Generating your own mbtiles file is documentated here: https://openmaptiles.org/docs/generate/generate-openmaptiles/ https://openmaptiles.org/docs/generate/generate-openmaptiles... and here is the belonging github repository https://github.com/openmaptiles/openmaptiles https://github.com/openmaptiles/openmaptiles But take care, rendering the entire planet took a lot of ressources. e.b. i7 sandy bridge with raid 0 ssd will take ~1 year for planet zoom level 0 to 14. And aws c5d.12xlarge will take 7 days only for zoom level 14.

traverseda 6y ago
> that you don't need a ~600GB postgress to serve the entire planet. That 600GB must surely include the full history? The xml dump of just the current openstreetmap data is only ~90GB, and generally XML dumps get smaller when you put them into a real database. That isn't a good comparison. I could have sworn the last time I checked this the docker image had dependencies that simply were not available, either in docker or on git but I guess I'm mis-remembering.
- chippy 6y ago
  90GB is a bz2 compressed file not raw xml See the wiki: https://wiki.openstreetmap.org/wiki/Planet.osm/full https://wiki.openstreetmap.org/wiki/Planet.osm/full
  - traverseda 6y ago
    Well I suck. I'm honestly not sure how I got so wrong on this issue.
- rmc 6y ago
  > That 600GB must surely include the full history? Nope! IME a regular `osm2pgsql` database for displaying maps which can be updated with changes needs about ~1TB of diskspace. There are many indexes needed.

chippy 6y ago

> Is this another one ... nope