Ticket: https://ies-svn.jrc.ec.europa.eu/issues/2219 Metadata for SDS
Ticket: https://ies-svn.jrc.ec.europa.eu/issues/2304 Metadata for SDS Category
Ticket: https://ies-svn.jrc.ec.europa.eu/issues/2305 Metadata for SDS Resource locator
Ticket: https://ies-svn.jrc.ec.europa.eu/issues/2306 Metadata for SDS Specification
Ticket: https://ies-svn.jrc.ec.europa.eu/issues/2307 Metadata for SDS Coordinate reference systems
Ticket: https://ies-svn.jrc.ec.europa.eu/issues/2308 Metadata for SDS Quality of service
Ticket: https://ies-svn.jrc.ec.europa.eu/issues/2309 Metadata for SDS Responsible party
Ticket: https://ies-svn.jrc.ec.europa.eu/issues/2310 Metadata for SDS Contains operation
Update TG Metadata with the extended elements defined for Spatial Data Services (SDS)
The extended elements for SDS are now defined and it is suggested that an implementation of these is defined in the TG using an extension to ISO19115/19
Ine de Visser (Leader)
What problems causes current solution ?¶
From the point of view of the average metadata custodian SDS extended metadata elements are rather unknown and might remain unnoticed, because these are not easy to find - not mentioned in CR (EC) No 1205/2008 Annex metadata IR or in metadata TG.
Check status of TG SDS
Check status of the extended schema
Check possibility of codelists for functioncode, category, QualityOfServiceCriteriaType, optionality..
Update TG MD with the SDS metadata elements
- Need to ensure consistency with TG section 2.2.X Resource locator and examples
- Need to ensure consistency with TG section 2.2.X Responsible party and examples
- Adress validation issues
- Adress metadata editor issues
- Adress metadata harvest issues
What can be a solution on current problem ?¶
Extended SDS metadata elements have been described in Draft TG for INSPIRE Spatial Data Services and services allowing spatial data services to be invoked. Additional background information also in INSPIRE spatial data services and services allowing spatial data services to be invoked– Draft Implementing Rules and annex to ammending reg 1089-2010.
Updates in metadata TG:
Extended MD elements with detailed description and xml examples should be added in to Basic Mapping chapter (2). Some current MD elements should have adjustable explanations.
Updating Detailed mapping chapter (3).
•How does it relate to IR ?¶
In the initial phase of work related to SDS and Invoke services there where
Implementation rules (INSPIRE spatial data services and services allowing spatial data services to be invoked– Draft Implementing Rules and annex to ammending reg 1089-2010.)
and Technical guidelines ( Draft TG for INSPIRE Spatial Data Services and services allowing spatial data services to be invoked.)
written for SDS.
It has though been decided that there should not be a separate IR for SDS. Instead there will be two amendments
Commission Regulation (EU) No 1311/2014 of 10 December 2014 amending Regulation (EC) No 976/2009 as regards the definition of an INSPIRE metadata element
Commission Regulation (EU) No 1312/2014 of 10 December 2014 amending Regulation (EU) No 1089/2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data services
The situation for the Draft TG for Inspire SDS is not clear. Will we both have updates of TG Metadata regarding the SDS metadata-elements and a TG Inspire SDS managing other perspectives than metadata
How will the solution affect existing tools ?¶
INSPIRE MD editor does not support adding these extended MD elements.
New validation tests will be required for existing MS implementations to ensure all mandatories are met
How will the solution affect existing metadata ?¶
Member states SDS (with conformance class 2, 3 and 4) metadata files will need improving.(that means retrofitted and revalidated and harvested)
What other issues in MIWG-8 is related to this change ?¶
MIWP-8 (D) Integrate metadata for interoperability into the Metadata TG coordinate reference system
What other groups within MIG-related workgroups could be linked to this issue ?¶
MIGWP-5 validation of the metadata