v4.2.0

This is a maintenance and bug fix release.

Notable new features and fixes

• CityJSON output now uses the latest CityJSON version 0.9.
• Using UTF-8 encoding for CityJSON output per default.

The release is based on the Importer/Exporter version 4.2.0, and thus incorporates all bug fixes and updates introduced with this release (more information).

Works with versions 4.0.x of the 3D City Database.

See the change log for the complete list of changes.

v4.1.0

This is a maintenance and bug fix release.

The release is based on the Importer/Exporter version 4.1.0, and thus incorporates all bug fixes and updates introduced with this release (more information).

Works with versions 4.0.x of the 3D City Database.

See the change log for the complete list of changes.

v4.0.0

We are happy to announce the new major version 4.0 of the Web Feature Service interface for the 3DCityDB. 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 WFS can connect to a 3DCityDB instance that has been extended with one or more CityGML ADEs, and can deliver ADE data to the client. For this to be possible, an ADE extension has to be implemented against the new ADE API of the Importer/Exporter and has to be copied into the ade-extensions folder within the WFS installation directory. Thus, if you have already implemented such an extension for the Importer/Exporter to be able to use it to import and export ADE data, then you can simply reuse this implementation for the WFS. An example for an ADE implementation is available here.

Notable new features and additions

• Added support for CityGML ADEs through ADE extensions.
• Added KVP over HTTP GET as additional service binding to simplify the integration with GIS and ETL software such as FME.
• Added CityJSON as additional output format besides CityGML.
• New LoD filter for WFS responses.
• Added support for CORS.
• Switched from Ant to Gradle as build system.
• 3DCityDB Docker images are now available for a range of 3DCityDB and WFS versions to support continuous integration workflows.

See the change log for the complete list of changes.

v3.3.2

This is a maintenance and bug fix release.

The release is based on the Importer/Exporter version 3.3.2, and thus incorporates all bug fixes and updates introduced with this release (more information).

Works with versions 3.0.0 - 3.3.x of the 3D City Database.

v3.3.1

This is a maintenance and bug fix release.

The release is based on the Importer/Exporter version 3.3.1, and thus incorporates all bug fixes and updates introduced with this release (more information). Most importantly:

• Fixed error when running on machines with single-core CPUs

Works with versions 3.0.0 - 3.3.x of the 3D City Database.

v3.3.0

This is a maintenance and bug fix release.

• Fixed SQL injection vulnerability. It is strongly recommended to update any 3DCityDB WFS service to this version.
• Java 8 is now required.
• Improved CORS support.
• Works with versions 3.0.0 - 3.3.0 of the 3D City Database

v3.2.0

This release works with version 3.2.0 of the 3DCityDB

v3.0.0

This is the first release of the Web Feature Service interface for the 3D City Database.

Significant features

• Compliant with version 2.0 of the OGC Web Feature Service standard (OGC Doc. No. 09-025r2) and with ISO 19142:2010.
• Supports CityGML 2.0 and 1.0 as output format.
• Satisfies the Simple WFS conformance class.
• Shares the same version number with the 3D City Database.
• Comprehensive documentation.