Raster checks

Raster checks

r1. File format is correct

The check can not be skipped. The result values of the check are: ok, aborted.

All file names are case-insensitive. The files can be located anywhere in the directory hierarchy, eg. all examples are valid: FTY_2015_020m_eu_03035_d04.tif, fty_020m/fty_2015_020m_eu_03035_d04.tif, 2015/fty/20m/fty_2015_020m_eu_03035_d04.tif.

The required files for all products are:

• GeoTiff file, .tif;
• Attribute table file, .tif.vat.dbf;
• Metadata file, .xml;

r2. File names match file naming conventions

The check can not be skipped. The result values of the check are: ok, aborted.

The required file naming convention for all products is:

<product_code>_<campaign_year>_<resolution>_<country_code>_<epsg_code>_<version>.tif

where:

• product_code is 3-letter code of the product, e.g. FTY, GRA, WAW, IMC, IMD, TCD;
• reference_year is 4-digit reference year, e.g. 2015;
• resolution is raster cell size in meters, e.g. 010m, 020m or 100m;
• country_code is 2-letter country code or AOI code, e.g. eu;
• epsg_code is a valid EPSG code identifying the raster coordinate reference system;
• version is product specific version identifier.

r3. Attribute table contains prescribed attributes

Each HRL raster delivery must have a .tif.vat.dbf file with a raster attribute table. Only attribute names are checked. The attribute names are case insensitive. The attribute table must always have the following attributes:

• value, corresponds to unique codes in the GeoTiff file
• count, corresponds to the number of raster cells belonging to each code.
• area_km2, the area in square kilometres covered by cells with the code.
• area_perc, the area in square kilometres covered by cells with the code, expressed as percent of total mapped area.
• class_name, a text description of the land use / landcover class corresponding to the code.

r4. CRS of file expressed as EPSG code match reference EPSG code

The EPSG authority must be part of the GeoTiff file's spatial reference system information. The only accepted EPSG code is EPSG:3035 (ETRS89 ETRS-LAEA equal-area projection). The EPSG code must be explicitly included in the CRS definition.

r5. Raster cell size is in accord with specification

All cells in the raster product must have the same cell size. Required cell size is defined by product specifications:

• 100-metre resolution products (HRL forest type, tree cover density, imperviousness, imperviousness change, grassland, water&wetness):
  • required raster cell size is 100 x 100 metres;
• 20-metre resolution products (HRL forest type, tree cover density, imperviousness, imperviousness change, grassland, water&wetness):
  • required raster cell size is 20 x 20 metres.

r6. Raster origin check

• Upper-left X, Y coordinates of the raster must be divisible by raster cell size with no remainder;
• Upper-left X, Y coordinates of the raster must be divisible by 1000 with no remainder.

r7. Raster has specified data type

The GeoTiff file in the raster delivery must conform to required data type. The required data type for all products is Byte (values from 0 to 255).

r8. Compression type check

A raster delivery must have a compression type specified. The compression type of the GeoTiff file must be LZW.

r9. Pixel values check

See dedicated page Raster values.

r10. Completeness check

The AOI is defined by the boundary package, see Boundaries. There must be no cell having the value set to NoData inside the AOI.

r11. Minimum mapping unit

See dedicated page Raster MMU.

r12. Metadata check

See dedicated page Raster metadata.

r13. Raster has a colour table

Each raster delivery GeoTiff file must have a colour table. The colour table must be embedded in the GeoTiff file and provided in form of .clr and .clr.txt text files which are part of the delivery. Values in the GeoTiff colour table, .clr colour table and .clr.txt colour table must match.

r14. Colors in the color table match product specification

See dedicted page Raster colour table.