Skip to content

CORINE Land Cover 2018 2024

Jump to bottom
Jiří Kadlec edited this page Dec 15, 2025 · 28 revisions

CORINE Land Cover 2018-2024

This product consists of four layers, i.e. a geopackage with two status layers (initial and reference) and two change layers (change and solar). Accepted data formats are: Geopackage (.gpkg) or file geodatabase (.gdb). Examples are provided below:

For each layer it is also required to provide a metadata xml file, please see the CLC2024 Metadata guide for info how to generate the metadata.

vector.unzip

Check description: Delivery file can be unzipped.

Required check, the check cannot be skipped.

Requirements: The delivery must be in a .zip file (e.g CLC2024_MT.zip) where the ZIP files contains one .GPKG/.GDB data file and the four required .xml metadata files.

vector.naming

Check description: Naming is in accord with specification.

Required check, the check cannot be skipped.

Requirements: Each CLC product must be in a GeoPackage (gpkg) or geodatabase (gdb) format. Geopackage must have four layers inside the GPKG file.

When using GDB, the geodatabase must have one feature dataset inside the geodatabase and four layers inside the feature dataset. The name of the feature dataset is the same as the name of the geodatabase (e.g geodatabase name CLC2024_MT.gdb, feature dataset name CLC2024_MT).

Naming convention:

The filename must match regex:

^clc2024_(?P<aoi_code>.+).gpkg$ or ^clc2024_(?P<aoi_code>.+).gdb$

  • the file name must start with ‘clc2024’
  • followed by an AOI code
  • the layer names must match regex:
    • ^clc24_(?P<aoi_code>.+)$ (reference layer, e.g. CLC24_MT)
    • ^clc18_(?P<aoi_code>.+)$ (initial layer, e.g. CLC24_MT)
    • ^cha1824_(?P<aoi_code>.+)$ (change layer, e.g. CHA1824_MT)
    • ^sol1824_(?P<aoi_code>.+)$ (solar layer, e.g. SOL1824_MT)
    • The AOI codes allowed are:
al
at
ba
be
bg
ch
cy
cz
de
dk
dk_fo
ee
es
es-cn
fi
fr
fr_glp
fr_guf
fr_mtq
fr_myt
fr_reu
gr
hr
hu
ie
is
it
li
lt
lu
lv
md
me
mk
mt
nl
no
pl
pt
pt_ram
pt_raa_ceg
pt_raa_weg
ro
rs
se
si
sk
tr
uk_gb
uk_ni
uk_gg
uk_je
xk

Naming example: clc2024_mt.gpkg

For each aoi code, QC tool will automatically select the AOI from the boundary package using Boundary source: clc2024/boundary_clc_{aoi_code}.gpkg

vector.attribute

Check description: Attribute table check.

Required check, the check cannot be skipped.

Requirements:

Required attributes for the Reference layer:
  • id: string (length=18);
  • code_24: string (length=3);
  • remark: string (length=20);
  • area_ha: real;
  • shape_area: real;
  • shape_length: real;
Required attributes for the Initial layer:
  • id: string (length=18);
  • code_18: string (length=3);
  • remark: string (length=20);
  • area_ha: real;
  • shape_area: real;
  • shape_length: real;
Required attributes for the Change layer:
  • id: string (length=18);
  • code_18: string (length=3);
  • code_24: string (length=3);
  • remark: string (length=20);
  • change: string (length=7);
  • chtype: string (length=1);
  • area_ha: real;
  • shape_area: real;
  • shape_length: real;
Required attributes for the Solar layer:
  • id: string (length=18);
  • code_18s: string (length=4);
  • code_24s: string (length=4);
  • remark: string (length=20);
  • change: string (length=9);
  • chtype: string (length=1);
  • area_ha: real;
  • shape_area: real;
  • shape_length: real;

Note: fid and objectid attributes are ignored by the QC tool.

vector.epsg

Check description: CRS (Projection) check.

Required check, the check cannot be skipped.

Requirements:

  • The vector must be assigned spatial reference system based on the location of the AOI:
al, 2462
at, 31287
ba, 8678
be, 3812
bg, 32634
ch, 2056
cy, 32636
cz, 5514
de, 25832
dk, 25832
dk_fo, 5316
ee, 3301
es, 25830
es_cn, 4083
fi, 3067
fr, 2154
fr_glp, 4559
fr_guf, 2972
fr_mtq, 4559
fr_myt, 4471
fr_reu, 2975
gr, 2100
hr, 3765
hu, 23700
ie, 2157
is, 8088
it, 32633
li, 31287
lt, 3346
lu, 2169
lv, 3059
me, 25834
mk, 6204
mt, 32633
nl, 28992
no, 25833
pl, 2180
pt, 3763
pt_ram, 5016
pt_raa_ceg, 5015
pt_raa_weg, 5014
ro, 3844
rs, 25834
se, 3006
si, 3912
sk, 5514
tr, 4326
uk_gb, 27700
uk_ni, 29902
uk_gg, 3108
uk_je, 3109
xk, 9141

