FeatureLevel Inundation Detection and Alerting for Improved flood

Feature-Level Inundation Detection and Alerting for Improved flood Mitigation Brian Marchand GEOG 596 A Winter 2010

GEOG 597 A Flood Hazards One of the most common hazards seen in the U. S. Major events occur almost yearly Inundated areas vary Warning lead-times vary The effects can be severe 2

GEOG 597 A Hurricane Floyd (Sept 1999) Road closures hard to track Evacuations difficult to plan Infrastructure inundated 57 Deaths $6 Billion in damage 3

GEOG 597 A Flood Mitigation Goals Protect life Protect property Protect the environment Increase public preparedness and response 4

GEOG 597 A Mitigation Through Mapping NOAA, NWS, USGS water status map 5 Hydrograph showing current and predictive conditions

GEOG 597 A Mitigation Through Mapping FIMAN web-based map viewer 6 FIMAN gage information and inundation map

GEOG 597 A Proposed System Map the impact on individual features Automated Time-based Issue alerts for inundated features Serve data using open formats Visualization using common tools 7

GEOG 597 A System Definition Floodplain Features (Roads) High Resolution DEM 8 Alerts Flood Inundation Maps Inundated Features in Google

GEOG 597 A Flood Inundation Maps Mark inundated areas Produced from various sources Not reliant on any technique Change over time Represent system input 9 10 ft River Stage Height 20 ft River Stage Height

GEOG 597 A Floodplain Features Advanced warning improves mitigation efforts Feature monitoring focuses efforts Many types of features are worthy of monitoring Respond differently to each type 10 Inundated roads at a 10 ft river height Inundated roads at a 20 ft river height

GEOG 597 A Digital Elevation Model (DEM) 3 D surface analysis requires a high-resolution DEM Determines feature elevation Determines the depth of inundation Requires a good source of data Tarboro/Princeville NC Road features in the DEM 11

GEOG 597 A Inundation Analysis 12

GEOG 597 A Inundated Features Highlight inundated features Stored separately from input feature sources Store additional information as feature attributes Time dependent Establish symbology for inundated features 13 Inundated Roads Traffic Conditions in Google Maps

GEOG 597 A Spatial Data Server Present data in most flexible format Store on server using Open Geospatial Consortium (OGC) formats Fully symbolized data Web Mapping Service (WMS) Keyhole Markup Language (KML) Fully attributed data for maximum exploitation Web Feature Service (WFS) 14 Inundated Roads in Google Earth

GEOG 597 A Change Detection & Alerting Alerts proactively sent to people Maximize advanced notice Improves awareness Requires stakeholder registration Change detection determines alerts are sent Alerts issued as events Event handlers send notifications 15

GEOG 597 A Prototype Scope Implementing the proposed system is outside of the scope of a capstone project Prototype Limitations Focused study area Predetermined inundation polygons Restrict analysis to a couple feature types 16

GEOG 597 A Study Area Tarboro/Princeville North Carolina Heavily flooded during Floyd USGS river gage data with live updates Inundation maps for river levels High resolution DEM Current roads 17 http: //nc. water. usgs. gov/flood/finmap/ Study Area 42. 7 ft River Stage

GEOG 597 A Prototype Approach Data preparation using Arc. GIS Simulated river stage information and acquire live from USGS Server technology using open-source tools 18

GEOG 597 A Goals and Objectives Improve flood mitigation tools Work with dynamic map layers Build experience with unfamiliar technologies Generate alerts from changes in data Build a prototype system 19

GEOG 597 A Anticipated Results Simulated and live river data will establish inundated areas Inundated features will be reflected in an continually updated layer Alerts will be generated for changes in the inundated features Inundated feature layers can be viewed in a broad range of clients 20

GEOG 597 A Project Timeline Prototype Implementation q Week 1 Data gathering and processing q Week 2 -3 Geodatabase development q Week 4 -6 Develop server processing framework q Week 7 Process live data (WSDL) q Week 8 Produce dynamic inundation maps q Week 9 -10 Spatial comparison of inundated features q Week 11 WFS, WMS, KML Geo. Server setup q Week 12 Event based notification q Week 13 Send text or email alerts q Week 11 -15 Final report 21

GEOG 597 A Future Considerations Navigation systems can incorporate and route around road closures Evaluate losses from property values 22

GEOG 597 A References 1. Federal Emergency Management Agency (2009). Flood Hazards, Retrieved February 11, 2010 from http: //www. fema. gov/hazard/flood/index. shtm 2. National Oceanic and Atmospheric Administration (2009). Hurricane Floyd 10 th Anniversary, Retrieved February 11, 2010 from http: //www. erh. noaa. gov/mhx/Floyd/index. php 3. Federal Emergency Management Agency (2010). News Photos, Photograph Library, http: //www. photolibrary. fema. gov/ 4. Colby, J. D. , Mulcahy, K. A. , Wang, Y. (2000). Modeling flooding extent from Hurricane Floyd in the coastal plains of North Carolina. Environmental Hazards. 2, 157 -168 5. U. S. Geological Survey (2009). Flood Hazards, Retrieved March 5, 2010 from http: //www. usgs. gov/hazards/floods/ 6. Gupta, S. , Hartkopf J. , and Ramaswamy, S. (1998). Event Notifier: A Pattern of Event Notification, Java Report, Vol. 3, No. 7, SIGS Publications. 7. Jones, J. L. (2004). Mapping a Flood…Before It Happens. U. S. Geological Survey Fact Sheet 2004 -3060, Retrieved January 18, 2010, from http: //pubs. usgs. gov/fs/2004/3060/ 8. Gall, M. , Boruff, B. J. , Cutler, S. L. (2007). Assessing Flood Hazard Zones in the Absence of Digital Floodplain Maps: Comparison of Alternative Approaches, Natural Hazards Review ASCE, February 2007 23

GEOG 597 A Questions? 24