Reference Information Specifications for Europe Overview Presentation to HACPB3

Reference Information Specifications for Europe

Overview Presentation to HACPB3

Wyn Cudlip (QinetiQ) and others RISE Participants

[email protected]

www.eu-rise.org

http://www.eu-rise.org/

Presentation to HACPB3, Brussels, 6th June, 2007. V1.0 Page 2

Project goals

• To define a methodology and guidelines for the creation of geospatial Data Product Specifications (DPS), consistent with international and industrial standards.

• To test the methodology by creating harmonised DPS for Hydrography, LandCover and Elevation; as input datasets to diffuse nutrient leakage modelling for the Water Framework Directive (WFD).

• To test the DPS in an on-line “Test Environment” with data from a test area (Sweden & Norway).

• To demonstrate the automatic creation of hDPs from existing databases


Presentation Overview

• Short intro to RISE project

• Deliverables provided so far

• Introduce additional presentations

• Response to External Reviewer comments

• Conclusions


RISE consortium

EuroGeographics

Lantmäteriet

BKG

Public Institutions -Source data providers

OGC-Europe

QinetiQ

IndustryTechnology

“HarmonisationAdvisory Committee & Planning Board”

“WFD & GMES”

“Key stakeholders”Users and applications

2 yr FP6 Project; started Sept. 05.Working relationship with MOTIIVE.


The RISE and MOTIIVE Projects

• FP6, SSA for GMES data harmonisation• Duration 24 months

• Started 1st September 2005

• RISE & MOTIIVE – complementary activities

• RISE -emphasis on methodology and schema testing

• MOTIIVE - emphasis on feature types and registries

and cost benefit analysis

• RISE - empashis on land

• MOTIIVE - emphasis on Marine


Approach

Requirements Use Cases

Conceptual schema (UML)

Testing

Prototype

Application schema (GML) Cost

benefit

Exploitation guidelines

RISEMethodology

Data Product Specification


Key Steps in the development of “harmonised” Data Product Specification

• Analyse Use Case

• Develop Conceptual Schema (in UML)• Including Feature Type Catalogue and Data Dictionary update

• Develop GML Application Schema• this can be automated

• e.g., UGAS, UML to GML conversion tool

• Define harmonised Data Product Specification

• Data Products created from existing data

• Goal: to create “on the fly” with suitable server software

Use CaseDevelopment

Use CaseDevelopment

Requirementsand Feature Types

Identification


Identification

Data Dictionary Update


DPS and App SchemaDevelopment


Implementation,testing and validation


Use CaseDevelopment

Use CaseDevelopment


Identification


Identification








RequirementsRequirementsRequirementsAs-is analysis

Gap analysis

Use CaseDevelopment

Use CaseDevelopment

Use CaseDevelopment

Use CaseDevelopment


Identification


Identification


Identification


Identification

App SchemaDevelopmentApp SchemaDevelopmentApp SchemaDevelopment

Data ProductSpecificationDevelopment




Implementation,testing and

validation(using WFS)

Che

cklis

t fo

r da

ta

Har

mon

isat

ion

requ

irem

ents

Che

cklis

t fo

r da

ta

Har

mon

isat

ion

requ

irem

ents

Checklist addresses steps to data harmonisation

Sup

port

ing

com

pone

nts:

fea

ture

dat

a di

ctio

nary

, C

RS

reg

istr

y, e

tc.

Sup

port

ing

com

pone

nts:

fea

ture

dat

a di

ctio

nary

, C

RS

reg

istr

y, e

tc.


Key assumptions

Mandatory:• Overview• Specification scopes• Data product identification• Data content and structure• Reference systems• Data quality• Data product delivery• Metadata

Optional:• Data capture• Data maintenance• Portrayal• Additional information

• A Data Specification is based on a data product specification (DPS) according to ISO 19131. Such a DPS includes the following sections:

• RISE harmonisation is concerned with more than just data content and structure.


1.2 Reference model

1. INSPIRE Information Model

1.7 Object referencing modelling

1.6 Coordinate refe-rencing and units model

1.1 INSPIRE Principles

2. Operational components/registers

3. Guidelines & Best Practice

2.2 Terminology

1.3 Application Schemas

2.1 Identifier Management

2.4 Dictionaries

1.8 Data translation model/guidelines

2.3 Feature catalogues 2.5 Conformance

1.4 ISO 19100 Profile

1.5 Multi-lingual text andcultural adaptibility

3.1 Metadata

3.2 Maintenance

3.3 Quality

3.4 Data Transfer

3.5 Derived re-porting & multiple representations

1.9 Portrayal model 3.6 Consistency between data

3.7 Data capturing

Data Harmonisation Components – Overview

(developed by INSPIRE Drafting Team „Data Specifications“ in collaboration with RISE; RISE

will focus on the methodology, the DT will focus on generic aspects of the conceptual model)


Relevant ISO Standards

