1 / 18

Hanko Rubach Dr. Christian Kiehle Judit Mays [rubach|kiehle|mays]@ l at- l on.de

Spatial Data Infrastructure Components as Building Blocks for Early Warning Systems. Hanko Rubach Dr. Christian Kiehle Judit Mays [rubach|kiehle|mays]@ l at- l on.de http://www. l at- l on.de/. EDIM Project Context. E arthquake D isaster I nformation System for the M armara Region, Turkey

kumiko
Download Presentation

Hanko Rubach Dr. Christian Kiehle Judit Mays [rubach|kiehle|mays]@ l at- l on.de

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. Spatial Data Infrastructure Components as Building Blocks for Early Warning Systems Hanko Rubach Dr. Christian Kiehle Judit Mays[rubach|kiehle|mays]@lat-lon.de http://www.lat-lon.de/

  2. EDIM Project Context • Earthquake Disaster Information System for the Marmara Region, Turkey • Joint-Project: University of Karlsruhe (GPIK), GeoForschungs-Zentrum Potsdam, HU Berlin, lat/lon GmbH, Delphi IMM, KOERI Istanbul • Funding provided by BMBF/Geotechnologien • Funded from 2007-2010 • Scope: SDI development with emphasis on sensor data, fine grained user management and sustainable spatial data infrastructure setup • Software development and conceptualisation

  3. 3 sub-projects: • In Part A, estimates of the degree of reliability will be delivered, as well as real-time information of earthquake source parameters and near-real-time shakemaps for the region. • In Part B, an advanced sensor technology of self-organising networks will be developed and tested, using Istanbul as an optimal geographical test site. • In Part C, data and information from A and B will be connected by a dynamic geo-information infrastructure and communicated with a user-oriented information and visualisation strategy.

  4. Motivation • Improve early warning information • Support rapid response • Provide decision support system components • Generate personalised visualisation for various stakeholders • Integrate sensor data • Use standardised software components • Use case: Marmara region

  5. .org • joint project between AG GIS, Dept. of Geography, Uni Bonn and lat/lon • free software in terms of FSF: LGPL • .aim • interoperability • management of geospatial data • setup of spatial data infrastructure (SDI) • .how • ISO-models and OGC-interfaces • abstraction from data sources • Java programming language / JEE web application • .now • most comprehensive implementation of OGC/ISO-standards in free software: • WMS & WCS (OGC reference implementations), WFS, CSW, WPS, 3D, SWE, etc. http://www.deegree.org/

  6. Sensor Data in Project SDI • Sensor information • Seismic events (E-Z-N-values) • Interface for further (pluggable) sensor nets • Uniform access over SOS protocol • Alerting network based on SOSEWIN software • Triggers notification in case of seismic events • Notification contains information on seismic event (time, location, seismic waves, etc.) • Propagation of events into Portal software

  7. Publish-Subscribe Mechanism • Indirect network access through publish-subscribe mechanism (SOAP communication) • Register portal component to message-notification broker • Receive alerting messages asynchronously • Parse alerting message and extract user-specific information • Bridges gap between portal software and real-time alerting system

  8. SOSEWIN Integration

  9. Interoperability – the technical details • SOS: OGC certified • Integration of external data: • historical seismic events • real-time access to on-site sensors in Istanbul

  10. Pre-EDIM Situation • Access to standardised interfaces and data services • Problem statement: • No integration of sensor data • No user-specific visualisation • No means for EWS

  11. Phase I – Integration of Security Layer • Security Layer as basis for personalisation • Proxy ensures standards-compliancy • User management based on services and database • Fine grained (spatial) definition of rights and roles

  12. Phase II – Integration of Sensor Data • Integration of sensor data Sensor Observation Service (SOS) • Integration of Early Warning Messages (SOSEWIN network) • Visualisation of sensor data (e.g. by charts)

  13. Visualisation of Sensor Data • Statistics based on sensor stations • Charts (e.g. for time series) • Raw data

  14. Phase 3 – Integration of Monitoring • Ensures operation of all critical services • Notifies administrator about service malfunction • Planned: Data & service backup through grid computing

  15. owsWatch – The SDI Service Monitor • Monitors OGC web services • Illustrates service response times • Triggers alerts in case of service malfunction (e.g. email, SMS, etc.) • Only accessible by authorised users

  16. Final Infrastructure – Challenges met • Integration of SOSEWIN access (through web service encapsulation) • Integration of sensor data (through deegree SOS Service & Client) • Integration of user specific rights management • Integration of service monitoring

  17. iGeoPortal – Access to the EDIM-Infrastructure • Personalised access to geoinformation • Individually configured for diverging user requirements (e.g. decision makers, administrators, etc.)

  18. Any questions? Spatial Data Infrastructure Components as Building Blocks for Early Warning Systems Hanko Rubach Dr. Christian Kiehle Judit Mays[rubach|kiehle|mays]@lat-lon.de http://www.lat-lon.de/

More Related