CLC 2024 Frequently Asked Questions

Frequently asked questions - CLC2024

How to prepare the metadata files

The QC Tool requires INSPIRE xml metadata files (one xml per layer) and a working unit PDF file to be present in the ZIP. See CLC 2024 Metadata Guide for more info.

QC Tool shows _delivery does not contain the expected metadata file (for the four layers)

In the ZIP file, the .gpkg and the .xml files should be directly under the ZIP (no subfolder). See example ZIP for Malta CLC2024_MT.zip

How to deal with the solar layer when you are not mapping solar panels

The QC Tool requires that all four layers (clc18_xx, clc24_xx, cha1824_xx, sol1824_xx) are included in the GeoPackage. If your country is not mapping solar panels, please still include an empty solar layer (with the required attributes) in the GPKG or GDB.

vector.change reports error features, although code_18 is different than code_24

In the vector.change check, the QC tool also checks that the code_18 and code_24 are consistent with the mapped change in the change attribute . For example if your mapped change is 211-324 then you must have code_18=211 and code_24=324. Mismatch between change and code_18 / code_24 is reported as error.

How to deal with solar changes in the change layer

"solar parks" change at level-4 such as 1211-1212 should be represented in the solar (SOL1824) layer. When generalized to change layer (CHA1824), it becomes 121-121. The change 121-121 is accepted by the QC tool for both chtype=T and chtype=R, because it is a level-3 generalisation of a valid real solar change.

vector.geometry reports self-intersections

The QC Tool uses the OGC rules for checking geometries and ring self-intersections are not allowed (although they may be valid in ArcGIS). To fix the ring self-intersection we recommend using the Fix Geometries tool in QGIS. It will repair the geometries, splitting any polygon with a ring self-intersection into two polygons.

QC tool reports overlaps or gaps

To remove any microscopic gaps or overlaps in the data, see How to fix overlaps and gaps

Please also note that the vector.gap check may report a large number of gap exceptions in the boundary buffer zone. These buffer zone exceptions are informative for us, no need to fix them, they will be resolved when we integrate the country-level CLC deliveries into the seamless European product.