circabc.europa.eu · Web viewIn cases where the MS has not used either UoM or APSFR the MS needs to report a 'bounding box' where they have available national FHRM and report the

Floods Directive GIS GuidanceGuidance on the reporting of spatial data to WISEDRAFT2018-01-22

WISE Floods Directive GIS Guidance DRAFT

ContentsQuick Start.........................................................................................................................................................................1WISE Reporting obligations................................................................................................................................................2

Floods reporting..............................................................................................................................................................2Data content......................................................................................................................................................................3

Units of Management (UoM)...........................................................................................................................................3Definitions...................................................................................................................................................................3Reporting units of management and subunits............................................................................................................3Constraints and quality control...................................................................................................................................3

Areas of Potential Significant Flood Risk.........................................................................................................................3Definitions...................................................................................................................................................................3Reporting areas of potential flood risk using the AreasofPotentialSignificantFloodRisk data set................................3Constraints and quality control...................................................................................................................................4

Preliminary Flood Risk Assessments...............................................................................................................................5Definitions...................................................................................................................................................................5Reporting preliminary flood risk assessments using the PreliminaryFloodRiskAssessment data set...........................5Constraints and quality control...................................................................................................................................5

Flood Hazard Maps and Flood Risk Maps........................................................................................................................6Definitions...................................................................................................................................................................6Reporting of Flood Hazards and Flood Risk Maps........................................................................................................6Reporting of Flood Hazards and Flood Risk Maps Medium Probability Scenario..........................................................6

Data quality.......................................................................................................................................................................8Coordinate reference systems...........................................................................................................................................9

Projection metadata files (.prj).......................................................................................................................................9Metadata..........................................................................................................................................................................10

INSPIRE metadata requirements for specific themes....................................................................................................10Reporting guidance for specific metadata elements....................................................................................................11

Data exchange.................................................................................................................................................................12Character encoding......................................................................................................................................................12File formats...................................................................................................................................................................12GML format...................................................................................................................................................................12Shapefile format...........................................................................................................................................................12File naming convention................................................................................................................................................13Data submission...........................................................................................................................................................14Resubmissions and updates.........................................................................................................................................14

Data policy.......................................................................................................................................................................15Data storage.................................................................................................................................................................15Data usage...................................................................................................................................................................15Data distribution...........................................................................................................................................................15

Floods Directive spatial datasets and INSPIRE themes....................................................................................................17INSPIRE Area Management / Restriction / Regulation Zones and Reporting Units Theme............................................17

Introduction...............................................................................................................................................................17Units of Management................................................................................................................................................17

INSPIRE Natural Risk Zones Theme..............................................................................................................................21Introduction...............................................................................................................................................................21Area of potential flood risk........................................................................................................................................21Preliminary Flood Risk Assessment...........................................................................................................................22Using thematic identifiers to relate two objects with different types........................................................................24

Quick reference card........................................................................................................................................................25References.......................................................................................................................................................................26Annex I – Glossary............................................................................................................................................................27Annex II: Recommendations on How to Publish Downloadable Datasets Compliant with INSPIRE Directive....................60

INSPIRE Compliance Overview..................................................................................................................................60Download a numeric representation of the data for downstream analysis...............................................................60Metadata...................................................................................................................................................................61Network services.......................................................................................................................................................64

i


Quick Start1. The following Floods Directive reference spatial data sets are required for reporting:

Units of Management (UoM); Areas of Potential Significant Flood Risk (AreasOfPotentialSignificantFloodRisk); Preliminary Floods Risk Assessments (PreliminaryFloodRiskAssessments); Floods Hazard and Risk Maps.

2. The geometry of AreasOfPotentialSignificantFloodRisk and PreliminaryFloodRiskAssessments must be reported using polygons or polylines or points. If applicable, separate files must be provided for each geometry type.

3. The quality of the data sets must be evaluated by the Data Providers before the submission. Attention must be paid to the spatial alignment across national and international borders for the purpose of producing a harmonised European level dataset. Reference data sets are available to support this alignment.

4. The coordinate reference system for spatial data must be ETRS89-GRS80 or ETRS89-LAEA. For areas outside the scope of ETRS89, WGS 84 must be used.

5. Metadata must be provided for each spatial data file, according to the INSPIRE metadata profile.

6. The spatial data files must be submitted as valid GML files, conformant with the schemas available in the Data Dictionary schemas (http://dd.eionet.europa.eu/schemasets/browse/).

7. The spatial data files may be prepared as shapefiles. The shapefile templates available in the resources page (xxx) must be used. The shapefiles must be converted to GML using the conversion tools available in the same page. The GML files must then be uploaded to the appropriate envelope in Reportnet CDR (http://cdr.eionet.europa.eu).

8. The spatial data files must follow the naming convention defined in this document.9. For the 20XX Floods Directive reporting, submissions to EIONET Reportnet must be

completed no later than XXnd XXXX 20XX.

1

http://dd.eionet.europa.eu/schemasets/browse/


WISE Reporting obligationsFloods reportingFor Data Providers reporting under Floods Directive, this document is Annex [] to the Floods Reporting Guidance 2017. It provides a guidance in the preparation and reporting of spatial data.The GML schemas, shapefile templates and supporting documents required for the Floods reporting are available in EIONET Reportnet via http://cdr.eionet.europa.eu/help/Floods/Floods_603_2016.

If you need assistance on issues not addressed in this document please contact the Floods Directive helpdesk at [email protected].

In accordance with the WISE reporting arrangements, Member States may update the data submitted to WISE at any time. Member States should ensure that the latest, correct information is available in WISE since that will be used for compliance checking and publication.

The quality, accuracy and validation of the information and data in WISE is the responsibility of the Member States. Quality assurance and control processes will be carried out by the WISE partners. The Commission, the EEA or its contracted partners may contact the Member State in case there is an indication that any of the data may be erroneous or misleading. This may lead to a resubmission request to the Member State.

2

mailto:[email protected]


Data contentThis section provides an overview of the content of the different Floods spatial data sets and of the constraints and requirements applicable to the spatial objects and their relationships. Examples to be provided provided to clarify some specific situations.

Units of Management (UoM)

DefinitionsDefinitions relevant for the Units of Management data set.

Concept Definition Related data setsUnits of Management

The Floods Directive (Article 3.2) allows Member States to identify units of management different from the river basin districts used for the Water Framework Directive. Units of management may be individual river basins and/or certain coastal areas, and may be entirely within national borders or may be part of an international unit of management or international river basin district.

AreaOfPotentialFloodRisk, PreliminaryFloodRiskAssessment,

Reporting units of management and subunitsUnits of management are reported in the UoM data set.Sub-units are reported in the SubUnit data set.

Constraints and quality controlThe UoM data set must form a complete tessellation of the national territory to the limit of the coastal waters (i.e. 1 nautical mile for the territorial waters baseline).

Note 1: In a tessellation, the polygons must fill the plane with no gaps, overlaps or self-intersecting boundaries.

Areas of Potential Significant Flood Risk

DefinitionsDefinitions relevant for the AreasofPotentialSignificantFloodRisk data set.

Concept Definition Related data setsAreas of Potential Flood Risk

Areas where there is a significant risk of flooding from local sources, such as surface water, ground water and ordinary watercourses. Areas of potential significant flood risk exist or might be considered likely to occur in the future for each river basin district, unit of management or the portion of an international river basin district or unit of management lying within a Member State’s territory.

PreliminaryFloodRiskAssessment, UoM

3


Reporting areas of potential flood risk using the AreasofPotentialSignificantFloodRisk data setIf the reference geometry of the areas of potential flood risk is a polygon, then the areas of potential flood risk must be reported in the AreaofPotentialSignificantFloodRisk data set. If the reference geometry is a line or a point, then the areas of potential flood risk must be reported in the AreaofPotentialSignificantFloodRisk_Line or AreaofPotentialSignificantFloodRisk_Point.

Constraints and quality control1. Each area of potential flood risk must be assigned to one and only one unit of

management.2. Areas of potential flood risk must not overlap each other. This requirement applies

regardless of the reference geometry: polygons must not overlap each over, line segments must not overlap each other (a node must exist at intersections) and finally lines and polygons cannot overlap each other.

3. Each area of potential flood risk must be reported as either overlapping two or more UoMs or as contained within its assigned unit of management.

4


Preliminary Flood Risk Assessments

DefinitionsDefinitions relevant for the PreliminaryFloodRiskAssessment data set.

Concept Definition Related data setsPreliminary Flood Risk Assessment

Article 4 of the Floods Directive requires Member States to undertake a Preliminary Flood Risk Assessment (PFRA) for each river basin district, unit of management or the portion of an international river basin district or unit of management lying within their territory by providing geographic location of past flood events and potential future flood events associated with the flood

The identification of areas with a potential significant flood risk (art. 5) will be based on available or readily derivable information including the requirements specified in the directive (art. 4).Available or readily derivable information should, where possible, include details of:

- Significant floods that have occurred in the past and their location, extent, conveyance routes and adverse consequences, and other floods that occurred in the past which would have significant adverse consequences if they occurred again;

- Potential adverse consequences of future floods;

- Impacts of climate change and long-term developments on the occurrence of floods; and,

- Other available or readily derivable information, as relevant to the Member State, on issues such as topography, the position of water courses and their general hydrological and geo- morphological characteristics, including flood plains as natural retention areas, the effectiveness of existing flood defence infrastructure, and the position of populated areas and areas of economic activity.

UoM, AreasOfPotentialFloodRisk

Reporting preliminary flood risk assessments using the PreliminaryFloodRiskAssessment data setIf the reference geometry of the preliminary flood risk assessment is a polygon, then the preliminary flood risk assessment must be reported in the PreliminaryFloodRiskAssessment dataset. If the reference geometry is a line or a point, preliminary flood risk assessment must be reported in the PreliminaryFloodRiskAssessment_Line or PreliminaryFloodRiskAssessment_Point.

Constraints and quality control1. Each preliminary flood risk assessment must be assigned to one and only unit of

management.

5


2. Preliminary flood risk assessments must not overlap each other. This requirement applies regardless of the reference geometry: polygons must not overlap each over, line segments must not overlap each other (a node must exist at intersections) and finally lines and polygons cannot overlap each other.

3. Each preliminary flood risk assessment must be reported as either overlapping two or more UoMs or as contained within its assigned unit of management.

6


Flood Hazard Maps and Flood Risk Maps

DefinitionsDefinitions relevant for the Flood Hazard Maps and Flood Risk Maps

Concept Definition Related data setsFloods Hazard Maps and Floods Risk Maps

Article 6 of the Floods Directive (http://ec.europa.eu/environment/water/flood_risk) requires Member States to prepare flood hazard maps and flood risk maps. The distinction between flood hazard maps and flood risk maps is (Reference #1):- the flood hazard maps should cover the geographical area

which could be flooded according to different probabilities, along with some hazard related information associated to those areas;

- the flood risk maps shall show the potential adverse consequences associated with floods under these probabilities, relating to human health, economic activity, the environment and cultural heritage.

UoM, AreasOfPotentialFloodRisk

Reporting of Flood Hazards and Flood Risk MapsFlood hazard maps must show the geographical area which could be flooded under different probabilities, whereas flood risk maps must show the potential adverse consequences of these flood scenarios. The flood maps must be prepared for the following flooding scenarios:

a) floods with low probability, or extreme event scenarios;b) flood with a medium probability (likely return period ≥ 100 years);c) floods with a high probability, where appropriate.

Member States have flexibility to assign specific flood probabilities to these scenarios.For each scenario, Member States must prepare information of flood extents and water depth or levels (art 6.4). Where appropriate, Member States can also prepare information on flow velocities or the relevant water flow.For each flooding scenario, the flood risk maps shall show:

1. the indicative number of inhabitants potentially affected;

2. type of economic activity of the area potentially affected;3. installations as referred to in Annex I to Council Directive 2008/1/EC (codified

version of Directive 96/61/EC of 24 September 1996) concerning integrated pollution prevention and control which might cause accidental pollution in case of flooding and potentially affected WFD protected areas.

The maps may show other information which the Member State considers useful such as the indication of areas where floods with a high content of transported sediments and debris floods can occur and information on other significant sources of pollution.For coastal flooding where there is an adequate level of protection in place, and for

7


groundwater flooding, Member States can provide justification for limiting the preparation of flood hazard maps to the low probability or extreme event scenario.

Reporting of Flood Hazards and Flood Risk Maps Medium Probability ScenarioIn the second cycle reporting exercise (22/03/2020 Flood Hazard Maps & Flood Risk Maps) as INSPIRE is being implemented, the format for reporting data and information exchange of Flood Hazard and Flood Risk Maps relating to the Medium Probability scenario should be in a decentralised mode as foreseen by the INSPIRE Directive through download services, and in line with a Shared Environmental Information System (SEIS) initiative and made available via WISE.Procedure on how to link to national maps from EU portalThis section outlines the procedure for Member States to register their national level Flood Hazard and Risk Maps (FHRM) under the reporting obligation for flood hazard maps and flood risk maps.This registration follows its own reporting process where MS are responsible for maintaining the links to their national maps, hence the most recent FHRM_links.xml should be made available at a source location within the member state to be utilised by the EEA. For the FHRM the links can be provided as either a list of PDF's, via a portal or through WFS.The links to national FHRMs should be made at the APSFR level where applicable. If a MS has used a different level for the identification of the APSFR (eg. UoM) then the links should be reported at this level. In cases where the MS has not used either UoM or APSFR the MS needs to report a 'bounding box' where they have available national FHRM and report the link at this level.

8


Data qualityData providers are recommended not to simplify or generalise the spatial data reported to WISE.The accuracy of the data should be documented in the metadata so that any further processing done in the production of the European reference data sets can respect the accuracy of the original data source.

Considering both WISE needs and the practical constraints of data availability, it is recommended that to report data with positional accuracy acceptable for cartographic representation at the 1:100000 scale or larger. The positional accuracy should always be kept as high as possible and ideally be similar to the national operational data sets.

Geodetic coordinates must be expressed in decimal degree, with a minimum recommended precision of 5 decimal places. Projected coordinates must be expressed in metre, with a minimum recommended precision of 1 decimal place. See the section on “Coordinate reference systems” for further information.

The quality of the data sets must be evaluated by the Data Providers before the submission.

