...
When the table is present the store will first search it for information about each geometry column to be classified, and fall back on the MDSYS views only if such table does not contain any information.
Using geometry metadata configuration
As of Weave 2.5.16 it's possible to specify the information contained in the geometry metadata table directly in the spatial engine configuration.
| Name | Description |
|---|---|
name | The table name |
schema | The optional table schema |
| type | The geometry type (point, line, curve, polygon, multipoint, multiline, multicurve, multipolygon) |
| srid | The geometry srid |
| dimension | The geometry dimension |
| Code Block | ||
|---|---|---|
| ||
<spatial:spatialengine id="sdbeos">
<dbtype>oracle</dbtype>
<host>sdbeos</host>
<port>1521</port>
<database>staging</database>
<user>data_viewer</user>
<passwd>ENCSSJKXUMJBMTPGEJFGCXCQFXJJZUTMJZJ</passwd>
<schema>ASSETS</schema>
<geometrymetadata>
<table name="PARK" type="multipolygon" srid="28355" dimension="2"/>
<table name="PROPERTY" type="polygon" srid="28355" dimension="2"/>
<table name="ROAD" type="line" srid="28355" dimension="2"/>
</geometrymetadata>
</spatial:spatialengine> |