Skip to content

Coastal Zones

Jiří Kadlec edited this page Feb 12, 2020 · 26 revisions

Coastal zones

There are three product layers which can be run through the QC Tool:
  • 1: Coastal Zones 2012 status (cz_2012) … initial status layer
  • 2: Coastal Zones 2018 status (cz_2018) … final status layer
  • 3: Coastal Zones Change 2012-2018 (cz_change_2012_2018) … change layer

Vector checks

vector.unzip

Check description: Delivery file can be unzipped.

Required check, the check cannot be skipped.

Requirements: Each Coastal Zones product layer must be delivered in a separate .zip file. The QC Tool will automatically recognize the product based on zip file name - the following naming is recommended:

  • CZ_2012_<DU_ID>_3035_<VERSION>.zip for Coastal Zones 2012 status
  • CZ_2018_<DU_ID>_3035_<VERSION>.zip for Coastal Zones 2018 status
  • CZ_Change_2012_2018_<DU_ID>_3035_<VERSION>.zip for Coastal Zones Change 2012-2018

vector.naming

Check description: Naming is in accord with specification.

Required check, the check cannot be skipped.

Requirements: Each Coastal Zones product must be in a geodatabase (gdb) or GeoPackage (gpkg) format. The geodatabase must contain one feature dataset with one feature class. The GeoPackage must contain one layer.

Each product also include a Metadata directory with an INSPIRE .xml metadata file. The .xml metadata file must have the same name as the product layer, e.g.: CZ_2012_DU001_3035_V1_0.xml.

Naming convention:

*1) Coastal Zones 2012 status (cz_2012) … initial status layer

If the delivery is in Geopackage format, filename must match regex:

+-- CZ_2012_<DELIVERY_UNIT>_3035_<VERSION>.zip     (Geopackage name),      e.g.: CZ_2012_DU001_3035_V1_0.gpkg
    +-- CZ_2012_<DELIVERY_UNIT>_3035_<VERSION>.zip,           e.g.: CZ_2012_DU001_3035_V1_0

If the delivery is in Geodatabase format, filename must match regex:

+-- CZ_2012_<DELIVERY_UNIT>_3035_<VERSION>.zip     (Geodatabase name),      e.g.: CZ_2012_DU001_3035_V1_0.gdb/
    +-- CZ_2012_<DELIVERY_UNIT>_3035_<VERSION>/    (Feature dataset name),  e.g.: CZ_2012_DU001_3035_V1_0/
        +-- CZ_2012_<DELIVERY_UNIT>_3035_<VERSION>   (Feature class name),    e.g.: CZ_2012_DU001_3035_V1_0
where
  • <DELIVERY_UNIT> is the code of the delivery unit;
  • <VERSION> is the delivery version, e.g. V1_0, V1_1, V2_0;

*2) Coastal Zones 2018 status (cz_2018) … final status layer

If the delivery is in Geopackage format, filename must match regex:

+-- CZ_2012_<DELIVERY_UNIT>_3035_<VERSION>.zip     (Geopackage name),      e.g.: CZ_2018_DU001_3035_V1_0.gpkg
    +-- CZ_2012_<DELIVERY_UNIT>_3035_<VERSION>.zip,           e.g.: CZ_2018_DU001_3035_V1_0

If the delivery is in Geodatabase format, filename must match regex:

+-- CZ_2018_<DELIVERY_UNIT>_3035_<VERSION>.zip     (Geodatabase name),      e.g.: CZ_2018_DU001_3035_V1_0.gdb/
    +-- CZ_2018_<DELIVERY_UNIT>_3035_<VERSION>/    (Feature dataset name),  e.g.: CZ_2018_DU001_3035_V1_0/
        +-- CZ_2018_<DELIVERY_UNIT>_3035_<VERSION>   (Feature class name),    e.g.: CZ_2018_DU001_3035_V1_0
where
  • <DELIVERY_UNIT> is the code of the delivery unit;
  • <VERSION> is the delivery version, e.g. V1_0, V1_1, V2_0;

*3) Coastal Zones Change 2012-2018 (cz_change_2012_2018) … change layer

If the delivery is in Geopackage format, filename must match regex:

+-- CZ_Change_2012_2018_<DELIVERY_UNIT>_3035_<VERSION>.zip     (Geopackage name),      e.g.: CZ_Change_2012_2018_DU001_3035_V1_0.gpkg
    +-- CZ_Change_2012_2018_<DELIVERY_UNIT>_3035_<VERSION>.zip,           e.g.: CZ_Change_2012_2018_DU001_3035_V1_0

If the delivery is in Geodatabase format, filename must match regex:

+-- CZ_Change_2012_2018_<DELIVERY_UNIT>_3035_<VERSION>.zip     (Geodatabase name),      e.g.: CZ_Change_2012_2018_DU001_3035_V1_0.gdb/
    +-- CZ_Change_2012_2018_<DELIVERY_UNIT>_3035_<VERSION>/    (Feature dataset name),  e.g.: CZ_Change_2012_2018_DU001_3035_V1_0/
        +-- CZ_Change_2012_2018_<DELIVERY_UNIT>_3035_<VERSION>   (Feature class name),    e.g.: CZ_Change_2012_2018_DU001_3035_V1_0
where
  • <DELIVERY_UNIT> is the code of the delivery unit;
  • <VERSION> is the delivery version, e.g. V1_0, V1_1, V2_0;

vector.attribute

Check description: Attribute table check.

Required check, the check cannot be skipped.

Requirements:

1. Coastal Zones 2012 status (CZ_2012)... initial status layer

Required attributes:
  • “id“: “string“, (length=50), unique feature identifier
  • “du“: “string“, coastal zones delivery unit ID, should match the “du“ of AOI in the boundary package
  • “code_1_12“: “integer“, LCLU class code level 1
  • “code_2_12“: “integer“, LCLU class code level 2
  • “code_3_12“: “integer“, LCLU class code level 3
  • “code_4_12“: “integer“, LCLU class code level 4
  • “comment_12“: “string“, MMU area size exception comment
  • “nodata_12“: “integer“, indicator that polygon was not mapped in 2012 (0 or 1)
  • “area_ha“: “real“, area of polygon in hectares

Ignored: “shape_area“, “shape_length“

2. Coastal Zones 2018 status (CZ_2018)... final status layer

Required attributes:
  • “id“: “string“, (length=50), unique feature identifier
  • “du“: “string“, coastal zones delivery unit ID, should match the “du“ of AOI in the boundary package
  • “code_1_18“: “integer“, LCLU class code level 1
  • “code_2_18“: “integer“, LCLU class code level 2
  • “code_3_18“: “integer“, LCLU class code level 3
  • “code_4_18“: “integer“, LCLU class code level 4
  • “comment_18“: “string“, MMU area size exception comment
  • “nodata_18“: “integer“, indicator that polygon was not mapped in 2012 (0 or 1)
  • “area_ha“: “real“, area of polygon in hectares

Ignored: “shape_area“, “shape_length“

3. Coastal Zones Change 2012-2018 (CZ_Change_2012_2018)... change layer

Required attributes:
  • “id“: “string“, (length=50), unique feature identifier
  • “du“: “string“, coastal zones delivery unit ID, should match the “du“ of AOI in the boundary package
  • “code_1_12“: “integer“, LCLU class code level 1, 2012
  • “code_2_12“: “integer“, LCLU class code level 2, 2012
  • “code_3_12“: “integer“, LCLU class code level 3, 2012
  • “code_4_12“: “integer“, LCLU class code level 4, 2012
  • “code_1_18“: “integer“, LCLU class code level 1, 2018
  • “code_2_18“: “integer“, LCLU class code level 2, 2018
  • “code_3_18“: “integer“, LCLU class code level 3, 2018
  • “code_4_18“: “integer“, LCLU class code level 4, 2018
  • “nodata_12“: “integer“, indicator that polygon was not mapped in 2012 (0 or 1)
  • “nodata_18“: “integer“, indicator that polygon was not mapped in 2018 (0 or 1)
  • “comment“: “string“, area size exception comment
  • “changecode“: “string“, "CODE4_12"_"CODE4_18" e.g. "2110_1111"
  • “area_ha“: “real“, area of polygon in hectares

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.
  • The INSPIRE compliance of the metadata is checked with the validator at http://inspire.ec.europa.eu/validator/ using Metadata (TG version 2.0) test suite.
  • Each delivery must contain a 'Metadata' subdirectory with one XML document named <layer_name>.xml where layer_name is the name of the geodatabase or geopackage, e.g.
