Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

A spatial engine provides access to a service that can perform spatial operations, such as determining what entities fall within a polygon; The spatial engine also provides a spatial perspective to the entities that the system will use. For example, providing details about the coordinate reference system that the entity is stored in.

The spatial engine will generally be something like ArcSDE, Oracle Spatial, Shapefiles or WFS, and usually at least one spatial engine will be defined.

Because there are different spatial engines available, there are different configuration parameters available for each one. Consequently, the content of a spatial engine tag will be different depending upon the actual spatial engine being used.

Namespace

urn:com.cohga.server.spatial.geotools#1.0

Tags

spatialengine

Properties

Name

Type

Required

Description

id

string

yes

unique identifier

Sub-tags

Depends on type of spatial engine

Content

Depends on type of spatial engine

Examples

Connecting to ArcSDE

<spatial:spatialengine id="arcsde">
	<dbtype>arcsde</dbtype>
	<server>hostname</server>
	<port>5151</port>
	<user>username</user>
	<password>password</password>
	<pool>
		<minConnections>2</minConnections>
		<maxConnections>5</maxConnections>
		<timeOut>10000</timeOut>
		<testOnBorrow>true</testOnBorrow>
		<testOnReturn>false</testOnReturn>
		<testWhileIdle>false</testWhileIdle>
		<timeBetweenEvictionRunsMillis>5000</timeBetweenEvictionRunsMillis>
		<whenExhaustedAction>block</whenExhaustedAction>
	</pool>
</spatial:spatialengine>

Connecting to Oracle Spatial

<spatial:spatialengine id="oracle">
	<dbtype>oracle</dbtype>
	<host>hostname</host>
	<port>1521</port>
	<user>username</user>
	<passwd>password</passwd>
	<schema>SCHEMA</schema>
	<instance>instance</instance>
</spatial:spatialengine>

Connecting to Microsoft SQL Server

<spatial:spatialengine id="sqlserver">
	<dbtype>sqlserver</dbtype>
    <host>hostname</host>
    <port>1433</port>
    <user>username</user>
    <passwd>password</passwd>
    <database>password</database>
    <schema>SCHEMA</schema>
    <geometrymetadatatable>v_geometry_columns</geometrymetadatatable>
</spatial:spatialengine>

Connecting to Microsoft SQL Server using JNDI

<spatial:spatialengine id="sqlserver">
	<dbtype>sqlserverjndi</dbtype>
    <jndi><![CDATA[java:comp/env/jdbc/spatialDS]]></jndi> <!-- Prior to 2.5.28 this must be <jndiReferenceName>...</jndiReferenceName> -->
</spatial:spatialengine>

Connecting to a Shapefile directory

<spatial:spatialengine id="shapefile">
	<dbtype>shapefiledir</dbtype>
	<url><![CDATA[file:C:/data_dir/data]]></url>
	<memorymapped>true</memorymapped>
</spatial:spatialengine>

Connecting to WFS

<spatial:spatialengine id="wfs">
	<dbtype>wfs</dbtype>
	<url><![CDATA[http://hostname/wfs]]></url>
	<protocol>get</protocol>
	<username>username</username>
	<password>password</password>
	<timeout>5000</timeout>
	<buffersize>100000</buffersize>
	<gzip>true</gzip>
	<lenient>true</lenient>
</spatial:spatialengine>

Connecting to ArcGIS

<spatial:spatialengine id="arcgis">
	<dbtype>arcgis</dbtype>
	<url><![CDATA[https://services.arcgis.com/3vStCH7NDoBOZ5zn/arcgis/rest/services/Potable_Water_Pipe/FeatureServer]]></url>
	<crs>EPSG:28356</crs>
</spatial:spatialengine>
  • No labels