Download to get the file - Marine Metadata Interoperability

ResEau:
A Water Portal SensorWeb
Implementation
John Cree
National Information Strategies Division
Strategic Information Integration Directorate
Environment Canada
08 March 2006
RésEau:
A Water Portal SensorWeb Implementation
RésEau is a Government On-Line demonstration initiative
focused on water information. RésEau supports clean,
safe, and secure water for all Canadians and ecosystems.
Specifically, RésEau seeks to establish partnerships and
projects to demonstrate the sharing, discovery, access, and use
of water information over the Internet through the use of
standards and specifications endorsed by the CGDI and the
OGC.
2
Project Overview
RésEau – “Building Canadian Water Connections”
Projects and Partnerships: leadership role in pulling together existing data and
information (including water quality, quantity, and use) from distributed networks of
partners across numerous Canadian jurisdictions
Sound Science / Technical Architecture
Scientific integrity is key starting with credible water quality, quantity and use data.
Standards and specifications endorsed by the Canadian Geospatial Data
Infrastructure and the Open Geospatial Consortium are an essential foundation of
RésEau
Products - Interactive Web Portal
This Interactive Web Portal forms the dynamic focal point of RésEau. The portal
includes data, interpreted information, tools, and services to facilitate the
interconnection of water information from distributed sources to promote a greater
understanding of complex water issues for enhanced decision making.
3
Standards and Specifications
Standards Used: (to link to water related info in any given geographical
area)
• OGC
–
–
–
–
WMS, WFS - for mapping of monitoring locations
WMC documents – Load/save application state, predefined maps
SensorML – description of monitoring locations, variables measured
SOS created on one set of monitoring stations/variables
• FGDC
- for description of information collections, tools e.g. Water Use
Calculator
• GeoRSS
- for geo-relevant news feeds (locally, by watershed etc.)
4
Application Framework
3 –Tier
framework
End-User
Applications
(WFS/WMS)
ftp Valids
Server
GCMD
SOS
Search &
Discovery
Services
CIP RM
Translator
Web
Client
EDG
Gateway
CIP
ODL
CIP-V0 Parser
Constructor
IMS
CIP
V0-CIP
Web
ServerODLTranslator CIP Client
Services
Web
ftp Valids
Constructor
Parser
Components
GCMD
Client
Server
ODL
CIP
ODL
EDG
Web IMS Server
CIP-V0
Constructor
Parser
IMS
CIP
Gateway
Client (GSFC)
V0-CIP
Distributed
Data Components
Client CIP
TranslatorODLServer
Web
Constructor
Parser
Client
ODL
IMS Server
(GSFC)
Maps courtesy of Environment Canada
CIP RM
Translator
XML
5
SensorWeb Implementation
Why SensorML?
Environment Canada is a monitoring department
Vast amount of our information holdings are instrument based
such as:
•
•
•
•
•
Water Quality*
Water Quantity*
Air Quality
Climate Monitoring
Pollutant Releases
Requirement to:
•
•
•
•
Describe instruments (Characteristics, Properties) and monitoring sites
Report Observations / Measurements
Integrate real-time and non real-time information
Disseminate information and maintain Interoperability
6
SensorML Implementation
- How does it fit
- physical location as <sml:System> using system.xsd
- identification, classification, description, related info/links, history
of events at stations, variables measured/outputs
- RésEau prescribed a SensorML template for partners
- based on a “typical” water monitoring station
- funding for partners was contingent on producing data and
metadata following prescribed standards/profiles
- SensorML version 1.0.30 – Sept. 2005
- Implementation
- database to XML mapping (Altova, XSLT transformations)
- produced a unified output of SensorML
- Example (raw XML):
http://maps.seapei.ca/crq/SensorML/ca.seapei.crq-1.xml
7
SensorML Discovery
– Requirements
• Discover station metadata
• Visualize station locations
• Access observation data
8
Station Discovery
Framework
Active
Hydrometric
Real-Time
Sensor
Observation
Service
Active
Hydrometric
Real-Time
Data/Map
Server
WFS
ftp Valids
Server
GCMD
Web
Client
EDG
Gateway
Web
GCMD
Client
CIP
ODL
CIP-V0 Parser
Constructor
IMS
CIP
V0-CIP
ServerODLTranslator CIP Client
ftp Valids
Constructor
Parser
Search
&
Server
ODL Discovery
CIP RM
Translator
Services
CIP
ODL
EDG
Web IMS Server
CIP-V0
Constructor
Parser
IMS
CIP
Gateway Client (GSFC)
V0-CIP
Distributed
SensorML
Documents
Harvester
Client CIP
TranslatorODLServer
Web
Translator
Constructor
Parser
stationList
SensorML
Client Harvester
SensorML
XML
ODL
SensorML
CIP RM
IMS Server
(GSFC)
Maps courtesy of Environment Canada
9
Sensor Observation Service
– For extraction of station data
– SOS (OGC 05-088r1, Version 0.1.1)
– Deployment using MapServer
SOS Implementation Details:
http://mapserver.gis.umn.edu/development/rfc/ms-rfc-13
SOS: Get Capabilities:
http://map2.ns.ec.gc.ca/envirodatows/service.aspx?service=SOS&version
=0.0.31&request=GetCapabilities
SOS: DescribeSensor:
http://map2.ns.ec.gc.ca/envirodatows/service.aspx?service=SOS&version
=0.0.31&request=DescribeSensor&sensorID=YT10AA0001
10
Station Discovery
Framework
Active
Hydrometric
Real-Time
Sensor
Observation
Service
Active
Hydrometric
Real-Time
Data/Map
Server
ftp Valids
Server
GCMD
Web
Client
EDG
Gateway
Web
GCMD
Client
CIP
ODL
CIP-V0 Parser
Constructor
IMS
CIP
V0-CIP
ServerODLTranslator CIP Client
ftp Valids
Constructor
Parser
Search
&
Server
ODL Discovery
CIP RM
Translator
Services
CIP
ODL
EDG
Web IMS Server
CIP-V0
Constructor
Parser
IMS
CIP
Gateway Client (GSFC)
V0-CIP
Distributed
SensorML
Documents
Harvester
Client CIP
TranslatorODLServer
Web
Translator
Constructor
Parser
stationList
SensorML
Client Harvester
SensorML
XML
ODL
SensorML
CIP RM
IMS Server
(GSFC)
Maps courtesy of Environment Canada
11
SensorML System
Water monitoring station profile:
With stylesheet applied:
http://map.ns.ec.gc.ca/ReseauDataSearch/showMetadata.do?type=statcat&
xmlfile=http://gov.pe.ca/envengfor/waterdata/XML/0.xml
Raw SensorML XML:
http://gov.pe.ca/envengfor/waterdata/XML/0.xml
Stylesheet:
ResEauSensorML.xsl
12
ResEau:
A Water Portal SensorWeb Implementation
Questions?
John Cree
[email protected]
13