v3.3.1

This is a maintenance and bug fix release.

• Fixed database version check to be able to connect to future bug fix releases of the 3D City Database
• Fixed issues with 3D SRIDs under Oracle and PostGIS (more work required)
• Fixed BBOX calculation under PostGIS
• Fixed missing XML namespace declarations when doing a tile-based CityGML export
• Fixed error when running on machines with single-core CPUs
• Catch errors when resolving XLinks to solid geometries
• Added missing exception handling to ImpExpCmd.java
• Minor changes to geometry API
• Minor changes to balloon template handler API
• Updated citygml4j to version 2.4.1

The 3D City Database schema and procedures have not been updated with this release. Thus, no upgrade action is required for version 3.3 instances of the 3D City Database.

v3.3.0

We are happy to introduce the new 3DCityDB-Web-Map-Client as latest component of the 3D City Database ecosystem. The 3DCityDB-Web-Map-Client is a Cesium-based 3D web viewer that allows for direct 3D visualization and interactive exploration of arbitrarily large semantic 3D city models based on datasets (KML/glTF modes + online spreadsheets) exported using the importer/exporter.

With this release, the license of the 3D City Database and all tools has been changed to Apache License, Version 2.0. See the LICENSE file for more details. Note that previous versions of the software continue to be licensed under GNU LGPL 3.0 license. To request a version before 3.3.0 under Apache License 2.0 create a GitHub issue.

Notable changes to the importer/exporter tool:

• The 3DCityDB-Web-Map-Client is bundled with the importer/exporter and can be chosen to be installed during the installation process.
• Java 8 is now required.
• Completely revised and updated documentation.
• Fixed bug that caused missing altitude mode in KML exports when choosing clamp to ground (#10).
• Fixed bug with locale sensitive strings that caused the importer/exporter to not start correctly (#9).
• Textures can now be embedded in glTF files (#7).
• Direct upload of attribute data to Google Spreadsheet has been removed from the Spreadsheet Generator Plugin. This functionality might come back in future releases.

Notable changes to the database schema and procedures:

• Added missing foreign key constraint from BRIDGE.ID to CITYOBJECT.ID (PostgreSQL)
• The MIGRATION scripts for Oracle have been optimized to achieve a better performance.
• Reworked all UPGRADE scripts.
• Fixed CITYDB_PKG bugs under Oracle Locator.
• Fixed issues in the DELETE package.
• Removed delete_cityobject_cascade function from DELETE package.
• Fixed CREATE_DB issues when SRID cannot be found.
• Completely revised and updated documentation.

v3.2.0

Notable changes to the importer/exporter tool

• New glTF export in addition to the KML/COLLADA export

The exported glTF files can be directly visualized with the 3dcitydb-web-map client based on the open-source web globe Cesium. We are currently working on a comprehensive documentation for the glTF export and the 3dcitydb-web-map client. It will be released soon - so stay tuned.

v3.1.0

Notable changes to the database schema and procedures:

• Implemented user request to readd column GMLID_CODESPACE on tables CITYOBJECT, APPEARANCE, SURFACE_GEOMETRY, ADDRESS, SURFACE_DATA, CITYMODEL (were dropped in 3.0.0)
• ADDRESS table extended to store GMLID
• Added database procedures to calculate the ENVELOPE of city objects
• Optimization of MIGRATION script for Oracle
• Bugfix in BRIDGE Oracle schema preventing import of bridges with thematic surfaces

Notable changes to the importer/exporter tool

• Fixed bug in BRIDGE importer preventing import of bridges with thematic surfaces
• Fixed KML/COLLADA export of CityObjectGroup features
• Added user dialog to control GMLID_CODESPACE during import
• Added user dialog to calculate the ENVELOPE of city objects in the database
• Changed the way global appearances are imported
• Importer/Exporter now checks the version of the 3DCityDB before connecting
• Texture metadata is imported even if texture images are chosen to be not imported
• Updated to citygml4j 2.2.2
• Minor bugfixes and improvements

v3.0.0

Significant changes with respect to the previous software version 1.6.0

• Adaption and extension of the CityGML Importer/Exporter as well as of the KML/ COLLADA Exporter to the new database schema / CityGML 2.0. CityGML 1.0 datasets can be converted on-the-fly into CityGML 2.0. Export and import of CityGML 1.0 datasets are still supported.
• Performance improvements when reading and writing large CityGML datasets over a network
• Improved support of 3D city models which use texture atlases regarding a more compact storage and a higher import, export, and visualization performance.
• Improved handling of 3D models with large coordinate values in the KML/COLLADA Exporter.
• Both Oracle and PostGIS databases are supported by the same Import/Export tool (there are no longer separate versions of the Import/Export tool).
• Unified concept for the storage of image data in Oracle and PostGIS.
• The 3D City Database now shares the same version number.
• Completely reworked, extended, and updated documentation.

Notable new features and functionalities

• Support of all new CityGML 2.0 feature types like bridges and tunnels with respect to the previous version of CityGML. Support of CityGML 2.0’s grouping concept for generic attributes.
• CityGML Solid geometry objects are now stored as 3D solid geometries in Oracle (starting from version 11g) and PostGIS in addition to their decomposition into the individual boundary surfaces.
• The newly included ‘Spreadsheet Generator’ plugin allows exporting data from a 3D City Database instance into tables. Supported output formats are Microsoft Excel, CSV, and Google Spreadsheets.
• Schema files of the database schemas are included for Oracle and PostGIS.
• Support of GenericCityObjects having point and/or line geometries in the KML/ COLLADA Exporter.

Dropped items or functionalities

• The ‘Merging’ plugin of the previous Importer/Exporter version 1.6.0 was not updated to the new database schema and has been removed.
• The tool for importing and exporting raster data for Oracle Spatial is no longer supported. Please use third party software instead.