INSPIRE Technical Guidances for View and Discovery Network .../media/Geopunt/Geowijzer/INSPIRE... · 1. INSPIRE in a nutshell 2. Network Services in a nutshell 3. The Guidelines 4

INSPIRE Technical Guidances for View and Discovery Network Services

Thursday 20th of January 2011, Ghent

Bart Cosyn & Joeri Robbrecht

Welcome!

INSPIRE Technical Guidances

Agenda / Ordre du jour � 1. INSPIRE in a nutshell� 2. Network Services in a nutshell� 3. The Guidelines� 4. Common approaches for View & Discovery� 5. Discovery Service TG� Lunch break� 6. View Service TG� 7. INSPIRE Domain Model� 8. The Road Ahead� 9. Q&A / Discussion

This information session will be held in English. Questions can be asked in English, French or

Dutch. Generally, answers will be given in English. If we cannot answer your question, we will write it

down and get back to you with an answer. These sessions are interactive. So if you have questions,

don’t hesitate to ask them. We are native Dutch speaking, so forgive us any lingual hickups.

Please provide us your e-mail so that we can contact you.


INSPIRE in a Nutshell

Bringing data together through a Spatial Data Infra structure

Data easily discoverable

and accessible to users

Like a road infrastructure makes it possible to

connect different sites, a spatial data infrastructure

makes it possible to connect data located at

different sources

Easier development of new applications

and services

Institutionalframework

Information Services

Fundamental data sets

Technical standards

Components


� INSPIRE lays down general rules to establish an infrastructure for spatial information in Europe for the purposes of Community environmental policies and policies or activities which may have an impact on the environment.

� INSPIRE to be based on the infrastructures for spatial information established and operated by the Member States.

� INSPIRE does not require collection of new spatial data

� INSPIRE does not affect existing Intellectual Property Rights

INSPIRE Directive – General Provisions


INSPIRE ComponentsI. Metadata

II. Harmonisation and interoperability of spatial data sets and services

III. Network services (discovery, view, download, transform, middleware)

IV. Data and Service sharing (policy)V. Coordination and measures for Monitoring & Reporting

INSPIRE is a Framework DirectiveDetailed technical provisions for the issues above will be laid

down in Implementing Rules (IR)IRs will be submitted to the Committee (comitology)Once decided, IRs will be published as a Regulation


INSPIRE Spatial Data Scope

Annex I1. Coordinate reference systems2. Geographical grid systems3. Geographical names4. Administrative units5. Addresses6. Cadastral parcels7. Transport networks8. Hydrography9. Protected sites

Annex I1. Coordinate reference systems2. Geographical grid systems3. Geographical names4. Administrative units5. Addresses6. Cadastral parcels7. Transport networks8. Hydrography9. Protected sites

Annex II1. Elevation2. Land cover3. Ortho-imagery4. Geology

Annex II1. Elevation2. Land cover3. Ortho-imagery4. Geology

Harmonised spatial data specifications more stringent for Annex I and II than for Annex III


Annex III1. Statistical units2. Buildings3. Soil4. Land use5. Human health and safety6. Utility and governmental

services7. Environmental monitoring

facilities8. Production and industrial

facilities9. Agricultural and

aquaculture facilities10.Population distribution –

demography

Annex III1. Statistical units2. Buildings3. Soil4. Land use5. Human health and safety6. Utility and governmental

services7. Environmental monitoring

facilities8. Production and industrial

facilities9. Agricultural and

aquaculture facilities10.Population distribution –

demography

11.Area management/restriction/regulation zones & reporting units

12.Natural risk zones13.Atmospheric conditions14.Meteorological geographical

features15.Oceanographic geographical

features16.Sea regions17.Bio-geographical regions18.Habitats and biotopes19.Species distribution20.Energy Resources21.Mineral resources

11.Area management/restriction/regulation zones & reporting units

12.Natural risk zones13.Atmospheric conditions14.Meteorological geographical

features15.Oceanographic geographical

features16.Sea regions17.Bio-geographical regions18.Habitats and biotopes19.Species distribution20.Energy Resources21.Mineral resources

INSPIRE Thematic Scope


Documents

