Inspire ec water standards and waterml workshop
Download
1 / 19

INSPIRE, EC Water Standards and WaterML Workshop - PowerPoint PPT Presentation


  • 173 Views
  • Uploaded on

INSPIRE, EC Water Standards and WaterML Workshop. Keiran Millard ([email protected]). HR Wallingford. Not for profit research, consultancy and software organisation in hydraulic engineering Floods, water, energy, maritime, coasts

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' INSPIRE, EC Water Standards and WaterML Workshop' - quon-bell


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Inspire ec water standards and waterml workshop

INSPIRE, EC Water Standards and WaterML Workshop

Keiran Millard

([email protected])


Hr wallingford
HR Wallingford

Not for profit research, consultancy and software organisation in hydraulic engineering

Floods, water, energy, maritime, coasts

Key role in the (on going) development of MarineXML

Marine data exchange (issues) are not much different to water data exchange

Leading INSPIRE Implementation Project MOTIIVE

Specifications for data exchange

Invited to contribute these findings to WaterML workshop and report on water data exchange in Europe

Page 2


Motiive scope
MOTIIVE Scope

Premise (of call)

GMES Service will be more cost-effective to deploy through the use and adoption of OGC/ISO Interoperability standards

This interoperability will entail true ‘mix and match’ between (and amongst) ‘core’ and ‘downstream’ data processors.

Scope (of Motiive)

How do you apply ISO/OGC Standards to the coastal/marine community?

Land:sea interaction (Marine Overlays on Topology)

What do the standards look like and how does a ‘cost benefit’ manifest itself?

Page 3


Motiive outputs
Motiive Outputs

What has Motiive achieved?

Development and Testing of INSPIRE Data Product Methodology

Community needs for harmonisation

Community Feature Types (published as UML and XSD)

Feature Type Catalogue implementation

Motiive, INSPIRE and OGC

MOTIIVE provides an ‘earth science’ perspective on Inspire

Delivery of a web-enabled catalogue for the Inspire Themes to lodge their FT’s

  • These findings will be useful to any community where datasets exchanged between members are ‘representation on environmental phenomena’ such as water quality, air temperature, water flows...

Page 4


INSPIRE Methodology for Data Products

Work within your community (SDIC – Spatial Data Interest Community) to develop these specifications


Observation feature types
‘Observation’ Feature Types

Data Product Specification related to measuring and observations requires Feature Types based on:

Scientific utility of the sampling regime

Limitations of the observation process

CSML (Climate Science Modelling Language)

Consistent with community practice

ESRI, UniData, NOAA

Feature types and storage descriptors

Binding to NetCDF, GRIB etc.

Implemented in UML and GML

Page 8


Csml feature types
CSML Feature Types

Presently in Release 2

Page 9


Csml feature types grid series
CSML Feature Types (Grid Series)

INSPIRE does not mandate operations for FTs – but most communities will require this

Page 10


Observation feature types1
‘Observation’ Feature Types

Motiive Testbed

Generic (CSML) Time Series

TidalWaterLevelTimeSeries

Graph and Table Service

Page 11






Waterml workshop
WaterML Workshop

  • Water Resources Information Model Workshop

    • Canberra, Australia, 25-27 September, 2007

    • There were 34 participants representing 18 organizations from 3 geographical areas (Australia-New Zealand, USA,-Canada, and Europe).

  • The workshop was convened in response to developments in:

    • the institutional environment, with increased expectations and demands for more extensive, integrated and timely information, frequently across organisational boundaries;

    • the technological environment, with improvements in information networks, sensor technologies, processing services, and with a proliferation of information models and exchange formats for water resources information.

In a nutshell…

XML is great. Everyone is using XML as a exchange mechanism for water data; but everyone is doing this differently.

This negates the bigger benefits of shared applications and information aggregation

How can we work together?


Wise and waterml workshop
WISE and WaterML Workshop

In addition to MOTIIVE, presented the WISE data exchange schemas and the WISE services.

This was not to comment on the schema design process, but to highlight the type of information that needs to be exchanged.

Page 21


Waterml workshop outputs
WaterML Workshop Outputs

  • What should be the thematic scope for a harmonized water resources information model? What key feature types should be included, and at what stage?

    • The scope for the water resources information model should contain a core set of entities that are not governed by other standards authorities.

    • These should include themes such as: surface water, atmospheric water and groundwater, and involve aspects such as water quality, quantity, water use including consumption, management and transport, as well as scientific modelling of water resources.

    • Key entities involved in these themes include: observations and measurements, properties that are observed and measured (e.g. porosity), features that possess properties (aquifer), processes and events (water flow, flood), human artefacts (instruments, wells).


Waterml workshop outputs1
WaterML Workshop Outputs

  • How should the harmonized model be achieved? What is the target level of abstraction for the model (conceptual, logical, physical). Should the model be an aggregation, conflation, or selection of existing initiatives?

    • A common conceptual data model should be developed for core entities; the model should be drawn from existing efforts (by re-using and harmonising existing content) and be modular, extensible and well-defined.

    • A small number of exchange formats (e.g. XML) should be developed to exploit the model, which should be hosted in a common registry alongside the model and related vocabularies. The common conceptual model and exchange format should be tested by existing information systems in a coordinated testbed.



Links
Links


ad