For each dataset, the sections on "Constraints and quality control" express a number of requirements on the topology and/or spatial relationships between different types of spatial units. However, and to keep the model as simple as possible, topology is handled implicitly rather than explicitly. There is therefore a prerequisite for "implicit topology", i.e. the data provided should be sufficiently clean to support automated topological construction based on the reported geometry.

Attention must be paid to the spatial alignment across national and international borders for the purpose of producing a harmonised European level data set. Reference data sets are made available to support this alignment and are provided in the public or restricted access area accessible by the authorised reporters, and subject to use conditions. The following European wide reference data sets are provided:

EEA coastline, source EEA Country boundaries, source EuroBoundaryMap – Eurogeographics.

The EEA coastline for analysis is available at http://www.eea.europa.eu/data-and-maps/data/eea-coastline-for-analysis-1 and may be used, subject to the constraints expressed in its metadata (http://www.eea.europa.eu/data-and-maps/data/eea-coastline-for-analysis-1#tab-metadata).

9

http://www.eea.europa.eu/data-and-maps/data/eea-coastline-for-analysis-1#tab-metadata

http://www.eea.europa.eu/data-and-maps/data/eea-coastline-for-analysis-1#tab-metadata

http://www.eea.europa.eu/data-and-maps/data/eea-coastline-for-analysis-1


Coordinate reference systems

The spatial data sets must be provided in one of the following coordinate reference systems (CRS): ETRS89-GRS80 (urn:ogc:def:crs:EPSG::4258) ETRS89-LAEA (urn:ogc:def:crs:EPSG::3035) WGS 84 (urn:ogc:def:crs:EPSG::4326) The geometry of spatial objects should be reported in the ETRS89-GRS80 geodetic coordinate system (urn:ogc:def:crs:EPSG::4258). For areas outside the scope of ETRS89, such as overseas territories, WGS 84 (urn:ogc:def:crs:EPSG::4326) must be used. The geometry of spatial objects may also be reported in the ETRS89-LAEA projected coordinate system (urn:ogc:def:crs:EPSG::3035). Again, an exception applies for areas outside the scope of ETRS89, where the geodetic coordinate system WGS 84 (urn:ogc:def:crs:EPSG::4326) must be used. Note that for the quality control procedures applied to the spatial data, the ETRS89-LAEA projected coordinate system will be used.

Projection metadata files (.prj) Valid projection metadata files (.prj) for the shapefile format are provided below:

For ETRS89-GRS80 (urn:ogc:def:crs:EPSG::4258)GEOGCS["ETRS89",DATUM["D_ETRS_1989",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]]

For ETRS89-LAEA (urn:ogc:def:crs:EPSG::3035)PROJCS["ETRS_1989_LAEA",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Azimuthal_Equal_Area"],PARAMETER["False_Easting",4321000.0],PARAMETER["False_Northing",3210000.0],PARAMETER["Central_Meridian",10.0],PARAMETER["Latitude_Of_Origin",52.0],UNIT["Meter",1.0]]

For WGS 84 (urn:ogc:def:crs:EPSG::4326)GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]]

10


MetadataA metadata file must be provided for each spatial data file. As defined in the “CIS Guidance Document No. 22”:

Since the majority of WISE datasets and services will fall under the scope of INSPIRE, this guidance recommends the adoption of a profile which extends the INSPIRE metadata to include all those additional elements already agreed by the WISE community. This guidance recommends the use of INSPIRE terminology for element names wherever possible, thus ensuring compatibility with metadata created in other environmental policy areas.

The content and structure of the metadata file must be in conformance to the “INSPIRE Metadata Implementing Rules: Technical Guidelines based on EN ISO 19115 and EN ISO 19119”:

The use of these guidelines to create INSPIRE metadata ensures that the metadata is not in conflict with ISO 19115. However, full conformance to ISO 19115 implies the provision of additional metadata elements which are not required by the INSPIRE Implementing Rule on Metadata. Additional metadata elements are required by the INSPIRE Implementing Rules for the Interoperability of Spatial Datasets and Services. An overview list of these additional elements is provided in Annex B.

