-
Notifications
You must be signed in to change notification settings - Fork 4
Riparian Zones 2012
Riparian Zones 2012 (RPZ_2012)
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 2012 product contains a single status layer.
Check description: Delivery file can be unzipped.
Required check, the check cannot be skipped.
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]_lclu2012_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 ‘2012’ (2012 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_du003_lclu2012_v01.gdb
Check description: Attribute table check.
Required check, the check cannot be skipped.
Requirements:
- Required attributes:
-
“id“: “integer““du_id“: “string““maes_1“: “integer““maes_2“: “integer““maes_3“: “integer““maes_4“: “integer““ua“: “string““area_ha“: “real““nodata“: “integer““comment“: “string“
- Attributes to be ignored:
-
“shape_area““shape_length“
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);
Check description: Data can be imported into database
Required check, the check cannot be skipped.
Check description: Metadata.
Optional check, the check may be skipped.
Requirements:
All vector deliveries must contain an INSPIRE compliant XML metadata document.
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“];
-
Check description: Valid codes.
Optional check, the check may be skipped.
Requirements:
Set of valid codes for attribute maes_1:
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
Set of valid codes for attribute maes_2:
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:
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:
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
There is an exception:
If a non-NULL value is present in the ua column, the rule of valid codes does not apply.
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. ;
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. ;
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)
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
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:
- If one of the following values is present in the
maes_4column [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. - If one of the following values is present in the
maes_4column [1210, 1220, 6220, 9110, 9120], the minimum mapping unit is 0.1 ha. This is relevant for the linear features. - If one of the following comments is present in the
commentcolumn: [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. - If a non-null value is present in the
uacolumn, the rule of minimum mapping unit does not apply.
-
area_column_name:area_ha -
area_ha: 0.5 -
code_column_name:maes_4 -
urban_feature_codes: [1111, 1112, 1113, 1120, 1210, 1220, 1230, 1240, 1310, 1320, 1400] -
urban_area_ha: 0.25 -
linear_feature_codes: [1210, 1220, 6220, 9110, 9120] -
linear_area_ha: 0.1 -
marginal_area_ha: 0.2 -
comment_column_names:[comment] -
area_ha: 0.5 -
comment: [Area size exception (inside RZ_AoI / outside UA Core Region), Area size exception (at RZ_AoI / UA Core Region boundary)]
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
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). ;
Check description: No neighbouring polygons with the same code.
Optional check, the check may be skipped.
Requirements:
Two polygons which have the same value in column maes_4 cannot be neighbouring.
Exceptions- such polygons can be neighbouring if:
- There is a non-NULL value in column
ua - One of the following comments is present in the
commentcolumn: [“Braided river”, “Different water levels”, “Flooded area”]
-
code_column_names: [maes_4] -
initial_ua_column_name: null -
final_ua_column_name:ua -
comment_18: [“Braided river”, “Different water levels”, “Flooded area”]
-
How To Use QC Tool
-
Checks
-
Products
-
- HRL Imperviousness
- HRL Tree Cover and Forest
- HRL Grassland
- HRL Water and Wetness
-
HRL Small Woody Features
- HRL Small Woody Features 2015: Raster 100m
- HRL Small Woody Features 2015: Vector Raster 5m
- HRL Small Woody Features 2018: Raster 100m
- HRL Small Woody Features change 2018: Raster 100m
- HRL Small Woody Features change 2018-2021: Raster 100m
- HRL Small Woody Features 2018: Vector Raster 5m
- HRL Small Woody Features 2018: Revised Woody Vegetation Layer 5m
- HRL CLC Backbone