Boundaries

Boundaries

Completeness checks (r10 and v10) perform a spatial overlay of a checked delivery with a reference area-of-interest (AOI). Each product may have a distinct set of AOI's. Due to license restrictions, AOI boundaries cannot be distributed along with the QC tool. Instead, AOI boundaries shall be distributed as a separate boundary package. The boundary package is a large zip file which will be made available on EEA website for authorized service providers. It must be added to the QC tool by the service provider after installation.

General structure

The boundary package shall be distributed as a zip file with a predefined directory structure. The directory tree is organized by product and AOI.

+-- boundaries/
    +-- raster/
        +-- mask_eu_default_020m.tif
        +-- mask_eu_default_100m.tif
        +-- mask_eu_waw_020m.tif
        +-- mask_eu_waw_100m.tif
    +-- vector/
        +-- boundary_rpz.shp
        +-- boundary_n2k.shp
        +-- clc/
            +-- boundary_clc_al.shp
            +-- boundary_clc_at.shp
            +-- boundary_clc_bg.shp
            .....
            +-- boundary_clc_uk_ni.shp

Boundary for raster products

The file must be supplied in GeoTiff format and must be named:

mask_<aoi_code>_<product>_<resolution>.tif

where:

• aoi_code is an unique identifier of the AOI and must be always set to eu;
• product is an identifier of the product without resolution suffix, allowed values are:
  • waw for Water and Wetness,
  • default for other products;
• resolution is a resolution of the product; must be set to 020m or 100m.

The file must contain one only raster band, its spatial reference system must be EPSG:3035 and the band must follow the rules:

• the band is of type Byte;
• the NoData property is set to 255.
• the content of the band represents a mask, where following values are allowed:
  • 1 represents cell inside the reference AOI;
  • 255 represents cell outside the reference AOI.

Boundaries for vector products - CLC

The Corine Land Cover (CLC) AOI boundaries must be located in the vector/clc subdirectory of the boundary package.

The files must be supplied in polygon shapefile format and must be named:

boundary_clc_<countrycode>.shp

where:

• countrycode is the ISO 3166-1 code of a country or autonomous area and must have one of the following values:
  • al for Albania;
  • at for Austria;
  • ba for Bosnia and Herzegovina;
  • be for Belgium;
  • bg for Bulgaria;
  • ch for Switzerland;
  • cy for Cyprus;
  • cz for Czechia;
  • de for Germany;
  • dk for Denmark;
  • ee for Estonia;
  • es for Spain;
  • es_cn for Canary Islands;
  • fi for Finland;
  • fr for France;
  • fr_glp for Guadeloupe;
  • fr_guf for French Guiana;
  • fr_mtq for Martinique;
  • fr_myt for Mayotte;
  • fr_reu for Réunion;
  • gr for Greece;
  • hr for Croatia;
  • hu for Hungary;
  • ie for Ireland;
  • is for Iceland;
  • it for Italy;
  • xk for Kosovo;
  • li for Liechtenstein;
  • lt for Lithuania;
  • lu for Luxembourg
  • lv for Latvia;
  • me for Montenegro;
  • mk for FYR Macedonia;
  • mt for Malta;
  • nl for Netherlands;
  • no for Norway;
  • pl for Poland;
  • pt for Portugal;
  • pt_raa for Azores;
  • pt_raa_ceg for Azores, central and eastern group;
  • pt_raa_weg for Azores, western group;
  • pt_ram for Madeira;
  • ro for Romania;
  • se for Sweden;
  • si for Slovenia;
  • sk for Slovakia;
  • tr for Turkey;
  • uk for United Kingdom of Great Britain and Northern Ireland;
  • uk_je for Jersey;
  • uk_ge for Guernsey;
  • uk_ni for Northern Ireland;

When looking for the country AOI the countrycode in the name of the geodatabase is matched against the countrycode in the boundary file name.

Boundary for vector products - Natura 2000 and Riparian zones

The file must be supplied in shapefile format and must be named:

boundary_<product>.shp

where:

• product is an identifier of the product, allowed values are:
  • rpz for Riparian zones;
  • n2k for Natura 2000.

The file must containing polygon features.

The file must have an attribute which uniquely identifies a delivery unit. When looking for the boundary the value of particular attribute in the delivery is matched against the value of the attribute in the boundary file. The particular attribute differ by product:

• rpz: du_id;
• n2k: id.

Boundary for urban atlas

Urban atlas products have boundary file included as part of the delivery. So, the v10 completeness check uses such included file and no external boundary file is needed.

Notes

Some files in the boundary package have legal restrictions (typically national boundary maps).