Skip to content

Riparian Zones 2012 2018

Jump to bottom
Jiří Tomíček edited this page Dec 15, 2025 · 16 revisions

Riparian Zones 2012-2018 (RPZ_2018)

This product consists of a single combined layer.

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), FlatGeobuf (fgb), GeoParquet (parquet) or shapefile (shp) format. The geodatabase must contain one feature dataset with one feature class.

Naming convention:

The layer name must match regex:

^rpz_(?P<aoi_code>du[0-9]{3})[a-z]_lclu_2018_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 2018_2012 (2018 is the reference year)
  • the name must end with ‘_v’ followed by 2 numbers

The boundary source is: boundary_rpz.shp

Example of filename: rpz_du003a_lclu_2018_2012_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“

Ignored: “shape_area“, “shape_length“, “geometry_bbox.xmax“, “geometry_bbox.xmin“, “geometry_bbox.ymax“, “geometry_bbox.ymin“

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,

Set of valid codes for attribute maes_2_12:

0,
11, 12, 13, 14,
21, 22, 23,
30, 31, 32, 33, 34, 35, 36,
40, 41, 42,
50, 51, 52, 53,
60, 61, 62, 63,
70, 71, 72,
80, 81, 82, 83, 84,

Set of valid codes for attribute maes_3_12:

0,
111, 112, 121, 122, 123, 124, 131, 132, 140,
211, 212, 220, 221, 222, 231, 232, 233, 234,
300, 311, 312, 321, 322, 331, 332, 340, 350, 360,
400, 410, 421, 422,
500, 510, 520, 530,
600, 610, 621, 622, 631, 632, 633,
700, 711, 712, 721, 722, 723,
800, 811, 812, 813, 821, 822, 823, 824, 831, 832, 840,

Set of valid codes for attribute maes_4_12:

0,
1111, 1112, 1113, 1120,
1210, 1220, 1230, 1240,
1310, 1320,
1400,
2110, 2120, 2200, 2210, 2220, 2310, 2320, 2330, 2340,
3000, 3110, 3120, 3210, 3220, 3310, 3320, 3400, 3500, 3600,
4000, 4100, 4210, 4220,
5000, 5100, 5200, 5300,
6000, 6100, 6210, 6220, 6310, 6320, 6330,
7000, 7110, 7121, 7122, 7210, 7220, 7230,
8000, 8110, 8120, 8130, 8210, 8220, 8230, 8240, 8310, 8320, 8400,

Set of valid codes for attribute maes_1_18:

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

Set of valid codes for attribute maes_2_18:

0,
11, 12, 13, 14,
21, 22, 23,
30, 31, 32, 33, 34, 35, 36,
40, 41, 42,
50, 51, 52, 53,
60, 61, 62, 63,
70, 71, 72,
80, 81, 82, 83, 84,

Set of valid codes for attribute maes_3_18:

0,
111, 112, 121, 122, 123, 124, 131, 132, 140,
211, 212, 220, 221, 222, 231, 232, 233, 234,
300, 311, 312, 321, 322, 331, 332, 340, 350, 360,
400, 410, 421, 422,
500, 510, 520, 530,
600, 610, 621, 622, 631, 632, 633,
700, 711, 712, 721, 722, 723,
800, 811, 812, 813, 821, 822, 823, 824, 831, 832, 840,

Set of valid codes for attribute maes_4_18:

0,
1111, 1112, 1113, 1120, 1210, 1220, 1230, 1240, 1310, 1320, 1400,
2110, 2120, 2200, 2210, 2220, 2310, 2320, 2330, 2340,
3000, 3110, 3120, 3210, 3220, 3310, 3320, 3400, 3500, 3600,
4000, 4100, 4210, 4220,
5000, 5100, 5200, 5300,
6000, 6100, 6210, 6220, 6310, 6320, 6330,
7000, 7110, 7121, 7122, 7210, 7220, 7230,
8000, 8110, 8120, 8130, 8210, 8220, 8230, 8240, 8310, 8320, 8400,

There is an exception:

If one of the following values is present in the ua_18 column: [UA2018, UA2012, NoData], the rule of valid codes does not apply.

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.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

AOI is defined by boundary package, see Boundaries. For every delivery the AOI consists of riparian zones delimited by delivery unit. The delivery unit is an area defined by Riparian zones specification. The value of du_id attribute indicates the delivery unit the feature is covered by and thus the AOI the feature is member of.

vector.mmu

Check description: Minimum mapping unit.

Optional check, the check may be skipped.

Requirements:

  • feature satisfying general requirements:
    • feature having area >= 0.5ha;
    • feature is being completely covered by an Urban Atlas Core Region;
  • feature satisfying exceptional requirements:
    • feature touching the boundary by a line and having area >= 0.2ha;
    • urban feature having area > 0.25ha;
    • linear feature (roads, railways, rivers) having area >= 0.1ha;
    • feature participating in complex change if the total area of all the participating features is >= 0.5 ha;
    • feature with one of the following comments in the comment_18 attribute:
Area size exception (inside RZ_AoI / outside UA Urban centre)
Area size exception (at RZ_AoI / UA Urban centre boundary)

Notes:

  • Boundary is created by unioning all features except ones being completely covered by an Urban Atlas Core Region.
  • non-null value of the attribute ua_18 declares that the feature is completely covered by an Urban Atlas Core Region.
  • urban feature has value 1 in maes_1_18 or maes_1_12 attribute;
  • linear feature has one of the values [1210, 1220, 6220, 7110, 8110, 8120] in maes_4_18 or maes_4_12 attribute;
  • One feature can have multiple comments in the comment_18 attribute. If a feature has multiple comments, they should be separated by ";".

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:

  • feature satisfying general requirements:
    • feature has no neighbouring feature of the same classes recorded in attributes maes_4_12 and maes_4_18;
    • feature is completely covered by Urban Atlas Core Region.
  • feature satisfying exception requirements:
    • feature having value in the comment_12 or comment_18 attribute one of:
      • Braided river
      • Different water levels
      • Flooded area
Notes:
  • Feature is completely covered by an Urban Atlas Core Region if it has the attribute ua_18 set to non-null value.
  • One feature can have multiple comments in the comment attribute. If a feature has multiple comments, they should be separated by ;.

Clone this wiki locally