Skip to content

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

Assets 3

@yaozhihang yaozhihang released this Apr 17, 2019 · 136 commits to master since this release

This is a minor maintenance and bug fix release.

Notable new features and additions

  • Added the -pid-file command-line argument to create a file storing the process ID of the Importer/Exporter at the provided path. This can be useful to check whether the Importer/Exporter is running or to issue a kill command to end it.
  • Updated Spreadsheet Plugin to version 3.1.2.
  • Updated ADE Manager Plugin to version 1.1.2.
  • Updated 3DCityDB-Web-Map to version 1.7.1.
  • Minor fixes and improvements.

See the change log for the complete list of changes.

Assets 3

@clausnagel clausnagel released this Feb 13, 2019 · 164 commits to master since this release

This is a maintenance and bug fix release.

Notable new features and additions

  • Reworked Plugin API to support non-GUI plugins. #78
    Previous versions of the Plugin API focused on plugins with a GUI. But there is also benefit in having plugins that are just hooked into internal processes such as CityGML imports and exports. This version brings first support for such non-GUI plugins. A new CityGMLExportExtension has been added as a first extension point for non-GUI plugins. Using this extension, a plugin receives and can process all CityGML features before they are written to the output file. Besides using XSLT stylesheets for CityGML exports, this adds another way of having full control over the output. Note: Due to the changes to the Plugin API, make sure to only use plugins built for this version.
  • Property projections can now also be defined for abstract feature types.
  • Fixed broken feature type filter for CityGML imports. #75
  • Fixed NPE in GeometryConverter when using affine transformations during CityGML imports. #77

See the change log for the complete list of changes.

Assets 3

@clausnagel clausnagel released this Jan 9, 2019 · 228 commits to master since this release

This is a maintenance and bug fix release.

Notable new features and additions

  • Added support for using SQL queries and XML-based filter expressions in CityGML exports. Please refer to the documentation to learn more about the new filter capabilities.
  • Added support for importing CityGML data from ZIP/GZIP files and for exporting CityGML content to ZIP/GZIP files. #62, #63
  • The map window now uses OSM Nominatim as the default geocoding service. Google Maps services can still be used but require a Google API key. #61

See the change log for the complete list of changes.

Assets 3

@clausnagel clausnagel released this Sep 18, 2018 · 377 commits to master since this release

We are happy to announce the new major version 4.0 of the Importer/Exporter. During the past year, we have worked hard to implement support for CityGML Application Domain Extensions (ADEs). The ADE mechanism is a built-in feature of CityGML that allows users to extend the CityGML data model with additional types, attributes and relations, which carry information required for specific applications and which are integrated with the predefined 3D city objects. ADEs are becoming more and more popular, and are defined for various application fields such as energy assessment and simulation (Energy ADE) or modelling of utility networks (UtilityNetwork ADE). A non-exhaustive list of further ADE developments is available here.

With this release, the 3DCityDB database schema can be dynamically extended by arbitrary ADEs. We have developed a transform method that reads the XML Schema definition of an ADE and automatically derives a relational schema that seamlessly integrates with the 3DCityDB core schema. This method is presented in detail here, and has been implemented in the newly available ADE Manager Plugin for our Importer/Exporter tool. The plugin allows users to register one or more ADEs with an existing 3DCityDB instance and automatically generates SQL scripts to work with the ADE data (e.g. for the performant deletion of ADE objects from the database). The Importer/Exporter tool itself has been extended with an ADE API. So, if you want to use this tool to import and export ADE data, then you have to implement this API. An example for an ADE implementation is available here.

Notable new features and additions

  • Added new extension mechanism to support arbitrary CityGML ADEs.
  • Added new ADE manager plugin to dynamically extend a 3DCityDB instance with support for a given CityGML ADE.
  • Added support for connecting to different database schemas with the same user.
  • Added support for XSL transformations on CityGML imports and exports.
  • Added support for importing CityGML files with flat hierarchies.
  • Added support for importing gml:MultiGeometry objects consisting only of surfaces.
  • New LoD filter for CityGML exports.
  • Source code has been split into modules that are available as Maven artifacts from Bintray.
  • Switched from Ant to Gradle as build system.

See the change log for the complete list of changes.

Assets 3

@clausnagel clausnagel released this Nov 14, 2017 · 719 commits to master since this release

This is a maintenance and bug fix release.

Notable changes to the importer/exporter tool:

  • Resolved potential memory leaks in CityGML exporter
  • Fixed KML/COLLADA/glTF export bug in handling of surface geometries with multiple surface data for different appearance themes (#25)
  • BBOX filtering during exports is now always performed on the database and not at the client side
  • Fixed issues in CityGML SAX writer which mainly caused invalid WFS responses
  • Fixed backslash issue when importing world files
  • Fixed bug that caused the CityGML import to fail due to empty geometries
  • Fixed invalid Railway example dataset
  • Minor fixes and improvements

The importer/exporter is shipped with the latest version 1.4 of the 3DCityDB-Web-Map-Client, which features Cesium version 1.35 as well as better support for mobile devices, such as optimized user interface and the "first-person view" mode that utilizes real-time GPS information.

Update of database schema and procedures:
The 3D City Database schema and procedures have been updated to version 3.3.1 with this release. Please check the release notes for an overview of the changes.

Due to a bug in the creation of spatial indexes on PostgreSQL/PostGIS, it is strongly recommended to upgrade your existing 3DCityDB instance to version 3.3.1.

Assets 3

@clausnagel clausnagel released this Nov 21, 2016 · 789 commits to master since this release

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.

Assets 3

@clausnagel clausnagel released this Aug 29, 2016 · 826 commits to master since this release

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.
Assets 3

@clausnagel clausnagel released this Mar 24, 2016 · 902 commits to master since this release

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.

Assets 3

@clausnagel clausnagel released this Mar 10, 2016 · 983 commits to master since this release

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
Assets 3
You can’t perform that action at this time.