Boundaries

Boundaries

When signed in on the homepage (http://qc-tool-demo.gisat.cz/) as administrator, at the top right-hand corner there is a Boundaries button redirecting to a boundary management form. Here use the green Upload Boundary Package button in the top left-hand corner to add a Zip file with all required AOI boundaries. To obtain the boundary package, please contact the EEA staff. Please note, when uploading boundaries the Boundary Package needs to follow certain structure:

• It needs to be in a zipped file
• The zip file needs to contain two folders: raster and vector
• Each folder has to contain all the boundaries files which are supposed to be present on the website because with every upload the current Boundaries Package is being rewritten.
• Boundaries within each folder need to be in a shp format
• For each boundary there need to be all related files present (at least dbf, prj, shp, shx), these are not zipped

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_default_020m_eu.tif
        +-- mask_default_100m_eu.tif
        +-- mask_waw_020m_eu.tif
        +-- mask_waw_100m_eu.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_<product>_<resolution>_<aoi_code>.tif

where:

• 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.
• aoi_code is an unique identifier of the AOI and must be always set to eu;

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 are located in the vector/clc subdirectory of the boundary package. Every AOI has associated one shapefile containing single polygon geometries covering the whole AOI. The shapefile 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 values specified in the Country Codes list.

When looking for the country AOI the countrycode in the name of the geodatabase is matched against the countrycode in the boundary file name. The spatial reference system (SRS) of the shapefile must match the spatial reference system of the delivery.

Boundary for vector products - all other vector products

Every such product has associated one shapefile or geopackage containing single polygon geometries covering all the AOIs. The file must be named:

boundary_<product>.shp

where product is an identifier of the product:

• rpz for Riparian zones 2012;
• rpz_2018 for Riparian zones 2018;
• n2k for Natura 2000.
• ua for Urban Atlas 2012, Urban Atlas 2018, Urban Atlas 2018 STL
• cz for Coastal Zones 2012 and Coastal Zones 2018

A collection of all the features demarcating the area of particular AOI forms one boundary unit. What AOI the feature is part of is determined by the value of the dedicated attribute:

• Riparian zones: du_id denoting delivery unit;
• Natura 2000: id denoting Natura 2000 site.
• Coastal zones: du denoting delivery unit;
• Urban atlas: fua denoting functional urban area;

As one delivery may elaborate more than one AOI, the datasource contains the same dedicated attribute which enables to identify the AOI particular feature is member of.