In practice, this means that the INSPIRE metadata requirements must be met (including the metadata elements for interoperability defined in Annex B of the INSPIRE Metadata Implementing Rules). Conformance with ISO 19115 is encouraged but not strictly required. A specific WISE metadata profile is no longer required. The authoring and editing of metadata files can be done in a number of ways including the use of a metadata editor capable of exporting an XML file conformant to the ISO 19139 schema. See, for example, the editor and the validator available at the INSPIRE Geoportal (http://inspire-geoportal.ec.europa.eu).

INSPIRE metadata requirements for specific themesThe INSPIRE Data Specification on Natural Risk Zones sets specific requirements for the metadata: see section 8 (Dataset-level metadata) of the specification document.

These requirements must be followed for the Areas of Potential Significant Flood Risk (AreasOfPotentialSignificantFloodRisk) and Preliminary Floods Risk Assessments (PreliminaryFloodRiskAssessments).

11

http://inspire-geoportal.ec.europa.eu/


Reporting guidance for specific metadata elementsReporting guidance for specific metadata elements.

Metadata element

Reporting guidance

2.1 Topic category

Select at least option Environment. This element is required.

3.1 Keyword value

Select the appropriate keywords from the WISE metadata keywords list (http://converters.eionet.europa.eu/xmlfile/WISE_metadata_keywords_1.xml) and identify the corresponding vocabulary (Floods Directive). This element is required.

5.1 Temporal extent

Provide the period covered by the spatial data reported. The period should be defined by the planning period for which the real-world entities are expected to be valid. This element is required.

5.2 Date of publication

Provide the date of the reporting deadline of the period specified with Metadata element 5.1. This element is required.

5.3 Date of last revision

Provide the date of the last submitted update to the data set. This element is required.

8.2. Limitations on public access

Limitations on public access, if any, must be clearly stated in the metadata. If no restrictions are stated, Category 3 will be applied (see the Data policy section, below). Note that, for safety or security reasons, Data Providers may flag that the location of some monitoring sites (e.g. drinking water abstractions) must not be published. These restrictions are set at record-level and are always applied, regardless of the classification of the data set.

Reporting dates in the metadata files .

Submission

Temporal extent Date of publication

Date of last revision

1 From XXXX-XX-XX to XXXX-XX-XX

XXXX-XX-XX XXXX-XX-XX

12

http://converters.eionet.europa.eu/xmlfile/WISE_metadata_keywords_1.xml


Data exchangeCharacter encodingThe character encoding for all data and metadata files must be UTF-8.

File formatsThe spatial data sets must be reported using GML files.

Data Providers may prepare the data using the shapefile format. Shapefile templates are available, and a shapefile to GML conversion tool is also provided (see below). The GML files resulting from this conversion must be uploaded to the delivery envelope in CDR. The shapefiles must not be uploaded to the delivery envelope.

Some restrictions were adopted in the schemas to allow a similar description of the data sets regardless of the file format (GML or shapefile). For example, each type of geometry is reported in a separate data file (due to the limitations of the shapefile format).See the CDR help page for further information (http://cdr.eionet.europa.eu/help/floods/) – To be updated

GML formatThe schemas are available in the Data Dictionary (http://dd.eionet.europa.eu/schemaset/ ) – To be updated

Shapefile formatShapefile templates are provided in the CDR help page. The templates must be used when preparing the data and using the conversion tools to from shapefile to GML.

Shapefiles must have the three structural files (*.shp, *.shx and *.dbf) and the *.prj and *.cpg files. Shapefiles without the *.prj projection file (or with an incorrect definition of the coordinate system) will not be processed by the conversion tools. The *.cpg file is also mandatory as it is explicitly identifies the character encoding used in the *.dbf file. Remember that the mandatory encoding is UTF-8.Shapefiles with different fields in the attribute table will not be processed. This includes: additional fields, different field names or different field types. Note that the field names in a shapefile must have a maximum of 10 characters, so a "short" version of the GML names was defined for the shapefile templates (see the "Quick Reference Card" in page 27).

The DBF format used in the shapefile attribute table does not support NULL values (i.e. there is no difference between a NULL string and an empty string, or between a NULL value and a zero value). Also the structure of the table is fixed for all records (i.e. even if an optional attribute is not provided or is not applicable to a given record). To circumvent these limitations, Data Providers are requested to explicitly provide the conventional null values depending on the field type:

Use 'NotApplicable' for string fields;

13

http://cdr.eionet.europa.eu/help/floods/


Use -9999 for numeric fields; Use 9999-12-31 for date fields.

The DBF format has a maximum length of 254 characters for string fields. Be aware of this limitation.

File naming conventionThe filenames of the spatial data sets must follow the following naming convention: [DataSetType]_[UoMCode]_[Date] File naming convention.

Code Description[DataSetType] Identification of the content of the data set.

AreaofPotentialSignificantFloodRisk, for polygonal geometries AreaofPotentialSignificantFloodRisk_Line, for linear geometries AreaofPotentialSignificantFloodRisk_Point, for point geometries PreliminaryFloodRiskAssessment, for polygonal geometries PreliminaryFloodRiskAssessment_Point, for point geometries PreliminaryFloodRiskAssessment_Line, for linear geometries

[euUoMCode] Unit of management code[Date] Submission date in the format YYYYMMDD

Examples:

AreaofPotentialSignificantFloodRisk_XZ_XXXXXXXX AreaofPotentialSignificantFloodRisk_Line_XZ_XXXXXXXX AreaofPotentialSignificantFloodRisk_Point_XZ_ XXXXXXXX

The file extension depends on the file format. gml (for the spatial data file)

14


Data submissionData must be uploaded in the Reportnet Central Data Repository (CDR).

Data Providers reporting under Floods are referred to the instructions provided in the Annex X of the Floods Reporting Guidance 2017. Collections have already been created in CDR for the reporting of spatial data:

http://cdr.eionet.europa.eu/{country_code}/eu/floods/spatial/

Resubmissions and updatesIf data is resubmitted or updated, then complete data sets have to be uploaded.Incomplete spatial data sets will not pass the referential integrity quality control and thus cannot be further processed.

15


Data policyUnder the "WISE Reporting Arrangements", Member States have agreed on the conditions applicable to spatial data (see Annex 1 of the WISE Reporting Arrangements). For ease of reference, an extract of the current agreement (dated 2007-03-01) is transcribed below. The agreement may be subject to future changes.

Data storageThe European Commission (EC) and the European Environmental Agency (EEA) will store the geographic datasets on servers managed and accessible by the staff of the EC and the EEA. DG Environment will distribute parts or the entire datasets within the Commission, the EEA and to contractors, these last for the sole purpose of activities executed for the Commission and/or the EEA and limited to the duration of those activities.

Data usageThe Commission and the EEA are authorised to use the geographic data in the context of environmental policy definition, implementation, assessment and analysis: As geographic reference, i.e. creating a geographical context for other data; For the production of maps, publications, posters, presentations, web sites and any other

electronic publication on the Internet. Electronic publication will be in the form of image maps;

For spatial and statistical analysis; For deriving new geographic datasets by applying data manipulation procedures, e.g.

combining different geographic datasets, generalisation procedures including smoothing and dropping of spatial features, adding new attribute information;

For inclusion of the geographic data in other applications provided that it will not possible to extract the original geographic data.

Data distributionThe Commission and the EEA are authorized to distribute geographic data, if The source is acknowledged and, The data is not used for commercial purpose – unless approved by the provider - and, The data provider has not explicitly restricted their dissemination beyond what specified

at point 2[…]Distribution media of geographic data are paper publications, electronic publications, offline distribution on physical supports (e.g. CD-ROMs) and online distribution via the Internet services. Geographic data may be distributed as feature services on the Internet or vector data on physical support, only if data distribution conditions are met as specified in the metadata.

The metadata related to the geographic data and the derived geographic data will be distributed via a data catalogue service within the Commission, the EEA and to the public without any restrictions.An acknowledgement of source including statement on legal constraints on access and use of geographic data, where appropriate, will be supplied with geographic data and derived products as part of the metadata information or as an accompanying document. […]

16


Categories for distribution of geographic data and derived products as part [of the] metadata element on data constraints: Category 1: Internal use within Commission and EEA, publication as maps on paper or in

electronic format as image maps. Category 2: Distribution of derived data and products under predefined conditions with

the aim of decreasing the spatial accuracy or resolution of the geographic data. Category 3: Distribution of original data electronically as feature service or on physical

support.

17


Floods Directive spatial datasets and INSPIRE themesINSPIRE Area Management / Restriction / Regulation Zones and Reporting Units Theme

IntroductionThis section provides information about the relationship between the Floods Directive spatial data set units of management and the INSPIRE Area Management / Restriction / Regulation Zones and Reporting Units Theme (Annex III).

Units of ManagementThe table below shows the reporting data structure.Units of management schema.

# GML data element Definition Multiplicity ReportingGuidance1 geometry -- Definition -- The

geometry representing the spatial extent of the spatial object.

[1..1] -- Guidance --

2 inspireIdLocalId -- Definition -- A local identifier, assigned by the data provider. The local identifier is unique within the namespace, that is no other spatial object carries the same unique identifier. -- Description -- NOTE It is the responsibility of the data provider to guarantee uniqueness of the local identifier within the namespace. [Source: Feature Catalogue 'INSPIRE application schemas' http://inspire.ec.europa.eu/data-model/approved/r4618/fc/#_C33423]

[1..1] -- Guidance -- It is recommended that Data Providers reporting under Floods Directive use the value of the euUoMCode as the object's localId. -- Additional information -- Recommendation 3: The localId attribute of the external object identifier of a spatial object shall be the same as the ID used for reporting obligations under the Water Framework Directive [2000/60/EC]. [Source: http://inspire.ec.europa.eu/documents/Data_Specifications/INSPIRE_DataSpecification_AM_v3.0.pdf , page 150]

18


# GML data element Definition Multiplicity ReportingGuidance3 inspireIdNamespace -- Definition --

Namespace uniquely identifying the data source of the spatial object. -- Description -- NOTE The namespace value will be owned by the data provider of the spatial object and will be registered in the INSPIRE External Object Identifier Namespaces Register. [Source: Feature Catalogue 'INSPIRE application schemas' http://inspire.ec.europa.eu/data-model/approved/r4618/fc/#_C33423]

[0..1] -- Guidance -- Optional. Data Providers must report the namespace of the data source of the spatial object, if an INSPIRE data set was used for reporting.

4 inspireIdVersionId -- Definition -- The identifier of the particular version of the spatial object, with a maximum length of 25 characters. If the specification of a spatial object type with an external object identifier includes life-cycle information, the version identifier is used to distinguish between the different versions of a spatial object. Within the set of all versions of a spatial object, the version identifier is unique. -- Description -- NOTE The maximum length has been selected to allow for time stamps based on ISO 8601, for example, "2007-02-12T12:12:12+05:30" as the version identifier.NOTE 2 The property is void, if the spatial data set does not distinguish between different versions of the spatial object. It is missing, if the spatial object type does not support any life-cycle information. [Source: Feature Catalogue 'INSPIRE application schemas' http://inspire.ec.europa.eu/data-model/approved/r4618/fc/#_C33423]

[0..1] -- Guidance -- Optional. Data Providers must report the version of spatial object, if an INSPIRE data set was used for reporting and life-cycle info is supported.

19


# GML data element Definition Multiplicity ReportingGuidance5 thematicIdIdentifier -- Definition -- Unique

identifier used to identify the spatial object within the specified identification scheme. [Source: Feature Catalogue 'INSPIRE application schemas' http://inspire.ec.europa.eu/data-model/approved/r4618/fc/#_C33431]

[1..1] -- Guidance -- Data Providers reporting under Floods Directive must use the euUoMCode as the thematicIdIdentifier. Data Providers are required to report this element. Note that the value of thematicIdIdentifier attribute will be the same as the value of the localId attribute, if the Data Provider followed the INSPIRE recommendation (i.e. if the euUoMCode was used as the localId value).

6 thematicIdIdentifierScheme

-- Definition -- Identifier defining the scheme used to assign the identifier. -- Description -- NOTE 1: Reporting requirements for different environmental legislation mandate that each spatial object is assigned an identifier conforming to specific lexical rules.NOTE 2: These rules are often inconsistent so a spatial object may be assigned multiple identifiers which are used for object referencing to link information to the spatial object. [Source: Feature Catalogue 'INSPIRE application schemas' http://inspire.ec.europa.eu/data-model/approved/r4618/fc/#_C33431]

[1..1] -- Guidance -- Data Providers reporting under Floods Directive must use the default value 'euUoMCode' for the thematicIdIdentifierScheme attribute..

7 beginLifespanVersion -- Definition -- Date and time at which this version of the spatial object was inserted or changed in the spatial data set. -- Description -- NOTE This date is recorded to enable the generation of change

[0..1] -- Guidance -- Conditional. Data Providers should report this information, if available. Data Providers must report this information if the endLifespanVersion value is reported.

20


# GML data element Definition Multiplicity ReportingGuidanceonly update files.

8 nameTextInternational

-- Definition -- Name, in English. English exonym, or understandable English version of the name of the geographical feature or spatial object.

[0..1] -- Guidance -- Optional. It is recommended that Data Providers report this information. Data Providers are not strictly required to provide this information.

9 nameText -- Definition -- Name, in the national language. National language endonym, or national language version of the name of the geographical feature or spatial object.

[1..1] -- Guidance --

10

nameLanguage -- Definition -- Language code of the language used in the nameText attribute value.

[1..1] -- Guidance --

11

designationPeriodBegin

-- Definition -- [Beginning of the] time period defining when the management, restriction or regulation zone was legally designated or became effective in the real world.

[1..1] -- Guidance --

12

designationPeriodEnd -- Definition -- [End of the] time period defining when the management, restriction or regulation zone was legally designated or became effective in the real world.

[0..1] -- Guidance -- Conditional. Data Providers are required to report this information only if the end of the validity period is known or has already occorred. Data Providers reporting under Floods Directive are not required to provide this information, as it is expected that only currently designated areas of management are reported. This attribute is kept in the data model to allow future updates and support the traceability of changes to objects previously reported.

13

zoneType -- Definition -- High-level classification defining the type of Management, Restriction or Regulation Zone.

[1..1] -- Guidance -- Data Providers reporting under Floods Directive must use the default value unitOfManagement for the zoneType attribute.

14

link -- Definition -- Hyperlink to where additional information on the Area of Management or Reporting Unit is available on the web,

[0..1] -- Guidance --

21


# GML data element Definition Multiplicity ReportingGuidanceat national level.

INSPIRE Natural Risk Zones Theme

IntroductionThis section provides information about the relationship between the Floods Directive spatial data sets for areas of potential flood risk and preliminary flood risk assessment and the INSPIRE Natural Risk Zone theme (Annex III).

In addition, this section provides information about the conceptual mapping between the elements in the Floods spatial data model and the elements in the INSPIRE data model.

Area of potential flood riskThe table below shows the reporting data structure.Area of potential flood risk schema.

# GML data element Definition Multiplicity

Data type

1 geometry -- Definition -- The geometry representing the spatial extent of the spatial object.

[1..1] GM_MultiSurface


[1..1] String254Type

3 inspireIdNamespace -- Definition -- Namespace uniquely identifying the data source of the spatial object. -- Description -- NOTE The namespace value will be owned by the data provider of the spatial object and will be registered in the INSPIRE External Object Identifier Namespaces Register. [Source: Feature Catalogue 'INSPIRE application schemas' http://inspire.ec.europa.eu/data-model/approved/r4618/fc/#_C33423]


4 inspireIdVersionId -- Definition -- The identifier of the particular version of the spatial object, with a maximum length of 25 characters. If the specification of a spatial object type with an external object identifier includes life-cycle information, the version identifier is used to distinguish between the different versions of a spatial object. Within the set of all versions of a spatial object, the version identifier is unique. -- Description -- NOTE The maximum length has been selected to allow for time stamps based on ISO 8601, for example, "2007-02-12T12:12:12+05:30" as the version identifier.NOTE 2 The property is void, if the spatial data set does not distinguish between different versions of the spatial object. It is missing, if the spatial object type does not support any life-cycle information. [Source:

[0..1] String25Type

22



Data type

Feature Catalogue 'INSPIRE application schemas' http://inspire.ec.europa.eu/data-model/approved/r4618/fc/#_C33423]

5 thematicIdIdentifier -- Definition -- Unique identifier used to identify the spatial object within the specified identification scheme. [Source: Feature Catalogue 'INSPIRE application schemas' http://inspire.ec.europa.eu/data-model/approved/r4618/fc/#_C33431]

[1..1] FeatureUniqueEUCodeType



[1..1] IdentifierSchemaType = euAPSRCode

7 beginLifespanVersion -- Definition -- Date and time at which this version of the spatial object was inserted or changed in the spatial data set.

[0..1] WiseDateTimeType

8 endLifespanVersion -- Definition -- Date and time at which this version of the spatial object was superseded or retired in the spatial data set.



-- Definition -- Name, in English. English exonym, or understandable English version of the name of the geographical feature or spatial object.


10

nameText -- Definition -- Name, in the national language. National language endonym, or national language version of the name of the geographical feature or spatial object.


11


[1..1] WiseLanguageCode_Enum

12

validFrom -- Definition -- The date when the phenomenon started to exist in the real world.


13

validTo -- Definition -- The time from which the phenomenon no longer exists in the real world.


14

specificHazardType -- Definition -- Additional classification of the natural hazard that further specifies the hazard type according to a nomenclature that is specific to this dataset.

[1..1] SpecificHazardTypeValue

15

link -- Definition -- Hyperlink to where additional information on the Area of Potential Risk (APSFR) is available on the web, at national level.

[0..1] URLType

Preliminary Flood Risk AssessmentThe table below shows the reporting data structure.Preliminary Flood Risk Assessment schema

23



Data type

1 geometry -- Definition -- The geometry representing the spatial extent of the spatial object.

[1..1] GM_MultiSurface



3 inspireIdNamespace -- Definition -- Namespace uniquely identifying the data source of the spatial object. -- Description -- NOTE The namespace value will be owned by the data provider of the spatial object and will be registered in the INSPIRE External Object Identifier Namespaces Register. [Source: Feature Catalogue 'INSPIRE application schemas' http://inspire.ec.europa.eu/data-model/approved/r4618/fc/#_C33423]


4 inspireIdVersionId -- Definition -- The identifier of the particular version of the spatial object, with a maximum length of 25 characters. If the specification of a spatial object type with an external object identifier includes life-cycle information, the version identifier is used to distinguish between the different versions of a spatial object. Within the set of all versions of a spatial object, the version identifier is unique. -- Description -- NOTE The maximum length has been selected to allow for time stamps based on ISO 8601, for example, "2007-02-12T12:12:12+05:30" as the version identifier.NOTE 2 The property is void, if the spatial data set does not distinguish between different versions of the spatial object. It is missing, if the spatial object type does not support any life-cycle information. [Source: Feature Catalogue 'INSPIRE application schemas' http://inspire.ec.europa.eu/data-model/approved/r4618/fc/#_C33423]

[0..1] String25Type

5 thematicIdIdentifier -- Definition -- Unique identifier used to identify the spatial object within the specified identification scheme. [Source: Feature Catalogue 'INSPIRE application schemas' http://inspire.ec.europa.eu/data-model/approved/r4618/fc/#_C33431]

[1..1] FeatureUniqueEUCodeType



[1..1] IdentifierSchemaType = euPFRACode

7 beginLifespanVersion -- Definition -- Date and time at which this version of the spatial object was inserted or changed in the spatial data set.


8 endLifespanVersion -- Definition -- Date and time at which this version of the spatial object was superseded or retired in the spatial data set.



-- Definition -- Name, in English. English exonym, or understandable English version of the name of the


24



Data type

geographical feature or spatial object.10

nameText -- Definition -- Name, in the national language. National language endonym, or national language version of the name of the geographical feature or spatial object.


11


[1..1] WiseLanguageCode_Enum

12

validFrom -- Definition -- The date when the phenomenon started to exist in the real world.


13

validTo -- Definition -- The time from which the phenomenon no longer exists in the real world.


14

specificHazardType -- Definition -- Additional classification of the natural hazard that further specifies the hazard type according to a nomenclature that is specific to this dataset.

[1..1] SpecificHazardTypeValue

15

determinationMethod -- Definition --Specifies if the Preliminary Flood Risk Area result is delineated after modelling or determined after interpretation.

[1..1] DeterminationMethodValue

16

probabilityOfOccurrence

-- Definition -- The probability of occurrence of a hazard event, expressed as a value between 0 and 1. ' -- Description --This is the inverse value of the return period.

[0..1] double

17

returnPeriod -- Definition --Long-term average interval of time or number of years within which an event will be equalled or exceeded [UNESCO].

[0..1] double

18

link -- Definition --Hyperlink to where additional information on the Preliminary Floods Risk Areas (PFRA) is available on the web, at national level.

[0..1] URLType

25


Using thematic identifiers to relate two objects with different typesIn WISE, the thematic identifiers are also used to link objects of different types. Figure 1 and provide an overview of the existing associations.

Figure 1. Overview of the relationships between different Floods Directive spatial object types.

26


Quick reference card

27


References

INSPIRE Data Specification on Natural Risk Zones – Technical Guidelines http://inspire.jrc.ec.europa.eu/documents/Data_Specifications/

INSPIRE Metadata Implementing Rules: Technical Guidelines based on EN ISO 19115 and EN ISO 19119. http://inspire.ec.europa.eu/documents/Metadata/MD_IR_and_ISO_20131029.pdf

28


Annex I – GlossaryExtracted from the web page: http://inspire-regadmin.jrc.ec.europa.eu/glossary

Label Definition Description Status

Actor

An actor specifies a role played by a user or any other system that interacts with the system under consideration (UML 2.1.2 Superstructure, Clause 16) Valid

Addressable object

Spatial object type which can have instances to which it is meaningful to associate addresses in the context of the INSPIRE scope.

Note: Most common addressable objects are real properties, cadastral parcels, buildings, entrances to buildings, dwellings, flats, condominiums/common holds etc., inside a building. Addressable objects can also be other types of sites or constructions like mooring places, points of interest, sports fields, parks, traffic terminals, technical constructions, points of service delivery e.g. for utilities, post etc. Valid

Aerodrome reference point

The designated geographical location of an aerodrome, located near the initial or planned geometric centre of the aerodrome and normally remaining where originally established Valid

Airport/Heliport

A defined area on land or water (including any buildings, installations and equipment) intended to be used either wholly or in part for the arrival, departure and surface movement of aircraft/helicopters Valid

Application data Data in support of user requirements

NOTE The term is generally used as a complementary term to &quot reference data". For example, the road network objects is considered &quot reference dataâ€ � and navigation information attached to the road network objects is considered &quot application dataâ€ �. Valid

Application schema

Conceptual schema for data required by one or more applications [ISO 19101] Valid

Aqueduct

A pipe or artificial channel designed to transport water from a remote source, usually by gravity Valid

29

http://inspire-regadmin.jrc.ec.europa.eu/glossary



Aquifer

Subsurface layer or layers of rock or other geological strata of sufficient porosity and permeability to allow either a significant flow of groundwater or the abstraction of significant quantities of groundwater. Valid

Artificial water body

A body of surface water created by human activity. Valid

basic property unit

The basic unit of ownership that is recorded in the land books, land registers or equivalent. It is defined by ownership and homogeneous real property rights, and may be made up of one or several parcels. Retired

Bifurcation A fork or division of a watercourse Valid

Bridge

A man-made structure spanning and providing passage over a body of water, depression, or other obstacles Valid

Cadastral gap

Area which is not supposed to be covered by cadastral parcels, due to national regulation.

EXAMPLE- in many countries, the sea- in France and Belgium, the public domain (roads, rivers)Note: should not be confused with areas not yet surveyed and registered. Valid

Cadastral overlap

Area which may be covered by several cadastral parcels, due to national regulation.

EXAMPLE in United Kingdom, overlapping parcels may occur where rights are registered at the same space but at different heights e.g. a block of flats where an individual parcel is recorded for each flat. Valid

Character string

Means the value domain of metadata elements expressed as a set of characters treated as a unit Valid

CisternA man-made container used for collection or storage of rain water Valid

Class

Description of a set of objects that share the same properties, constraints, and semantics [UML 2.1.2 - modified] Valid

CodelistValue domain including a code for each permissible value [ISO 19136] Valid

Compound coordinate reference system

A coordinate reference system using two other independent coordinate reference systems, one for the horizontal component and one for the vertical component, to describe a position, in accordance with EN ISO 19111 Valid

Conceptual model

Model that defines concepts of a universe of discourse [ISO 19101] Valid

30



Conceptual schema

Formal description of a conceptual model [ISO 19101]

EXAMPLE ISO 19107 contains a formal description of geometrical and topological concepts using the conceptual schema language UML. Valid

Conceptual schema language

Formal language based on a conceptual formalism for the purpose of representing conceptual schemas [ISO 19101]

EXAMPLE UML, EXPRESS, ORM and INTERLIS are examples of conceptual schema languages. Valid

ConfluencePoint where different watercourse branches merge into one Valid

Coordinate reference system

A coordinate reference system is a coordinate system related to an object by a datum (from: ISO 19111:2007). Valid

Coordinate system

A coordinate system specifies how coordinates are to be assigned to points by means of mathematical rules (from: ISO 19111:2007). Valid

Coverage

Spatial object that acts as a function to return values from its range for any direct position within its spatial, temporal or spatiotemporal domain [ISO 19123 - modified]

EXAMPLE Orthoimage, digital elevation model (as grid or TIN), point grids etc. Valid

CP controlled gap

Area which is not supposed to be covered by cadastral parcels, due to national regulation. Gap in the real world Retired

CP controlled overlap

Area which may be covered by several cadastral parcels, due to national regulation. Overlap in the real world. Retired

CP uncontrolled gap

Area which is covered by cadastral parcels in the real world but not in the database. Retired

CP uncontrolled overlap

Area which is covered by only one cadastral parcel in the real world but by several parcels in the database. Retired

Cross section (watercourse)

A series of profiles of the watercourse bed geometry taken along the length of the watercourse Valid

Culvert

A sewer or drain crossing under a road, track, or embankment, without affecting the construction of the crossed feature Valid

Dam

A barrier constructed to hold back water and raise its level to form a reservoir or to prevent flooding. Valid

Data harmonisation

Providing access to spatial data through network services in a representation that allows for combining it with other harmonised data in a coherent way by using a common set of data product specifications

NOTE This includes agreements about coordinate reference systems, classification systems, application schemas, etc. Valid

31



Data interoperability component

Individual aspect that will be addressed to support the interoperability of spatial data sets [DS-D2.5]

EXAMPLE Rules for application schemas, identifier management, terminology, etc. are examples of the components. Valid

Data interoperability process

Process of developing harmonised data product specifications and implementing the necessary arrangements to transform spatial data into interoperable spatial data [DS-D2.5]

NOTE Two general options exist: The reference version of the spatial data set may either be changed/restructured itself (&quot harmonisedâ€�) or it may be kept as-is and the transformation may occur on-the-fly whenever a spatial data service operating on the spatial data set is invoked. In cases where the location of a spatial object has to be changed to comply with Article 10 (2), it is expected that the location information in the reference version of the spatial data set is updated to reflect the mutual consent. Valid

Data product

Data set or data set series that conforms to a data product specification [ISO 19131] Valid

Data product specification

Detailed description of a data set or data set series together with additional information that will enable it to be created, supplied to and used by another party [ISO 19131] Valid

Data set Identifiable collection of data [ISO 19115] ValidData set series

Collection of data sets sharing the same product specification [ISO 19115] Valid

Data specification

(used as a synonym to data product specification)

NOTE If the context is unambiguous, &quot data specificationâ€ � is often used instead of &quot INSPIRE data specificationâ€ � to improve readability. Valid

dataset

identifiable collection of data [ISO 19115:2005, Geographic information â€” Metadata] Retired

Datum

A datum is a parameter or set of parameters that define the position of the origin, the scale, and the orientation of a coordinate system (from: ISO 19111:2007). Valid

Deep water route

A route in a designated area within defined limits which has been accurately surveyed for

Valid

32


Label Definition Description Statusclearance of sea bottom and submerged obstacles to a minimum indicated depth of water

Dike / leveeAn embankment built to restrict the flow of water Valid

Discharge rate Rate of water flow in the segment

units of measure should be a volume rate of flow, e.g. m^3/s Valid

Discovery service (discovery)

Services making it possible to search for spatial data sets and services on the basis of the content of the corresponding metadata and to display the content of the metadata.

The service is included in the classification of the spatial data service types, described in the metadata element "Spatial data service type". Valid

Download service (download)

Service that enables copies of spatial data sets, or parts of such sets, to be downloaded and, where practicable, accessed directly.


Dynamic segmentation

A way of modelling linear networks where segmentation of the linear elements is independent of the attribution.

NOTE Typically dynamic segmentation is achieved by defining the attributes as separate objects having their locations defined by using linear referencing mechanisms, allowing attributes refer to parts of the linear elements. Valid

Endonym

Name of a spatial object in one of the languages occurring in that area where the spatial object is situated [UNGEGN Glossary of Terminology - modified] Valid

Entity Real-world phenomenon [DS-D2.5] ValidEnumeration

Data type whose values are enumeration literals [UML 2.1.2 - modified] Valid

ESDIEuropean spatial data infrastructure as built based on the INSPIRE Directive [DS-D2.5]

NOTE The ESDI is expected to include, for example, additional content beyond the data provided by those that are legally mandated to do so according to the directive. Valid

ETRS89/EVRS

ETRS89/EVRS is a compound (ISO 19111) coordinate reference system used for unambiguous 3D georeferencing in Europe area Retired

Eurocontrol Eurocontrol is the European Organisation for the Safety of Air Navigation. The civil and military intergovernmental organisation now

Valid

33


Label Definition Description Statuscounts 38 Member States from across Europe. It is based in Belgium with specialised offices in six other European countries.

European Terrestrial Reference System 1989 (ETRS89)

European Terrestrial Reference System 1989 (ETRS89) is used as the horizontal component of ETRS89/EVRS Retired

European Vertical Reference System (EVRS)

European Vertical Reference System (EVRS) is used as the vertical component of ETRS89/EVRS. Retired

EuroRoadS

An EC funded project (2003-2006) with the aim of producing a specification framework to support interoperable road information. Valid

Exonym

Name used in a specific language for a spatial object situated outside the area where that language is spoken, and differing in its form from the name used in an official or well-established language of that area where the spatial object is located [UNGEG Valid

External object identifier

Unique object identifier which is published by the responsible body, which may be used by external applications to reference the spatial object [DS-D2.5] Valid

FeatureAbstraction of real world phenomena [ISO 19101]

NOTE The term &quot (geographic) featureâ€ � as used in the ISO 19100 series of International Standards, in other specifications like IHO S-57, and in this document is synonymously with spatial object as used in this document. Unfortunately &quot spatial objectâ€ � is also used in the ISO 19100 series of International Standards, however with a different meaning: a spatial object in the ISO 19100 series is a spatial geometry or topology. Valid

Feature catalogue

Catalogue(s) containing definitions and descriptions of the spatial object types, their attributes and associated components occurring in one or more spatial data sets, together with any operations that may be applied [ISO 19110 â€“ modified] Valid

Feature concept

Concept that may be specified in detail as one or more spatial object types [ISO/DIS

Valid

34


Label Definition Description Status19126 â€“ modified]

Feature concept dictionary

Dictionary that contains definitions of and related descriptive information about concepts that may be specified in detail in a feature catalogue [ISO/DIS 19126] Valid

Feature-related concepts

Abstract specification of the semantics of a property of a spatial object type [DS-D2.5] Valid

FictitiousAn indication that the geometry of the feature is not well defined Valid

Flow direction

Direction of water flow in the segment relative to digitisation of segment geometry Valid

Foreshore

That part of the shore or beach which lies between the low water mark and the coastline/shoreline. The same condition may exist in non-contiguous off-shore areas Valid

Free text

Means the value domain of metadata elements expressed in one or more natural languages Valid

Gazetteer

Directory of instances of a class or classes of features containing some information regarding position [ISO 19112] Valid

General feature model

Meta-model for spatial object types and their property types specified by ISO 19109 [DS-D2.5] Valid

Geodetic coordinate system

A coordinate system in which position is specified by geodetic latitude, geodetic longitude and (in the three-dimensional case) ellipsoidal height, in accordance with EN ISO 19111 Valid

Geodetic datum

Geodetic datum is a datum describing the relationship of a two- or threedimensional coordinate system to the Earth (from: ISO 19111:2007). Valid

Geographic identifier

Spatial reference in the form of a label or code that identifies a location [ISO 19112] Valid

Geographical grid system

Harmonised multi-resolution grid with a common point of origin and standardised location and size of grid cells [INSPIRE Directive]

NOTE 1 Geographical grid systems are not limited to rectified grids or grids using cell axes parallel to the meridians.NOTE 2 This document adopts the definition of the 2003 Workshop on European Reference Grids, which includes not only the grid describing the domain of a coverage but also its range. Thus, a 'geographical grid' is equivalent to an ISO 19123 coverage. The

Valid

35


Label Definition Description Statusunqualified term 'grid' may refer either to a grid geometry or a geographical grid (coverage) depending on the context.

Glacier

A large mass of snow and ice moving slowly down a slope or valley from above the snowline Valid

Grid

Network composed of two or more sets of curves in which the members of each set intersect the members of the other sets in an algorithmic way

NOTE The curves partition a space into grid cells. (from: ISO 19123) Valid

Grid cell A cell delineated by grid curves Valid

Grid pointPoint located at the intersection of two or more curves in a grid (from: ISO 19123) Valid

Groundwater

All water which is below the surface of the ground in the saturation zone and in direct contact with the ground or subsoil. Valid

Harmonised data product specifications

Set of data product specifications that support the provision of access to interoperable spatial data through spatial data services in a representation that allows for combining it with other interoperable spatial data in a coherent way [DS-D2.5]

NOTE 1 The harmonised data product specifications will be based on the data interoperability components. Valid

Heavily modified

An object that may once have been natural, but has been extensively modified

e.g. a river that has been canalised Valid

Heavily modified water body

A body of surface water which as a result of physical alterations by human activity is substantially changed in character, as designated by the Member State in accordance with the provisions of WFD Annex II. Valid

Homologous spatial objects

Set of spatial objects that correspond to the same real-world phenomenon, but are described by different information according to the different levels of details or point of views [DS-D2.5] Valid

Identifier

Linguistically independent sequence of characters capable of uniquely and permanently identifying that with which it is associated [ISO 19135] Valid

Infrastructure for spatial information

Means metadata, spatial data sets and spatial data services network services and technologies agreements on sharing, access and use and coordination and monitoring mechanisms, processes and procedures, established, operated or made available in accorda Valid

INSPIRE application schema

Application schema specified in an INSPIRE data specification [DS-D2.5] Valid

36


Label Definition Description StatusINSPIRE data specification

Harmonised data product specification for a theme adopted as an Implementing Rule [DS-D2.5] Valid

INSPIRE geo-portal

Means an Internet site, or equivalent, providing access to the services referred to in Article 11(1) [INSPIRE Directive] Valid

Inter-modal connection

A connection between two elements in different transport networks that use a different transport mode, giving the possibility to change transported media (people, goods, etc) from one transport mode to another Valid

Internal object identifier

Unique object identifier which is used internally and is not intended to be used to identify or reference the spatial object by external applications [DS-D2.5] Valid

Interoperability

Means the possibility for spatial data sets to be combined, and for services to interact, without repetitive manual intervention, in such a way that the result is coherent and the added value of the data sets and services is enhanced [INSPIRE Directive] Valid

Interoperable spatial data

Spatial data conformant to the harmonised data product specifications [DS-D2.5] Valid

Invoke spatial data service (invoke)

Service that allows defining both the data inputs and data outputs expected by the spatial service and a workflow or service chain combining multiple services. It also allows defining the external web service interface of the workflow or service chain.


Large lake Lakes that have a surface area &gt 500 km2. Valid

Large river

Rivers that have a catchment area &gt 50,000 km2 or main tributaries that have a catchment area &gt 5,000 km2. Valid

Level of detail

Quantity of information that portrays the real world

NOTE The concept comprises data capturing rules of spatial object types, the accuracy and the types of geometries, and other aspects of a data specification. In particular, it is related to the notions of scale and resolution. Valid

Life-cycle information

Set of properties of a spatial object that describe the temporal characteristics of a version of a spatial object or the changes between versions Valid

Life-cycle rules

Rules that specify the types of changes to a spatial object that result in either the creation

Valid

37


Label Definition Description Statusof a new version or in the deletion / retirement of the spatial object

Lineage

Means the history of a data set, and the life cycle from collection and acquisition through compilation and derivation to its current form, in accordance with EN ISO 19101 Valid

Linear element

1-dimensional object that serves as the axis along which linear referencing is performed.

NOTE Also known as curvilinear element. Valid

Linear reference system

Reference system that identifies a location by reference to a segment of a linear spatial object and distance along that segment from a given point [ISO 19116 - modified]

NOTE synonymous with linear referencing system.EXAMPLE kilometre markers along a motorway or railway, references along the centre line of a river spatial object from the intersection with a bridge spatial object. Valid

Linear referencing

Specification of a location relative to a one-dimensional object as a measurement along (and optionally offset from) that element.

NOTE An alternative to specifying a location as a two or three dimensional spatial position. Valid

Linguistic text Text consisting of or related to language ValidMain lake Lakes that have a surface area &gt 10 km2. Valid

Main riverRivers that have a catchment area &gt 500 km2. Valid

Man made watercourse

A watercourse entirely created by man for drainage or transportation purpose, this includes canals and ditches. Valid

Map projection

A change of coordinates, based on a one-to-one relationship, from a geodetic coordinate system to a plane, based on the same datum, in accordance with EN ISO 19111 Valid

Metadata

Means information describing spatial data sets and spatial data services and making it possible to discover, inventory and use them [INSPIRE Directive]

NOTE A more general definition provided by ISO 19115 is "data about data" Valid

Metadata element

Means a discrete unit of metadata, in accordance with EN ISO 19115

Metadata for spatial data sets and spatial data set series includes the following metadata elements (Table 1):- Resource title- Resource abstract- Resource type- Resource locator- Unique resource identifier- Resource language- Topic category- Keyword- Geographic bounding box- Temporal reference- Lineage- Spatial

Valid

38


Label Definition Description Statusresolution- Conformity- Conditions for acess and use- Limitations on public access- Responsible organisation- Metadata point of contact- Metadata date- Metadata languageMetadata for spatial data services includes the following metadata elements (Table 2):- Resource title- Resource abstract- Resource type- Resource locator- Coupled resource- Spatial data service type- Keyword- Geographic bounding box- Temporal reference- Spatial resolution- Conformity- Conditions for acess and use- Limitations on public access- Responsible organisation- Metadata point of contact- Metadata date- Metadata language

Metadata element - Conditions for access and use

This metadata element defines the conditions for access and use of spatial data sets and services, and where applicable, corresponding fees as required by Article 5(2)(b) and Article 11(2)(f) of Directive 2007/2/EC.

The value domain of this metadata element is free text.The element must have values. If no conditions apply to the access and use of the resource, &apos no conditions applyâ€™ shall be used. If conditions are unknown, &apos conditions unknownâ€™ shall be used.This element shall also provide information on any fees necessary to access and use the resource, if applicable, or refer to a uniform resource locator (URL) where information on fees is available. Valid

Metadata element - Conformity

The requirements referred to in Article 5(2)(a) and Article 11(2)(d) of Directive 2007/2/EC relating to the conformity, and the degree of conformity, with implementing rules adopted under Article 7(1) of Directive 2007/2/EC shall be addressed by the follo

7.1. SpecificationThis is a citation of the implementing rules adopted under Article 7(1) of Directive 2007/2/EC or other specification to which a particular resource conforms.A resource may

Valid

39


Label Definition Description Statusconform to more than one implementing rules adopted under Article 7(1) of Directive 2007/2/EC or other specification.This citation shall include at least the title and a reference date (date of publication, date of last revision or of creation) of the implementing rules adopted under Article 7(1) of Directive 2007/2/EC or of the specification.7.2. DegreeThis is the degree of conformity of the resource to the implementing rules adopted under Article 7(1) of Directive 2007/2/EC or other specification.The value domain of this metadata element is defined in Part D.Degree of conformity:1. Conformant (conformant)The resource is fully conformant with the cited specification.2. Not Conformant (notConformant)The resource does not conform to the cited specification.3. Not evaluated (notEvaluated)Conformance has not been evaluated.

Metadata element - Coupled resource

If the resource is a spatial data service, this metadata element identifies, where relevant, the target spatial data set(s) of the service through their unique resource identifiers (URI).

The value domain of this metadata element is a mandatory character string code, generally assigned by the data owner, and a character string namespace uniquely identifying the context of the identifier code (for example, the data owner). Valid

Metadata element - Geographic bounding box

This is the extent of the resource in the geographic space, given as a bounding box.

The bounding box shall be expressed with westbound and eastbound longitudes, and southbound and northbound latitudes in

Valid

40


Label Definition Description Statusdecimal degrees, with a precision of at least two decimals.

Metadata element - Keyword

If the resource is a spatial data service, at least one keyword from Part D.4 shall be provided. If a resource is a spatial data set or spatial data set series, at least one keyword shall be provided from the general environmental multilingual thesaurus

For each keyword, the following metadata elements shall be provided:3.1. Keyword valueThe keyword value is a commonly used word, formalised word or phrase used to describe the subject. While the topic category is too coarse for detailed queries, keywords help narrowing a full text search and they allow for structured keyword search.The value domain of this metadata element is free text.3.2. Originating controlled vocabularyIf the keyword value originates from a controlled vocabulary (thesaurus, ontology), for example GEMET, the citation of the originating controlled vocabulary shall be provided.This citation shall include at least the title and a reference date (date of publication, date of last revision or of creation) of the originating controlled vocabulary.Part D.4 of the Regulation on metadata includes the Classification of spatial data services. The keywords are based on the geographic services taxonomy of EN ISO 19119. This taxonomy is organised in categories, the subcategories defining the value domain of the classification of spatial data services. Valid

Metadata element - Limitations on public access

When Member States limit public access to spatial data sets and spatial data services under Article 13 of Directive 2007/2/EC, this metadata element shall provide information on the limitations and the reasons for them. If there are no limitations on public access, this metadata element shall indicate that fact.

The value domain of this metadata element is free text. Valid

Metadata element -

This is a statement on process history and/or overall quality of the spatial data set. Where

The value domain of this metadata element is free

Valid

41



Lineage

appropriate it may include a statement whether the data set has been validated or quality assured, whether it is the official version (if multiple versions exist) text.

Metadata element - Metadata date

The date which specifies when the metadata record was created or updated.

This date shall be expressed in conformity with ISO 8601. Valid

Metadata element - Metadata language

This is the language in which the metadata elements are expressed.

The value domain of this metadata element is limited to the official languages of the Community expressed in conformity with ISO 639-2. Valid

Metadata element - Metadata point of contact

This is the description of the organisation responsible for the creation and maintenance of the metadata.

This description shall include:â€” the name of the organisation as free text,â€” a contact e-mail address as a character string. Valid

Metadata element - Resource abstract

This is a brief narrative summary of the content of the resource.


Metadata element - Resource language The language(s) used within the resource.

The value domain of this metadata element is limited to the languages defined in ISO 639-2. Valid

Metadata element - Resource locator

The resource locator defines the link(s) to the resource and/or the link to additional information about the resource.

The value domain of this metadata element is a character string, commonly expressed as uniform resource locator (URL). Valid

Metadata element - Resource title

This a characteristic, and often unique, name by which the resource is known.


Metadata element - Resource type

This is the type of resource being described by the metadata.

The value domain of this metadata element is defined in Part D.1.1. Resource type:1.1. Spatial data set series (series)1.2. Spatial data set (dataset)1.3. Spatial data services (services) Valid

Metadata element - Responsible organisation

For the purposes of Article 5(2)(d) and Article 11(2)(g) of Directive 2007/2/EC, the following two metadata elements shall be provided: 9.1. Responsible party 9.2. Responsible party role.

9.1. Responsible partyThis is the description of the organisation responsible for the establishment, management, maintenance and distribution of the

Valid

42


Label Definition Description Statusresource.This description shall include:â€” the name of the organisation as free text,â€” a contact e-mail address as a character string.9.2. Responsible party roleThis is the role of the responsible organisation.The value domain of this metadata element is defined in Part D.Responsible party role:1. Resource Provider (resourceProvider)Party that supplies the resource.2. Custodian (custodian)Party that accepts accountability and responsibility for the data and ensures appropriate care and maintenance of the resource.3. Owner (owner)Party that owns the resource.4. User (user)Party who uses the resource.5. Distributor (distributor)Party who distributes the resource.6. Originator (originator)Party who created the resource7. Point of Contact (pointOfContact)Party who can be contacted for acquiring knowledge about or acquisition of the resource.8. Principal Investigator (principalInvestigator)Key party responsible for gathering information and conducting research.9. Processor (processor)Party who has processed the data in a manner such that the resource has been modified.10. Publisher (publisher)Party who published the resource.11. Author (author)Party who authored the resource.

Metadata element - Spatial data

This is a classification to assist in the search of available spatial data services. A specific service shall be categorised in only one

The value domain of this metadata element is defined in Part D.3 of the

Valid

43



service type category.

Regulation on metadata.3. SPATIAL DATA SERVICE TYPE3.1. Discovery Service (discovery)Services making it possible to search for spatial data sets and services on the basis of the content of the corresponding metadata and to display the content of the metadata.3.2. View Service (view)Service that makes it possible, as a minimum, to display, navigate, zoom in and out, pan or overlay viewable spatial data sets and to display legend information and any relevant content of metadata.3.3. Download Service (download)Service that enables copies of spatial data sets, or parts of such sets, to be downloaded and, where practicable, accessed directly.3.4. Transformation Service (transformation)Service that enables spatial data sets to be transformed with a view to achieving interoperability.3.5. Invoke Spatial Data Service (invoke)Service that allows defining both the data inputs and data outputs expected by the spatial service and a workflow or service chain combining multiple services. It also allows defining the external web service interface of the workflow or service chain.3.6. Other Service (other)

Metadata element - Spatial resolution

Spatial resolution refers to the level of detail of the data set. It shall be expressed as a set of zero to many resolution distances (typically for gridded data and imagery-derived products) or equivalent scales (typically for maps or map-derived product

An equivalent scale is generally expressed as an integer value expressing the scale denominator.A resolution distance shall be expressed as a numerical value associated with a unit of length. Valid

44



Metadata element - Temporal reference

This metadata element addresses the requirement to have information on the temporal dimension of the data as referred to in Article 8(2)(d) of Directive 2007/2/EC. At least one of the metadata elements referred to in points 5.1 to 5.4 shall be provided.

The value domain of the metadata elements referred to in points 5.1 to 5.4 is a set of dates. Each date shall refer to a temporal reference system and shall be expressed in a form compatible with that system. The default referencesystem shall be the Gregorian calendar, with dates expressed in accordance with ISO 8601.5.1. Temporal extentThe temporal extent defines the time period covered by the content of the resource. This time period may be expressed as any of the following:â€” an individual date,â€” an interval of dates expressed through the starting date and end date of the interval,â€” a mix of individual dates and intervals of dates.5.2. Date of publicationThis is the date of publication of the resource when available, or the date of entry into force. There may be more than one date of publication.5.3. Date of last revisionThis is the date of last revision of the resource, if the resource has been revised. There shall not be more than one date of last revision.5.4. Date of creationThis is the date of creation of the resource. There shall not be more than one date of creation. Valid

Metadata element - Topic category

The topic category is a high-level classification scheme to assist in the grouping and topic-based search of available spatial data resources.

2. TOPIC CATEGORIES IN ACCORDANCE WITH EN ISO 191152.1. Farming (farming)Rearing of animals and/or cultivation of plants.This category applies to Directive 2007/2/EC spatial data theme Annex III(9) Agricultural and aquaculture facilities.2.2.

Valid

45


Label Definition Description StatusBiota (biota)Flora and/or fauna in natural environment.This category applies to the following Directive 2007/2/EC spatial data themes: Annex III(17) Bio-geographical regions, Annex III(18) Habitats and biotopes, Annex III(19) Species distribution.2.3. Boundaries (boundaries)Legal land descriptions.This category applies to the following Directive 2007/2/EC spatial data themes: Annex I(4) Administrative units, Annex III(1) Statistical units.2.4. Climatology / Meteorology / Atmosphere (climatologyMeteorologyAtmosphere)Processes and phenomena of the atmosphere.This category applies to the following Directive 2007/2/EC spatial data themes: Annex III(13) Atmospheric conditions, Annex III(14) Meteorological geographical features.2.5. Economy (economy)Economic activities, conditions and employment.This category applies to the following Directive 2007/2/EC spatial data themes: Annex III(20) Energy resources, Annex III(21) Mineral resources.2.6. Elevation (elevation)Height above or below sea level.This category applies to the following Directive 2007/2/EC spatial data theme: Annex II(1) Elevation.2.7. Environment (environment)Environmental resources, protection and conservation.This category applies to the following Directive 2007/2/EC spatial data theme: Annex I(9)

46


Label Definition Description StatusProtected sites.2.8. Geoscientific Information (geoscientificInformation)Information pertaining to earth sciences.This category applies to the following Directive 2007/2/EC spatial data themes: Annex III(3) Soil , Annex II(4) Geology, Annex III(12) Natural risk zones.2.9. Health (health)Health, health services, human ecology, and safety.This category applies to the following Directive 2007/2/EC spatial data theme: Annex III(5) Human health and safety.2.10. Imagery / Base Maps / Earth Cover (imageryBaseMapsEarthCover)Base maps.This category applies to the following Directive 2007/2/EC spatial data themes: Annex II(3) Orthoimagery, Annex II(2) Land cover.2.11. Intelligence / Military (intelligenceMilitary)Military bases, structures, activities.This category does not apply specifically to any Directive 2007/2/EC spatial data themes.2.12. Inland Waters (inlandWaters)Inland water features, drainage systems and their characteristics.This category applies to the following Directive 2007/2/EC spatial data theme: Annex I(8) Hydrography.2.13. Location (location)Positional information and services.This category applies to the following Directive 2007/2/EC spatial data themes: Annex I(3) Geographical names, Annex I(5) Addresses.2.14. Oceans (oceans)Features and characteristics of salt

47


Label Definition Description Statuswater bodies (excluding inland waters).This category applies to the following Directive 2007/2/EC spatial data themes: Annex III(16) Sea regions, Annex III(15) Oceanographic geographical features.2.15. Planning / Cadastre (planningCadastre)Information used for appropriate actions for future use of the land.This category applies to the following Directive 2007/2/EC spatial data themes: Annex I(6) Cadastral parcels, Annex III(4) Land use, Annex III(11) Area management/restriction/regulation zones &amp reporting units.2.16. Society (society)Characteristics of society and cultures.This category applies to the following Directive 2007/2/EC spatial data themes: Annex III(10) Population distribution â€“ demography.2.17. Structure (structure)Man-made construction.This category applies to the following Directive 2007/2/EC spatial data themes: Annex III(2) Buildings, Annex III(8) Production and industrial facilities, Annex III(7) Environmental monitoring facilities.2.18. Transportation (transportation)Means and aids for conveying persons and/or goods.This category applies to the following Directive 2007/2/EC spatial data theme: Annex I(7) Transport networks.2.19. Utilities / Communication (utilitiesCommunication)Energy, water and waste systems and communications infrastructure and

48


Label Definition Description Statusservices.This category applies to the following Directive 2007/2/EC spatial data theme: Annex III(6) Utility and governmental services.

Metadata element - Unique resource identifier A value uniquely identifying the resource.

The value domain of this metadata element is a mandatory character string code, generally assigned by the data owner, and a character string namespace uniquely identifying the context of the identifier code (for example, the data owner). Valid

Multicultural

Multiplicity in systems of values held by different groups: ethnic, regional, or professional [Hofstede G. 1980. Cultureâ€™s Consequences, Sage: London â€“ modified] Valid

MultilingualIn or using several languages [Oxford Dictionary] multilingual Valid

Multiple representation

Representation of the relationship between homologous spatial objects [DS-D2.5] multiple representation Valid

Namespace

Means a collection of names, identified by a uniform resource identifier (URI) reference, which are used in extensible markup language (XML) documents as element names and attribute names Valid

Natura2000

Natura 2000 is a European Union-wide network of nature protection areas established under the 1992 Habitats Directive. The aim of the network is to assure the long-term survival of Europe's most valuable and threatened species and habitats. It is comprised of Special Areas of Conservation (SAC) designated by Member States under the Habitats Directive, and also incorporates Special Protection Areas (SPAs) designated under the 1979 Birds Directive. The establishment of this network ofprotected areas also fulfils a Community obligation under the UN Convention on Biological Diversity. Valid

Natural watercourse

Natural rivers and streams naturally preserved and that have been canalised either for navigation or for preventing flood disaster Valid

Navaid equipment

A physical navaid equipment placed on the Earth surface, like Very High Frequency Omnidirectional Radio Range (VOR), Distance Measuring Equipment (DME), localizer,

Valid

49


Label Definition Description StatusTactical Air Navigation Beacon (TACAN) etc., which help in guiding aircraft traffic safely

ObjectIn this document used synonymous with spatial object object Valid

Object referencing

Consistent method of referencing spatial data to location using existing spatial objects [DS-D2.5] object referencing Valid

Ontology

Representation of a set of concepts within a domain and the relationships between those concepts [Wikipedia] Valid

Other service (service) N/a


Postal address

Set of information which, for a postal item, allows the unambiguous determination of an actual or potential delivery point, usually combined with the specification of an addressee and/or mailee. (Universal Postal Union 2006)

Note: The description of postal delivery points most often uses the common address comÂ¬ponents like e.g. thoroughfare name and locator (address number etc.), in addition they can also include specific postal designations like post codes and P.O. box identifiers. Although these postal designators originally were intended solely for the use of the postal service, especially the post code has frequently been adopted and used for other purposes â€“ as a generic place identifier. Valid

Profile

Set of one or more base standards or subsets of base standards, and, where applicable, the identification of chosen clauses, classes, options and parameters of those base standards, that are necessary for accomplishing a particular function [ISO 19106]

NOTE A profile is derived from base standards so that by definition, conformance to a profile is conformance to the base standards from which it is derived. Valid

Property Plot of land and fixed objects attached to it.

Note 1: may include, but not restricted to, real property.Note 2: may not have a one to one relationship with cadastral parcel. Valid

Protected Area

Protected Sites and Protected Areas are synonymous. Valid

Protected Site

A Protected Site is an area designated or managed within a framework of international,

Valid

50


Label Definition Description StatusCommunity and Member States' legislation to achieve specific conservation objectives. Protected Sites and Protected Areas are synonymous.

Public authority

Means:(a) any government or other public administration, including public advisory bodies, at national, regional or local level (b) any natural or legal person performing public administrative functions under national law, including specific duties, ac Valid

Quality

Means the totality of characteristics of a product that bear on its ability to satisfy stated and implied needs, in accordance with EN ISO 19101 Valid

Railway yard

An area crossed by a number of parallel railway tracks (usually more than two) interconnected between them, which are used to stop trains in order to load / unload freight without interrupting the traffic of a main railway line Valid

Reference data

Spatial objects that are used to provide location information in object referencing [DS-D2.5]

NOTE Typical reference data are topographic or cadastral data. Valid

Reference grid

Reference grid is a grid defined in the real world in order to be used for indirect geo-referencing. Retired

Reference model

Architectural framework for a specific context, e.g. an application or an information infrastructure [DSD2.5] Valid

Register

Set of files containing identifiers assigned to items with descriptions of the associated items [ISO 19135] Valid

RegistryInformation system on which a register is maintained [ISO 19135] register Valid

Resolution

Resolution expresses the size of the smallest object in a spatial data set that can be described. It refers to the amount of detail that can be discerned. It is also known as granularity. Resolution is also limited because geo-spatial databases are intent

NOTE In a regular gridded coverage (e.g. raster data in 2D grids), resolution expresses the area in the real world that is represented by the size of a raster cell. Valid

Resource

Means an information resource that has a direct or indirect reference to a specific location or geographic area Valid

River basin

The area of land from which all surface run-off flows through a sequence of streams, rivers and, possibly, lakes into the sea at a single river mouth, estuary or delta. Valid

River basin district

The area of land and sea, made up of one or more neighbouring river basins together with their associated groundwaters and coastal waters, which is identified under Article 3(1)

Valid

51


Label Definition Description Statusas the main unit for management of river basins.

RiverbankThe limit line between the water area of a river and the area of land. Valid

Scale

The relation between the dimensions of features on a map and the geographic objects they represent on the earth, commonly expressed as a fraction or a ratio. A map scale of 1/100,000 or 1:100,000 means that one unit of measure on the map equals 100,000 of

NOTE A data set has no real scale as the user may choose at which scale he or she wants to display it. Nevertheless, it is usually not appropriate to display a data set at an arbitrary scale, so typically some scale information is associated with a data set (or its data product specification). This may be a scale range or a medium scale (i.e. it is relevant to use and display the data set around this &quot medium scaleâ€ �). Valid

Significant point

A specified geographical location used to define an Air Traffic Service (ATS) route, the flight path of an aircraft or for other navigation/ATS purposes Valid

Sluice gate A gate used to regulate the flow of water Valid

SnowfieldA large area permanently covered by snow or ice over land or water. Valid

Spatial data Means any data with a direct or indirect reference to a specific location or geographical area [INSPIRE Directive]

NOTE The use of the word &quot spatialâ€ � in INSPIRE is unfortunate as in the everyday language its meaning goes beyond the meaning of &quot geographicâ€� â€“ which is considered by the Drafting Team as the intended scope â€“ and includes subjects such as medical images, molecules, or other planets to name a few. However, since the term is used as a synonym for geographic in the draft Directive, this document uses the term &quot spatial dataâ€� as a synonym for the term &quot geographic dataâ€ � used by the ISO 19100 series of International Standards and which is defined as &quot data

Valid

52


Label Definition Description Statuswith implicit or explicit reference to a location relative to the Earth.â€ �

Spatial data services

Means the operations which may be performed, by invoking a computer application, on the spatial data contained in spatial data sets or on the related metadata Valid

Spatial data services - classification

N/a 4. CLASSIFICATION OF SPATIAL DATA SERVICESThe keywords are based on the geographic services taxonomy of EN ISO 19119. This taxonomy is organised in categories, the subcategories defining the value domain of the classification of spatial data services.100 Geographic human interaction services (humanInteractionService)This category comprises the following subcategories:101 Catalogue viewer (humanCatalogueViewer)Client service that allows a user to interact with a catalogue to locate, browse, and manage metadata about geographic data or geographic services.102 Geographic viewer (humanGeographicViewer)Client service that allows a user to view one or more feature collections or coverages.103 Geographic spreadsheet viewer (humanGeographicSpreadsheetViewer)Client service that allows a user to interact with multiple data objects and to request calculations similar to an arithmetic spreadsheet but extended to geographic data.104 Service editor (humanServiceEditor)Client service that allows a user to control geographic processing services.105 Chain definition editor

Valid

53


Label Definition Description Status(humanChainDefinitionEditor)Provides user interaction with a chain definition service.106 Workflow enactment manager.(humanWorkflowEnactmentManager)Provides user interaction with a workflow enactment service.107 Geographic feature editor (humanGeographicFeatureEditor)Geographic viewer that allows a user to interact with feature data.108 Geographic symbol editor (humanGeographicSymbolEditor)Client service that allows a human to select and manage symbol libraries.109 Feature generalisation editor (humanFeatureGeneralizationEditor)Client service that allows a user to modify the cartographic characteristics of a feature or feature collection by simplifying its visualisation, while maintaining its salient elements â€“ the spatial equivalent of simplification.110 Geographic data-structure viewer (humanGeographicDataStructureViewer)Client service that allows a user to access part of data set to see its internal structure.200 Geographic model/information management service (infoManagementService)This category comprises the following subcategories:201 Feature access service (infoFeatureAccessService)Service that provides a client access to and management of a feature store.202 Map access service (infoMapAccessService)Service that provides a

54


Label Definition Description Statusclient access to a geographic graphics, i.e. pictures of geographic data.203 Coverage access service (infoCoverageAccessService)Service that provides a client access to and management of a coverage store.204 Sensor description service (infoSensorDescriptionService)Service that provides the description of a coverage sensor, including sensor location and orientation, as well as the sensorâ€™s geometric, dynamic, and radiometric characteristics for geo-processing purposes.205 Product access service (infoProductAccessService)Service that provides access to and management of a geographic product store.206 Feature type service (infoFeatureTypeService)Service that provides a client to access to and management of a store of feature type definitions.207 Catalogue service (infoCatalogueService)Service that provides discovery and management services on a store of metadata about instances.208 Registry Service (infoRegistryService)Service that provides access to store of metadata about types.209 Gazetteer service (infoGazetteerService)Service that provides access to a directory of instances of a class or classes of real-world phenomena containing some information regarding position.210 Order handling service (infoOrderHandlingServic

55


Label Definition Description Statuse)Service that provides a client with the ability to order products from a provider.211 Standing order service (infoStandingOrderService)Order handling service that allows a user to request that a product over a geographic area be disseminated when it becomes available.300 Geographic workflow/task management services (taskManagementService)This category comprises the following subcategories:301 Chain definition service (chainDefinitionService)Service to define a chain and to enable it to be executed by the workflow enactment service.302 Workflow enactment service (workflowEnactmentService)The workflow enactment service interprets a chain and controls the instantiation of services and sequencing of activities.303 Subscription service (subscriptionService)Service to allow clients to register for notification about events.400 Geographic processing services â€“ spatial (spatialProcessingService)This category comprises the following subcategories:401 Coordinate conversion service (spatialCoordinateConversionService)Service to change coordinates from one coordinate system to another coordinate system that is related to the same datum.402 Coordinate transformation service (spatialCoordinateTransformationService)Service to change coordinates from

56


Label Definition Description Statusa coordinate reference system based on one datum to a coordinate reference system based on a second datum.403 Coverage/vector conversion service (spatialCoverageVectorConversionService)Service to change the spatial representation from a coverage schema to a vector schema, or vice versa.404 Image coordinate conversion service (spatialImageCoordinateConversionService)A coordinate transformation or coordinate conversion service to change the coordinate reference system for an image.405 Rectification service (spatialRectificationService)Service for transforming an image into a perpendicular parallel projection and therefore a constant scale.406 Orthorectification service (spatialOrthorectificationService)A rectification service that removes image tilt and displacement due to terrain elevation.407 Sensor geometry model adjustment service (spatialSensorGeometryModelAdjustmentService)Service that adjusts sensor geometry models to improve the match of the image with other images and/or known ground positions.408 Image geometry model conversion service (spatialImageGeometryModelConversionService)Service that converts sensor geometry models into a different but equivalent sensor geometry model.409 Subsetting service (spatialSubsettingService)Service that extracts data

57


Label Definition Description Statusfrom an input in a continuous spatial region either by geographic location or by grid coordinates.410 Sampling service (spatialSamplingService)Service that extracts data from an input using a consistent sampling scheme either by geographic location or by grid coordinates.411 Tiling change service (spatialTilingChangeService)Service that changes the tiling of geographic data.412 Dimension measurement service (spatialDimensionMeasurementService)Service to compute dimensions of objects visible in an image or other geodata.413 Feature manipulation services (spatialFeatureManipulationService)Register one feature to another, an image, or another data set or coordinate set correcting for relative translation shifts, rotational differences, scale differences, and perspective differences. Verify that all features in the Feature Collection are topologically consistent according to the topology rules of the Feature Collection, and identifies and/or corrects any inconsistencies that are discovered.414 Feature matching service (spatialFeatureMatchingService)Service that determines which features and portions of features represent the same real world entity from multiple data sources, e.g., edge matching and limited conflation.415 Feature generalisation service (spatialFeatureGeneralizationService)Service that

58


Label Definition Description Statusreduces spatial variation in a feature collection to increase the effectiveness of communication by counteracting the undesirable effects of data reduction.416 Route determination service (spatialRouteDeterminationService)Service to determine the optimal path between two specified points based on the input parameters and properties contained in the Feature Collection.417 Positioning service (spatialPositioningService)Service provided by a position-providing device to use, obtain and unambiguously interpret position information, and determines whether the results meet the requirements of the use.418 Proximity analysis service (spatialProximityAnalysisService)Given a position or geographic feature, finds all objects with a given set of attributes that are located within a user-specified distance of the position or feature.500 Geographic processing services â€“ thematic (thematicProcessingService)This category comprises the following subcategories:501 Geoparameter calculation service (thematicGoparameterCalculationService)Service to derive application-oriented quantitative results that are not available from the raw data itself.502 Thematic classification service (thematicClassificationService)Service to classify regions of geographic data based on thematic attributes.503 Feature generalisation service

59


Label Definition Description Status(thematicFeatureGeneralizationService)Service that generalises feature types in a feature collection to increase the effectiveness of communication by counteracting the undesirable effects of data reduction.504 Subsetting service (thematicSubsettingService)Service that extracts data from an input based on parameter values.505 Spatial counting service (thematicSpatialCountingService)Service that counts geographic features.506 Change detection service (thematicChangeDetectionService)Service to find differences between two data sets that represent the same geographical area at different times.507 Geographic information extraction services (thematicGeographicInformationExtractionService)Services supporting the extraction of feature and terrain information from remotely sensed and scanned images.508 Image processing service (thematicImageProcessingService)Service to change the values of thematic attributes of an image using a mathematical function.509 Reduced resolution generation service (thematicReducedResolutionGenerationService)Service that reduces the resolution of an image.510 Image Manipulation Services (thematicImageManipulationService)Services for manipulating data values in images: changing colour and contrast values, applying various filters, manipulating

60


Label Definition Description Statusimage resolution, noise removal, &apos stripingâ€™, systematic-radiometric corrections, atmospheric attenuation, changes in scene illumination, etc.511 Image understanding services (thematicImageUnderstandingService)Services that provide automated image change detection, registered image differencing, significance-ofdifference analysis and display, and area-based and model-based differencing.512 Image synthesis services (thematicImageSynthesisService)Services for creating or transforming images using computer-based spatial models, perspective transformations, and manipulations of image characteristics to improve visibility, sharpen resolution, and/or reduce the effects of cloud cover or haze.513 Multiband image manipulation (thematicMultibandImageManipulationService)Services that modify an image using the multiple bands of the image.514 Object detection service (thematicObjectDetectionService)Service to detect real-world objects in an image.515 Geoparsing service (thematicGeoparsingService)Service to scan text documents for location-based references, such as a place names, addresses, postal codes, etc., in preparation for passage to a geocoding service.516 Geocoding service (thematicGeocodingService)Service to augment location-based text references with

61


Label Definition Description Statusgeographic coordinates (or some other spatial reference).600 Geographic processing services â€“ temporal (temporalProcessingService)This category comprises the following subcategories:601 Temporal reference system transformation service (temporalReferenceSystemTransformationService)Service to change the values of temporal instances from one temporal reference system to another temporal reference system.602 Subsetting service (temporalSubsettingService)Service that extracts data from an input in a continuous interval based on temporal position values.603 Sampling service (temporalSamplingService)Service that extracts data from an input using a consistent sampling scheme based on temporal position values.604 Temporal proximity analysis service (temporalProximityAnalysisService)Given a temporal interval or event, find all objects with a given set of attributes that are located within a userspecified interval from the interval or event.700 Geographic processing services â€“ metadata (metadataProcessingService)This category comprises the following subcategories:701 Statistical calculation service (metadataStatisticalCalculationService)Service to calculate the statistics of a data set.702 Geographic annotation

62


Label Definition Description Statusservices (metadataGeographicAnnotationService)Services to add ancillary information to an image or a feature in a feature collection.800 Geographic communication services (comService)This category comprises the following subcategories:801 Encoding service (comEncodingService)Service that provides implementation of an encoding rule and provides an interface to encoding and decoding functionality.802 Transfer service (comTransferService)Service that provides implementation of one or more transfer protocols, which allows data transfer between distributed information systems over offline or online communication media.803 Geographic compression service (comGeographicCompressionService)Service that converts spatial portions of a feature collection to and from compressed form.804 Geographic format conversion service (comGeographicFormatConversionService)Service that converts from one geographic data format to another.805 Messaging service (comMessagingService)Service that allows multiple users to simultaneously view, comment about, and request edits of feature collections.806 Remote file and executable management (comRemoteFileAndExecutableManagement)Service that provides access to secondary storage of geographic features as if it were local to the client.

63


Label Definition Description StatusSpatial data set

Means an identifiable collection of spatial data [INSPIRE Directive] Valid

Spatial data set series

Means a collection of spatial data sets sharing the same product specification Valid

Spatial object

Means an abstract representation of a real-world phenomenon related to a specific location or geographical area [INSPIRE Directive]

NOTE It should be noted that the term has a different meaning in the ISO 19100 series. It is also synonymous with "(geographic) feature" as used in the ISO 19100 series. Valid

Spatial object type Classification of spatial objects [DS-D2.5]

NOTE In the conceptual schema language UML a spatial object type will be described by a class with stereotype &lt &lt FeatureType&gt &gt . Valid

Spatial reference system

System for identifying position in the real world [ISO 19112]

NOTE Spatial reference systems do not necessarily use coordinates to identify a position. Valid

Spatial schema

Conceptual schema of spatial geometries and topologies to be used in an application schema [DSD2.5] Valid

SpringA flow of water rising or welling naturally from the earth. Valid

Static segmentation

A way of modelling geographic information in general and linear networks in particular where the segmentation of the elements is dependent on the set of attributes defined for the linear element.

NOTE A linear element describing a road segment using this approach must be split in smaller segments whereever an attribute (such as road width, speed limit, pavement type) changes value. Valid

Sub-basin

The area of land from which all surface run-off flows through a series of streams, rivers and, possibly, lakes to a particular point in a water course (normally a lake or a river confluence). Valid

TankA container used for the storage of liquids or gases Valid

Temporal reference system

Reference system against which time is measured [ISO 19108] Valid

Temporal schema

Conceptual schema of temporal geometries and topologies to be used in an application schema [DS-D2.5] Valid

Thematic identifier

Descriptive unique object identifier applied to spatial objects in a defined information theme [DSD2.5] Valid

64



ThemeGrouping of spatial data according to Annex I, II and III of the INSPIRE Directive [DS-D2.5] Valid

Third partyMeans any natural or legal person other than a public authority [INSPIRE Directive] Valid

Topological gap

Area which is covered by cadastral parcels in the real world but not in the database.

EXAMPLE topological gaps may occur when assembling cadastral parcels coming from several cadastral sheets or after format conversions. Valid

Topological overlap

Area which is covered by only one cadastral parcel in the real world but by several parcels in the database.

EXAMPLE topological overlaps may occur when assembling cadastral parcels coming from several cadastral sheets or after format conversions. Valid

Transformation

An act, process, or instance of change in structure, appearance, or character [Webster]

NOTE In the context of INSPIRE two types of transformations are in particular relevant. The transformation of coordinates from one reference system to another and the transformation of a query or data instance from one application schema to another. Valid

Transformation service (transformation)

Service that enables spatial data sets to be transformed with a view to achieving interoperability.


Unique object identifier

Identifier associated with a spatial object [DS-D2.5] Valid

UnitDefined quantity in which dimensioned parameters are expressed [ISO 19111] Valid

Universe of discourse

View of the real or hypothetical world that includes everything of interest [ISO 19101] Valid

Use case

A use case defines a goal-oriented set of interactions between actors and the system under consideration. Valid

Vanishing point

Point where a watercourse disappears underground Valid

Version Particular variation of a spatial object NOTE A version of a spatial object is associated with a version identifier allowing to

Valid

65


Label Definition Description Statusdistinguish two versions of the same spatial object. Versions are usually also associated with temporal information allowing a user to analyse the evolution of a spatial object. EXAMPLE If a spatial object type Building has an attribute functionalUse, the value of the attribute changes due to a change in the way the building is used, and the life-cycle rules of the data set specify that a change in this attribute value will result in a new version, then a new version will be created and the existing version will be marked as superseded in its life-cycle information â€“ often by specifying an end date/time for the lifespan of the version.

View service (view)

Service that makes it possible, as a minimum, to display, navigate, zoom in and out, pan or overlay viewable spatial data sets and to display legend information and any relevant content of metadata.


WellA hole drilled or dug into the earth or sea bed for the extraction of liquids or gases Valid

Wharf

A structure built along or at an angle to the shore of navigable waters so that ships may lie alongside to receive and discharge cargo and passenger Valid

66


Annex II: Recommendations on How to Publish Downloadable Datasets Compliant with INSPIRE Directive In this section, more details on INSPIRE Implementing Rules are given, and specific recommendations with regard to their use for implementation.

INSPIRE Compliance OverviewINSPIRE provides a common European framework for interoperability, specifying how datasets can be assembled and published so that they are interoperable and can be used in cross-border scenario’s such flooding (70% of all fresh water bodies in Europe are part of trans-boundary river basins). The choice of how this should be done is down to the community of users. INSPIRE makes data interoperable – it does not improve the information contained within a dataset.The fundamental components are shown in Error: Reference source not found.Figure 2. Conceptual overview of Inspire Components.

cmp InspireOv erv iew

InspireNetworkService

InspireDataObject

DataSet

+ Inspire_GCM

+ Inspire_HD+ Inspire_OF

+ Inspire_SD+ Inspire_SR

«interface»View Serv ice

+ Portrayal Rules

MetaData

+ InspireCore

+ ThematicExtension

«interface»DownloadServ ice

+ download formats

«interface»CatalogueServ ice

An Inspire dataset shall be basedon the Inspire general conceptual model (GCM). The GCM shall extended to be specific to each of the Inspire themes.

A dataset shall only correspond to one Inspire Theme

«user story»Find and ev lauate

a dataset of interest A

«user story»View a map or

chart of the data in a standardized way

«user story»Download a numeric representation of the data for downstream

analysis

An Inspire data object needs to be available via an Inspire network service

Core Inspire Metadata shall be used to describe a data set to support its discovery

The core metadata can be extended with thematic metadata descibedBy

Download a numeric representation of the data for downstream analysisA download service provides a standard way to access a data set. This can include the ability to query a data set in space and time, select features in that dataset and download the results in the form of a dataset. In order to do this, the download service requires:

A dataset in a standard format A set of rules for supported download formats

67


As with the view service, the dataset needs to comply with the specifications of one of the Inspire annexes and the same constraints/requirements therefore apply. The data itself may be stored in database tables, or files or a hybrid of the two. INSPIRE doesn’t mandate how the data is stored – this is largely a matter of deployment efficiency, e.g. available technology or structure of the data. There should, however, be a standard way to query the content of the dataset (especially time, feature and spatial extent) e.g. according to the OGC Web Feature Service or Web Coverage Service specification.It should be noted that how the data is stored can be different to the download formats. In addition, the format delivered to the user is not fixed. INSPIRE makes recommendations in the technical guidance on download formats, but a community may request other formats to be included. Note: A format for data must specify both an encoding and content model.It should also be noted that it is possible under INSPIRE to pre-package data downloads; this means the extent and content of the download is defined by the data publisher.

MetadataData sets and the Spatial Data Services providing them need to be able to be interrogated by the parties requiring the provided information to be made available. In INSPIRE two equally important requirements must be met to address this need:

Data and service providers need to describe their resources (both datasets and services) using the metadata elements according to the corresponding INSPIRE Regulations;

Discovery Services need to be set up in order to provide online access to query the provided metadata mentioned above.

The following documentation should be used for the implementation of the first of the abovementioned requirements:

Commission Regulation (EC) No 1205/2008 of 3 December 2008 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards metadata and subsequent amendments1

INSPIRE Metadata Implementing Rules Technical Guidelines based on EN ISO 19115 and EN ISO 19119 (version 1.3)2

Technical Guidance for the implementation of INSPIRE dataset and service metadata based on ISO/TS 19139:2007 (version 2.0.1)3

The metadata elements defined as “metadata required for interoperability” are actually defined in Article 13 of the Implementing Rules on the Interoperability of Spatial Datasets and Services4.Spatial datasets and dataset series metadataThe metadata needed for datasets and datasets series according to INSPIRE are described in Error: Reference source not found5.Table 1. Metadata requirements

Element name INSPIRE multiplicity INSPIRE obligation / condition / noteResource title 1 Mandatory Resource abstract 1 Mandatory Resource type 1 Mandatory Resource locator 0..* Mandatory if a URL is available to obtain more

information on the resources and/or access related services.

Unique resource identifier 1..* Mandatory

1 https://inspire.ec.europa.eu/Legislation/Metadata/65412 https://inspire.ec.europa.eu/documents/inspire-metadata-implementing-rules-technical-guidelines-based-en-iso-19115-

and-en-iso-13 https://inspire.ec.europa.eu/id/document/tg/metadata-iso191394 https://inspire.ec.europa.eu/Legislation/Data-Specifications/2892

68


Element name INSPIRE multiplicity INSPIRE obligation / condition / noteResource language 0..* Mandatory if the resource includes textual information. Topic category 1..* Mandatory Keyword value 1..* Mandatory Originating controlled vocabulary

0..1 Conditional: Mandatory for each keyword if the keyword value originates from a controlled vocabulary

Geographic bounding box 1..* Mandatory Temporal reference At least one of Temporal extent, Date of publication,

Date of last revision or Date of creation must be givenTemporal extent 0..* Conditional Date of publication 0..* Conditional Date of last revision 0..1 Conditional Date of creation 0..1 Conditional Lineage 1 Mandatory Spatial resolution 0..* Mandatory if an equivalent scale or a resolution distance

can be specified Conformity 1..* Mandatory Specification 1 Mandatory for each conformity statement Degree 1 Mandatory for each conformity statement Conditions applying to access and use

1..* Special values for unknown conditions or no applying conditions may be used

Limitations on public access

1..* Special value for no limitations may be used

Responsible organisation 1..* Mandatory Responsible party 1 Mandatory for each responsible organisation Responsible party role 1 Mandatory for each responsible organisation Metadata point of contact 1..* Mandatory Metadata date 1 Mandatory Metadata language 1 Mandatory

Spatial data services metadataThe metadata needed for spatial data services according to INSPIRE are described in Error: Reference source not found6.Table 2. Metadata requirements for spatial data services

Element name INSPIRE multiplicity INSPIRE obligation / condition / note Resource title 1 Mandatory Resource abstract 1 Mandatory Resource type 1 Mandatory Resource locator 0..* Conditional, mandatory if linkage to service is available Coupled resource 0..* Conditional, mandatory if linkage to data sets on which

the service operates are available. Spatial data service type 1 Mandatory Keyword value 1..* Mandatory Originating controlled vocabulary

0..1 Conditional, mandatory for each keyword if the keyword value originates from a controlled vocabulary

Geographic bounding box 0..* Conditional, mandatory for services with an explicit geographic extent.

Temporal reference At least one of Temporal extent, Date of publication, Date of last revision or Date of creation must be given

Temporal extent 0..* Conditional Date of publication 0..* Conditional Date of last revision 0..1 Conditional Date of creation 0..1 Conditional Spatial resolution 0..* Mandatory when there is a restriction on the spatial

resolution for this service Conformity 1..* Mandatory Specification 1 Mandatory for each conformity statement Degree 1 Mandatory for each conformity statement Conditions applying to access and use

1..* Special values for unknown conditions or no applying conditions may be used

Limitations on public access

1..* Special value for no limitations may be used

69


Element name INSPIRE multiplicity INSPIRE obligation / condition / note Responsible organisation 1..* Mandatory Responsible party 1 Mandatory for each responsible organisation Responsible party role 1 Mandatory for each responsible organisation Metadata point of contact 1..* Mandatory Metadata date 1 Mandatory Metadata language 1 Mandatory Category 0..1 Conditional, mandatory for an Invocable Spatial Data

Service in order to comply with Annex V of [Regulation 1089/2010]

Coordinate Reference System Identifier

1..* Mandatory if relevant for an Interoperable Spatial Data Service in order to comply with Annex VI of [Regulation 1089/2010]

Quality of service 3..* Mandatory for an Interoperable Spatial Data Service. Three criteria for minimum quality of service shall be given to comply with Annex VI of [Regulation 1089/2010]: Availability, Performance and Capacity

Invocation metadata 1..* Mandatory for a Harmonised Spatial Data Service in order to comply with Annex VII of [Regulation 1089/2010]

Interoperability of spatial datasets and services metadataError: Reference source not found7 describes the metadata elements defined as “metadata required for interoperability” in Article 13 of the Implementing Rules on the Interoperability of Spatial Datasets and Services. They are applicable to all Spatial Data Themes.Table 7. Metadata requirements

Metadata element Definition Multiplicity Condition

Coordinate reference system

Description of the coordinate reference system(s) used in the data set.

1..*

Temporal reference system

Description of the temporal reference systems used in the dataset.

0..* Mandatory, if the spatial data set or one of its feature types contains temporal information that does not refer to the Gregorian Calendar or the Coordinated Universal Time.

Encoding Description of the computer language construct(s) specifying the representation of data objects in a record, file, message, storage device or transmission channel.

1..*

Character encoding The character encoding used in the data set.

0..* Mandatory if an encoding is used that is not based on UTF-8.

Spatial representation type

The method used to spatially represent geographic information.

1..*

Data Quality–Logical consistency–Topological consistency Correctness of the explicitly encoded

topological characteristics of the data set as described by the scope.

0..* Mandatory if the data set includes types from the Generic Network Model and does not assure centreline topology (connectivity of centrelines) for the network.

70


INSPIRE metadata toolsA metadata editor tool is available in the INSPIRE geoportal5 to generate metadata files in XML encoding for spatial data sets, series and network services. In addition, a RESTful Web service that can be invoked by HTTP request to validate INSPIRE Metadata is also available6.The validator is not intended to be an operational tool, and at the time of writing only supports validation against version 1.3 of the metadata technical guidelines. All the files of the Validator including documentation are available under EU Public License from the JoinUp Platform7.Currently, the design and implementation of a new more comprehensive INSPIRE validator containing validation functionality for data sets, services and metadata is in progress under the work of the MIG sub project MIWP 2016.3: Validation and conformity testing, with the support of the ISA Action ARE3NA (A Reusable INSPIRE Reference Platform)8 and its follow-up ISA2 Action ELISE (Enabling Digital Government through Geospatial and Location Intelligence)9 The current validator already includes, among others, the tests for the Metadata TG version 1.3; the component providing the Abstract and Executable Test Suites for the TG version 2.0 are yet to be developed. More links to validate data sets, services and metadata are:

Interoperability Test Bed: https://joinup.ec.europa.eu/asset/itb/home A reusable open source reference tool for testing INSPIRE data, metadata and

services:https://github.com/interactive-instruments/etf-webapphttps://hub.docker.com/r/iide/etf-webapp/

An online tutorial entitled "Developing Abstract and Executable Test Suites for the INSPIRE validator:https://joinup.ec.europa.eu/elibrary/presentation/developing-abstract-and-executable-test-suites-inspire-validator

Network servicesNetwork Services10 are services provided for in Article 11(1) of INSPIRE Directive for the discovery, viewing, download and transformation of spatial data sets and services and services allowing spatial data services to be invoked. The service shall be conformant regarding the specific requirements in Regulation 976/200911.Member States shall establish and operate a network of the following services for the spatial data sets and services for which metadata have been created in accordance with this Directive:

Discovery Services View Services Download Services Transformation Services Services allowing spatial data services to be invoked

Experience in the Member States has shown that it is important, for the successful implementation of an infrastructure for spatial information, that a minimum number of services be made available to the public free of charge. Member States should therefore make available, as a minimum and free of charge the following 12 :

Discovery Services View Services

5 http://inspire-geoportal.ec.europa.eu/editor6 http://inspire-geoportal.ec.europa.eu/validator2 7 https://joinup.ec.europa.eu/software/validator/home8 https://joinup.ec.europa.eu/community/are3na/description9 https://ec.europa.eu/isa2/actions/elise_en10 https://inspire.ec.europa.eu/network-services/4111 https://inspire.ec.europa.eu/Legislation/Network-Services/4112 http://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32007L0002&rid=1

71

https://inspire.ec.europa.eu/network-services/41

https://hub.docker.com/r/iide/etf-webapp/

https://github.com/interactive-instruments/etf-webapp

https://joinup.ec.europa.eu/asset/itb/home

https://joinup.ec.europa.eu/community/are3na/description

https://joinup.ec.europa.eu/software/validator/home

http://inspire-geoportal.ec.europa.eu/validator2

http://inspire-geoportal.ec.europa.eu/editor


According to COMMISSION REGULATION (EC) No 976/2009 of 19 October 200913, the INSPIRE Directive obliges MS to provide:

Not later than 2011

Member States shall provide the Discovery and View Services in conformity with this Regulation.

Not later than 2012

Member States shall provide the Download Services in conformity with this Regulation.

Member States shall provide the Transformation Services in conformity with this Regulation.

For the purpose of publishing data for exchanging purposes, view and download services will be required to be accessible and discoverable through a Member States SDI.

Representation of the INSPIRE service bus

Network services and spatial data services are accessed by applications and geoportals via the INSPIRE service bus and available through the INSPIRE Geoportal.INSPIRE Discovery servicesINSPIRE Discovery Services allow users and computer programs to search for spatial datasets and services based on their metadata records. The INSPIRE Discovery Services are implemented in a consistent and compatible way across Europe and are based on European and International standards and current practices.

The following operations must be implemented: Get Discovery Service Metadata: Provides all necessary information about the

Discovery Service and describes service capabilities. Discover Metadata: Allows requesting INSPIRE metadata elements of spatial data

sets and services from a Discovery Service. Publish Metadata: Allows editing of INSPIRE metadata elements of resources in the

Discovery Service (push or pull metadata mechanisms). Editing meaning insert, update and delete.

Link Discovery Service: Allows the declaration of the availability of a Discovery Service for the discovery of resources through the Member State Discovery Service while maintaining the resource metadata at the owner’s location.

13 http://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:02009R0976-20101228&from=EN

72


For detailed information see document “Technical Guidance for the implementation of INSPIRE Discovery Services”14. INSPIRE View Services requirementsAs definition, view services should allow, as a minimum, display, navigate, zoom in/out, pan, or overlay spatial datasets and display legend information and any relevant content of metadata.The following) documentation should be used for the implementation of View Services:

Commission Regulation (EC) No 976/2009 of 18 October 2009 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards the Network Services (INSPIRE Network Services regulation)15.

INSPIRE Technical Guidance for INSPIRE View Services (version 3.11)16.The INSPIRE Technical Guidance for View Services (version 3.1) offers a viable delivery solution based on an extended implementation of the [ISO 19128] – Web Map Service (WMS version 1.3). In summary, regular WMS are tagged with INSPIRE metadata elements through declared extended capabilities elements in the GetCapabilities response from the WMS. This response is described in the Network Services Regulation as the Get View Service Metadata operation.The INSPIRE View Service profile is designed to implement the operations described in the following sections which are mandated in the Network Service regulation.INSPIRE View Services operationsA compliant INSPIRE View Service must support the operations of Error: Reference source not found.See Annex V, INSPIRE view services specifications, for Table 6.Other parameters needed to publish INSPIRE View Service are:

1. Coordinate reference system: INSPIRE View Service layers must be able to be simultaneously viewed using a single coordinate reference system and the View Service shall support at least the Coordinate Reference Systems in Annex I, point 1 of Directive 2007/2/EC.

2. Image format: INSPIRE View Services must support at least one of the following image formats: The Portable Network Graphics (PNG) format, The Graphics Interchange Format (GIF), without compression

INSPIRE View Services qualityThe quality of spatial services is critical to ensure the usefulness of the end applications and user satisfaction. However, there are no standards of how to measure this, and the methods and tools used can give different results. One recommended way to set up the quality of the services can be the Technical Guidance for the implementation of INSPIRE View Services mentioned above, in particular its Annex F “Quality of Services”. This annex only concerns the performance, capacity and availability of the services. It establishes that a test image (470 kilobytes – 800x600 colour 8 bits) should be served in less than 5 seconds in normal situation. The minimum number of simultaneously served service requests to a view service, according to the performance quality of service, shall be 20 per second.Apart from the performance and availability, some other aspects should be considered17: INSPIRE compatibility, using the official validators for services, when applies: as INSPIRE

is coming into a practical implementation phase there is a great need of tools for validation (metadata, service and data). There is a validation service (Webservice)

14 https://inspire.ec.europa.eu/documents/technical-guidance-implementation-inspire-discovery-services-015 https://inspire.ec.europa.eu/documents/commission-regulation-ec-no-9762009-19-october-2009-implementing-directive-

20072ec16 https://inspire.ec.europa.eu/documents/technical-guidance-implementation-inspire-view-services-117 See https://github.com/inspire-eu-validation/ and https://github.com/inspire-eu-validation/view-service/tree/master/iso-19128)

73

https://github.com/inspire-eu-validation/view-service/tree/master/iso-19128

https://github.com/inspire-eu-validation/

https://inspire.ec.europa.eu/documents/technical-guidance-implementation-inspire-discovery-services-0


available at the EU-portal and some countries have also developed tools for validation of metadata and services, for instance in the Netherlands and Germany. These validators might include slightly different interpretations of standards. To ensure that result from a test of conformity are identical, a common, officially approved, validator should be accessible from INSPIRE web site.

Language check: The default language for the service must be provided in order the user to be able to know which language can be expected to be used if the capabilities document when no language is explicitly requested.

Layers comprehension: For the default style of each harmonized layer, the default style specified in the corresponding data specification (or, if none was specified, the default style according to the INSPIRE Generic Conceptual Model [INS GCM]) has to be used.

Layers order: A containing Category Layer itself includes a Name by which a map portraying all of the nested layers can be requested at once.

Bounding box correctness: The minimum bounding rectangle of the area covered by the Layer in all supported CRS shall be given. The bounding box shall be expressed in decimal degree with a precision of at least 2 decimals.

Initial zoom: If the type of the resource was dataset or series, Each spatial resolution is either an equivalent scale OR a ground sample distance.

Portrayal check: A containing Category Layer itself includes a Name by which a map portraying all of the nested layers can be requested at once.

Coordinate reference systems check: Verify that all references to spatial coordinate reference systems are using one of the http URIs approved for use in INSPIRE data sets. All INSPIRE spatial datasets must be provided at using at least one geographical coordinate system based on either ETRS89 (for datasets within continental Europe) or ITRS (outside continental Europe).

Compatibility with any tool, such as ArcGIS, QGIS: If a linkage for a service is available, the Resource Locator shall be a valid URL providing one of the following:

- A link to a web with further instructions- A link to a service capabilities document- A link to the service WSDL document (SOAP Binding)- A link to a client application that directly accesses the service

UTF encoding: UTF-8 has been the dominant character encoding for the World Wide Web since 2009, and as of October 2017 accounts for 89.9% of all Web pages. The W3C recommends UTF-8 as the default encoding in XML and HTML.

Formats and attributes correctness: GetMap operation metadata shall be mapped to the wms:GetMap element in the GetCapabilities response. Either PNG or GIF format (without LZW compression) with transparency shall be supported by the View service INS NS, Annex III, Part B. Furthermore, when a layer is requested in one of the supported formats, the response should be encoded in this format.

Examine the data set against the requirements associated with the GML application schema defined in the INSPIRE schemas: https://inspire.ec.europa.eu/schemas/.INSPIRE Download Services requirementsAs definition, download services, enable copies of complete spatial datasets, or of parts of such sets, to be downloaded.

74


The following documentation should be used for the implementation of Download Services: Commission Regulation (EU) No 1088/2010 of 23 November 2010 amending

Regulation (EC) No 976/2009 as regards download services and transformation services18.

Technical Guidance for the implementation of INSPIRE Download Services Version 3.119

Technical Guidance for the implementation of INSPIRE Download Services using Web Coverage Services (WCS)20.

INSPIRE Download Services operationsIn order to be in conformity with Article 11(1) (c) of Directive 2007/2/EC, the Download Service shall at least provide the operations listed in Error: Reference source not found.

Download services operations

Operation RoleGet Download Service Metadata

Provides all necessary information about the service, the available Spatial Data Sets, and describes the service capabilities.

Get Spatial Data Set The Get Spatial Data Set operation allows the retrieval of a Spatial Data Set.Describe Spatial Data Set This operation returns the description of all the types of Spatial Objects

contained in the Spatial Data Set.Link Download Service Allows the declaration, by a Public Authority or a Third Party, of the availability of

a Download Service for downloading Spatial Data Sets or, where practicable, Spatial Objects, through the Member State’s Download Service while maintaining the downloading capability at the Public Authority or the Third Party location.

Options for INSPIRE Download Services ImplementationThe INSPIRE Network Services Regulation provides two abstract options for the delivery of Download Services:

1. Implementation of pre-defined dataset download service(s): A pre-defined dataset download service provides for the simple download of pre-defined datasets (or pre-defined parts of a dataset) with no ability to query datasets or select user-defined subsets of datasets. A pre-defined dataset or a pre-defined part of a dataset could be (for example) a file stored in a dataset repository, which can be downloaded as a complete unity with no possibility to change content, whether encoding, the coordinate reference system, etc.

2. Direct access download service(s): A direct access download service extends the functionality of a pre-defined dataset download service to include the ability to query and download subsets of datasets. The direct access download service allows more control over the download than the simple download of a pre-defined dataset or pre-defined part of a dataset. It can therefore be considered to be more advanced than pre-defined dataset download. In this case, the spatial information is typically stored in a repository (e.g. a database) and only accessible through a middleware data management system (although the precise implementation may vary). The term direct access is used to mean the capability of a client application or client service to interact directly with the contents of the repository, e.g. by retrieving parts of the repository based upon a query. The query can be based upon spatial or temporal criteria, or by specific properties of the instances of the spatial object types contained in the repository.

18

19 https://inspire.ec.europa.eu/documents/technical-guidance-implementation-inspire-download-services20 https://inspire.ec.europa.eu/id/document/tg/download-wcs

75

Documents

circabc.europa.eu · Web viewIn cases where the MS has not used either UoM or APSFR the MS needs to report a 'bounding box' where they have available national FHRM and report the