®®

© 2011 Open Geospatial Consortium, Inc.© 2011 Open Geospatial Consortium, Inc.

Modernization of the Surface Modernization of the Surface Observations Hub in Meteo-France based Observations Hub in Meteo-France based

on SWE standards on SWE standards

76th OGC Technical Committee

Bonn, Germany

Yann GéninAlexandre Robin, Frédéric Guillaud

March 2, 2011

Sponsored byUnited Nations Platform for Space-based Information for

Disaster Management and Emergency Response - UN-SPIDER

OGC®

Current surface observation landscapeCurrent surface observation landscape

• Heterogeneous networks– COBALT, RADOME, PATAC, AURORE, …

> 1000 real time stations

• Regional acquisition (RADOME Hub)

Copyright © 2011 Open Geospatial Consortium

552 RADOME

~500 PATAC (autres et RIC)

~500 RIC SPC (DGPR)

250 OARA (Salamandre, feux de forêt, sémaphores…)

OGC®

Acquisition levelsAcquisition levels

• Sensors – Plugged onto in-situ station computer …

• In-situ station computers : – depend on heterogeneous networks …

• XARIA (RADOME network)

• PULSIA (SALAMANDRE network)

• OPALE/COBALT (synoptic/ aeronautic

network with human presence)

• MIRIA (measure networks not under

MF responsibility : Power plants,

railways, motorways, …)

• NIVOSE (mountain networks)

• Regional acquisition system – RADOME hub

Copyright © 2011 Open Geospatial Consortium

OGC®

Project’s objectives

• Re-engineering of the regional RADOME hub• Centralization in Toulouse (redundancy in Paris )• Ability to handle new sensors, new (standard) transport

protocols (http)• Standardization of public interfaces (Web Services, XML,

OGC SWE)

OGC®

Target architecture

Raw Data Harvesting Platform (PFC)

SWE Server

(52 North)

Networks Monitoring & Administration

SOS1.0

SPS1.0

BUFR encoding

SensorML

Data SWE Common

BUFS Ascii

FTP

Data dissemination TRANSMET

WMO BUFR

Dial-Up MODEMS

RAS Server(multiple communication

channels aggregation)

In-Situ Station

ComputerIn-Situ Station

Computer

In-Situ Station

ComputerPublic Switched Telephone Network

OGC®

SWE concepts mapping : Overview

• Feature-of-Interest– The stations and their localizations if any (ie : 07149, Orly Airport)

(feature-of-interest)

– Localization in the Station (ie : 07149 QFU 26)(feature of interest as well, sampling points in the feature of interest)

• Offering– Parameter aggregate on the basis of sensor type :

(ie : Wind, Temperature, Moisture, Visibility, Precipitations …)

• Procedure – The whole network for each offering

(ie : Wind Network, Temperature Network, …)

– For each station (in-situ metrological configuration)

• Observed Properties– Parameters (or phenomena) > 150 !

OGC®

SWE Mapping issues : case of multiple localizations

06

26

24

08

20

02

07149-Main 2608 MED

2406 MED

Feature-Of-Interest

Sampling-Points

OGC®

Issue : Phenomenon stuff

Surface parameters

WMO tables

CF conventions

• Up to 150 parameters• Many of them undefined in existing registries• Fortunately not available everywhere !

• RDF / SKOS dictionary seems to meet requirements• hierarchical / horizontal semantic relation• Multilingual definitions

OGC®

Data acquisition

• Measurement frequency up to 1 minute• Up to 150 parameters• Up to 1000 real-time stations• Acquisition wave : up to 100 stations to be processed within

a 30 seconds slot (pool of 100 dial-up modems)• Up to one month data retention• This leads to huge « Observation » table

– Double partitioning TimeStamp / Offering

• SWE service : SOS InsertObservation

OGC®

Network administration

• Create / Update / Delete station's profile– Communication (protocol, …)– Identification, localization – Metrological configuration (sensor modules, addresses,

calibration parameters, …)– Planning for data acquisition & data transfer – Subscriptions for notifications (parameters, alert thresholds)

• SWE Services : SOS & SPS – SOS RegisterSensor / UpdateSensor / DeleteSensor– SPS Submit / GetStatus – Issue : Useful UpdateSensor / DeleteSensor not supported

in SOS 1.0 (will be available in SOS 2.0) This has been implemented on 52 N by Alex Robin

• SWE Data model : SensorML

OGC®

Network monitoring

• Sensors and in-situ computer station status – Daily status message (sensors and station status)– Daily and on-demand station’s logs (to be visualized as is)– Communication logs (after each transfer, to be visualized as is)

• SWE Service : SOS InsertObservation / GetObservation – Sensor status parameters are handled as meteorological

properties in a dedicated offering– The daily status message is decoded, and the sensor status

information stored in the 52 N database through SOS InsertObservation

– Sensor status values are retrieved through SOS GetObservation for monitoring.

– Time series for met parameters are also retrieved through SOS GetObservation for monitoring in order to detect anomalies.

OGC®

Next steps & milestones

• Finalize the server : By October 2011– Initialize station / network configuration– Data quality checks– Statistical parameters computation– RDF/SKOS phenomena dictionary

• Developments on client side : March – December 2011– Administration / Monitoring console– SWE Common to BUFR

• SWE 2.0 migration : Late 2011 – Early 2012 – depending on 52N availability

• Upper level observations ?• Feedback at September and / or December 2011 TCs

OGC®

© 2010 Open Geospatial Consortium

Wind Offering …

OGC®

© 2010 Open Geospatial Consortium

Sample RDF/SKOS Dictionary