0.8.1

PgOSM Flex 0.8.1

---

Commit hash: 79de29f

The commit hash from this git repo shows up with the PgOSM Flex version number in SELECT pgosm_flex_version FROM osm.pgosm_flex; If you see this version with a different commit hash, it indicates you are using a latest Docker image with untagged features.

---

Backend changes

• Add protection against overwrite #313, adds new --force option via #327
• Fixes #318 - Change DB management from Sqitch to simple in-Python method #324
• Finish removing UUID #325

Changes to osm.pgosm_flex

N/A

Data changes

N/A

Upgrade notes for --replication

N/A

Documentation

• Routing Examples #317
• Add geofaker #319
• Layersets / Layers #321, #329
• Various update modes #331

---

Full Changelog: 0.8.0...0.8.1

0.8.0

PgOSM Flex 0.8.0

This release comes with multiple ⚠️ breaking changes. ⚠️ While breaking changes are included, the overall impression I have of PgOSM Flex is it is production ready, even though it's still a sub 1.0 release. Absent any major bugs/shifts in the near future, a 1.0 release is getting closer.

---

Commit hash: 45843be

The commit hash from this git repo shows up with the PgOSM Flex version number in SELECT pgosm_flex_version FROM osm.pgosm_flex; If you see this version with a different commit hash, it indicates you are using a latest Docker image with untagged features.

---

Backend changes

These are ⚠️ breaking changes ⚠️

