Skip to content

Coastal Zones 2012

Jiří Kadlec edited this page Feb 21, 2020 · 15 revisions

Coastal zones 2012

This product consists of a single status layer.

The product definition contains following checks:

Check description: Delivery file can be unzipped.

Required check, the check cannot be skipped.

Requirements: The product must be delivered in a .zip file.

Note: If the .zip file name starts with CZ_2012 (e.g. CZ_2012_DU001_3035_V1_0.zip), then the QC Tool will automatically recognize the product as Coastal Zones 2012.

Check description: Naming is in accord with specification.

Required check, the check cannot be skipped.

Requirements: The product must be in a geopackage (gpkg) with one layer or a geodatabase (gdb) with one feature class.

Naming convention

The layer name must match expression:

cz_2012_<DELIVERY_UNIT>_3035_<VERSION>
where
  • <DELIVERY_UNIT> is the code of the delivery unit, e.g. DU001;
  • <VERSION> is the delivery version, e.g. V1_0, V1_1, V2_0;
Example - Geopackage (.gpkg) delivery

+-- CZ_2012_DU001_3035_V1_0.gpkg     (Geopackage name)
    +-- CZ_2012_DU001_3035_V1_0      (Layer name)
Example - Geodatabase (.gdb) delivery

+-- CZ_2012_DU001_3035_V1_0.gdb/     (Geodatabase name)
    +-- CZ_2012_DU001_3035_V1_0/     (Feature dataset name)
        +-- CZ_2012_DU001_3035_V1_0/ (Feature class name)

Note: Layer naming is case-insensitive, both CZ_2012_DU001_3035_V1_0 and cz_2012_du001_3035_v1_0 are valid layer names.

Check description: Attribute table check.

Required check, the check cannot be skipped.

Requirements: The layer must have required attributes with expected data type.

Required attributes:
  • “id“: “string“,, 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 attributes: “shape_area“, “shape_length“

Note: Attribute naming is case-insensitive, both CODE_1_12 and code_1_12 is a valid attribute names. Extra attributes not in Required and Ignored list are not allowed.

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:

  • The delivery must contain a Metadata subdirectory with one XML metadata 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)
  • The XML metadata document must be compliant with INSPIRE metadata specifications.
  • 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.

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