Vector checks

Vector checks

QC tool does not take tolerance into account during spatial relationship operations such as overlaps, gaps, touches. The aim is to make the deliveries portable across the tools without any hassle.

vector.naming: Naming is in accord with specification

The check can not be skipped. The result values of the check are: ok, aborted.

Currently there are specialized naming check modules for various vector products: * vector.naming_clc * vector.naming_n2k * vector.naming_rpz * vector.naming_ua_gdb * vector.naming_ua_shp

The delivery must contain all prescribed layers, see dedicated page Symbolic layer names.

If the delivery is supplied in the geodatabase format, there should be one only geodatabase in the zip file. The directory of the geodatabase may be located anywhere in the directory hierarchy, eg. all examples are valid: clc2012_mt.gdb, mt/clc2012_mt.gdb, 2012/mt/clc2012_nt.gdb.

If the delivery is supplied in the shapefile format, there may be multiple shapefiles in the zip file. Each shapefile corresponds to one layer. The shapefiles may be located anywhere in the directory hierarchy, eg. all examples are valid: dk001l2_kobenhavn_ua2012.shp, dk001l2_kobenhavn/dk001l2_kobenhavn_ua2012.shp, shapefiles/dk001l2_kobenhavn/dk001l2_kobenhavn_ua2012.shp.

See also dedicated page Naming conventions.

vector.format: File format is correct

The check can not be skipped. The result values of the check are: ok, aborted.

The allowed format for products:

• CORINE Land Cover: geodatabase;
• Urban Atlas: geodatabase or shapefiles;
• Riparian zones: shapefiles;
• Natura 2000: shapefiles;

vector.attribute. Attribute table contains prescribed attributes

See dedicated page Attributes.

vector.epsg: CRS of layer expressed as EPSG code match reference EPSG code

See dedicated page CRS.

vector.unique: Unique attribute check

See dedicated page Unique attributes.

vector.enum: Valid codes

See dedicated page Valid codes.

vector.non_probable_changes: Non-probable changes

See dedicated page Non-probable changes.

vector.singlepart: No multipart polygons

All layers in all vector products except Urban Atlas boundary layer:

• feature satisfying general requirements:
  • feature is a single-part polygon; a single-part polygon may contain holes, but may not contain multiple exterior rings.

Reference:

• OGC Simple feature access specification, http://www.opengeospatial.org/standards/sfa,
  • chapter 6.1.11 Polygon,
  • chapter 6.1.13 MultiSurface.

vector.geometry: Geometries are valid

• feature satisfying general requirements:
  • Feature with valid geometries as defined by Open Geospatial Consortium's OpenGIS specification. See https://postgis.net/docs/using_postgis_dbmanagement.html#OGC_Validity
• For each feature with invalid geometry, the invalid geometry reason (i.e. self-intersection) and invalid geometry location can be found in the attachment error table.

vector.gap: Completeness

See dedicated page Vector completeness.

vector.mmu: Minimum mapping unit

See dedicated page Vector MMU.

vector.mmw: Minimum mapping width

See dedicated page Vector MMW.

vector.overlap: No overlapping polygons

See dedicated page Overlapping polygons.

vector.neighbour: No neighbouring polygons with the same code

See dedicated page Neighbouring polygons.

vector.change: Features have distinct code in initial and final year

See dedicated page Change codes.

vector.inspire: Metadata

See dedicated page Vector metadata.