Stadia MapsweeklyOSM 830 is out: osm2pgsql 2.3.0 drops with major tile expiry changes, iD 2.41.0 ships with smarter relation editing, and OpenMapEditor relaunches as MapDraw (local-first, AGPL, contributes to OSM directly). Also, a shout-out to @ianthetechie for his post on routing privacy and billing as the unseen foundations of any mapping product.
Jakob Miksch#osm2pgsql version 2.3.0 released:
- improved expire functionality
- style testing util for #lua import scripts
- new id cache function
- more geometry processing functions
- various cleanup and bug fixes
#osm2pgsql got funding to reduce ressource usage 🎉
needed for keeping pace with the every growing amount of #openstreetmap data
#osm #postgis #postgresql
https://osm2pgsql.org/news/2026/04/25/ngi0-grant-for-osm2pgsql.html
good news for #osm2pgsql
the main user of the tool, namely the #OSM foundation, switched to the new "flex" configuration based on #lua
so the "old" way of configuration can be retired
https://osm2pgsql.org/news/2026/04/20/osm-carto-switches-to-flex.html
Amᵃᵖanda#osm2pgsql's flex backend / themepark stuff is pretty cool TBH
#osm2pgsql version 2.2 released with a new "locator" feature and callbacks for deleted objects
#osm #openstreetmap #postgres #postgresql #postgis #gis #geodata
https://github.com/osm2pgsql-dev/osm2pgsql/releases/tag/2.2.0
#osm2pgsql code got some cleanup
#openstreetmap #osm #postgis #postgresql #cpp #gis
https://osm2pgsql.org/news/2025/08/21/zero-warnings.html
#openstreetmap #osm #postgis #postgresql #cpp #gis
https://osm2pgsql.org/news/2025/08/21/zero-warnings.html
Sven GeggusIn case someone is interested. Importing an #Openstreetmap planet file into #postgresql using #osm2pgsql in non-slim mode took me just under 5 hours here and requires a machine with at least 128GB RAM.
#osm2pgsql FAQ:
If you don’t need your database to be updateable and you have enough RAM, use non-slim mode.
Unfortunately it does not tell what "enough" roughly means means.
If you don’t need your database to be updateable and you have enough RAM, use non-slim mode.
Unfortunately it does not tell what "enough" roughly means means.
@isotopp @masek Dealing with #Openstreetmap data I usually have a lot of utf-8 crap *inside* #postgresql string columns. LTR and RTL just came to my mind. #osm2pgsql will likely also support utf-8 in table names and indexes %-/