• Removed --schema-name option, users can manually rename when needed #314
• Reworked structure osm.pgosm_flex meta table (#298, #304, #312)

Changes to osm.pgosm_flex

New columns

• layerset
• import_mode

Removed columns

• project_url
• import_uuid
• default_date
• osm2pgsql_replication
• osm2pgsql_mode

Data changes

N/A

Upgrade notes for --replication

No manual changes required.

Documentation

• Improve permissions section #310
• Example using osmium for w/ --input-file - #315

---

Full Changelog: 0.7.2...0.8.0

0.7.2

PgOSM Flex 0.7.2

Commit hash: 0b91c81

The commit hash from this git repo shows up with the PgOSM Flex version number in SELECT pgosm_flex_version FROM osm.pgosm_flex; If you see this version with a different commit hash, it indicates you are using a latest Docker image with untagged features.

Backend changes

• QGIS layer styles data updated for custom db name and/or schema name #308

Data changes

N/A

Upgrade notes for --replication

N/A

Documentation

• Add troubleshooting page #308
• Fix broken links #306
• Rename pages to lowercase #305

---

Full Changelog: 0.7.1...0.7.2

0.7.1

PgOSM Flex 0.7.1

Commit hash: 814f3bd

The commit hash from this git repo shows up with the PgOSM Flex version number in SELECT pgosm_flex_version FROM osm.pgosm_flex; If you see this version with a different commit hash, it indicates you are using a latest Docker image with untagged features.

Backend changes

N/A

Data changes

• Replication failures reported in osm.pgosm_flex.import_status #293 / #303
• Added UUID, planning to remove in #304
• Add osm2pgsql_replication #295

Upgrade notes for --replication

N/A

Documentation

Converted documentation from raw MD into mdbook format, deployed to https://pgosm-flex.com

#299, #300, #301

---

Full Changelog: 0.7.0...0.7.1

0.7.0

PgOSM Flex 0.7.0

⚠️ Breaking Changes ⚠️

PgOSM Flex 0.7.0 introduces two breaking changes.

• Removed the original --append mode; replaced with --replication in 0.6.3 - #285
• Removed --skip-dump - Using pg_dump is no longer default, use --pg-dump to enable - #289

Commit hash: 18acc46

The commit hash from this git repo shows up with the PgOSM Flex version number in SELECT pgosm_flex_version FROM osm.pgosm_flex; If you see this version with a different commit hash, it indicates you are using a latest Docker image with untagged features.

Backend changes

• Disables use of pg_dump by default, removes --skip-dump and replaces with --pg-dump to enable #289
• Enable --update mode to wrap osm2pgsql's ability to use --create vs --append #275 #285, #291, #292
• Original --append functionality moved to --replication #285 (really happened in 0.6.3)

Data changes

• Using osm2pgsql-replication ignores --osm-date argument #296

Upgrade notes for --replication

N/A

Other

• Documentation improvement, minor code cleanup - #288, #297

---

Full Changelog: 0.6.3...0.7.0

0.7.0.rc.2

PgOSM Flex 0.7.0.rc2

⚠️ Breaking Changes ⚠️

PgOSM Flex 0.7.0 introduces two breaking changes.

• Removed the original --append mode; replaced with --replication in 0.6.3 - #285
• Removed --skip-dump - Using pg_dump is no longer default, use --pg-dump to enable - #289

Commit hash: COMING SOON

The commit hash from this git repo shows up with the PgOSM Flex version number in SELECT pgosm_flex_version FROM osm.pgosm_flex; If you see this version with a different commit hash, it indicates you are using a latest Docker image with untagged features.

Backend changes

• Disables use of pg_dump by default, removes --skip-dump and replaces with --pg-dump to enable
• Enable --update mode to wrap osm2pgsql's ability to use --create vs --append #275 #285, #291, #292
• Original --append functionality moved to --replication #285 (really happened in 0.6.3)

Data changes

• Using osm2pgsql-replication ignores --osm-date argument #296

Upgrade notes for --replication

N/A

Other

• Documentation improvement, minor code cleanup - #288, #297

---

Full Changelog: 0.6.3...0.7.0.rc.2

0.7.0.rc.1

PgOSM Flex 0.7.0.rc1

⚠️ Breaking Changes ⚠️

PgOSM Flex 0.7.0 introduces two breaking changes.

• Removed the original --append mode; replaced with --replication in 0.6.3 - #285
• Removed --skip-dump - Using pg_dump is no longer default, use --pg-dump to enable - #289

Commit hash: COMING SOON

The commit hash from this git repo shows up with the PgOSM Flex version number in SELECT pgosm_flex_version FROM osm.pgosm_flex; If you see this version with a different commit hash, it indicates you are using a latest Docker image with untagged features.

Backend changes

• Disables use of pg_dump by default, removes --skip-dump and replaces with --pg-dump to enable
• Enable --update mode to wrap osm2pgsql's ability to use --create vs --append #275 #285, #291, #292
• Original --append functionality moved to --replication #285 (really happened in 0.6.3)

Data changes

N/A

Upgrade notes for --replication

N/A

Other

• #288 Documentation improvement, minor code cleanup

---

Full Changelog: 0.6.3...0.7.0.rc.1

0.6.3

PgOSM Flex 0.6.3

🎉 New option: --sp-gist 🎉

The --sp-gist option enables building SP-GIST indexes on the geometry columns. Requires osm2pgsql 1.8.0.

⚠️ Breaking Changing Coming in 0.7.0 ⚠️

This release sets the stage for breaking changes coming in 0.7.0: The original --append mode is now deprecated, with existing functionality moving to --replication. Replication more accurately reflects what is happening under the hood via osm2pgsql-replication. This also avoids confusion with the specific --append flag in osm2pgsql itself. Thank you @SailorMax for reporting #275 to explain this!

Commit hash: 97a1fe3

The commit hash from this git repo shows up with the PgOSM Flex version number in SELECT pgosm_flex_version FROM osm.pgosm_flex; If you see this version with a different commit hash, it indicates you are using a latest Docker image with untagged features.

Backend changes

• Moving --append to --replication - #277, #278, #282, #283
• Logging improvements #273
• More consistent interface with replication mode #272
• Documentation improvements #274, #282

Data changes

• Moved index creation to Lua (from post-processing SQL) #279
• Adds quite a few new indexes to make them more consistent #279
• Enable option of GIST or SP-GIST index via --sp-gist #280

Upgrade notes for --append

The differences introduced in 0.6.3 are all about indexes. By moving index creation from the post-processing to SQL scripts. many index names changed. Other new indexes were created, ultimately being more consistent about which columns are indexed.

The full SQL difference is in the following migration script. Note: The CREATE INDEX commands will fail if you do not have the associated table created. Manually review and update the script before running.

https://github.com/rustprooflabs/pgosm-flex/blob/main/db/data-migration/0.6.3.sql

---

Full Changelog: 0.6.2...0.6.3

0.6.2

PgOSM Flex 0.6.2

This release is one step closer to taking the Experimental tag off the append feature. It also goes back to stable PostGIS releases instead of development releases.

Commit hash: 7a12896

The commit hash from this git repo shows up with the PgOSM Flex version number in SELECT pgosm_flex_version FROM osm.pgosm_flex; If you see this version with a different commit hash, it indicates you are using a latest Docker image with untagged features.

Backend changes

These backend changes should have zero impact to data loaded to PostGIS.

• Fix bug preventing --append with --input-file #264 - Thank you @petrell9!
• Fix Docker base image to use PostGIS 3.3 instead of PostGIS Dev - #269
• Add step to Makefile to test --append mode with --input-file #271
• Speed up make by switching functional tests to use minimal layerset #271
• Quiet the logged output a bit. Plus minor Python cleanup #267

Data changes

• No changes in this release.

Upgrade notes for --append

No manual adjustments for upgrade.

Full Changelog: 0.6.1...0.6.2

0.6.1

PgOSM Flex 0.6.1

Commit hash: f79eb1c

The commit hash from this git repo shows up with the PgOSM Flex version number in SELECT pgosm_flex_version FROM osm.pgosm_flex;

Data changes

• Geometry columns set to NOT NULL for all tables #261

Documentation changes

• Add Code of Conduct #263
• Improve quality control queries #259

Backend changes

These backend changes should have zero impact to data loaded to PostGIS.

• Update Docker base image to Postgis w/ Postgres 15 #260
• Update Lua styles to use improvements made in osm2pgsql 1.7.0 and 1.7.1, code cleanup, remove unproductive comments #261
• Bump Python requirements for psycopg and osmium #258

Notes for --append users

PgOSM Flex 0.6.1 now creates all geometry columns as NOT NULL, while 0.6.0 and prior were NULLable. It is recommended (but not required) to run the ALTER TABLE commands below to update your table's definitions with the NOT NULL constraint.

ALTER TABLE osm.amenity_line ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.amenity_polygon ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.amenity_point ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.building_point ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.indoor_point ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.indoor_line ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.indoor_polygon ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.infrastructure_point ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.place_polygon_nested ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.infrastructure_line ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.infrastructure_polygon ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.landuse_point ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.leisure_point ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.leisure_polygon ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.natural_line ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.landuse_polygon ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.natural_polygon ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.place_point ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.natural_point ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.place_line ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.place_polygon ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.poi_line ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.poi_point ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.poi_polygon ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.building_polygon ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.public_transport_point ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.public_transport_line ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.public_transport_polygon ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.road_point ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.road_polygon ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.shop_point ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.shop_polygon ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.traffic_point ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.road_line ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.traffic_line ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.traffic_polygon ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.water_point ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.water_polygon ALTER COLUMN geom SET NOT NULL;
ALTER TABLE osm.water_line ALTER COLUMN geom SET NOT NULL;

Generating above statements

The above alter table queries were generated using the PgDD extension.

SELECT FORMAT('ALTER TABLE %s.%s ALTER COLUMN %s SET NOT NULL;',
                s_name, t_name, c_name)
    FROM dd.columns
    WHERE source_type = 'table'
        AND s_name = 'osm'
        AND c_name = 'geom'
;

Full Changelog: 0.6.0...0.6.1