The 3D City Database WFS is shipped as a Java WAR (web archive) file.
Please download the WFS distribution package from
http://www.3dcitydb.org/. Besides the WAR file, the distribution package
also contains Java libraries that render mandatory dependencies for the
WFS service and that must be installed as shared libraries in your
Alternatively, you may build your own WAR file from the source
code provided on [GitHub](https://github.com/3dcitydb/web-feature-service).
This requires that you are experienced in building Java web applications
from source using Gradle. No further documentation is provided here.
Please follow the following installation steps:
Step 1: Install and properly configure your Java servlet container
Please refer to the documentation of your servlet container for
hints on installation and configuration. Make sure that the servlet
container uses Java 8 (or higher) for running web applications.
Step 2: Install the mandatory JAR libraries in your servlet container
The WFS service requires mandatory JAR libraries to be available in
the servlet container. This mainly comprises JDBC libraries for
connecting to the database system running the 3D City Database instance.
The libraries are shipped with the distribution package. The list of
libraries will look like this:
ojdbc8-184.108.40.206.jar (Oracle JDBC driver)
postgresql-42.2.5.jar (PostgreSQL JDBC driver)
postgis-jdbc-2.3.0.jar (PostGIS JDBC extension)
The libraries must be installed as shared libs or common libs
(terminology may differ) in your servlet container. For Apache Tomcat 7
(or higher), this simply means placing the JAR files into the lib folder
of the Tomcat installation directory. Afterwards, you need to restart
Tomcat. Please refer to the documentation of your servlet container for
Step 3: Deploy the WFS WAR file on your servlet container
If your servlet container is correctly set up and configured, simply
deploy the WAR file to install the WFS web service. Again, the way to
deploy a WAR file varies for different servlet containers. For Apache
Tomcat servers, copy the WAR file into the webapps folder, which, per
default, is in the installation directory of the Apache Tomcat server.
This will automatically deploy the application. Alternatively, use the
web-based Tomcat manager application to deploy WAR files on the
server. The manager application is included in a default installation.
For more information on deploying WAR files on Tomcat or different
servlet containers, please refer to the corresponding documentation
If you use the automatic deployment feature of Tomcat as
described above, the name of the WAR file will be used as context path
in the URL for accessing the application. For example, if the WFS WAR
file is named citydb-wfs.war, then the context path of the WFS service
http://[host][:port]/citydb-wfs/. To pick a different context
path, simply rename the WAR file or change Tomcat’s default behavior.
Step 4: Configure your servlet container (optional)
Make sure that your servlet container has enough memory assigned
(heap space ~ 1GB or more).
You may, for instance, use the Java command-line option -Xms for
Step 5: Configure the WFS service
The WFS must be configured to meet your needs. For instance, this
includes providing connection details for the 3D City Database
instance and the definition of the feature types that shall be served
through the interface. These settings must be manually edited in the
configuration file config.xml of the service. A graphical user dialog
will be developed for a future release. Please check the next chapter
for how to configure the WFS.
Changes to the config.xml file typically require a reload or
restart of the WFS web application (a restart of the servlet container
itself is, of course, not required). Please check to documentation of
your favorite servlet container for how to do so. In case of Apache
Tomcat, you can simply use the manager application to reload web
Step 6: Install ADE extensions (optional)
As a last step, you may install additional CityGML ADE extensions
for the WFS. This step is optional and requires a compiled and
ready-to-use ADE extension package. Simply copy the contents of the
ADE extension package to the WEB-INF/ade-extensions directory of your
deployed WFS application. The WEB-INF directory is typically located
in the application
folder, which is generally named after the WAR
file and itself is a subfolder of the webapps folder in the Tomcat
installation directory (see Fig. 4.1
The CityGML ADE must also be registered in the 3DCityDB instance
to which your WFS service shall connect.