Skip to content

Releases: 3dcitydb/3dcitydb

v5.1.3

Choose a tag to compare

@clausnagel clausnagel released this 06 Mar 14:26

This is a bugfix and maintenance release. See the changelog for full details.

v5.1.2

Choose a tag to compare

@clausnagel clausnagel released this 25 Feb 21:16

This is a bugfix and maintenance release. See the changelog for full details.

v5.1.1

Choose a tag to compare

@clausnagel clausnagel released this 06 Dec 13:46

This is a bugfix and maintenance release. See the changelog for full details.

v5.1.0

Choose a tag to compare

@clausnagel clausnagel released this 24 Aug 13:02

This is a minor release introducing schema enhancements, new functions, and important fixes:

  • Extended JSON schema mapping with new attributes (relationType, lod) and added an index on appearance.theme for better query performance.
  • Added new database functions (get_current_schema, set_current_schema, schema_exists, db_properties).
  • Provided upgrade scripts to update existing 3DCityDB v5 instances to the latest version.
  • Unified and improved handling of functions using the schema_name parameter.
  • Fixed issues with get_feature_envelope, delete scripts for grouped/related features, and Docker setup.

We recommend upgrading an existing 3DCityDB v5. Use the upgrade-db script included in the download package and follow the upgrade guide in the online documentation.

See the changelog for full details.

v5.0.0

Choose a tag to compare

@clausnagel clausnagel released this 17 Mar 06:56

🚀 We are excited to announce the release of the new 3D City Database v5, with full support for CityGML 3.0! 🚀

This major update features a completely redesigned, significantly simplified, and streamlined database schema, delivering enhanced performance and flexibility. CityGML 2.0 and 1.0 remain fully supported, with seamless on-the-fly upgrading and downgrading between versions. Learn more about the 3DCityDB v5 and its new tools in our all-new online documentation.

Note

3DCityDB v5 is not backwards compatible, and legacy 3DCityDB v4 tools such as the Importer/Exporter and the Web Feature Service do not support it. However, the 3DCityDB v4 suite remains stable and operational and is now in maintenance mode. We recommend upgrading to 3DCityDB v5 to benefit from new features and improvements.

v4.4.2

Choose a tag to compare

@clausnagel clausnagel released this 28 Feb 16:31

This is a minor bugfix and maintenance release. See the change log for details.

v5.0.0-beta.3

v5.0.0-beta.3 Pre-release
Pre-release

Choose a tag to compare

@clausnagel clausnagel released this 11 Feb 14:52

Changes in this beta release include:

  • Added new terminate functions for terminating features with or without their sub-features, allowing for metadata updates (termination_date, lineage, updating_person, reason_for_update). [#248]
  • Fixed delete functions to ensure implicit geometries are only deleted if they are no longer referenced. [#245]
  • Partial indexes are no longer used for FK columns of the property table. [#247]

v5.0.0-beta.2

v5.0.0-beta.2 Pre-release
Pre-release

Choose a tag to compare

@clausnagel clausnagel released this 18 Dec 07:23

Changes in this beta release include:

  • Added missing delete functions.
  • Use partial indexes ignoring NULL values for val_* columns of the property table.
  • Added CityGML 3.0 definitions for feature types, data types and their attributes to the JSON-based schema mapping.

v4.4.1

Choose a tag to compare

@clausnagel clausnagel released this 14 Nov 19:19

This is a minor bugfix and maintenance release. See the change log for details.

v5.0.0-beta.1

v5.0.0-beta.1 Pre-release
Pre-release

Choose a tag to compare

@clausnagel clausnagel released this 07 Nov 06:36

What's Changed

Full Changelog: 5.0.0-alpha.4...v5.0.0-beta.1