v0.2.0 Docker Support

Change Log

0.2.0

NEW

• The tool is now also available as a Docker Image,
  see a3a8f9f.

---

🐋 HOW TO RUN USING DOCKER

The following example shows how Docker can be applied in most simple use cases:

1. Create a working directory, such as <WORKING_DIR>. This shall be the default project directory in the following steps.

   mkdir <WORKING_DIR>

2. Create a configuration file:

   mkdir <WORKING_DIR>/config
   touch <WORKING_DIR>/config/config.txt

   The instructions and examples of such configuration files are given here.

3. Create a directory to store input CityGML datasets:

   mkdir <WORKING_DIR>/input

   Then copy the files that need to be matched inside this directory.

4. Pull the latest docker image:

   docker pull sonnguyentum/citygml-change-detection[:Tag]

   where [:Tag] is the version of the Docker image. The list of all tags is available here.

5. Run the Docker container based on the pulled image:

   docker run --rm --name citygml-change-detection -it \
     -v <WORKING_DIR>/config:/citygml-change-detection/config \
     -v <WORKING_DIR>/input:/citygml-change-detection/input \
     -v <WORKING_DIR>/output:/citygml-change-detection/output \
     sonnguyentum/citygml-change-detection[:Tag] \
     "-SETTINGS=<WORKING_DIR>/config/config.txt"

   The argument --rm means that the Docker container is temporary and shall be automatically removed afterwards.

6. The change detection results are now stored in the directories <WORKING_DIR>/output.

🌊 HOW TO BUILD AND PUBLISH IN DOCKER

The Dockerfile used to build the Docker image mentioned above is also included. To build the image, change to the project directory and execute the following command:

docker build -t citygml-change-detection .

OR include a tag to publish in DockerHub:

docker build -t <username>/<repository>[:Tag] .
docker push <username>/<repository>[:Tag]

v0.1.6

Change Log

0.1.6

NEW

• This project is now using Gradle instead of Maven and can be built and published to JFrog Artifactory using the Gradle plugin, see c43173b.
• Added categorization of detected changes to facilitate more user-friendly reading/interpretation, see 6ba3c1e.
• Added example scripts for running the program using parallel execution (such as for tiles), see cbc57d1.
• Added handling of empty city models while exporting RTree images, see 5e0494e.
• Added a statistics bot StatBot, see ea6695a.
• Added option for mapping only one city model (instead of two), see 29069a6.
• Added option for mapping only (without matching/editing), see 29069a6.

UPDATE

• Optimized database memory consumption of very large datasets, see 29069a6.

FIXES

• Fixed matching values of length elements with respect to error tolerance, seee474001.

Release v0.1.5 in Bintray JCenter

Installation and Run

1. Installation

The simplest and fastest way to get the program up and running is to import this project from Bintray JCenter.
Simply add the following lines in the respective option file.

Maven

<dependency>
  <groupId>tum-gis</groupId>
  <artifactId>citygml-change-detection</artifactId>
  <version>0.1.5</version>
  <type>pom</type>
</dependency>

Gradle

dependencies {
    implementation 'tum-gis:citygml-change-detection:0.1.5'
}

Ivy

<dependency org='tum-gis' name='citygml-change-detection' rev='0.1.5'>
  <artifact name='citygml-change-detection' ext='pom'></artifact>
</dependency>

2. Run

After the configuration file has been modified, rebuild the project to download all the dependencies needed.
Then start the program using the following code:

CityGMLChangeDetection program = new CityGMLChangeDetection("config.txt");
program.execute();

The config.txt file contains all configuration parameters needed to run the program.
These parameteres are defined here.