1 / 20

WP 9 (former Task 1b of WP 1): Data infrastructure

This project aims to develop a comprehensive data infrastructure for ESONET, including a knowledge base, sensor registry, and data management plan.

elks
Download Presentation

WP 9 (former Task 1b of WP 1): Data infrastructure

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WP 9 (former Task 1b of WP 1): Data infrastructure Robert Huber UNI-HB rhuber@wdc-mare.org Esonet 2nd all regions workshop, Paris 5.10.-7.10.2009

  2. Integration ESONET WP9 Data infrastructure Knowledge Base Data management plan Sensor Registry Sensor Observation Service

  3. Task 9a: Data management plan (Lead: Michel Andre [UPC] ) • Objectives: • Site specific documentation on data management • Data management protocol (guide) for ESONET/EMSO • Evaluation of demo mission data management: • Data collection, what data is acquired and in what way has it been processed • Data QC, what is being done to control the quality of the acquired data • Data archiving, what preparations are made to preserve the data in the long term • Data transfer, i.e. who has access to what part of the data and in what format is the data distributed. • Results: • D70 Updated data management plan

  4. Task 9b: Knowledge base (Lead: Robert Huber [UNI-HB] ) • Objectives: • General information platform and will serve data from all ESONET institutions and observatories • Topology of observatories • Sensor registry • Data management plan • Data archive • User friendly front-end service on the ESONET website to access the ESONET data infrastructure • Full text search engine • Mapping interfaces • Near real time access to selected demo sites (SOS) • Results: • Operational ESOMET web data portal • D44 ESONET knowledge base

  5. Task 9b: Knowledge base • Data portal • Access to archived data • Metadata portal • Data Warehouse • Distributed system (Open Source panFMP) • Based on Standards (OAI-PMH etc..data m. plan) • Access to Sensor Registry etc. • Access to SOS.(life data)

  6. Task 9b: Knowledge base • Data and information portal

  7. Task 9b: Knowledge base • Future data portal

  8. Task 9c: Data infrastructure: Sensor Registry (Lead: Eric Delory [dbscale] -> WP2) • Objectives: • Central catalogue of observatories and sensors • User friendly entry interface • Data stored in native XML database (eXist) as OGC standard SensorML (XML) • OGC CSW (Catalogue Service) as GEOSS interface. • Results: • Operational Sensor registry • D71 ESONET sensor registry

  9. Task 9c: Data infrastructure: Sensor Registry (Lead: Eric Delory [dbscale]) • existDB (native XML database) • written in Java: • Eclipse Ganymede IDE • Apache Tomcat 5 Application Server • Open SourceJava libraries • web based

  10. Task 9c: Data infrastructure: Sensor Registry (Lead: Eric Delory [dbscale]) • Prototype options: • Register a new sensorML • Upload an existing sensorML • Add a History • Add a new Component

  11. Task 9c: Data infrastructure: Sensor Registry (Lead: Eric Delory [dbscale]) • Register a new sensorML: • Predefined ESONET Obs • Sensor type spec. forms • Basic sensor description

  12. Task 9c: Data infrastructure: Sensor Registry (Lead: Eric Delory [dbscale]) • Upload existing sensorML: • Upload XML files from yourharddisk

  13. Task 9c: Data infrastructure: Sensor Registry (Lead: Eric Delory [dbscale]) Add History (events)

  14. Task 9c: Data infrastructure: SOS development and implementation(Lead: Thierry Carval [IFREMER]) • Objectives: • Sensor Observation Service (SOS) software as interface for sensors and retrieving sensor data. • Provide observatories with SOS services which will be used to connect to these observatories and collect their data. • Data wrapper tools if necessary • Results: • Operational SOS • D43 Data infrastructure productive version

  15. Task 9c: Data infrastructure: SOS development and implementation(Lead: Thierry Carval [IFREMER]) • SOS: • Observation Service Interface Standard • OGC (Open Geospatial Cons.) SensorWeb Enablement (SWE). • API for managing deployed sensors and retrieving sensor data and specifically “observation” data

  16. Task 9c: Data infrastructure: SOS development and implementation(Lead: Thierry Carval [IFREMER]) • Ifremer‘s SOS -> • XML output • Machine-machine protocol

  17. Task 9c: Data infrastructure: SOS development and implementation(Lead: Thierry Carval [IFREMER]) SOS Client

  18. Task 9d: Data infrastructure: Prototype implementation(Lead: Robert Huber [UNI-HB] ) • Objectives: • Putting things together.. • Implement the ESONET data flow from acquisition to data publication as drafted in dmp • Use OGC and other standards (SOS, CSW, OAI-PMH) for data access, data exchange (GEOSS, GMES etc.) • Test of infrastructure -> demo missions • Results: • Operational Data infrastructure • D43 Data infrastructure productive version

  19. Task 9d: Integration

  20. Thank you!

More Related