A spatial engine provides access to a service that can perform spatial operations, one of the available spatial engines is for a WFS service.
Namespace
urn:com.cohga.server.spatial.geotools#1.0
Tags
spatialengine
Properties
Name |
Type |
Required |
Description |
id |
string |
yes |
Unique identifier |
dbtype |
'wfs' |
yes |
The name of the driver to use, in this case WFS |
url |
string |
yes |
The URL that points to the WFS servers get capabilities request |
protocol |
string |
no |
'post' to use POST requests, 'get' to use GET or 'auto' or not set for auto |
encoding |
string |
no |
The character encoding to use for the XML requests sent to the WFS server |
username |
string |
no |
The userid used when connecting to the WFS server |
password |
string |
no |
The password used when connecting to WFS server |
timeout |
integer |
no |
Time in ms to timeout a request, default 3000ms |
buffersize |
integer |
no |
The number of features to buffer, default 10 |
gzip |
boolean |
no |
Indicates that gzip compression should be performed when communicating with the WFS server, default is 'true' |
lenient |
boolean |
no |
Indicates that the spatial engine should try and be forgiving of the data it receives from the WFS server, default is 'false' |
Sub-tags
None
Content
None
Examples
<spatial:spatialengine id="spatialengine.wfs"> <dbtype>wfs</dbtype> <url><![CDATA[http://vmrunout:8080/geoserver/ows?service=WFS&request=GetCapabilities]]></url> <protocol>get</protocol> <username>username</username> <password>password</password> <timeout>60000</timeout> <buffersize>100000</buffersize> <gzip>false</gzip> <lenient>true</lenient> </spatial:spatialengine>