Skip to content

Riparian Zones

Jump to bottom
marketajindrova edited this page Feb 13, 2020 · 12 revisions

Riparian Zones (RZ)

Riparian Zones represent transitional areas occurring between land and freshwater ecosystems, characterised by distinctive hydrology, soil and biotic conditions and strongly influenced by the stream water.

Riparian Zones Land Cover/ Land Use layer (rpz layer containing status data for both 2012 and 2018) can be checked by using the QC Tool.

Vector checks

vector.unzip

Check description: Delivery file can be unzipped.

Required check, the check cannot be skipped.

vector.naming

Check description: Naming is in accord with specification.

Required check, the check cannot be skipped.

Requirements: Each Riparian Zone product must be in a geodatabase (gdb), GeoPackage (gpkg) or shapefile (shp) format. The geodatabase must contain one feature dataset with one feature class.

Naming convention:

The filename must match regex:

^rpz_(?P<aoi_code>du[0-9]{3})[a-z]_lclu(?P<reference_year>2012)_v[0-9]{2}$

  • the name must start with ‘rpz_’
  • followed by an AOI code which consists of: Letters ‘du’ followed by 3 numbers
  • followed by ‘_lclu’
  • followed by reference year
  • the name must end with ‘_v’ followed by 2 numbers

The boundary source is: boundary_rpz.shp

Example of filename: rpz_du003_lclu2012_v01.gdb

vector.attribute

Check description: Attribute table check.

Required check, the check cannot be skipped.

Requirements:

Required attributes:
  • “id“: “integer“
  • “du_id“: “string“
  • “maes_1_12“: “integer“
  • “maes_2_12“: “integer“
  • “maes_3_12“: “integer“
  • “maes_4_12“: “integer“
  • “maes_1_18“: “integer“
  • “maes_2_18“: “integer“
  • “maes_3_18“: “integer“
  • “maes_4_18“: “integer“
  • “changecode“: “string“
  • “ua_12“: “string“
  • “ua_18“: “string“
  • “area_ha“: “real“
  • “nodata_12“: “integer“
  • “nodata_18“: “integer“
  • “comment_12“: “string“
  • “comment_18“: “string“
Attributes to be ignored:
  • “shape_area“
  • “shape_length“

vector.epsg

Check description: CRS (Projection) check.

Required check, the check cannot be skipped.

Requirements:

The vector must be assigned spatial reference system EPSG: 3035 (ETRS89 ETRS-LAEA equal-area projection);

vector.import2pg

Check description: Data can be imported into database

Required check, the check cannot be skipped.

vector.inspire

Check description: Metadata.

Optional check, the check may be skipped.

Requirements:

All vector deliveries must contain an INSPIRE compliant XML metadata document.

vector.unique

Check description: Unique attribute check.

Optional check, the check may be skipped.

Requirements: The value in the column 'id' must be unique for each input/row.

Parameters:
  • "unique_keys": [“id“];

vector.enum

Check description: Valid codes.

Optional check, the check may be skipped.

Requirements:

Set of valid codes for attribute nodata_12:

0, 1

Set of valid codes for attribute nodata_18:

0, 1

Set of valid codes for attribute maes_1_12:

0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10

Set of valid codes for attribute maes_2_12:

0,
11, 12, 13, 14,
21, 22, 23,
31, 32, 33, 34, 35,
41, 42,
51, 52,
61, 62, 63,
71, 72,
81, 82,
91, 92,
100

Set of valid codes for attribute maes_3_12:

0,
111, 112, 121, 122, 123, 124, 131, 132, 140,
211, 212, 221, 222, 231, 232, 233, 234,
311, 312, 321, 322, 331, 332, 341, 342, 350,
410, 421, 422,
511, 512, 520,
610, 621, 622, 631, 632, 633,
710, 721, 722,
811, 812, 813, 821, 822,
911, 912, 913, 921, 922, 923, 924,
1000

Set of valid codes for attribute maes_4_12:

0,
1111, 1112, 1113,
1120, 1210, 1220, 1230, 1240,
1310, 1320,
1400,
2110, 2120, 2210, 2220, 2310, 2320, 2330, 2340,
3110, 3120, 3210, 3220, 3310, 3320, 3410, 3420, 3500,
4100, 4210, 4220,
5110, 5120, 5200,
6100, 6210, 6220, 6310, 6320, 6330,
7100, 7210, 7220,
8110, 8120, 8130, 8210, 8220,
9110, 9120, 9130, 9210, 9220, 9230, 9240,
10000

Set of valid codes for attribute maes_1_18:

0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10

Set of valid codes for attribute maes_2_18:

0,
11, 12, 13, 14,
21, 22, 23,
31, 32, 33, 34, 35,
41, 42,
51, 52,
61, 62, 63,
71, 72,
81, 82,
91, 92,
100

Set of valid codes for attribute maes_3_18:

0,
111, 112, 121, 122, 123, 124, 131, 132, 140,
211, 212, 221, 222, 231, 232, 233, 234,
311, 312, 321, 322, 331, 332, 341, 342, 350,
410, 421, 422,
511, 512, 520,
610, 621, 622, 631, 632, 633,
710, 721, 722,
811, 812, 813, 821, 822,
911, 912, 913, 921, 922, 923, 924,
1000

Set of valid codes for attribute maes_4_18:

