[](https://travis-ci.org/geoserver/wps-remote) [](https://coveralls.io/github/geoserver/wps-remote?branch=master)
RemoteWPS
[RemoteWPS] is an open source software written in Python part of the GeoServer (http://geoserver.org) project that allows users to publish their executables as GeoServer WPS Processes through the XMPP protocol.
RemoteWPS is meant to be used along with the GeoServer “wps-remote” plugin for the WPS (https://github.com/geoserver/geoserver/tree/master/src/community/wps-remote).
Being a community-driven project, RemoteWPS is developed, tested, and supported by a diverse group of individuals and organizations from around the world.
## License
RemoteWPS licensed under the [GPL](http://www.gnu.org/licenses/old-licenses/gpl-2.0.html).
## Using
You can install the “wps-remote” Python package by using the PyPi distribution
pip install wps-remote==2.14.1
Please refer to the [user guide](http://docs.geoserver.org/latest/en/user/community/remote-wps/index.html) for detailed information on how to install and use RemoteWPS.
## API Reference Doc
## Bugs
Through GeoServer JIRA.
GeoServer uses [JIRA](https://osgeo-org.atlassian.net/projects/GEOS), hosted by [Atlassian](https://www.atlassian.com/), for issue tracking.
## Mailing Lists
Through GeoServer Mailing Lists.
The [mailing list page](http://geoserver.org/comm/) on the GeoServer web site provides access to the various mailing list, as well as some indication of the [code of conduct](http://geoserver.org/comm/userlist-guidelines.html) when posting to the lists
## Contributing
Through GeoServer Process.
Please read [the contribution guidelines](https://github.com/geoserver/geoserver/blob/master/CONTRIBUTING.md) before contributing pull requests to the GeoServer project.
## More Information
Visit the [website](http://geoserver.org/) or read the [docs](http://docs.geoserver.org/).
Change Log
- 2.14.1 [2018-09-14 11:48:37] (aligned with GeoServer Remote WPS Plugin - 2.14.x)
Fixes: inputs and outputs mime-types declaration on service.config
Cleanup: removing non source code stuff
Resilience: resource_monitoring now skips non-python/readable processes without dying
Resilience: processbot identifies relative paths for executable commands
- 2.12.0 [2017-07-03 12:13:10] (aligned with GeoServer Remote WPS Plugin - 2.12.x)
Fix for: Inputs application/json mapping error
Fix for: Inputs application/vnd.geo+json support
Fix for: Date input / output parsing
Fix for: JSON ID error
Improved robustness of wps agent
Allowed “-” in string input parameters
Fix for: Catch resource clean exception
Fix for: Input / output parameters are not sorted according to the process definition
- 2.11.2 [2017-02-16 10:12:23]
SFTP/FTP pluggable uploaders support
Minor refactoring and code cleanup
- 2.9.3 [2016-03-31 17:24:47]
Added “processbot” XMPP connection checks
Added “servicebot” check “processbot” status error and send error message impersonating the underlying process
Added “NetCDF Output” example on service.config
- 2.9.2 [2016-03-17 17:33:19]
Added “process_blacklist” property to “service.config” file
Added “proc_is_running(self, proc_names)” to “ResourceMonitor(threading.Thread)” background thread
- 2.9.1 [2016-03-16 11:09:56]
Added “GetLoadAverageMessage” XMPP message for resource monitoring
Added “ResourceMonitor(threading.Thread)” background thread collecting resource consuption data
On GeoServer side the “remoteConfig.properties” file on GEOSERVER_DATA must be updated with the properties xmpp_cpu_perc_threshold = 80.0 xmpp_mem_perc_threshold = 80.0
Metadata
Release files for wps-remote 2.15.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| wps-remote-2.15.0.tar.gz | 63.3 kB | Without provenance | Details for wps-remote-2.15.0.tar.gz |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| wps_remote-2.15.0-py2-none-any.whl | Python 2 | none | any | Details for wps_remote-2.15.0-py2-none-any.whl |
| wps-remote-2.15.0.linux-x86_64.tar.gz | Details for wps-remote-2.15.0.linux-x86_64.tar.gz |
Total release size: 7.9 MB
Release files / wps-remote-2.15.0.tar.gz
| Download URL | wps-remote-2.15.0.tar.gz |
|---|---|
| Size | 63.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
21c53a2917a4dfbc8c7f8328f744fb72eba57db9ae290e450e2553e587a1b4d3
|
|
BLAKE2b-256 checksum How to use checksums |
9fcfe2df820cd94fa699055fadd31c986fe9e2afc3ce3012785b8e16c4838e5e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/2.7
|
Release files / wps_remote-2.15.0-py2-none-any.whl
| Download URL | wps_remote-2.15.0-py2-none-any.whl |
|---|---|
| Size | 3.9 MB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
c36d3f32a97a28d8f547ff767693e5c6e5b7f3a0ba0e56bcab95b135e3c61683
|
|
BLAKE2b-256 checksum How to use checksums |
1bd4d9d569fc664535a95733dd78aa12c698dacea714fb8769d273c7c50970e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/2.7
|
Release files / wps-remote-2.15.0.linux-x86_64.tar.gz
| Download URL | wps-remote-2.15.0.linux-x86_64.tar.gz |
|---|---|
| Size | 3.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3d5484b51bcab87db400182ee6b808edbe7816f5d03a12e343adf811fd527f5d
|
|
BLAKE2b-256 checksum How to use checksums |
12851569bbfa86ac123c8662c41da11607febfce57aa1fc681c062007b0b0542
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/2.7
|
Security for wps-remote 2.15.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.