CityDoctor2 Extensions
Extension modules to the core functionality of CityDoctor2.
Loading
The extension modules can be loaded into Maven by two methods:
- Adjusting the pom.xml file of CityDoctorParent by moving the respective modules out of the comment block in the module list (found near the end of the file).
- Importing the module with Maven.
The CityDoctorGUI extension module is loaded by default.
Building
If a module was loaded by including it in the module list of CityDoctorParent, Maven will
automatically build it while building CityDoctor2.
If a module is imported with Maven, it needs to be built directly with Maven.
After building, the jars can be found in the /target subdirectory of each respective extension module's directory.
Module Information
CityDoctorGUI
The GUI module offers a graphical user interface for CityDoctor2, including a model viewer, allowing the visual inspection of validation results and detected errors.
View-Plugins
The GUI is expandable via plugins, enabling the creation of views for custom functionalities or extensions of the CityDoctor2 core.
Custom views can be created by extending the Abstract class View
of the CityDoctorGUI and need to be registered by calling
ViewRegistration.registerView(View view);
before starting the GUI.
Usage
⚠ CityDoctorGUI requires a JDK/JRE containing the JavaFX library to run.
Prebuilt binaries for the GUI are available in CityDoctorReleases. After extracting the archive the GUI can be started with start.bat.
Binaries can be built with Maven using the create-binaries profile from the CityDoctorParent directory:
mvn install -P create-binaries
Lastly, the GUI can also be started by calling MainWindow.main(args[])
.
CityDoctorHealer
CityDoctorHealer implements functionalities for the automated repair of geometries containing errors. The healer uses naive approaches to fix geometrical errors, and thus, it cannot be guaranteed that semantical correctness is maintained after the healing process.
Usage
Usage of CityDoctorHealer is similar to CityDoctor. An example start command looks like this:
java -classpath libs/*;plugins/*;CityDoctorHealer-<version>.jar de.hft.stuttgart.citydoctor2.CityDoctorHealer -in <path-to-gml-file>.gml -config <path-to-validation-config>.yml -xmlReport <path-to-xml-output>.xml -pdfReport <path-to-pdf-output>.pdf -out <path-to-output-gml>.gml
Note: Unlike CityDoctor core, the -out argument is required.
The -xml-output and -pdfReport arguments are still optional.
To prevent infinite loops the Healer
class has a limit for the number of healing iterations (default: 200). This limit
can be changed by calling Healer.setNumberOfIterations(int limit)
.
CityDoctorHealerGUI
CityDoctorGUI-view for CityDoctorHealer. Allows fine control over the automated healing steps, including a preview of the result of each healing step.
Usage
See CityDoctorGUI View-plugins
CityDoctorHealerGenetic
CityDoctorHealerGenetic uses a genetical algorithm to establish an optimal CityDoctorHealer healing-plan for geometries containing errors.
Usage
⚠ This module is currently not being developed and in a prototypical state. As of CityDoctor2 version 3.15.0, this module is still functional, but may break at any point.
Usage is nearly identical to CityDoctorHealer, only requiring changing the classpath to the HealerGenetic jar.
A View-Plugin for CityDoctorGUI is included.
CityDoctorAutoPro
The AutoPro (short for automated processing) module is an interface for the conversion of the internal data model to a C++ representation, to allow use of advanced functionalities of CGAL with CityDoctor2.
Usage
⚠ The AutoPro module is deprecated and will be removed in a future release, once the CGAL functionalities have been ported to Java.
AutoPro requires a collection of .dll-files to run, some of which are not available as FOSS and thus cannot be
distributed with this project.
Access to the collection, or information about the required .dll-files, can be granted upon request for a valid reason.
Contact a Maintainer of this project for further information in this regard.