3dcitydb Versions Save

What's Changed

• Added function get_child_objectclass_ids by @yaozhihang in https://github.com/3dcitydb/3dcitydb/pull/166
• Reworked "delete_property" function by @clausnagel in https://github.com/3dcitydb/3dcitydb/pull/217
• Docker image for 3DCityDB v5 by @BWibo in https://github.com/3dcitydb/3dcitydb/pull/216
• Docker v5 beta image releases by @BWibo in https://github.com/3dcitydb/3dcitydb/pull/218
• Add schema mapping information by @clausnagel in https://github.com/3dcitydb/3dcitydb/pull/222
• Use consistent naming scheme for file names by @clausnagel in https://github.com/3dcitydb/3dcitydb/pull/224

Full Changelog: https://github.com/3dcitydb/3dcitydb/compare/5.0.0-alpha.3...5.0.0-alpha.4

This is a minor release. Use the SQL scripts in the UPGRADE folder to upgrade an existing 3DCityDB instance to this version.

Notable new features and changes

• Added support for PolarDB/Ganos database. #134
• Updated system requirements for Oracle (>= 19c), PostgreSQL(>= 11), and PostGIS(>= 2.5). #154, #155

See the change log for the complete list of changes.

This is a first alpha version of the next major version of the 3DCityDB. Please note that this version only supports PostgreSQL/PostGIS and is meant for testing purpose only.

This is a minor release. Use the SQL scripts in the UPGRADE folder to upgrade an existing 3DCityDB instance to this version.

Notable new features and changes

• PostgreSQL: Run VACUUM ANALYZE after DB migration or upgrade. #87
• PostgreSQL: The VACUUM_SPATIAL_COLUMNS.sql has been simplified and now also works for ADE tables. #77
• Added two new columns GMLID and GMLID_CODESPACE to the IMPLICIT_GEOMETRY table. #79

See the change log for the complete list of changes.

This is a minor release. Use the SQL scripts in the UPGRADE folder to upgrade an existing 3DCityDB instance to this version.

Notable new features and changes

• This release changes all primary key columns under PostgreSQL to use 64-bit bigint as data type instead of 32-bit integer. This substantially increases the maximum value of primary keys and, thus, the number of city objects and surface geometries that can be stored in the database. Foreign key columns as well as affected database functions have been updated correspondingly. #66
• The upgrade and migration scripts take care to correctly update existing 3DCityDB instances running on PostgreSQL. This also includes ADE schemas that have been registered with a 3DCityDB instance. Note that 3DCityDB instances running on Oracle are not affected by this change.

See the change log for the complete list of changes.

This is a minor release. Use the SQL scripts in the UPGRADE folder to upgrade an existing 3DCityDB instance to this version.

Notable new features and changes

• This release brings support for running the 3D City Database in a Docker container. The work is based on the previous developments from TUM GIS at https://github.com/tum-gis/3dcitydb-docker-postgis, which have been moved to the 3DCityDB GitHub repository. Kudos to TUM GIS for this great contribution. #54
• The IS_XLINK column of the SURFACE_GEOMETRY table can now take the values 0, 1, and 2 to be able to distinguish between geometry references across top-level features (IS_XLINK = 1) and references within the same top-level feature (IS_XLINK = 2). This information helps to substantially increase the performance of CityGML exports in case mainly local references are used (which is true for most real-world CityGML datasets). The Importer/Exporter version 4.3.0 fully supports this change. importer-exporter #159

See the change log for the complete list of changes.

This is a maintenance and bug fix release. See the change log for the complete list of changes.

This is a maintenance and bug fix release. See the change log for the complete list of changes.