• INSPIRE Directive• Implementing Rules (Regulations,

Decisions

• This is the law, no room for discussion

The Law

• Guidance documents• Framework documents

• These are best practices, gathered and documented by expert groups. These document should be used during implementation to achieve interoperability between MemberStates. No legal obligation.

Advisory


Legal Documents

Legal documents (The Law)• Directive 2007/2/EC of the European Parliament and of the Council of

14 March 2007 establishing an Infrastructure for Spatial Information in the European Community (INSPIRE) 14.03.2007

• INSPIRE Metadata Regulation 03.12.2008• Commission Decision regarding INSPIRE monitoring and

reporting 05.06.2009• Regulation on INSPIRE Network Services 19.10.2009• Regulation on INSPIRE Data and Service Sharing 29.03.2010• COMMISSION REGULATION implementing Directive 2007/2/EC of

the European Parliament and of the Council as regards interoperability of spatial data sets and services 10.12.2010

• Commission Regulation amending Regulation (EC) No 976/2009 as regards download services and transformation service 10.12.2010


Advisory Documents

Advisory (common sense) documents• Data specifications (Annex I, II & III)• Technical Guidances for INSPIRE Network Services• Technical reports & architecture documents• INSPIRE good practice in data and service sharing• Guidances for monitoring and reporting• Reference documents (definitions, glossaries)• And so on …

• These documents (legal & advisory) and more information ontheir purpose is available at http://inspire.jrc.ec.europa.eu


INSPIRE in a Nutshell – BE organisation


INSPIRE in a Nutshell – Timing Implementation Timetable

Milestone date Description

24th December 2010 Metadata available for spatial data corresponding to Annex I and II9th May 2011 Discovery and view services operational with IOC

9th November 2011 Discovery and view services operational

May 2012Download and Transformation services operational wi th IOC

November 2012 Download and Transformation services operational

June 2012 Newly collected and extensively restructured Annex I spatial data sets available

24th December 2013 Metadata available for spatial data corresponding to Annex III

January 2015 Newly collected and extensively restructured Annex II and III spatial data sets available

June 2017 Other Annex I spatial data sets available in accordance with IRs for Annex I

30-May-2019 Other Annex II and III spatial data sets available in accordance with IRs for Annex II and III


INSPIRE Network Servicesin a Nutshell

Network services


Overview INSPIRE NetworkService Use cases


Implementation proces of INSPIRE Network Services

Implementingrule +

amendements

DRAFT Technical Guidance

Testing Technical Guidance

Implementation as IOC Implementation

Drafting teams IOC Task Force Member States


Proces: Status

Service IR Draft TG Test TG

Discovery X X X Feb 2011

View X X X Feb 2011

Transformation X X

Download X X

Invoke

Spatial Data Service

?


Documents


� “Initial Operating Capability” means the ability of a Network Service to provide full functionality without guaranteeing • quality of service in conformity with the rules set out in

Regulation, or • access to the service for all users through the INSPIRE

geo-portal� Not later than 18 months after the date of entry

into force of the network services Regulation, Member States shall provide the Discovery and View Services with initial operating capability.

May 9th 2011

Initial Operating Capability


Initial Operating Capability Task Force

� Purpose• to help and support the implementation of INSPIRE in the

Member States� Scope

• architectural aspects and implementation of Network Services to ensure interoperability with the INSPIRE geoportal and among Member States

� Focus on • Update of the INSPIRE Discovery and View Services

Technical Documentation/Guidelines



� Produce unambiguous specifications, which minimize as much as possible diversity in interpretation for implementation

� Best Practices and preliminary implementations of INSPIRE services in the Member States

� Help promote exchange of experiences, according to National policies and the INSPIRE Directive and Regulations.


� 2 representatives per MS – Belgium: Joeri Robbrecht –Bart Cosyn

� IOC TF services team: FI, DK, DE, FR, PL, AUT, UK, (NL), BE, CZ, EC

� Service team edited TG and released TG 2.12 after agreement by IOC TF (Krakau)

� Service team tests TG 2.12 and will release a new version February 2011.

� First phase project lead by AUT, BE edited View, DK edited Discovery

� Second phase project lead by UK, BE tests View, BE partially edited View, EC tests Discovery and View

� Third phase: Editing by Commission, final tests



IOC TF Services team� Edited and tested Technical Guidance (last official

release = 2.12 of June 2010)� Produced Remarks towards drafting teams

• Data specifcations: naming conventions• Metadata (use of ISO and IETF for language parameter)

� INSPIRE Domain model� Limited the scope of IOC TF

• Use of existing standards CSW, WMS etc ..• No geoRM for first phase• No SOAP for View (use of existing implementations)

� Requested clarifications to EC• Implementation of Link View• Set up of registries for INSPIRE


Phased Approach

First decisions/solutions:

Phase I (2010 – May 2011)

• Use existing standards• Language parameter• Service Response Metadata• Link View/Discovery Service• INSPIRE metadata• Need for testing => testboard

Phase II (June 2011+)

• Common GeoRM solution• SOAP


Overview over the meetings

Rotterdam Jun. 2009

Ispra Oct. 2009

Vienna Meeting Jan. 2010

Amersfoort Mar. 2010

Gent May 2010

Krakow Jun. 2010

KickoffIOCTF

Phase I / IIDomain Model

TG´s 2.1Language Par.

TG´s v2.1Comments Resolution

TG´s v2.12release

KickoffService Team

„Issues List“


Edinburgh Sep. 2010

Ispra Oktober 2010

Kopenhagen Jan 2011

Testingprogress

TG´s v2.12review

TG´s v3release

Overview over the meetings

+ several intermediate TELECON meetings


Towards full-ISO and back� From start the suggestion to set up a specific INSPIRE

schema� Request to stay close to ISO� From tests appeared problems with different versions of ISO

schemas (GML, codelists ….)� New implementation started in october 2010 with specific

schemas for INSPIRE. � Mainly changes in the examples. Basic agreements on the

global solution is still valid


Towards full-ISO and back� Interesting discussions within IOC TF:

• How to map to ISO?

• How to keep it simple and in accordance with the legal requirements

• Keep different guidelines in line with each other

• How to avoid that current implementations fail after upgrading to an INSPIRE compliant implementation

� Result: Move from a simple implementation with special INSPIRE elements towards TG 2.12 were ISO namespaces and elements were used to define specific INSPIRE elements. In line with ISO/TS19139

� From tests appeared problems with different versions of ISO schemas (GML, codelists ….)

� New implementation started in October 2010 with specific schemas for INSPIRE. Mainly changes in the examples and element values. The global mapping remained


IOC TF Services team� Demonstrates implementations:

• GDI-Vlaanderen: testbed- http://discovery.beta.agiv.be/soap/csw.svc?wsdl

- http://ogc.beta.agiv.be/ogc/wms/vrbgINSP?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetCapabilities

• http://wms.geoimage.at/dop-1mfree-beta101221/?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetCapabilities (Austria)

• WMTS of Poland and France• Validator for CSW by Germany (http://www.gdi-

de.org/testprogramm)� Online INSPIRE schemas:

• http://www.inspire-geoportal.eu/schemas/latest/




Common approaches for INSPIRE Network ServicesDiscovery Service Technical GuidanceView Service Technical Guidance

Common Approachesfor Discovery and View

Metadata / Language

Basic concept to extend OGC for INSPIRE requirements

Client – LayerService – Layer

Network Service


Basic concept to extend OGC for INSPIRE requirements

Client – LayerService – Layer

TG base on OGC-Standards

INSPIRE requirements via OGC-Extension-mechanism:

e.g Language, metadata

use OGC-Extension-mechanismfor additional INSPIRE requirements

standard OGC-Client still works with

INSPIRE Network Service

Clients may use additionalfunctionality of

INSPIRE Network Servicee.g. INSPIRE-Geoportal (EU)

mandatory for each NS !


Principles to implement INSPIRE Language requirements

1. INSPIRE requires NS to declare what languages are supported (it is mandatory to support at least one language)

2. required:1. Additional Parameter “Language” for GetCapabilities-Operation

(http/get) to be supported2. Extended Capabilities declare

1. the list of supported languages and 2. the current language3. the default language


Principles to implement INSPIRE Language requirements

Affected operations:WMS.GetCapabilities: ExtendedCapabilities

+ translated natural language fields (title, abstract)

CSW.GetCapabilities: ExtendedCapabilities+ translated natural language fields

(title, abstract)CSW.GetRecord: already supported by

CSW2.0.2AP_ISO1.0

Optional:common concept for other operations (http/get and http/post)e.g. WMS.GetMap() if required (currently not required)


example


Activity Diagrams for clarity


Principles to implement INSPIRE metadata

requirements (Get Service Metadata operation)

� GetCapabilities response includes the INSPIRE metadata elements

� Service Metadata2 scenarios to choose from for publishing INSPIRE service

metadata

• Scenario 1- Discovery based

– Reference in the extended capabilities to anINSPIRE service metadata record in a Discoverycatalogue

• Scenario 2- (Extended) Capabilities

– INSPIRE service metadata is described in capabilities and extended capabilities



requirements (Get Service Metadata operation)

� GetCapabilities response: Scenario 1• <metadataURL> (extended capability) is used to reference

the INSPIRE service metadata available through an INSPIRE Discovery service.

• INSPIRE Service metadata is managed separate from the service in the Discovery catalogue.

• Mandatory CSW ISO AP/ISO 19128:2005(E)-WMS 1.3.0 metadata elements shall be mapped to INSPIRE metadata elements to realize a consistent interface.

• This scenario assumes the existence of INSPIRE metadata for the network service in an INSPIRE Discovery catalogue.

• To fulfill the specific language requirements of the NS regulation, a language section still needs to be added in the extended capability of the service

• The schema for the extended capabilities is described in the TG’s.



requirements (Get Service Metadata operation)� GetCapabilities response: Scenario 2

• All INSPIRE metadata elements are mapped to CSW ISO AP / 19128:2005(E) – WMS1.3.0 capabilities

• The mapping is provided in the Technical Guideline.• INSPIRE metadata elements that cannot be mapped to

standard capabilities are implemented as extended capabilities and mapped to ISO19115:2003 types (ISO/TS 19139 encoding) in v2.12. (this has changed in the latest version, where proprietary INSPIRE xml types are used again)

• Metadata is published through the service capabilities document.

• To fulfill the specific language requirements of the NS regulation, a language section is added in the extended capabilities.

• The schema for the extended capabilities is described in the TG’s.


Extended capabilities XML schema v2.12 forview services (still under construction)<?xml version="1.0" encoding="UTF-8"?>

<schema

xmlns:inspire_vs="http://inspire.europa.eu/networkservice/view/1.0"

... version="1.0.0">

<import namespace= ... />

<element name="ExtendedCapabilities" type="inspire_vs:ExtendedCapabilitiesType"

substitutionGroup="wms:_ExtendedCapabilities"/>

<complexType name="ExtendedCapabilitiesType">

...

<sequence>

<element name="ResourceLocator" type="gmd:CI_OnlineResource_Type"minOccurs="0"/>

<element name="MetadataUrl" type="gmd:CI_OnlineResource_Type" minOccurs="0"/>

<element name="ResourceType" type="gmd:MD_ScopeCode_PropertyType"

minOccurs="0"/>

<element name="TemporalReference" type="gmd:EX_Extent_Type" minOccurs="0"/>

<element name="Conformity" type="gmd:DQ_ConformanceResult_Type" minOccurs="0"

maxOccurs="unbounded"/>

<element name="MetadataPointOfContact" type="gmd:CI_ResponsibleParty_Type"

minOccurs="0"/>

<element name="MetadataDate" type="gco:Date_Type" minOccurs="0"/>

<element name="SpatialDataServiceType" type="srv:SV_ServiceType_Type"

minOccurs="0"/>

<element name="InspireKeywords" type="gmd:MD_Keywords_Type" minOccurs="0"/>

<element name="Languages" type="inspire_vs:LanguagesType" minOccurs="0"/>

<element name="CurrentLanguage" type="inspire_vs:LanguageType"/>

</sequence>

</complexType>

...

</schema>

INSPIRE namespace

INSPIRE service metadata

INSPIRE Language support

Overriding the abstract

wms:_ExtendedCapabilities element


Most recent version of the Extended Capabilities

XML schema http://inspire.ec.europa.eu/schemas/latest/

XML structure changes, principle stays the same


INSPIRE Discovery ServiceTechnical Guideline v2.12 and Up

1. Implementing Rules for Discovery Services

2. Technical Guidance document

� General background

� INSPIRE specific constraints� Discovery Service operations overview � Request and response parameters for all operations� Discovery Service queryables� Multilingual aspects

Content


The Implementing Rules for Discovery services document consists of:

1. Abstract model with operations and their parameters2. Search criteria3. Performance requirements

• Performance • Availability• Capacity

Contents IR document for Discovery service (The Law)


Implementing Rules for Discovery ServicesAbstract model operations (1)

In order to be in conformity with Article 11(1) of the Directive 2007/2/EC, the Discovery Service shall provide the operations listed in Table 3 of this Annex.

Operation Role

Get DiscoveryService Metadata

Provides all necessary information about the serviceand describes service capabilities.

Discover Metadata The Discover Metadata operation allows requestingINSPIRE metadata elements of resources based on aquery statement to be retrieved from the targetDiscovery Service.


In order to be in conformity with Article 12 of Directive 2007/2/EC, the Discovery Service shall support the operations listed in Table 4 of this Annex.

Operation Role

Publish Metadata The Publish Metadata operation allows to edit INSPIREmetadata elements of resources in the DiscoveryService (push or pull metadata mechanisms). Editingmeaning insert, update and delete

Link DiscoveryService

The Link Discovery Service function allows thedeclaration of the availability of a Discovery Service forthe Discovery of resources through the Member StateDiscovery Service while maintaining the resourcemetadata at the owner location

Implementing Rules for Discovery ServicesAbstract model operations (2)


Implementing Rules for Discovery ServicesSearch criteria (1)

[1] See Article 11 (2) of the directive.

In order to be in conformity with the minimum set of search criteria set out in Article 11(2) of Directive 2007/2/EC, the Discovery Service shall support searching with the INSPIRE metadata elements (listed in Annex II of the Commission Regulation on Network Services). Minimum search criteria INSPIRE metadata elements

keywords Keywordclassification of spatial data and services;

(For spatial data sets and spatial data set series)

Topic category

classification of spatial data and services

(For spatial data services)

Spatial data service type

the quality and validity of spatial data sets Lineagethe quality and validity of spatial data sets Spatial resolutiondegree of conformity with the implementing rulesprovided for in Article 7(1) of Directive 2007/2/EC

Specification

degree of conformity with the implementing rulesprovided for in Article 7(1) of Directive 2007/2/EC

Degree

geographical location Geographic bounding boxconditions applying to the access to and use of spatialdata sets and services

Conditions applying to access and use

conditions applying to the access to and use of spatialdata sets and services

Limitations on public access

the public authorities responsible for theestablishment, management, maintenance anddistribution of spatial data sets and services

Responsible party

the public authorities responsible for theestablishment, management, maintenance anddistribution of spatial data sets and services

Responsible party role


Implementing Rules for Discovery ServicesSearch criteria (2)

[1] See Article 11 (2) of the directive.

The following INSPIRE metadata elements or set of elements shall be also available as search criteria:(a) Resource Title;(b) Resource Abstract;(c) Resource type;(d) Unique Resource Identifier;(e) Temporal Reference.

To allow for discovering resources through a combination of search criteria, logical and comparison operators shall be supported.To allow for discovering resources based on the geographic location of the resource, the spatial operator listed in Table 2 shall be supported.

Operator Name PropertyIntersects Requires the Geographic Bounding

Box INSPIRE metadata element tointersect a defined Area of Interest


PerformanceThe response time for sending the initial response to a Discovery service

request shall be maximum 3 seconds in normal situation.

Normal situation represents periods out of peak load. It is set at 90% of the time.

CapacityThe minimum number of served simultaneous requests to a discovery service

according to the performance Quality of Service shall be 30 per second.

AvailabilityThe probability of a Network Service to be available shall be 99% of the time.

Implementing Rules for Discovery ServicesQuality of Service


The base specification of an INSPIRE Discovery Service is [CSW ISO AP] as defined by [INS DIS].

Although this specification [CSW ISO AP] lays down the basic behaviour of an INSPIRE Discovery Service some aspects need to be extended with respect to the requirements of the INSPIRE Directive and the Implementing Rules for Metadata [INS MD]. These aspects are:• Discovery Service Operations • Discovery Service Queryables• Discovery Service Multilingual aspects

This is an INSPIRE profile of [CSW ISO AP].

[CSW ISO AP] = OGC™ Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile for CSW 2.0, version 1.0.0 (2007)

[INS DIS] = COMMISSION REGULATION (EC) No 976/2009 of 19 October 2009 , Implementing Directive 2007/2/EC of the European

Parliament and of the Council as regards the Network Services

[INS MD] = INSPIRE Metadata Regulation, Commission Regulation (EC) No 1205/2008

Discovery Service Technical GuidanceGeneral Background


Discovery Service Technical GuidanceINSPIRE specific constraints

SC1. Link Discovery Service is mandatory. This means that in any case, the federated search through a GetRecords request shall be supported (probable not a correct constraint since federated isn’t mentioned in the Directive or the Commission Regulation -> needs to be discussed in IOC TF NS ST)

SC2. The list of federated catalogues, if any, shall be advertised on the capabilities document of the INSPIRE Discovery Service instance

SC3. The additional search attributes listed in Annex II of the Commission Regulation are mandatory and shall be supported

SC4. The additional search attributes listed in Annex II of the Commission Regulation 4 shall be advertised on the capabilities document of the INSPIRE Discovery Service instance

SC5. The resource type ‘http://www.isotc211.org/schemas/2005/gmd’ shall be supported in case of a supported harvesting operation

Commission Regulation = COMMISSION REGULATION (EC) No 976/2009 of 19 October 2009 , Implementing

Directive 2007/2/EC of the European Parliament and of the Council as regards the Network Services


� The Guideline is based on the OGC CSW standard• OGC 07-045, OGC Catalogue Services Specification 2.0.2 - ISO

Metadata Application Profile for CSW 2.0, version 1.0.0 ([CSW ISO AP])

� Operations required by INSPIRE

� Operations required in addition by CSW ISO AP• DescribeRecord and GetRecordByID• Optional: GetDomain

INSPIRE operation OGC CSW operation

Get Discovery Service Metadata OGC_Service.GetCapabilitiesDiscover Metadata CSW Discovery.GetRecords

CSWT Manager.Transaction orCSWT Manager.HarvestCombination of OGC_Service.GetCapabilities andCSW Discovery.GetRecordsOR using Publish Metadata operation:CSWT Manager.Transaction or CSWT Manager.Harvest

Publish Metadata

Link Discovery service

Discovery Service Technical GuidanceDiscovery Service operations overview


Bindings and Protocols� Bindings and Protocols

• Follow OGC CSW ISO AP, meaning:

OGC CSW operation BindingOGC_Service.GetCapabilities GET KVPCSW Discovery.GetRecords POST + SOAPCSW Discovery.DescribeRecord POST + SOAPCSW Discovery.GetDomain POST + SOAPCSW Manager.GetRecordByID GET KVPCSWT Manager.Transaction POST + SOAP

CSWT Manager.Harvest POST + SOAP


Discovery Service Technical GuidanceGet Discovery Service metadata -> GetCapabilities

Request parameters : Additional Parameter “Language” for GetCapabilities-Operation

(http/get) to be supported (compared to [CSW ISO AP]).Ex:

http://discovery.beta.agiv.be/kvp/?REQUEST=GetCapabilities&SERVICE=CSW&LANGUAGE=ENG

Response parameters : - Discovery service metadata- Operations metadata- LanguagesParameters, part of the getcapabilities response as defined in

clause 2.2. [INS DIS] in:- Table 2 in the TG explains the different parameters- In the Annexes you can find a full capabilities document- Table 3 with a mapping of getcapabilities CSW metadata

and INSPIRE metadata in the TGINSPIRE Technical Guidances

Get Discovery Metadata operationimplementation specifics

Already discussed, see the 2 scenarios described in the common approach section for INSPIRE metadata.

In the following slides we briefly look at the mapping of INSPIRE metadata to OGC CSW ISO AP elements.


Get Discovery Metadata operation� INSPIRE service metadata mappings – Regular capabilitiesINSPIRE Metadata element Capabilities CSW ISO APResource title (B1.1) /csw:Capabilities/Serviceidentification/TitleResource abstract (B1.2) /csw:Capabilities/ Serviceidentification/AbstractResource Type (B1.3) /ExtendedCapabilities/ResourceTypeResource Locator (B1.4) /csw:Capabilities/ OperationsMetadata/Operation/GetCapabilities/DCP/HTTP/@xlink:hrefCoupled Resource (B1.6) Not applicable to discovery serviceSpatial data service type (B2.2) /ExtendedCapabilities/SpatialDataServiceTypeKeyword value (B3.1) /ExtenededCapabilities/INSPIREKeywordsOriginating controlled vocabulary (B3.2) /ExtenededCapabilities/INSPIREKeywordsTemporal extent (B5.1) /ExtendedCapabilities/TemporalReferenceDate of publication (B5.2) /ExtendedCapabilities/TemporalReferenceDate of last revision (B5.3) /ExtendedCapabilities/TemporalReferenceDate of creation (B5.4) /ExtendedCapabilities/TemporalReferenceSpecification (B7.1) /ExtendedCapabilities/ConformityDegree (B7.2) /ExtendedCapabilities/ConformityConditions applying to access and use (B8.1) /csw:Capabilities/ Serviceidentification/FeesLimitations on public access (B8.2) /csw:Capabilities/ Serviceidentification/AccessConstraints

csw:Capabilities/ Serviceprovider/ProviderName Responsible party (B9.1) and

csw:Capabilities/ Serviceprovider/ServiceContact/ContactInfo/Address/ElectronicMailAddress

Responsible party role (B9.2) csw:Capabilities/ Serviceprovider/roleMetadata point of contac (B10.1) /ExtendedCapabilities/MetadataPointOfContactMetadata Date (B10.2) /ExtendedCapabilities/MetadataDateMetadata Language (B10.3) /ExtendedCapabilities/metadataLanguage


Get View Discovery Metadata operation� INSPIRE service metadata mappings – Extended

capabilitiesINSPIRE Metadata element Capabilities CSW ISO APResource title (B1.1) /csw:Capabilities/Serviceidentification/TitleResource abstract (B1.2) /csw:Capabilities/ Serviceidentification/AbstractResource Type (B1.3) /ExtendedCapabilities/ResourceTypeResource Locator (B1.4) /csw:Capabilities/ OperationsMetadata/Operation/GetCapabilities/DCP/HTTP/@xlink:hrefCoupled Resource (B1.6) Not applicable to discovery serviceSpatial data service type (B2.2) /ExtendedCapabilities/SpatialDataServiceTypeKeyword value (B3.1) /ExtenededCapabilities/INSPIREKeywordsOriginating controlled vocabulary (B3.2) /ExtenededCapabilities/INSPIREKeywordsTemporal extent (B5.1) /ExtendedCapabilities/TemporalReferenceDate of publication (B5.2) /ExtendedCapabilities/TemporalReferenceDate of last revision (B5.3) /ExtendedCapabilities/TemporalReferenceDate of creation (B5.4) /ExtendedCapabilities/TemporalReferenceSpecification (B7.1) /ExtendedCapabilities/ConformityDegree (B7.2) /ExtendedCapabilities/ConformityConditions applying to access and use (B8.1) /csw:Capabilities/ Serviceidentification/FeesLimitations on public access (B8.2) /csw:Capabilities/ Serviceidentification/AccessConstraints





Get View Discovery Metadata operation� INSPIRE service metadata mappings – not mapped

INSPIRE Metadata element Capabilities CSW ISO APResource title (B1.1) /csw:Capabilities/Serviceidentification/TitleResource abstract (B1.2) /csw:Capabilities/ Serviceidentification/AbstractResource Type (B1.3) /ExtendedCapabilities/ResourceTypeResource Locator (B1.4) /csw:Capabilities/ OperationsMetadata/Operation/GetCapabilities/DCP/HTTP/@xlink:hrefCoupled Resource (B1.6) Not applicable to discovery serviceSpatial data service type (B2.2) /ExtendedCapabilities/SpatialDataServiceTypeKeyword value (B3.1) /ExtenededCapabilities/INSPIREKeywordsOriginating controlled vocabulary (B3.2) /ExtenededCapabilities/INSPIREKeywordsTemporal extent (B5.1) /ExtendedCapabilities/TemporalReferenceDate of publication (B5.2) /ExtendedCapabilities/TemporalReferenceDate of last revision (B5.3) /ExtendedCapabilities/TemporalReferenceDate of creation (B5.4) /ExtendedCapabilities/TemporalReferenceSpecification (B7.1) /ExtendedCapabilities/ConformityDegree (B7.2) /ExtendedCapabilities/ConformityConditions applying to access and use (B8.1) /csw:Capabilities/ Serviceidentification/FeesLimitations on public access (B8.2) /csw:Capabilities/ Serviceidentification/AccessConstraints





Discovery Service Technical GuidanceDiscover metadata -> GetRecords

Request parameters : • Languages and Query

• The query parameter is realized by the filter statement of the GetRecordsRequest itself. The query has to support all search attributes (cfr. Search criteria slides).

• The language parameter is realized by using the Language queryable in a filter statement. With that a client can request metadata records in a specific metadata language.

Ex: http://discovery.beta.agiv.be/kvp/?REQUEST=GetRecords&SERVICE=CSW&VERSION=2.0.2&R

ESULTTYPE=results&OUTPUTSCHEMA=http://www.opengis.net/cat/csw/2.0.2&ELEMENTSETN

AME=full&MAXRECORDS=5&CONSTRAINT=<Filter

xmlns='http://www.opengis.net/ogc'><And><PropertyIsEqualTo><PropertyName>Language</Prop

ertyName><Literal>dut</Literal></PropertyIsEqualTo><PropertyIsEqualTo><PropertyName>Topic

Category</PropertyName><Literal>environment</Literal></PropertyIsEqualTo></And></Filter>&ty

peNames=gmd:MD_Metadata&CONSTRAINTLANGUAGE=FILTER&CONSTRAINT_LANGUAGE

_VERSION=1.1.0

Response parameters : No additional parameters required.


Discovery Service Technical GuidancePublish - Edit metadata (push) -> Transaction

• This is a difficult one. Let’s have a preview at the work on the Discovery Service TG in progress.

• TG v2.0 just referenced the CSW ISO AP, but there is nothing concrete in there as well.

• Possible outcome : An interface for a SOAP based service that realises an insert/update/delete query against a metadata catalogue or a restfull URL (HTTP put , delete) for the same operation. Discussion is going on.


Discovery Service Technical GuidancePublish - Collect metadata (pull) -> Harvest

Request parameters : Within the context of INSPIRE an INSPIRE Discovery Service is at least able to harvest single metadata documents that are provided through some online location.[CSW ISO AP] specifies a harvest operation that is based on the related operation of

the underlying base specification [OGC CSW]. For an INSPIRE Discovery Service, the following settings have to be met if a resource is requested to be harvested by a catalogue service instance.

RESOURCETYPE: The resource type of the resource being harvested has to be http://www.isotc211.org/schemas/2005/gmdRESOURCEFORMAT: The resource format of the resource being harvested has to be “application/xml”An example request is included.

Response parameters : No additional parameters required.

To be honest : The same discussion going on as for Transactional. Probable implementation through the GetRecords operation.


Discovery Service Technical GuidanceLink Discovery service

Request parameters : No additional parameters required. However, it is demanded that the hopCount attribute of the Distributed search element of a GetRecords request should always have the value “2” to avoid circular searches.

An example request is provided in the TG. (Let’s have a look)


Discovery Service Technical Guidance

Link Discovery service : Implementation recommandati on 1

� Link View Service• Definition : “The Link Discovery Service function 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 location.”

• Recommended implemented using the Publish metadata operation of the Discovery Service, ie. CSWT:Transaction or CSWT:Harvest

• Rationale: Services related to INSPIRE, form a "virtual" network of services: The publish metadata operation enables to link services into this network (publish-find-bind paradigm)


Discovery Service Technical GuidanceLink Discovery service : Implementation recommandati on 2

� Link View Service (alternative implementation)• Implementation by federated search at the Discovery Service

- Was recommended in Discovery TG in ver 2.0

• Using operations CSW:GetRecords and CSWGetCapabilities• Rationale: The GetRecords operation is able to search and

to present metadata records from federated Discovery Services. Federated Discovery Services are advertised in the Capabilities.


[CSW ISO AP ] as the base specification for the INSPIRE Discovery Service is based on the ISO 19115/19119 information model. As such it is required that the abstract INSPIRE metadata elements (see [INS MD]) could be requested through the INSPIRE Discovery Service interface within a query.

The relation between ISO 19115 and ISO 19119 and the elements of the INSPIRE Metadata IR is described in [INS MD IMPL].

Clause 12.1.9 Table 4 in the TG defines the required mappings to common queryables specified by [CSW ISO AP] and [OGC CSW]. Clause 12.1.9 Table 5 in the TG defines additional queryables required by [INS MD] and [INS MD IMPL].

All supported ISO queryables shall be advertised in the section “SupportedISOQQueryables”; in addition, all INSPIRE queryablesshall be listed in the section “AdditionalQueryables”.

Example request is included in the TG.

Discovery Service Technical GuidanceDiscovery Service queryables


Discovery Service Technical GuidanceMultilingual aspects

> 70

An INSPIRE Discovery Service must indicate the languages that are supported to formulate values within a query. This requires that a client application must be able to determine the supported languages of the values of the queryables.

To indicate the supported languages the following has to be supported by a capabilities document that is returned by an INSPIRE Discovery Service:

•The capabilities document shall be returned in the default language

•A list of supported languages for queryable values defined by a 3-letter code as described in ISO 639-2

•The translations to other supported languages shall be referenced in the “ExtendedCapabilities” element, as a link to an online resource.

Service exceptions shall be returned within a “ServiceException” element, in the requested language or if no language is specified, in the default language.


Some final considerations

> 71

• Extended capabilities have to be finalized.

• Publish (Transaction, Harvest) still needs some work.

• Our own SDI Testbed proves that an INSPIRE compatible Discoveryservice is feasable (We still have to implement Transaction and Harvest though).

• Maybe it would be interesting to have some implementation recommendations for the implementation of federated searches as well.

• So far, no attention has been paid on authentication/authorization aspects of the Discovery service.



INSPIRE View ServiceTechnical Guideline v2.12 and Up

Technical Guidance View (1)� Major references:

• ISO 19128• ISO 19115• INSPIRE network Architecture• Domain model• Implementing Rule

� TG = ISO 19128 profile� Implementation depends on preferred scenario:

• Scenario 1: Metadata reference in Capabilities referring to a metadata repository. Metadata advisory pushed to GetCapabilities.

• Scenario 2: All metadata in Capabilities• Intermediate scenarios are possible: Metadata for services

and reference to data it operates on should be available.


Technical Guidance View operations

Operatie ISO19128 INSPIRE

Getcapabilities M M

Getmap M M

Getfeature info O O

Link View C

Can be implementedby discovery service reference


View service requests� Must be conform to ISO 19128� Additional parameter:

• LANGUAGE (INSPIRE extension)• If no parameter specified or if language not supported:

Default Language� Version 1.3.0 MUST be supported

Request parameter Mandatory / optional

Description

VERSION=version O Request version : 1.3.0

SERVICE=WMS M Service type. Fixed value : WMS.The ServiceType for an ISO 19128:2005(E) – WMS1.3.0 isfixed to “WMS”.

REQUEST=GetCapabilities M Request name. Fixed value : GetCapabilities

LANGUAGE=code O Request language (INSPIRE extension).

FORMAT=MIME_type O Output format of service metadata. Defaults to text/xml.


How� Available using discovery service and harvested from

repository/ available in GetCapabilities and harvested or both…

� Metadata near to the service vs central metadata• Depends on scale• Degree of central management• No general rules. Scaling depends on MS implementation.• Using CoupledResource and ResourceLocator


Namespace and Schema Instance<WMS_Capabilities version="1.3.0"

xmlns="http://www.opengis.net/wms "

xmlns:inspire_vs="http://inspire.ec.europa.eu/resource/1.0 "

xmlns:xlink="http://www.w3.org/1999/xlink "

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance "

xsi:schemaLocation="http://inspire.ec.europa.eu/resource/1.0 http://www.inspire-geoportal.eu/schemas/0.13/network/view/wms/INSPIRE_ VIEW_GetCapabilities_INSPIRESchema_WMS_eng.xsd ">


View service metadataINSPIRE Metadata elements

(Mandatory - Conditional)

ISO19128:2005(E) elements of

<WMS_Capabilities>

Resource Title (M) wms:Title

Resource Abstract (M) wms:Abstract

Resource Type (M) inspire_vs:ResourceType

(Extended Capabilities)

Resource Locator (C) inspire_vs:ResourceLocator


Coupled Resource (C) wms: MetaDataURL (Layer property)

Spatial Data Service Type (M) inspire_vs:SpatialDataServiceType(Extended Capabilities)

Keyword (M) wms:Keyword ; inspire_vs:InspireKeywords

Geographic Bounding Box (M) wms:EX_GeographicBoundingBox (Layer property)

Temporal Reference (M) inspire_vs:TemporalReference(Extended Capabilities)

Spatial Resolution (C) wms:Abstract

Conformity (M) inspire_vs:Conformity(Extended Capabilities)

Conditions for Access and Use (M) wms:Fees

Limitations on Public Access (M) wms:AccessConstraints

Responsible Organisation (M) wms:ContactInformation

Metadata Point of Contact (M) inspire_vs:MetadataPointOfContact(Extended Capabilities)

Metadata Date (M) inspire_vs:MetadataDate(Extended Capabilities)

Metadata Language (M) inspire_vs:Language(Extended Capabilities)


DESCRIPTION OF SERVICE

<wms:Service>


Mapping of INSPIRE elements (1)� Some in standard ISO 19128 elements:

INSPIRE Metadata elements

(Mandatory - Conditional)

ISO19128:2005(E) elements of

<WMS_Capabilities>

Resource Title (M) wms:Title

Resource Abstract (M) wms:Abstract

Coupled Resource (C) wms:MetaDataURL (Layer property)

Keyword (M) wms:Keyword

Geographic Bounding Box (M) wms:EX_GeographicBoundingBox (Layer property)

Spatial Resolution (C) wms:Abstract

Conditions for Access and Use (M) wms:Fees

Limitations on Public Access (M) wms:AccessConstraints

Responsible Organisation (M) wms:ContactInformation


Mapping of INSPIRE elements (2)� Others in ExtendedCapabilities element (ISO 19128

compliant)� In version 1.1.1 of WMS known as

“VendorSpecificCapabilities”� INSPIRE elements with a specific INSPIRE schema:

• http://www.inspire-geoportal.eu/schemas/latest/Resource Type (M) inspire_vs:ResourceType


Resource Locator (C) inspire_vs:ResourceLocator (NOT wms:onlineresource)


Spatial Data Service Type (M) inspire_vs:SpatialDataServiceType(Extended Capabilities)

Keyword (M) inspire_vs:InspireKeywords

Temporal Reference (M) inspire_vs:TemporalReference(Extended Capabilities)

Conformity (M) inspire_vs:Conformity(Extended Capabilities)

Metadata Point of Contact (M) inspire_vs:MetadataPointOfContact(Extended Capabilities)

Metadata Date (M) inspire_vs:MetadataDate(Extended Capabilities)

Metadata Language (M) inspire_vs:Language(Extended Capabilities)


Example description service<ContactInformation><ContactPersonPrimary><ContactPerson>AGIV</ContactPerson> <ContactOrganization>AGIV</ContactOrganization> </ContactPersonPrimary><ContactPosition />

<ContactAddress><AddressType>Postal </AddressType> <Address>Gebroeders Van Eyckstraat 16 </Address> <City>Gent</City> <StateOrProvince /> <PostCode>9000</PostCode> <Country>Belgium </Country> </ContactAddress><ContactVoiceTelephone>+3292615200</ContactVoiceTelephone> <ContactFacsimileTelephone>+3292615299</ContactFacsimileTelephone> <ContactElectronicMailAddress>[email protected] </ContactElectronicMailAddress> </ContactInformation><Fees>none </Fees> <AccessConstraints>GDI-Vlaanderen testbed terms of use

(http://gditestbed.agiv.be/page/Terms-of-use-of-the -SDI-Flanders-Testbed.aspx) </AccessConstraints>


Example ExtendedCapabilities<inspire_vs:ExtendedCapabilities><inspire_vs:ResourceLocator><inspire_vs:URL>

http://ogc.beta.agiv.be/ogc/wms/vrbgINSP ?</inspire_vs:URL> <inspire_vs:MediaType>

application/vnd.eu.europa.ec.inspire.resource+xml</inspire_vs:MediaType> </inspire_vs:ResourceLocator><inspire_vs:ResourceType>

Service</inspire_vs:ResourceType>

</inspire_vs:ExtendedCapabilities>


Example Conformity<inspire_vs:Conformity><inspire_vs:Specification><inspire_vs:Title>

INSPIRE Directive 2007/2/EC</inspire_vs:Title> <inspire_vs:DateOfPublication>

2008-11-28</inspire_vs:DateOfPublication>

</inspire_vs:Specification><inspire_vs:Degree>

notEvaluated</inspire_vs:Degree>

</inspire_vs:Conformity>


Example Language<inspire_vs:SupportedLanguages>

<inspire_vs:DefaultLanguage>dut</inspire_vs:DefaultLanguage> <inspire_vs:SupportedLanguage>eng</inspire_vs:SupportedLanguage><inspire_vs:SupportedLanguage>fra</inspire_vs:SupportedLanguage>

</inspire_vs:SupportedLanguages>


Example Keyword<inspire_vs:MandatoryKeywordxsi:type="inspire_vs:classificationOfSpatialDataService"><inspire_vs:KeywordValue>infoMapAccessService</inspire_vs:KeywordValue>

</inspire_vs:MandatoryKeyword><inspire_vs:Keyword>

<inspire_vs:KeywordValue>Administrative units</inspire_vs:KeywordValue>

</inspire_vs:Keyword>


DESCRIPTION OF LAYERS

<wms:Layer>


Description of Layer = metadatafor data

Metadata elements ISO19128:2005(E) standard elements of <wms:Layer>

Resource Title wms:Title

Resource Abstract wms:Abstract

Keyword wms:KeywordList

Geographic Bounding Box wms:EX_GeographicBoundingBox

Unique Resource Identifier wms:Identifier + wms:AuthorityURL

Name wms:Name

Coordinate Reference Systems wms:CRS

Styles wms:Style

Legend URL wms:Style/wms:LegendURL

Dimension Pairs wms:Dimension[@name,@units]

Link to metadata of the corresponding spatial dataset

(operates on)

wms:MetadataURL

Coupled Resource (Service metadata mapped to a Layerproperty)

wms:DataURL


Example of reference to metadataof the Layer (Coupled Resource)

<MetadataURL type="ISO19115:2005"><Format>text/xml </Format> <OnlineResource

xlink:href="http://discovery.beta.agiv.be/kvp/?REQUEST=GetRecordById&SERVICE=CSW&VERSION=2.0.2&ELEMENTSETNAME=summary&ID=2a164246-9025-4426-8eb2-08273e710299&OUTPUTSCHEMA=http://www.isotc211.org/2005/inspire_vs " xlink:type="simple " /> </MetadataURL>


Supported CRS

CRS value Usage

EPSG:4258 ETRS89 geographic (Continental Europe)

EPSG:4326 WGS 84 (World), Low resolution datasets

CRS:84 WGS 84 (Outside continental Europe)

� Defined by TWG Dataspecs


Layer Name� Defined by TWG Dataspecs

Theme Examples of layer names

Geographical names GN.GeographicalNames

Administrative units AU.AdministrativeUnit

Addresses AD.Address

Cadastral parcels CP.CadastralParcel

Transport networks TN.RoadTransportNetwork.RoadArea

Hydrography HY.Network

Protected sites PS.ProtectedSite


Style� Defined by TWG Dataspecs

<wms:Style>

<wms:Name>inspire_vs:DEFAULT</wms:Name>

<wms:Title>Style for roads</wms:Title>

</wms:Style>


Category Layer� Use of nested layer for grouping data with different

feature types


GetMap response� image /png or image/gif� Transparency

21-1-2011Editeer via Beeld > Koptekst en voettekst

OverviewINSPIRE Domain Model

Motivation� Technical Guidance Documents focus on the technical

components of INSPIRE• network service types, metadata, spatial data

� But: Many use cases and workflows in a SDI span across various technical components


Use Cases - Example� “I found a metadata document for a spatial dataset, how

can i use it?”� “I am visualizing a layer of a view service and am

interested in the spatial dataset for further analysis; how do i find an appropriate download facility?”

� requires linkages between spatial datasets, services & metadata


The Domain Model� Identify, describe, link and relate the technical

components of INSPIRE together to…� …help understand the nature of technical components

and the linkages, their purpose, context and how they could interact to realize use cases and workflows


Scope� Version 1.0

• Identify gaps that are not directly visible when working on single aspects, e.g. single Technical Guidance documents (TG)

• Get a common understanding of INSPIRE (from the technological point of view)

• Provide input for the finalization of the technical guidance documents for view and discovery and if applicable to metadata


Scope� Future Versions

• Provide input for an updated INSPIRE architecture document (or a core element of this document)

• Subsequent extension by additional TGs (Download/Invoke/Transformation services, additional annex themes, etc)

• Subsequent extension by taking additional aspects into account (Schema`s, Registries, Access Control/GeoRM entities)

• Input for future evolution of INSPIRE specifications


Scenario to build the Domain Model

� “By Example” makes it easier to understand� Netherlands have a national spatial dataset

“TOP10NL”. This spatial dataset contains a collection of spatial objects that are instances of spatial object type StatisticalUnits::NUTSRegion. The SpatialDataSet is accessible in three ways: • 1. display of layers that represent spatial objects via a view

service BaseData.NL• 2.direct access to spatial objects via a download service

BaseData.NL• 3. access/download of a predefined dataset in a compressed

format (e.g. zip file) via a download service

� Variants are also covered


INSPIRE Domain Model


Domain Model v1.0 Where it all comes together


Domain Model : Specific cases


Results� The domain model helped clarifying…

• how to access metadata from service capabilities & use of identifiers

• Implementation possibilities for different situations for spatial datasets and how to make them available for view & download

• Possibilities to describe services with metadata and link with metadata for spatial datasets


The Road Ahead

The road ahead (1)� In February 2011 – stable guidances for the IOC phase� Implementation of IOC by Member States� Review of the guidances after the IOC phase based on

feedback� Request from EC to extend the activities of the IOC TF

and his Services team to other network services• Download• Transformation

� Registries: IOC Task Force decided for the implementation of a register of Discovery network services.

� Discussion and guidance on Authentication mechanisms based on technologies being considered by the IOC-TF (“SAML” and “Shibboleth”)


� Implementation and testing of other services + Editing draft TG (if approved)

� Extent the INSPIRE Domain model and guarantee interoperability

� Follow activities of OGC/ISO to adopt INSPIRE requirements and keep TG’s in line with standards


The road ahead (2)

Statement from the Commission� The IOC Task Force proves to be an efficient forum for

enabling interoperability among the INSPIRE technical components.

� There is still a lot to be done and resources are scarce.


Discussion & [email protected]

[email protected]