+-- CZ_2018_DU001_3035_V1_0.gpkg          (Geopackage name),
+-- Metadata/                             (Metadata subfolder),
        +-- CZ_2018_DU001_3035_V1_0.xml   (INSPIRE 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 row in the attribute table.

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

vector.enum

Check description: Valid codes.

Optional check, the check may be skipped.

Set of valid codes for attributes code_1_12 and code_1_18:

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

Set of valid codes for attributes code_2_12 and code_2_18:

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

Set of valid codes for attributes code_3_12 and code_3_18:

0,
111, 112,
121, 122, 123, 124,
131, 132, 133, 134,
140,
211, 212,
221, 222,
231, 232, 233, 234,
311, 312,
321, 322,
331, 332,
340,
350,
360,
410,
421, 422,
510,
520,
530,
611, 612,
621, 622, 623,
631, 632, 633,
711, 712,
721, 722, 723,
811, 812, 813,
821, 822, 823, 824,
831, 832, 833,
841, 842

Set of valid codes for attributes code_4_12 and code_4_18:

0,
1111, 1112, 1113, 1121, 1122,
1210, 1220,
1231, 1232, 1233, 1234, 1235, 1236, 1237,
1240,
1310, 1320, 1330, 1340,
1400,
2110, 2120,
2210, 2220,
2310, 2320, 2330, 2340,
3110, 3120,
3210, 3220,
3310, 3320,
3400,
3500,
3600,
4100,
4210, 4220,
5100,
5200,
5300,
6110, 6120,
6211, 6212,
6220, 6230,
6311, 6312,
6320, 6330,
7110, 7121, 7122,
7210, 7220, 7230,
8110, 8120, 8130,
8210, 8220, 8230, 8240,
8310, 8320, 8330,
8410, 8420

vector.change

Check description: Change layer has distinct codes in initial and final year.

Optional check, the check may be skipped.

Requirements: The value in the column 'code_4_12' must be different from the value of column 'code_4_18'. This check is only applicable for Coastal Zones Change 2012-2018 (cz_change_2012_2018) product.

Parameters:
  • “initial_code_column_name“: “code_4_12“;
  • “final_code_column_name“: “code_4_18“;

vector.singlepart

Check description: Singlepart polygon check.

Optional check, the check may be skipped.

Requirements: All layers of all vector products, feature 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_ha' coincide.

Optional check, the check may be skipped.

Requirements:

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

vector.gap

Check description: There is no gap in the AOI.

Optional check, the check may be skipped.

Requirements: AOI is defined by the AOI file aoi_cz_2018.gpkg in the boundary package. All areas in the AOI with du_id equal to du_id in the layer file name must be covered by polygons.

Remarks: vector.gap check is not applicable for the change product layer (cz_change_2012_2018).


vector.mmu

Check description: Minimum mapping unit.

Optional check, the check may be skipped.

Requirements:

1) Coastal Zones 2012 status (cz_2012) & 2) Coastal Zones 2018 status (cz_2018)

Feature satisfying general requirements:

  • Feature having area >= 0.5 ha;

Feature satisfying exceptional requirements:

  • Feature of class 7230 (Intertidal flats) and 8420 (Coastal waters) having area >= 0.25 ha;
  • Feature touching the boundary by a line and having area >= 0.1 ha;
  • Linear feature (road, railway, river) touching another linear feature (road, railway, river) by line and having area >= 0.1 ha;
  • Urban feature (except linear features) touching touching road or railway feature and having area >= 0.25 ha;

Notes:

  • Linear feature (road, railway, river) has code 1210 or 1220 or 8110 or 8120
  • Road or railway feature has code 1210 or 1220.
  • Urban feature has code 1.x (1111, 1112, 1113, 1121, 1122, 1231, 1232, 1233, 1234, 1235, 1236, 1237, 1240, 1210, 1320, 1330, 1340, 1400)

2) Coastal Zones Change 2012-2018 (cz_change_2012_2018)

Feature satisfying general requirements:

  • Feature having area >= 0.5 ha;

Feature satisfying exceptional requirements:

  • Feature of class 7230 (Intertidal flats) and 8420 (Coastal waters) having area >= 0.25 ha;
  • Feature having area >= 0.05 ha and touching the boundary by a line;
  • Feature having area >= 0.05 ha and participating in complex change if the total area of all the participating features is >= 0.5 ha;

vector.mmw

Check description: Minimum mapping width.

Optional check, the check may be skipped.

Requirements:

  • if negative buffer applied on a geometry generates more than one geometry, such corresponding feature is reported as warning; the buffer size is 10 / 2 m;
  • only linear features are checked;
  • linear features have code 1210 or 1220 or 8110 or 8120;

vector.neighbour

Check description: No neighbouring polygons with the same code.

Optional check, the check may be skipped.

Requirements:

1) Coastal Zones 2012 status (cz_2012) & 2) Coastal Zones 2018 status (cz_2018)

  • All neighbouring features must have distinct class code.

2) Coastal Zones Change 2012-2018 (cz_change_2012_2018)

  • All neighbouring features must have distinct combination of (code_4_12, code_4_18).

vector.overlap

Check description: Minimum mapping unit.

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

Clone this wiki locally