0,
1111, 1112, 1113,
1120, 1210, 1220, 1230, 1240,
1310, 1320,
1400,
2110, 2120, 2210, 2220, 2310, 2320, 2330, 2340,
3110, 3120, 3210, 3220, 3310, 3320, 3410, 3420, 3500,
4100, 4210, 4220,
5110, 5120, 5200,
6100, 6210, 6220, 6310, 6320, 6330,
7100, 7210, 7220,
8110, 8120, 8130, 8210, 8220,
9110, 9120, 9130, 9210, 9220, 9230, 9240,
10000

vector.nodata (2012)

Check description: The consistency of NoData value across dependent columns within the attributes.

Optional check, the check may be skipped.

Requirements: If nodata_value = 1, then the values in the following dependent columns have to = 0 (maes_1_12 = 0, maes_2_12 = 0, maes_3_12 = 0, maes_4_12 = 0).

  • layers: „rpz“
  • nodata_column_name: „nodata_2012“
  • nodata_value: 1
  • dep_column_name: „maes_1_12“, „maes_2_12“, „maes_3_12“, „maes_4_12“
  • dep_value: 0

vector.nodata (2018)

Check description: The consistency of NoData value across dependent columns within the attributes.

Optional check, the check may be skipped.

Requirements: If nodata_value = 1, then the values in the following dependent columns have to = 0 (maes_1_18 = 0, maes_2_18 = 0, maes_3_18 = 0, maes_4_18 = 0).

  • layers: „rpz“
  • nodata_column_name: „nodata_2018“
  • nodata_value: 1
  • dep_column_name: „maes_1_18“, „maes_2_18“, „maes_3_18“, „maes_4_18“
  • dep_value: 0

vector.change

Check description: Features in column maes_4_12 (initial code column name) and maes_4_18 (final code column name) have different codes.

Optional check, the check may be skipped.

vector.singlepart

Check description: Singlepart polygon check.

Optional check, the check may be skipped.

Requirements: All features satisfying general requirements:

Feature is a single-part polygon; a single-part polygon may contain holes but may not contain multiple exterior rings. ;

vector.geometry

Check description: Geometries are valid.

Optional check, the check may be skipped.

Requirements:

Feature satisfying general requirements:

  • Feature with valid geometries as defined by Open Geospatial Consortium’s OpenGIS specification.
  • 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.

NOTE: Ring self-intersections while considered valid by ArcGIS are also reported as errors by the QC Tool. ;

vector.area

Check description: Calculated area and value in the column 'area' coincide.

Optional check, the check may be skipped.

Requirements:

  • unit: 10000, (value is in ha)
  • tolerance: 0.001 (calculated area and value in the column 'area' do not differ by more than 0.001 ha)

vector.gap

Check description: There is no gap in the AOI within each boundary unit.

Optional check, the check may be skipped.

Requirements: Each catchment area is described by a unique du_id value. Within each catchment area there should be no gap.

  • boundary_unit_column_name: du_id

vector.mmu

Check description: Minimum mapping unit.

Optional check, the check may be skipped.

Requirements: The minimum mapping unit is 0.5 ha.

There are several exceptions:

  1. If one of the following values is present in the maes_4_18 column [1111, 1112, 1113, 1120, 1210, 1220, 1230, 1240, 1310, 1320, 1400], the minimum mapping unit is 0.25 ha. This is relevant for the urban areas.
  2. If one of the following values is present in the maes_4_18 column [1210, 1220, 6220, 9110, 9120], the minimum mapping unit is 0.1 ha. This is relevant for the linear features.
  3. If one of the following comments is present in the comments column: [Area size exception (inside RZ_AoI / outside UA Core Region), Area size exception (at RZ_AoI / UA Core Region boundary)], the rule of minimum mapping unit does not apply.
  • area_column_name: area_ha
  • area_ha: 0.5
  • code_column_name: maes_4_18
  • urban_feature_codes: [1111, 1112, 1113, 1120, 1210, 1220, 1230, 1240, 1310, 1320, 1400]
  • linear_feature_codes: [1210, 1220, 6220, 9110, 9120]
  • exception_comments: [Area size exception (inside RZ_AoI / outside UA Core Region), Area size exception (at RZ_AoI / UA Core Region boundary)]

vector.mmw

Check description: Minimum mapping width.

Optional check, the check may be skipped.

Requirements:

Feature satisfying general requirements:

  • Feature with minimum width greater than 10 metres

vector.overlap

Check description: No overlapping polygons.

Optional check, the check may be skipped.

Requirements:

There must be no feature having any part of its interior common with any other feature (aka overlaps). ;

vector.neighbour

Check description: No neighbouring polygons with the same code.

Optional check, the check may be skipped.

Requirements:

Two polygons which have the same values in column maes_4_12 and also in column maes_4_18 cannot be neighbouring.

Exceptions- such polygons can be neighbouring if:

  1. There the value in initial_ua_column_name = ua_12 and the value in final_ua_column_name = ua_18
  2. One of the following comments is present in the comments column: [“Braided river”, “Different water levels”, “Flooded area”]
  • code_column_names: [maes_4_12, maes_4_18]
  • initial_ua_column_name: ua_12
  • final_ua_column_name: ua_18
  • exception_comments: [“Braided river”, “Different water levels”, “Flooded area”]

Clone this wiki locally