Skip to content

Latest commit

 

History

History
46 lines (28 loc) · 2.55 KB

spatial.md

File metadata and controls

46 lines (28 loc) · 2.55 KB

Spatial consistency

Version: 1

Purpose: Verify that the spatial information is consistent.

Prerequisites

n/a

Test method

Verify that hydrographic networks are spatially connected across data sets.

Automated assertions:

  • If the data set contains both WatercourseLink and SurfaceWater (Watercourse or StandingWater) features, use a geometry library to verify for each WatercourseLink that its centrelineGeometry is within the geometry of a single Watercourse or StandingWater feature. Verify for each HydroNode that its geometry is within a Watercourse or StandingWater feature, too. Otherwise report notWithin.

Manual assertions:

  • Review the data maintenance procedures and perform spot checks to verify that connectivity between hydrographic networks across state borders and – where applicable – also across regional borders (and data sets) within Member States is established and maintained by the respective authorities, using the cross-border connectivity mechanisms provided by the NetworkConnection type.

Reference(s):

  • TG DS-HY IR requirement Section 8.7.1 (1)
  • TG DS-HY IR requirement Section 8.7.1 (2)

Test type: Automated/Manual

Messages

Identifier Message text (parameters start with '$')
notWithin XML document '$filename', $featureType '$gmlid': The geometry is not within a single SurfaceWater feature from the Physical Waters application schema.

Contextual XPath references

The namespace prefixes used as described in README.md.

Abbreviation XPath expression
WatercourseLink //schema-element(hy-n:WatercourseLink)
SurfaceWater //schema-element(hy-p:SurfaceWater)
HydroNode //schema-element(hy-n:HydroNode)
centrelineGeometry $WatercourseLink/*:centrelineGeometry
geometry $SurfaceWater/*:geometry