inspire registers
DESCRIPTION
Management and possibility to uniquely reference various items of INSPIRE infrastructure 04.07.2013, TAIEX 53350 Macedonia Study visit on INSPIRE interoperability data sets and services @ Slovak environmental agency, Banská Bystrica, SlovakiaTRANSCRIPT
INSPIRE Registers
Martin Tuchyňa
10.07.2013, TAIEX Study visit on INSPIRE interoperability data sets and services
Slovak environmental agency, Banská Bystrica, Slovakia
Management and possibility to uniquely reference various items of INSPIRE infrastructure
Content
• Purpose of INSPIRE registers
• Why they are needed?
• Data harmonisation
• State of play
• Outlook
Purpose • The INSPIRE infrastructure involves a number of items, which require clear descriptions and the possibility to be referenced through unique identifiers. (INSPIRE themes, code lists, application schemas or discovery services)• Registers provide a means to assign identifiers to items and their labels, definitions and descriptions (in different languages).• The INSPIRE registry provides a central access point to a number of centrally managed INSPIRE registers.
Data harmonisation
• Architecture
Data specification development frameworkData specification development framework
Consolidated registersConsolidated registersD2.8.m.n
Data Specification
D2.8.m.nData Specification
provide fram ework provide fram ework
FeatureC oncept
D ictionary
C onsolidatedU M L m odel
FeatureC ata logueR egister
C R S /U oMregister
C ode lis treg is ter
G lossary
D 2.3 S cope and defin ition
of them es
D 2.3 S cope and defin ition
of them es
D 2.5 G enericC onceptua l
M odel
D 2.5 G enericC onceptua l
M odel
D 2.6 M etho-do logy
D 2.6 M etho-do logy
D 2.7 E ncodingguide lines
D 2.7 E ncodingguide lines
A pplica tionS chem a
A pplica tionS chem a Other
implementing rules
Other implementing
rules
D 1.3M etadata
D 1.3M etadata
D 3.x N etworkservices
D 3.x N etworkservices
D 3.x N etworkservices
D 3.x N etworkservices
D 3.x N etworkservices
D 3.x N etworkservices
dependency
CTCT
DT DSDT DS
TWGsTWGs
DT MDDT MD
DT NSDT NS
provide fram ew ork
provide change requests
provide baseline
Data specification development frameworkData specification development framework
Consolidated registersConsolidated registersD2.8.m.n
Data Specification
D2.8.m.nData Specification
provide fram ework provide fram ework
FeatureC oncept
D ictionary
C onsolidatedU M L m odel
FeatureC ata logueR egister
C R S /U oMregister
C ode lis treg is ter
G lossary
D 2.3 S cope and defin ition
of them es
D 2.3 S cope and defin ition
of them es
D 2.5 G enericC onceptua l
M odel
D 2.5 G enericC onceptua l
M odel
D 2.6 M etho-do logy
D 2.6 M etho-do logy
D 2.7 E ncodingguide lines
D 2.7 E ncodingguide lines
A pplica tionS chem a
A pplica tionS chem a Other
implementing rules
Other implementing
rules
D 1.3M etadata
D 1.3M etadata
D 3.x N etworkservices
D 3.x N etworkservices
D 3.x N etworkservices
D 3.x N etworkservices
D 3.x N etworkservices
D 3.x N etworkservices
dependency
CTCT
DT DSDT DS
TWGsTWGs
DT MDDT MD
DT NSDT NS
provide fram ew ork
provide change requests
provide baseline
Data harmonisation
Conceptual data models Registers
• spatial objects and their properties and relationships for 34 data themes
• cross-domain harmonization
• based on a common modelling framework
• managed in a common UML repository
Harmonised vocabularies
• to overcome interoperability issues caused by free-text and/or multi-lingual content
• allow more specific terms from local vocabularies in addition to the harmonized terms
Encoding
• GML application schemas as standard encoding
• conceptual models independent of concrete encodings
• also possible to derive other encodings (e.g. based on RDF)
• provide unique and persistent identifiers for resources
• allow their consistent management and versioning
• items can be made unique and referred to unambiguously
Key pillars of data interoperability
Data harmonisation
Conceptual data models Registers
• spatial objects and their properties and relationships for 34 data themes
• cross-domain harmonization
• based on a common modelling framework
• managed in a common UML repository
Harmonised vocabularies
• to overcome interoperability issues caused by free-text and/or multi-lingual content
• allow more specific terms from local vocabularies in addition to the harmonized terms
Encoding
• GML application schemas as standard encoding
• conceptual models independent of concrete encodings
• also possible to derive other encodings (e.g. based on RDF)
• provide unique and persistent identifiers for resources
• allow their consistent management and versioning
• items can be made unique and referred to unambiguously
Key pillars of data interoperability
described in INSPIRE Conceptual Framework documents
D2.6:Methodology
for Specification Development
D2.10.3: Common data models
D2.9: O&M Guidelines
D2.5: Generic Conceptual Model
D2.7: Guidelines for Encoding
State of play EU
• Consolidated UML Model
State of play EU• INSPIRE Registry (Old version)
State of play EU
• INSPIRE Registry (New version)
State of play EU• INSPIRE Registry
– Available formats:• HTML - html• XML - xml• ATOM - atom• JSON – json
– Content negotiation - RESTful web service(possibility to provide the same information in multiple formats and multiple languages)
– Available languages:
All the registry• English - en
Themes and Codelist items
• Bulgarian - bg• Czech - cz• Danish - da• German - de• Greek - el• Spanish - es• Estonian - et
• Finnish - fi• French - fr• Hungarian - hu• Italian - it• Lithuanian - lt• Latvian - lv• Maltese - mt• Dutch - nl• Polish - pl• Portuguese - pt• Romanian - ro• Slovak - sk• Slovenian - sl• Swedish - sv
State of play EU
• INSPIRE Registry – Themes EN/SK
State of play SK
• Environmental domain standard defining the data structure for exchange of spatial data • Taking into the consideration standardised structures on national and international level • Inventarisation of requirements for spatial data structure in order to fullfill legal and relevant use cases requirements within the domain of institutions under the MoE
• Feature Catalogue of Ministry of Environment (KO MŽP SR)
State of play SK
• Structure is based on geosystem landscape classification principles • Content of KO MŽP SR
– 124 objects including 806 attributes– sorted in 25 complexes– categorised in 3 landscape structures
• Exchange standardards implemented so far– DIGEST – GDF (Geographic Data Files) – S-57
• Organisational framework for maintenance –IMK till 2012–RPS INSPIRE
• Representation–Static overview (HTML, XLS,)–Webform for collection of update requirements –Physical implementation of database structure (ESRI ArcSDE)
• KO MŽP SR Overiew
Outlook EU
• Additional registers to be implmented: – Application Schema Register– Coordinate Reference System Register– Data Specification Guidance Register –(Discovery) Service Register – Object Identifier Namespace Register– Feature Catalogue Register – Locale Register – Portrayal Rule Register – Units of Measurement Register – XML Schema repository/register
Outlook SK
• Short term targets:– Deployment of Re3gistry– Transformtion of KO MŽP SR into the UML object oriented model, including database implementation – Mapinng relevant content of KO MŽP SR into INSPIRE UML model via Re3gistry
• Middle & long term vision – Identification of relevant use cases – Identification of need for SK domain extension of INSPIRE model– Support for automatized generation of aplication schemas
• Further activities
Thank you!
04.07.2013, TAIEX Study visit on INSPIRE interoperability data sets and services
Slovak environmental agency, Banská Bystrica, Slovakia