Skip to content

Raster checks

Jump to bottom
Jiří Kadlec edited this page Oct 4, 2019 · 26 revisions

Raster checks

raster.format: Delivery content uses specific file format

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;

The number of .tif files in the delivery must be equal to the number of layers in the product naming convention. Each .tif file must be a GeoTiff raster with a single band.

raster.naming: 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>_<reference_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.

raster.attribute: Attribute table is composed of 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.

raster.epsg: Raster uses specific 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.

raster.pixel_size: Pixel has specific size

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.
  • 10-metre resolution products (HRL 2018):
    • required raster cell size is 10 x 10 metres.

raster.origin: Bounding box upper left corner is positioned on grid

  • 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.

raster.bit_depth: Raster datatype is of specific bit depth

The GeoTiff file in the raster delivery must conform to required data type. The required data type is Byte (values from 0 to 255) or Int16 (values from -32768 to +32767)

raster.compress: Raster uses specific compression formats.

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

raster.value: Pixels have specific values

See dedicated page Raster values.

raster.gap: There is no gap in the AOI

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

raster.tile: The GeoTiff raster file is stored in tiled format

The data inside the GeoTiff raster file must be stored in tiles. The number of rows and columns in one tile must not be greater than the max_blocksize setting. Recommended tile size is 256 x 256 or 512 x 512 pixels. For more detail about tiled GeoTiff format, see the Cloud-Optimized GeoTiff specification (https://www.cogeo.org/).

raster.mmu: Minimum mapping unit

See dedicated page Raster MMU.

raster.inspire: Metadata are in accord with INSPIRE specification

See dedicated page Raster metadata.

raster.color: Color table is in accord with specification.

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 a tif.clr text file which is part of the delivery. Values in the GeoTiff colour table and in the .tif.clr colour table must match.

For product-specific colour table values see dedicated page Raster colour table.

Clone this wiki locally