19
http://www.52north.org/wps Climate Change Interoperability Challenge Project Proposal

Http:// Climate Change Interoperability Challenge Project Proposal

Embed Size (px)

Citation preview

Page 1: Http:// Climate Change Interoperability Challenge Project Proposal

http://www.52north.org/wps

Climate Change Interoperability ChallengeProject Proposal

Page 2: Http:// Climate Change Interoperability Challenge Project Proposal

http://www.52north.org/wps

Story

We know

• Climate change happens!

• Number of natural disasters increases dramatically

Page 3: Http:// Climate Change Interoperability Challenge Project Proposal

http://www.52north.org/wps

Story

Page 4: Http:// Climate Change Interoperability Challenge Project Proposal

http://www.52north.org/wps

Story

Consequences

• Question: How to deal with the aftermath?

• Observations to forecast such disasters and reduce the impacts

Page 5: Http:// Climate Change Interoperability Challenge Project Proposal

http://www.52north.org/wps

Scenario

• Feature of Interest: Elbe in Germany

• Flooding in Dresden Area

• Background: Hundret year flood in 2002

Page 6: Http:// Climate Change Interoperability Challenge Project Proposal

http://www.52north.org/wps

Flooding

Page 7: Http:// Climate Change Interoperability Challenge Project Proposal

http://www.52north.org/wps

Flooding

Prevention is better (and cheaper) than cure.

Page 8: Http:// Climate Change Interoperability Challenge Project Proposal

http://www.52north.org/wps

Sensors along the Elbe

Page 9: Http:// Climate Change Interoperability Challenge Project Proposal

http://www.52north.org/wps

Classic Sensors

Page 10: Http:// Climate Change Interoperability Challenge Project Proposal

http://www.52north.org/wps

Concept

• Hard wired

• ArcMap not used as viewing client

• Uses default browser with thin client

• Featureclass matching the input must exist

Page 11: Http:// Climate Change Interoperability Challenge Project Proposal

http://www.52north.org/wps

Observation

• Observation of features with potential danger

• Battery of gauge sensors

• Measuring water level (and changes)

• Storing into SOS• Integration into SDI

via SWE

Page 12: Http:// Climate Change Interoperability Challenge Project Proposal

http://www.52north.org/wps

What is SWE actually?

Page 13: Http:// Climate Change Interoperability Challenge Project Proposal

http://www.52north.org/wps

Connect SWE with AGD

• AGD Extension for SOS connections

• Automated geodatabase/featureclass creation

• Automated updates• Triggering further

modeling processes• Enable security• Integration of other SWE

services (z.B. SAS)

Page 14: Http:// Climate Change Interoperability Challenge Project Proposal

http://www.52north.org/wps

Prototype available

• Uses external client for visualizing gauge values

• No automated data structure creation (FC, GDB, etc.)

Page 15: Http:// Climate Change Interoperability Challenge Project Proposal

http://www.52north.org/wps

Concept

• Phase I.

• Phase II.

Page 16: Http:// Climate Change Interoperability Challenge Project Proposal

http://www.52north.org/wps

SOS (real time)

ArcGIS

WMS (AGS)

WFS (AGS)

SOS (canned data)

Phase I – Extension

Page 17: Http:// Climate Change Interoperability Challenge Project Proposal

http://www.52north.org/wps

Phase II – Security Layer

Page 18: Http:// Climate Change Interoperability Challenge Project Proposal

http://www.52north.org/wps

CCIP

• Phase I: Extension development (July – September)

• Phase II: Impl. of an security layer (September – Mid-October)

• Phase III. Testing and Presentation (from October)

Page 19: Http:// Climate Change Interoperability Challenge Project Proposal

http://www.52north.org/wps

Longterm

• AGS-SOS Integration

• TBD.