Skip to content

Coastal Zones

Jump to bottom
Jiří Kadlec edited this page Feb 3, 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“];

Clone this wiki locally