vector.inspire

Check description: Metadata.

Optional check, the check may be skipped.

Requirements:

  • The delivery must contain four XML metadata documents named <layer_name>.xml where layer_name is the name of the layer, e.g.
+-- clc2024_mt.gpkg                                    (Geopackage name),
+-- clc24_mt.xml                                       (INSPIRE XML metadata document for the clc24_mt reference layer)
+-- clc18_mt.xml                                       (INSPIRE XML metadata document for the clc18_mt initial layer)
+-- cha1824_mt.xml                                     (INSPIRE XML metadata document for the cha1824_mt change layer)
+-- sol1824_mt.xml                                     (INSPIRE XML metadata document for the sol1824_mt solar layer)
  • The XML metadata document must be compliant with INSPIRE metadata specifications.
  • The INSPIRE compliance of the metadata is checked with a built-in installation of the validator at http://inspire.ec.europa.eu/validator/ using Metadata (TG version 2.0) test suite.

vector.import2pg

Check description: Data can be imported into database

Required check, the check cannot be skipped.

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 input/row.

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

vector.enum

Check description: Valid codes.

Optional check, the check may be skipped.

Requirements:

Set of valid codes for initial layer (attribute code_18) and reference layer (attribute code_24) and change layer (attributes code_18 and code_24):

111,
112,
121,
122,
123,
124,
131,
132,
133,
141,
142,
211,
212,
213,
221,
222,
223,
231,
241,
242,
243,
244,
311,
312,
313,
321,
322,
323,
324,
331,
332,
333,
334,
335,
411,
412,
421,
422,
423,
511,
512,
521,
522,
523,
999

Set of valid codes for attribute code_18s of solar layer

111,
112,
122,
123,
124,
131,
132,
133,
141,
142,
211,
212,
213,
221,
222,
223,
231,
241,
242,
243,
244,
311,
312,
313,
321,
322,
323,
324,
331,
332,
333,
334,
335,
411,
412,
421,
422,
423,
511,
512,
521,
522,
523,
999,
1211,
1212

Set of valid codes for attribute code_24s of solar layer

1212

Set of valid codes for attribute chtype of solar and change layers

R,
T

vector.change

Check description: Features in Initial and Reference layers have different codes.

Optional check, the check may be skipped.

Requirements: This check is applicable to the change and solar layers. The code in reference year must be different from the code in the initial year.

Requirement for change layer: The value of the change column must be in format <code_18>-<code_24>.

Requirement for solar layer: The value of the change column must be in format <code_18s>-<code_24s>.

Exception: CLC products take into account technical change. The feature is a member of technical change if it has chtype attribute set to T. Such features are then reported as an exception instead of an error.

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' coincide.

Optional check, the check may be skipped.

Requirements:

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

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. For every delivery the AOI represents particular country (including sea buffer zone). The countrycode in the geodatabase name indicates the AOI all features in the layer are members of. For example in the geopackage 'clc2024_mt' mt is the countrycode and the delivery is checked against the AOI file vector/clc2024/boundary_clc_mt from the boundary package.

vector.mmu

Check description: Minimum mapping unit.

Optional check, the check may be skipped.

Requirements:

  1. Initial and Reference layers:
Feature satisfying general requirements:
  • Feature having area >= 25 ha;
Feature satisfying exceptional requirements:
  • Feature touching the boundary by a line;
  1. Change layer and Solar layer:
Feature satisfying general requirements:
  • Feature having area >= 5 ha;
Feature satisfying exceptional requirements:
  • Feature touching the boundary by a line
  • Feature participating in a complex change if the total area of all the participating features is >= 5 ha;

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 100 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:

  1. Initial and Reference layer:
  • Feature satisfying general requirements:
    • All neighbouring features have class distinct from the feature in question
  • Feature satisfying exception requirements:
    • The feature is a member of technical change
    • AND there is one neighbouring feature at least having the same class as the feature in question
  • Feature satisfying error requirements:
    • The feature is not a member of technical change
    • AND there is one neighbouring feature at least having the same class as the feature in question while not being member of technical change

The feature is member of technical change if it has chtype attribute set to T.

Contrary to most of checks, a feature may satisfy more requirement levels, in this case it may do both exception and error requirements.

  1. Change and Solar layers:

The requirement level rules are similar to those of reference layer, the only difference is that by the class is actually meant a tuple of initial year class and reference year class (code_18, code_24) for change layer and (code_18s, code_24s) for solar layer.

Clone this wiki locally
⚡