#osm2pgsql — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #osm2pgsql, aggregated by home.social.
-
#osm2pgsql got funding to reduce ressource usage 🎉
needed for keeping pace with the every growing amount of #openstreetmap data
#osm #postgis #postgresqlhttps://osm2pgsql.org/news/2026/04/25/ngi0-grant-for-osm2pgsql.html
-
#osm2pgsql got funding to reduce ressource usage 🎉
needed for keeping pace with the every growing amount of #openstreetmap data
#osm #postgis #postgresqlhttps://osm2pgsql.org/news/2026/04/25/ngi0-grant-for-osm2pgsql.html
-
#osm2pgsql got funding to reduce ressource usage 🎉
needed for keeping pace with the every growing amount of #openstreetmap data
#osm #postgis #postgresqlhttps://osm2pgsql.org/news/2026/04/25/ngi0-grant-for-osm2pgsql.html
-
#osm2pgsql got funding to reduce ressource usage 🎉
needed for keeping pace with the every growing amount of #openstreetmap data
#osm #postgis #postgresqlhttps://osm2pgsql.org/news/2026/04/25/ngi0-grant-for-osm2pgsql.html
-
#osm2pgsql got funding to reduce ressource usage 🎉
needed for keeping pace with the every growing amount of #openstreetmap data
#osm #postgis #postgresqlhttps://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 retiredhttps://osm2pgsql.org/news/2026/04/20/osm-carto-switches-to-flex.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 retiredhttps://osm2pgsql.org/news/2026/04/20/osm-carto-switches-to-flex.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 retiredhttps://osm2pgsql.org/news/2026/04/20/osm-carto-switches-to-flex.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 retiredhttps://osm2pgsql.org/news/2026/04/20/osm-carto-switches-to-flex.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 retiredhttps://osm2pgsql.org/news/2026/04/20/osm-carto-switches-to-flex.html
-
#osm2pgsql's flex backend / themepark stuff is pretty cool TBH
-
#osm2pgsql's flex backend / themepark stuff is pretty cool TBH
-
#osm2pgsql's flex backend / themepark stuff is pretty cool TBH
-
#osm2pgsql's flex backend / themepark stuff is pretty cool TBH
-
#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 #geodatahttps://github.com/osm2pgsql-dev/osm2pgsql/releases/tag/2.2.0
-
#osm2pgsql version 2.2 released with a new "locator" feature and callbacks for deleted objects
#osm #openstreetmap #postgres #postgresql #postgis #gis #geodatahttps://github.com/osm2pgsql-dev/osm2pgsql/releases/tag/2.2.0
-
#osm2pgsql version 2.2 released with a new "locator" feature and callbacks for deleted objects
#osm #openstreetmap #postgres #postgresql #postgis #gis #geodatahttps://github.com/osm2pgsql-dev/osm2pgsql/releases/tag/2.2.0
-
#osm2pgsql version 2.2 released with a new "locator" feature and callbacks for deleted objects
#osm #openstreetmap #postgres #postgresql #postgis #gis #geodatahttps://github.com/osm2pgsql-dev/osm2pgsql/releases/tag/2.2.0
-
#osm2pgsql version 2.2 released with a new "locator" feature and callbacks for deleted objects
#osm #openstreetmap #postgres #postgresql #postgis #gis #geodatahttps://github.com/osm2pgsql-dev/osm2pgsql/releases/tag/2.2.0
-
In 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.
-
In 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.
-
In 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.
-
In 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.
-
In 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. -
#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. -
#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. -
#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. -
@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 %-/
-
@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 %-/
-
@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 %-/
-
@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 %-/
-
@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 %-/
-
After I upgraded the #postgresql backend to the latest and greatest version of #osm2pgsql and replaced #hstore by #json (jsonb) at the @geofabrik #Openstreetmap hack-weekend the https://opencampingmap.org Website is now up and running again.
-
After I upgraded the #postgresql backend to the latest and greatest version of #osm2pgsql and replaced #hstore by #json (jsonb) at the @geofabrik #Openstreetmap hack-weekend the https://opencampingmap.org Website is now up and running again.
-
After I upgraded the #postgresql backend to the latest and greatest version of #osm2pgsql and replaced #hstore by #json (jsonb) at the @geofabrik #Openstreetmap hack-weekend the https://opencampingmap.org Website is now up and running again.
-
After I upgraded the #postgresql backend to the latest and greatest version of #osm2pgsql and replaced #hstore by #json (jsonb) at the @geofabrik #Openstreetmap hack-weekend the https://opencampingmap.org Website is now up and running again.
-
Oh wow!, #osm2pgsql, the powerhorse of #OpenStreetMap data processing, has reached a milestone, and released version 2!
🌐 https://github.com/osm2pgsql-dev/osm2pgsql/releases/tag/2.0.0
-
Oh wow!, #osm2pgsql, the powerhorse of #OpenStreetMap data processing, has reached a milestone, and released version 2!
🌐 https://github.com/osm2pgsql-dev/osm2pgsql/releases/tag/2.0.0