This project is a fort of the 52°North Web Processing Service and intends to provide an implementation of the transactional extension . WPS2.0 Transactional Extension Implementation Standard OGC 13-071r1 lightly modified to adapt to version 2.0 of WPS.
Please consult Wiki pages for detailed information about the project: WPS Transactional Wiki.
The 52°North Web Processing Service (WPS) enables the deployment of geo-processes on the web in a standardized way. It features a pluggable architecture for processes and data encodings. The implementation is based on the current OpenGIS specification: 05-007r7.
Its focus was the creation of an extensible framework to provide algorithms for generalization on the web.
More information available at the 52°North Geoprocessing Community.
The 52°North WPS provides wrappers to well-established (geographical) computation backends.
Use git to clone the WPS repository:
git clone https://github.com/52North/WPS.git
Then just run mvn clean install
on the repositories root directory.
Due to licensing issues all GeoTools based input/output handlers and algorithms are not included by default. If you want to use them (or any backend relying on them), you have to explicitly enable them with the with-geotools
profile:
$ mvn clean install -P with-geotools
To run your project in Eclipse with geotools support using the WTP plug-in (52n-wps-webapp -> Run As -> Run on Server) add the profile to the Active Maven profiles in the project properties of 52n-wps-webapp (right click on the project, select "Maven", add with-geotools
to the text field).
There are several ways to supply a wps_config.xml
file:
The supplied path will be written to the web.xml
and will be used at runtime. For this to work, the path should be absolute.
$ mvn install -Dwps.config.file=/path/to/external/file/that/will/be/used
The supplied file will be copied to the WAR file and will be used at runtime.
$ mvn install -Dinclude.wps.config.file=/path/to/external/file/that/will/be/copied
The supplied value will override every other configuration.
$ java [...] -Dwps.config.file=/path/to/external/file/that/will/be/used
This works well with a server configuration in Eclipse WTP. Open the server editor, click "Open launch configuration" and add the property to the VM arguments.
The supplied value will override every other configuration except a possible system property. See the [Apache Tomcat documentation](https://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Environment Entries):
<Context ...>
...
<Environment name="wps.config.file" value="/path/to/file"
type="java.lang.String" override="false"/>
...
</Context>
You can edit the web.xml
after creation and substitute another path:
<servlet>
<servlet-name>WPS</servlet-name>
<servlet-class>org.n52.wps.server.WebProcessingService</servlet-class>
<init-param>
<param-name>wps.config.file</param-name>
<param-value>/path/to/file</param-value>
</init-param>
</servlet>
Create a file named wps_config.xml
in the home directory of the user that executes the servlet container.
The WPS comes with a variety of integration tests which are performed using Jetty.
In order to execute integration tests in a maven build, activate the dedicated profile
through mvn clean install -Pwith-geotools,integration-test
.
You can find information about how to contribute to this project in the Geoprocessing Wiki.
This project consists of modules which are published under different licenses.
For details see the LICENSE and NOTICE files. Be aware that some modules contain their own LICENSE and NOTICE files.