• UML ISO 19103• Conceptual Schema ISO 19107/8/9• Application Schema ISO 19109• Feature Type ISO 19109• Data Dictionary ISO 19126• Data Product Specification ISO 19131• Quality ISO 19113/5• Metadata ISO 19115• Multi Lingual ISO 19139• Portrayal ISO 19117• GML ISIO 19136• Translating WFS ISO 19142+43


Original Project Phases

• Phase 1 (1st 6 months) – requirements and draft methodology.

• Phase 2 (2nd 6 months) – Use Cases analysis; Application Schema and harmonised data product specifications.

• Phase 3 (3rd 6 months) – Prototype and testing.

• Phase 4 (final 6 months) – interoperability testing and issue Final Guidelines


RISE Deliverables

RequirementsRequirementsRequirementsRequirements

Use Use CasesCasesUse Use

CasesCases

MethodologyMethodology

Conceptual Conceptual SchemaSchema

Conceptual Conceptual SchemaSchema

TestingTestingTestingTesting

PrototypePrototypePrototypePrototype

GMLGMLApplicationApplication

SchemaSchema

GMLGMLApplicationApplication

SchemaSchemaCost Benefit Cost Benefit

AnalysisAnalysisCost Benefit Cost Benefit

AnalysisAnalysis

Exploitation Exploitation GuidelinesGuidelines

Exploitation Exploitation GuidelinesGuidelines

Data Data SpecificationSpecification

Data Data SpecificationSpecification

ArchitectureArchitectureArchitectureArchitecture

Data Harmonisation Requirements ReportData Harmonisation Requirements ReportData Harmonisation Requirements ReportData Harmonisation Requirements Report

Use Case DescriptionsUse Case DescriptionsUse Case DescriptionsUse Case Descriptions

Exploitation GuidelinesExploitation GuidelinesExploitation GuidelinesExploitation Guidelines

Services Architecture OutlineServices Architecture OutlineServices Architecture OutlineServices Architecture Outline

Cost Benefit ReportCost Benefit ReportCost Benefit ReportCost Benefit Report

Test Environment ReportTest Environment ReportTest Environment ReportTest Environment Report

GML Application SchemaGML Application SchemaGML Application SchemaGML Application Schema

Data Product SpecificationData Product SpecificationData Product SpecificationData Product Specification

Conceptual Schema in UMLConceptual Schema in UMLConceptual Schema in UMLConceptual Schema in UML

Methodology & Guidelines for on Use Case & Schema DevelopmentMethodology & Guidelines for on Use Case & Schema DevelopmentMethodology & Guidelines for on Use Case & Schema DevelopmentMethodology & Guidelines for on Use Case & Schema Development

To come:

So far:


RISE Document Highlights

• User Harmonisation Requirements Document• Analysed 96 GMES Projects plus INSPIRE and WFD Initiatives.

• Use Case document• Analysis of Swedish and Swedish/Norwegian Use Cases

• Requirements for hydrography, Land Cover and Elevation (DEM)

• Methodology and Guidelines Document + Checklist• Passed to MOTIIVE, and INSPIRE Drafting Team on Data Specifications

• Application Schema in UML and GML (automatic conversion)

• Harmonised Data Product Specifications• Defines data products that can be generated automatically

• RISE Service Architecture Outline document• Places RISE activity in a broader !SO/OGC context


Later presentations to address:

• RISE Test Environment

• Cost Benefit Issues

• Exploitation Guidelines


External Reviewer Comments

• Concern regarding directions of the project and the possible approaches towards redirecting the projects towards it’s initial target: … “methodology and guidelines for the creation of implementation specifications”

• Recommendations: The Project should:

• …jointly review the process / flow of documents leading to the specification….

• Clarify how the current standards may be exploited / extended to include the necessary specification information for either an “outside producer” or an automated procedure.

• Update the Deliverables according to the findings / comments.


RISE Response to Reviewer Comments

• RISE activity is and always has been directed towards

developing a “methodology and guidelines for the creation of

implementation specifications”

• The RISE-generated Data Product Specifications have been

created for RISE test purposes and are not intended to have

broader application without additional development.

• Given the reviewers comments, RISE agrees that there is

scope to revise some of the documents in order to clarify

their scope and content and the improve their usability.

• Further discussion with the Reviewer is proposed to clarify

the issues.


Conclusion

• RISE has been able to follow the original proposal workplan without any major changes.

• The Test Environment Development and testing of the Data Product Specifications is behind the original schedule but it is still possible to complete the project as scheduled

• (subject to satisfactorily addressing the External Reviewers Comments)

• Final Deliverables to include:• Revised Use Case Document

• Revised Methodology and Guidelines Document (inc. lessons learnt)

• Final Data Product Specifications (+ revised UML & GML if necessary)

• And:• RISE Test Environment Document

• Cost Benefit Analysis Report

• Exploitation Guidelines

Documents

Reference Information Specifications for Europe Overview Presentation to HACPB3