The following walkthrough requires a working installation of BaseX with the TopoX plugin installed.
Before TopoX can be used in a test, the library must be initialized with the name of the database and the number of databases that will be used:
topox:init-db("MY-DB-000", xs:short(1))The first parameter ("MY-DB-000") is the database name.
Database names must be suffixed with a three digits index starting with 000. This is necessary because internally the suffix is used to encode references (see architecture documentation for details).
As second parameter the number of databases is passed.
The Features of interest are selected and projected. For example with this Query:
let $surfaces := $db/adv:AX_Bestandsdatenauszug/adv:enthaelt/wfsAdv:FeatureCollection/gml:featureMember/*[adv:modellart/adv:AA_Modellart[adv:advStandardModell = $modellart] and local-name() = ('AX_Fliessgewaesser', 'AX_Schiffsverkehr', 'AX_Strassenverkehr') and not(adv:hatDirektUnten) and adv:position/gml:Surface]
Multiple topologies can be set up for a set of Features and checked. The initialization of a new topology object -which represents a topological theme- is done with:
let $topoId := topox:new-topology(
'Tatsaechliche_Nutzung',
'/tmp',
$initialEdgeCapacity
)
where the first parameter is the name of the topology theme, the second one a path to a temporary output directory as string and the third one the expected number of edges that should exist in the data. The third parameter is used to initialize the data structure in an appropriate size and thus to increase the performance. It can be specified smaller than the actual number, but then internal reallocations and performance losses can be the result. In tests good results were achieved with a value of 1995000 * number of databases.
The call returns an integer as identifier for the topological theme that must be used in all further function calls.
The parsing and validation is started with:
let $dummy := topox:parse-surface($surfaces, 'adv:position/gml:Surface', $topoId)
The Features are passed in the first parameter. The second parameter is the path to the geometry properties starting from the passed Features. At present, GML LineStringSegments and Arcs are processed.
This function call will take some time depending on the amount of data.
During the parsing, errors are written to a temporary file. The detected errors include intersections and overlapping edges (see RING_OVERLAPPING_EDGES and RING_INTERSECTION error codes). The errors can be retrieved by using the topological-errors() function:
let $errors := topox:topological-errors($topoId, ('RING_INTERSECTION'))
for $error in $errors
let $isFeature := topox:feature($error/IS[1]/text())
let $isFeatureId := xs:string($isFeature/@gml:id)
order by $isFeatureId
return $isFeatureId || " : intersection at point " || $error/X/text() || " " $error/Y/text()
The structure that the topological-errors() function returns is described in the Topological errors types section.
A complete example can be found here.
The following post processing features must be called after the topological data structure has been built ( parse-surface() has been called ).
Holes -the surface of a Feature with an inner boundary that is not filled by another surface- can be detected by using the detect-holes() function:
let $holeCount := topox:detect-holes($topoId)The function returns the number of found holes. All detected issues are saved with the HOLE_EMPTY_INTERIOR error code and can be retrieved with the topological-errors() function.
Free-standing surfaces can be detected by using the detect-free-standing-surfaces() function:
let $freeStandingSurfaceCount := topox:detect-free-standing-surfaces($topoId)The function returns the number of found free-standing surfaces.
All detected issues are saved with the FREE_STANDING_SURFACE error code and can be retrieved with the topological-errors() function.
Some objects can describe certain boundaries, like units of administration dividing areas. With TopoX it can be tested whether the boundaries of the administrative units are exactly on the boundary points and edges of other features.
Boundaries can be condensed like topological themes and must be created with:
let $boundaryId := topox:new-boundary-check($topoId)where the parameter references a topological theme as basis for checks.
The second call to start the parsing of boundaries, is very similar to the parse-surface() function.
let $borderParsingDummy := topox:parse-boundary($borders, 'adv:position/gml:*', $boundaryId)If the points or edges of the boundaries do not overlap exactly with the basis data, BOUNDARY_POINT_DETACHED and BOUNDARY_EDGE_INVALID errors are reported in the error file.
This function will export a map with the topological errors as HTML file to the temp folder. This feature is still very experimental and intended for developers until now.
let $dummyMap := topox:export-erroneous-features-to-geojson($topoId, "Map")TopoX exposes the errors found via two functions: topological-errors-doc() and topological-errors(). The first function can be used to retrieve all errors as one node, the second one accepts a parameter to filter the errors for specific error types:
(: Get all erros :)
let $allErrors := topological-errors-doc($topoId)
(: Get only errors of the type RING\_INTERSECTION and the FREE\_STANDING\_SURFACE :)
let $ringAndFreeStandingSurfaceErrors := topological-errors($topoId,
('RING_INTERSECTION', 'FREE_STANDING_SURFACE'))The internal error structure, completly returned by the topological-errors-doc() function, looks like this:
<ete:TopologicalErrors xmlns:ete="http://www.interactive-instruments.de/etf/topology-error/1.0"
name="Tatsaechliche_Nutzung">
<e i="1" t="RING_INTERSECTION">
<IS>519785877976</IS>
<X>367300.055</X>
<Y>5614385.776</Y>
<CW>579820659004</CW>
<CCW>609885430083</CCW>
</e>
<e i="2" t="FREE_STANDING_SURFACE">
<X>364965.726</X>
<Y>5620249.802</Y>
<IS>365113240849</IS>
</e>
</ete:TopologicalErrors>The structure's root is the TopologicalErrors element and name attribute represents the topological theme. Below the root element, the errors can be found ( e elements). topological-errors() will only return these (filtered) error e elements.
Each error possesses an simple integer ID ( i attribute ) and the error type ( t attribute). The names and attributes are abbreviated to support faster parsing of the error file. An error code can possess various properties which will be described below.
The X and Y properties always stand for the X and Y coordinates. All other properties (IS, CW, CCW) reference a feature and its geometry in the database.
The feature can be queried with the feature(), the geometry with geometric-object() function:
let $error := topox:topological-errors($topoId, ('RING_INTERSECTION'))[1]
(: Feature gml:id :)
let $feature := topox:feature($error/CW[1]/text())
let $featureId := xs:string($feature/@gml:id)
(: Geometry gml:id :)
let $geometry := topox:geometric-object($error/CW[1]/text())
let $geometryId := topox:geometric-object($feature/../../../../@gml:id)
Even if multiple databases are used, the objects are automatically fetched from the corresponding database.
There are two Features that define an edge at two points. The features lie on the same side and therefore overlap. The IS property references the first object that is on the edge, the O refernces the object that collides with the existing one. The X, Y properties may reference either the start or the end point of the edge.
There are at least three edges that are connected at one point (X, Y properties). Due to their angles, two edges intersect in the course of the lines. The IS property references the object where the error has been detected. CW is the object that is connected counter-clockwise to the edge, CWW is the object that is connected counter-clockwise to the edge.
The surface of a Feature with an inner boundary is not filled by the surface of another Feature. The IS property (and X, Y properties) references the object where the error has been detected.
There are at least two free-standing surfaces. All surfaces except the largest, with the most edges, are reported. The IS property (and X, Y properties) references the object where the error has been detected.
A boundary point (X, Y properties) was defined that could not be found in the topological basis data. The IS property references the object where the error has been detected.
An edge (X, Y reference start point of the edge, X2, Y2 the end point) was defined that could not be found in the topological basis data. The IS property references the object where the error has been detected.
An edge could not be found. This is most likely a consequential error if others occurred and for instance the connection between two points has been invalidated in the data structure. If this is the only type of error that occurred, then this may indicate a bug in the software.
An error occurred while connecting an additional edge to a point. Attempting to traverse the angles of all connected edges has exceeded the maximum number of possible steps. If this is the only type of error that occurred, then this may indicate a bug in the software.
Note: In general the EDGE_NOT_FOUND and the INVALID_ANGLE errors can be ignored if errors have previously been reported with other error codes.