3 ms·
You are describing a problem inherent to using PostgreSQL, not OpenStreetMap itself. My presentation is specifically about my solution to this, which can easily
by bdon 6y ago
You are describing a problem inherent to using PostgreSQL, not OpenStreetMap itself. My presentation is specifically about my solution to this, which can easily import planet.pbf in 7-8 hours on a laptop with SSD, and can cut extracts for cities and countries like you describe based on minutely data:
https://2020.stateofthemap.org/sessions/JDNTHK/ https://2020.stateofthemap.org/sessions/JDNTHK/
https://github.com/protomaps/OSMExpress https://github.com/protomaps/OSMExpress
- berkes 6y agoIndeed, a lot is due to PostGIS. I'm using mimirsbrunn[1] a lot, lately, with Elasticsearch as storage; especially because it is fast. It does lack a processor that listens to changesets and imports those, though; so I still need to run a nightly rebuild of the entire database. Thanks for pointing me to your StateOfTheMap session. I'll "attend" it for sure. [1] https://github.com/CanalTP/mimirsbrunn https://github.com/CanalTP/mimirsbrunn