Skip to content

Natura 2000 2006

Jump to bottom
marketajindrova edited this page May 27, 2020 · 19 revisions

Natura 2000 2006

This product consists of a single status 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 Natura2000 product must be in a ESRI file geodatabase (gdb) or Geopackage (gpkg) format.

Naming convention:

The layer name must match regex:

^n2k_du[0-9]{3}[a-z]_Status2006_lclu_v[0-9]+_[0-9]{8}$

  • the name must start with 'n2k'
  • followed by a delivery unit number which consist of:
    • 'du'
    • 3 numbers [0-9]
    • A letter [a-z]
  • followed by 'Status2006'
  • followed by '_lclu'
  • followed by a version which consist of:
    • Letter 'v'
    • Followed by numbers
  • the ending must end with a date which consist of 8 numbers signifying the date of delivery (yyyymmdd)

Naming example: N2k_DU001A_Status2006_LCLU_v1_20120530.gdb with one layer named N2k_DU001A_Status2006_LCLU_v1_20120530

Boundary source: boundary_n2k.gpkg

vector.attribute

Check description: Attribute table check.

Required check, the check cannot be skipped.

Requirements:

Required attributes:

  • “id“: “integer“ (precision=9), identifier of the buffered n2k sites;
  • “uid“: “string“ (length=20), unique identifier of the feature geometry;
  • “sitecode“: “string“ (length=20), unique identifier of the n2k site;
  • “grasstype“: “string“ (length=254), predominant grassland type;
  • “code_1_06“: “integer“ (precision=9), class code of level 1 for LU/LC 2006;
  • “code_2_06“: “integer“ (precision=9), class code of level 2 for LU/LC 2006;
  • “code_3_06“: “integer“ (precision=9), class code of level 3 for LU/LC 2006;
  • “code_4_06“: “integer“ (precision=9), class code of level 4 for LU/LC 2006; * “comment_06“: “string“ (length=254), comment field for additional information for LU/LC 2006;
  • “nodata_06“: “integer“ (precision=9), unclassifiable area due to clouds, shadows, snow, haze or missing data (no satellite data available);
  • “area_ha“: “Double“, area in hectare;
  • “revision“: “integer“ (precision=9), note if a polygon has undergone a technical revision;

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:

  • 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, e.g.
+-- N2k_du001a_Status2006_lclu_v1_20060530.gdb           (Geodatabase name),
+-- Metadata/                                            (Metadata subfolder),
        +-- N2k_du001a_Status2006_lclu_v1_20060530.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.

vector.unique

Check description: Unique attribute check.

Optional check, the check may be skipped.

Requirements: The value in the column 'uid' must be unique for each input/row.

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

vector.enum

Check description: Valid codes. Below is a list of the allowed LC/LU codes for MAES1-4 level based on AD 03. Due to the foreseen nomenclature harmonisation between CZ and N2k these codes will be updated for the first LC/LU data delivery (DD-1).

Optional check, the check may be skipped.

Requirements:

Set of valid codes for attribute code_1_06:

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

Set of valid codes for attribute code_2_06:

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 attribute code_3_06:

111, 112,
121, 122, 123, 124,
131, 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,
610,
621, 623,
631, 632, 633,
711, 712,
721, 722, 723,
811, 812, 813,
821, 822, 823, 824,
831, 833,
840,

Set of valid codes for attribute code_4_06:

1110, 1120,
1210, 1220, 1230, 1240,
1310, 1340,
1400,
2110, 2120,
2210, 2220,
2310, 2320, 2330, 2340,
3110, 3120,
3210, 3220,
3310, 3320,
3400,
3500,
3600,
4100
4211, 4212,
4220,
5100,
5200,
5300,
6100,
6210, 6230,
6310, 6320, 6330,
7110, 7121, 7122,
7210, 7220, 7230,
8110, 8120, 8130,
8210, 8220, 8230, 8240,
8310, 8330,
8400,

vector.nodata

Check description: If a feature has nodata set, then all dependent attributes must have specific value.

Optional check, the check may be skipped.

Requirements: If nodata_06 = 1, then the values in the following dependent columns have to be set to 0: (code_1_06 = 0, code_2_06 = 0, code_3_06 = 0, code_4_06 = 0).

Parameters:
  • nodata_column_name: nodata_06
  • nodata_value: 1
  • dep_column_names: [code_1_06, code_2_06, code_3_06, code_4_06]
  • dep_value: 0

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.

vector.gap

Check description: There is no gap in the AOI.

Optional check, the check may be skipped.

Requirements: AOI is defined by boundary package. AOI represents the union of all Buffered Natura 2000 sites. The value of id attribute indicates the Natura 2000 site the feature is covered by. For every delivery there is a contract fixing the set of sites the delivery should supply.

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 satisfying exceptional requirements:
    • Feature with one or more exception comments in the comment_06 attribute:
Area size exception (at Natura2000 AoI boundary)
Area size exception (inside Natura2000 AoI boundary)
Splitted change
Areas related to change
Different water level
Flooded area
Braided River

Notes:

  • Linear feature (road, railway, river) has code_3_06 codes [1210, 1220, 8110, 8120];
  • Road or railway feature has code_3_06 codes [1210, 1220];
  • Urban feature has code_1_06 code 1x;
  • There may be multiple comments in the comment_06 attribute. In that case the comments must be separated by ";", e.g. Area size exception (inside Natura2000 AoI boundary); Areas related to change.

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 code_4_06;
  • feature satisfying exceptional requirements:
    • feature having one of the following comments present in the comment_06 column:
      • Braided River System;
      • Flooded area;
      • Temporal fluctuation of water level;

Clone this wiki locally
⚡