The amount of data in OSM is climbing continually, and therefore the memory and disk requirements of osm2pgsql have risen as well. To address this issue we have applied for and won a grant from the NGI0 Commons Fund. In this project we want to reduce the memory and disk usage of osm2pgsql by implementing more efficient storage formats, specifically for “intermediate” data used while processing, often called the “middle”. We are tentatively calling this CODA, the Compact OpenStreetMap Data Archive. This will not only help with resource consumption on the community-run OSM servers, but also enable wider use of OSM data, even on planet-scale, in low-resource environments available to small NGOs or to students. Long-time osm2pgsql developer Jochen Topf will be funded to work on this project for the next year or so. Progress and all the details will be published on the project’s webpage. This project is funded through the NGI0 Commons Fund, a fund established by NLnet with financial support from the European Commission’s Next Generation Internet programme, under the aegis of DG Communications Networks, Content and Technology under grant agreement No 101135429. Additional funding is made available by the Swiss State Secretariat for Education, Research and Innovation (SERI).

OpenStreetMap data to PostgreSQL/PostGIS converter

Well, I executed the osm2pgsql command without the -G param which is intended to do a multi geometry search: https://osm2pgsql.org/doc/manual.html#geometry-processing But I already did: sudo -u postgres osm2pgsql -s -C16G --flat-nodes=/tmp/osm-cache.bin --number-processes=8 /osmpbf/planet.osm.pbf -d osm Can I do something else in order to create multi geometry relations without starting from scratch?

I have downloaded some OSM data from geofabrik and used this to create a PostgreSQL/PostGIS database using the osm2pgsql tool: osm2pgsql -G -d -U postgres myfile.osm Examining the database in pgAdmin shows everything as I would expect: there are tables for planet_osm_line etc. which all have data including geometry column. However, when I connect to the database from QGIS and attempt to add layers, none of these tables appear in the Data Source Manager|PostGIS dialog. Searching on this site (and comparing with a working PostGIS database that I created using QGIS and some random shape files) led me to suspect that I might need a primary key field in my tables. But adding one with: ALTER TABLE planet_osm_line ADD COLUMN id SERIAL PRIMARY KEY; has not helped. I have also tried running osm2pgsql without the -G flag, changing the name of the geometry column to 'geom' to match what QGIS produced in my working database and changing projection in QGIS to Spherical Mercator (3857) to match the data in the PostGIS database. And I've made sure to name the connection as per the solution here: Why can't I open postgis layers in QGIS? As I'm quite new to all this I suspect I've overlooked something in my usage of either osm2pgsql or QGIS. Could someone point out the error of my ways? In case it's useful, I'm using: * osm2pgsql version 0.96.0 * QGIS 3.4.3-Madeira * PostgreSQL 11.1 * postgis_full_version(): POSTGIS="2.5.1 r17027" [EXTENSION] PGSQL="110" GEOS="3.7.1-CAPI-1.11.1 27a5e771" PROJ="Rel. 5.2.0, September 15th, 2018" GDAL="GDAL 2.3.2, released 2018/09/21" LIBXML="2.9.8" LIBJSON="0.13.1" LIBPROTOBUF="1.3.1" RASTER

I have created a OSM tile server using the https://switch2osm.github.io/ tutorial for ubuntu 18.04 with great success but no matter what I cannot display the map labels in English only, I have tried many solutions from the OpenStreetMap help forum but none seem to work for me. I tried adding the line node,way name:en text linear to the default.style in osm2pgsql so the field name:en gets included in the postgres database, but the name:en field never appears on the tables even re-building osm2pgsql, dropping the current table and re loading the map data into db did not help(I am using https://download.geofabrik.de/asia/azerbaijan-latest.osm.pbf from the switch2osm guide). Can you guide me?

I've downloaded OSM data from geofabrik site and use below command to import OSM data to PostgreSQL. osm2pgsql -c -d OSM --password -U postgres -H localhost -S E:\default.style E:\iran-latest.osm command run properly without any problems. But after importing I can't find extra fields and attributes in relevant tables. Created tables are planet_osm_point planet_osm_line planet_osm_polygon planet_osm_roads And planet_osm_point table has such columns osm_id z_order way where are the other attributes and columns?! I need the other fields

I have set up a PostgreSQL/PostGIS DB on an EC2 that contains my .osm data. I populated it with osm2pgsql. Now, I can create tiles on my local machine using the QGIS "Generate XYZ Tiles (Directory)" tool. However, it is a rather tedious process. For example, I have four layers in the current map layer I'm creating and they have been styled accordingly (it is fairly simple). Is there a way to set up and tell a headless (EC2) process these settings? I had quite a bit of compiling from source to even set up PostGIS and osm2pgsql on the EC2 so I've grown quite weary.

It appears that I have corrupted / overwrote the index planet_osm_nodes for my Open Street Map installation. I would like to recreate it, but am not sure of the access method (b-tree, GIST...) which osm2pgsql initially created it as. I am using postgres. I have tried this: create index planet_osm_nodes on public.planet_osm_nodes USING gist (id) But get errors Can anyone let me know how best to recreate this index?

Ive been creating and serving web-based maps such as this one for some time. Thats based on raster tiles, and an osm2pgsql database is used to store the data that the tiles are created from, on demand as a request to view a tile is made.

Nearly six years ago we introduced the “flex” output in osm2pgsql version 1.3.0 and then improved it over the years adding more and more functionality. About a month ago OpenStreetMap-Carto, the iconic OSM map style switched to using the “flex” output in version 6.0.0. And now the OSM Foundation has finished their gradual rollout of the new version. So the most important user of osm2pgsql doesn’t need the old “pgsql” output any more. That switch has been eagerly awaited by the osm2pgsql maintainers, because it means we can start planning to retire the old “pgsql” output in earnest. This will allow us to remove a lot of code and simplify other parts of osm2pgsql making it easier to maintain and improve in the long term. We have already marked the “pgsql” output as deprecated with version 2.0.0 released in 2024, so this shouldn’t come as a surprise. The old “pgsql” output will not go away immediately, but it will also not be available forever. If you are still using it, start migrating your styles.

This release adds two powerful building blocks that can be used to implement all sorts of new features. The new "Locators" and the "deleted callbacks" features seem simple by themselves, but they c...

OpenStreetMap data to PostgreSQL/PostGIS converter

This is a bugfix and maintenance release. The main visible change is that osm2pgsql now works better together with connection poolers and similar database middleware: prepared statements now use pr...

For outstanding contributions to any of the core tools, systems, processes or resources. Not limited to systems under OSMF control. The Rails port, osm2pgsql, openstreetmap-carto, iD, JOSM, mapnik…

Ive been creating and serving web-based maps such as this one for some time. Thats based on raster tiles, and an osm2pgsql database is used to store the data that the tiles are created from, on demand as a request to view a tile is made.