Releases: rustprooflabs/pgosm-flex
1.1.0
PgOSM Flex 1.1.0
Commit hash: ede13a4
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
- Fix
--update appendwhen 2nd region has overlapping data in place relations #397 - Thanks @jhon100! --skip-nestedactually skips the whole nested place polygon process, instead of just part #398place_polygon_nestedtable now respects--schema#398- Remove test from
makebroken by improvement in osm2pgsql #396
Data changes
- N/A
Documentation
- Improve documentation covering
--updatefunctionality #398 - Improve documentation for testing
osm2pgsqlfeature branches #396
Full Changelog: 1.0.2...1.1.0
Contributors
Assets 2
1.0.2
PgOSM Flex 1.0.2
Commit hash: 0c009a5
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
- Move
ImportModeclass tohelpers.py#389 - Handle error when latest replication too old #392
- Error linking to (new) docs for dev users #393
Data changes
osm_datechanged totimestamptzreported from PBF metadata or more accurate information #390
Documentation
- Help devs out when replication needs to be overwritten #393
Full Changelog: 1.0.1...1.0.2
1.0.1
PgOSM Flex 1.0.1
Commit hash: 6727773
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
Data changes
- Creates
UNIQUEindexes defined in Lua styles instead ofPRIMARY KEYdefined in post-import SQL #380
This change only impacts full imports. Refreshes using
--replicationwill not reflect this change.
Documentation
- Document
--pgosm-datebehavior #387
Full Changelog: 1.0.0...1.0.1
Contributors
Assets 2
1.0.0
PgOSM Flex 1.0.0
PgOSM Flex 1.0.0 is here! 🎉
This release indicates the overall stability of the project. Merge requests in the past 6+ months have been related to documentation, code cleanup, and keeping up with project dependencies (osm2pgsql and Postgres version updates). No bugs have been reported in 9+ months.
Recent osm2pgsql improvements significantly reduced active connections used with PgOSM Flex's data model with quite a few tables (see #376). The high connection load was the last major concern with production workloads on busy Postgres instances, and is no longer a significant issue.
Commit hash: 09efa14
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
Data changes
- N/A
Documentation
- Add Windows Documentation #377, #378 - Thank you @RPLLxD!
- Various documentation improvements working with @RPLLxD #373, #375, #379
Full Changelog: 0.10.3...1.0.0
Contributors
Assets 2
0.10.3
PgOSM Flex 0.10.3
Commit hash: 1cd1f98
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
- Update to osm2pgsql 1.10.0 #370
- Prevent using older version of PgOSM Flex w/
--replication#343 - Remove unused environment variable #367
- Include convert extension #364
Data changes
- N/A
Documentation
Full Changelog: 0.10.2...0.10.3
0.10.2
PgOSM Flex 0.10.2
Commit hash: f45b3f6
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
- Uses Postgres 16 and PostGIS 3.4 in-Docker #359
- Updated LuaRocks version #359
- Bundled PgDD version updated to 0.5.1 #359
- Removed final use of
add_row()#361
Data changes
- N/A
Documentation
- Fix comment details #358
Upgrade notes for --replication
N/A
Full Changelog: 0.10.1...0.10.2
0.10.1
PgOSM Flex 0.10.1
Commit hash: c3e755e
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
- Allow using custom schema name with
--schema-name#353 / #355 - Track
--input-fileused inosm.pgosm_flexmeta table #357
Data changes
- N/A
Documentation
- Improve routing examples #351
- Remove variables plugin from docbook due to install problems #352, #356
Upgrade notes for --replication
N/A
Full Changelog: 0.10.0...0.10.1
0.10.0
PgOSM Flex 0.10.0
This release contains
Commit hash: e7d967e
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
- Allow custom indexing #286, #344
- Bug fix: Properly skip nested polygon function when
place=falsein layerset - #347 reported by @asitemade4u - Update install steps in Dockerfile to avoid
NLOHMANN_INCLUDE_DIRerror #345
Data changes
- N/A
Documentation
Upgrade notes for --replication
The indexes created by default have changed, but in a way that is unlikely to affect the majority of users. There was no attempt made to provide a migration script for these changing indexes. PgOSM Flex (via osm2pgsql) makes no efforts to sync changes to indexes, the easiest way to update to the new default indexes is a clean import.
This release is a good time to re-evaluate your databases index usage, and determine if you want to continue using the defaults (either the original defaults, or the new!) or if you want to migrate to your own custom index definitions.
Full Changelog: 0.9.0...0.10.0
Contributors
Assets 2
0.9.0
PgOSM Flex 0.9.0
This release contains _all views for the building, shop and POI layers have been replaced by tables. The tables are built via osm2pgsql Flex style which enables loading only the combined table, instead of requiring the base point/line/polygon tables to be built first.
Commit hash: 50c6ddd
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
Data changes
Impacts with this change
The following subsections include minimized notes from #337 to explain a variety of shifts coming along with this change (#320).
The views have turned into tables and are not always created. Only some packaged layersets include these to avoid additional overhead by default.
vbuilding_all-->building_combined_pointvshop_all-->shop_combined_pointvpoi_all-->poi_combined_point
Pros / Cons
Enables loading combined point table w/out requiring load of full polygon data. This can be considerable size savings when larger polygons are involved in the source data but being simplified before loading to Postgres.
vbuilding_all and vshop_all were views doing the combination and simplification on-the-fly. Wasn't good for general querying performance beyond small regional data. New table structure is only points, and fully indexed.
Requires duplicating a bit of logic in the Lua styles. The negative impact was minimized by moving common logic into new helper methods. E.g. building and building_combined_point leverage common logic in building_helper. There is almost certainly room for improvement in these areas.
Increased data size with layerset=everything with more data loaded to tables. Because of additional overhead, not loading the new _combined tables in default layerset. However, this opened the opportunity to consider loading more _combined_points layers into lightweight layersets. These are discussed in the Layerset Changes subsection.
Layerset Changes
Layerset: Basic
- ❌ Remove
building_polygon - ➕ Add
building_combined_point - ➕ Add
poi_combined_point
Layerset: Everything
- ➕ Add
building_combined_point - ➕ Add
poi_combined_point - ➕ Add
shop_combined_point
Layerset: Minimal
- ❌ Remove
poi - ➕ Add
poi_combined_point
Documentation
- Improved comments on SQL objects #340
Upgrade notes for --replication
Need to manually drop old views and materialized view using the db/data-migration/0.9.0.sql script. The updated import makes no attempt to remove these legacy objects. Leaving these legacy objects behind shouldn't cause any actual problems other than having multiple sources to retrieve identical data. Leaving the extra MV will increase disk usage unnecessarily.
Full Changelog: 0.8.2...0.9.0