|
1
|
- Michael S. Scott, PhD
- msscott@salisbury.edu
- October 28, 2006
|
|
2
|
- What is the ESRGC?
- Project background, goal, & method
- Vulnerability project results
- Conclusions
- Goals of this workshop
|
|
3
|
- Eastern Shore Regional GIS Cooperative
- Mission: To support the development of GIS technology in municipalities
and counties on Maryland’s Eastern Shore
- Funded by the Regional Councils of the Mid-Shore and the Lower Shore
- www.esrgc.org
|
|
4
|
- Vulnerability – Potential for loss
- Situated at the intersection of the physical hazard and the social
system
- Unfortunately, not simply a matter of map overlay
- Depth of flood, recurrence, structure characteristics, mitigation
techniques, etc
- Very complex, interrelated system
|
|
5
|
- Complete a General Building Stock Damage and Loss analysis for a
100-year flood event for each county in the State, including the City of
Baltimore, using the latest HAZUS-MH Flood module
|
|
6
|
- For each jurisdiction, calculate 100-year flood zone using HAZUS-MH,
intersect with the amount and type of building stock to calculate loss
potential
- Run both riverine and coastal where appropriate
- Complete a Level 1 HAZUS analysis
- Using default data
- Consistent quality across jurisdictions
|
|
7
|
- Report will be made available at www.esrgc.org later today
- Over 1,328 square miles of Maryland are vulnerable to the 100-year flood
- 15 jurisdictions (of 24) are vulnerable to coastal flooding
|
|
8
|
- Building stock exposure (in 2001): $7.99 billion
- Building damage in sq ft: 109,665,000
- Worcester: over 21 million or
19.4% of state total
- Somerset: 5.7 million but 68% is
predicted to be “substantial
- Building damage in numbers of structures: 44,755
- Anne Arundel: 7,038 buildings damaged
- Direct economic losses: $8.12 billion
- Prince George’s: $1.28 billion
- Prince George’s, Anne Arundel, and Worcester equal almost 40% of
Maryland’s total loss potential
|
|
9
|
|
|
10
|
|
|
11
|
- Vulnerability to flooding in Maryland is not evenly distributed
- Prince George’s, Worcester, Anne Arundel, Montgomery, Washington,
Howard, Baltimore County, and Baltimore City disproportionately
effected
- Areas with large vulnerable areas happen to be forecasted for increased
development
- Dorchester, Somerset, Talbot, Caroline, Worcester
- There is a need to look more closely at particular trouble spots to
further refine the analysis
|
|
12
|
- Introduce the capabilities and limitations of HAZUS-MH
- Discuss the functionality of HAZUS-MH
- Examine the steps necessary to complete a Level 1 HAZUS-MH model run
|
|
13
|
- HAZUS-MH 1.2 – Level 1
- What it is and what it isn’t
- Capabilities
- Variables for consideration
- How it works
- How you get it
- Hardware requirements
- Software requirements
- Installation hints
|
|
14
|
- Designed to estimate a wide range of losses from flood (as well as other
hazards)
- Internally, several stochastic flood models provide the engine, as well
as ArcGIS 9.1.1
- Uncertainty/error are significant but not quantified in a Level 1
analysis
- New version scheduled to be released in late summer/early fall
|
|
15
|
- An rough estimate of potential losses
- A very useful and consistent tool to measure differences in
vulnerability across and between counties
- A dynamic modeling tool that allows the user to ask “what if” questions
- Helpful to prepare for the inevitable
- Complicated and computer-intensive
|
|
16
|
- A vulnerability crystal ball
- Calibrated to your specific economic situation
- Any better than its inputs
- A substitute for a engineering-based flood study
- Easy to use or interpret
|
|
17
|
- Calculating flood depths in both riverine and coastal contexts
- Modeling losses to the census block level
- Examining multiple dimensions of loss
- Analyzing multiple recurrence intervals or specific discharge amounts
- Viewing up to 4 counties simultaneously
|
|
18
|
- 30-meter digital elevation model
- General Building Stock
- 2000 Census of Housing data for buildings
- Dun & Bradstreet data for non-residential buildings
- US Department of Energy for regional differences in square footage,
construction types, etc
- Limited number of stream gauges
|
|
19
|
- Creates flow grid from DEM
- Identifies stream reaches from flow grid
- Associates each reach with a drainage area
- Identify stream gauges in drainage area
- Approximate the floodplain for each reach
- Create a set of flood depth cross sections
- Interpolate from cross sections to grid cells
|
|
20
|
- Characterize the shoreline (i.e. bluffs, dunes, erosion control)
- Enter flood depths per recurrence interval plus wave height (if
appropriate)
- Run one or more coastal flood models
- Dune/bluff erosion, wave height, and wave runup)
- From models, determine flood depth
|
|
21
|
- Uses depth-damage curves that need:
- Occupancy class, foundation type, and assumed first floor elevation
- Depth of flooding throughout the census block
- Uses NFIP claims to create depth-damage curves for “typical”
construction types
- Matches up buildings in a block and depth within a block to depth-damage
curves to estimate damage
|
|
22
|
- Request a copy from FEMA
- http://www.fema.gov/hazus/
- Set of DVDs and CDs
|
|
23
|
- FEMA recommended configuration
- 2.5 Ghz processor
- 512 GB RAM
- 80 GB HDD
- 800x600 video card
- ESRGC configuration
- 3.4 Ghz processor
- 2 GB RAM
- 80 GB HDD
- 128 MB, 1600x1200 video card
- Still takes approximately 8-10 hours per model run
|
|
24
|
- HAZUS-MH 1.1
- Avoid version 1.0 if at all possible
- Processing takes 3-4 times as long (several days for one county)
- Limit on raster processes
- Very buggy
- ArcGIS 9.0 – Service Pack 1
- Current SP is 3…must keep old version of Arc 9
- Must have ESRI’s Spatial Analyst
- Windows XP, Service Pack 1
|
|
25
|
- Start with a fresh copy of Windows and ArcGIS (no SP 2)
- Copy the entire data DVD on to the hard drive
- Must manually change the registry entry to point to the new location
- Increase your virtual memory to at least 4 GB
- If you are getting more than a couple hydrology/hydraulic errors in a
county, it’s possible you have corrupted installation disks
- If you have disks from before Feb 28, you need a major patch
|
|
26
|
- Create a study region
- Study region set-up
- Study case set-up
- Riverine flooding parameters
- Coastal flooding parameters
- Determine riverine and coastal hazard
- Analysis/loss estimation
- Report results
- Or…import a model run that’s already done!
|
|
27
|
- Choose your state
- Choose your county
- All flood modeling is done at the county level using census blocks,
even if you don’t want to analyze an entire county
- Maximum of 4 counties
- Implications in studying watershed vulnerability
|
|
28
|
|
|
29
|
|
|
30
|
|
|
31
|
- Decide on type of flooding
- Riverine, coastal, or both
- Makes a difference in the size and shape of the DEM you’ll need
- Download DEM from NED online
- The button to “Navigate directly to NED download” does not seem to be
working
- Go to http://seamless.usgs.gov and enter the bounding coordinates
manually
- Set the DEM data paths
- Will begin to build the hillshade visualization
|
|
32
|
|
|
33
|
|
|
34
|
|
|
35
|
|
|
36
|
|
|
37
|
|
|
38
|
|
|
39
|
|
|
40
|
- Calculate stream reaches
- Must chose minimum drainage area
- Essentially a level of precision
- Limited to computer processor and time
- Doesn’t modify the chosen floodplains
- Create study case
- Name and description
- Can have multiple study cases per county
- Different parameters per study case
- Selecting reaches and coastlines to be included in the study case.
- Be sure to select all the reaches and coastlines up front…you can’t
add more later
|
|
41
|
|
|
42
|
|
|
43
|
|
|
44
|
|
|
45
|
|
|
46
|
|
|
47
|
- Hydrologic analysis
- Individual drainage basins can be run separately
- All in a county can be selected at once
- If the analysis fails, there is a log to check what stream reach it
failed on
- This allows you to remove the offending reach
|
|
48
|
|
|
49
|
- Shoreline characterization
- Type of shoreline
- Rocky, large/small dunes, flood control structure
- Controls what models will run
- Flood height
- With or without wave setup
- 10, 50, 100, and 500 year flood
|
|
50
|
|
|
51
|
|
|
52
|
|
|
53
|
|
|
54
|
- By recurrence interval
- 10, 50, 100, and 500
- Single recurrence interval
- By discharge value
- By annualized loss
|
|
55
|
|
|
56
|
|
|
57
|
|
|
58
|
|
|
59
|
|
|
60
|
|
|
61
|
|
|
62
|
- Possibilities range from building stock damage to casualties to
essential facility damage to debris removal costs
- This study focused on general building stock damage and loss, as well as
indirect economic losses
- Includes damage by type and by occupancy, count of damaged buildings,
and economic losses such as structural damage, contents damage,
relocation costs, wage losses, etc.
- Some analysis results are dependent on others but the model accounts for
that automatically
|
|
63
|
|
|
64
|
- Results are reported with maps and tables
- Every variable calculated can be mapped by census block
- Crystal Reports automatically generates summary reports
|
|
65
|
|
|
66
|
|
|
67
|
|
|
68
|
|
|
69
|
|
|
70
|
|
|
71
|
|
|
72
|
|
|
73
|
- Luckily, most of this work has been done for you!
- Can import the model run used for the state study to examine your
county’s vulnerability
- Any changes to the model parameters will require a re-run.
|
|
74
|
|
|
75
|
- In the past:
- Counties without any results
- Stream reaches that cannot have hydrologic analysis completed
- Stream reaches that cannot have hydraulic analysis completed
- “Riverine and Coastal” model runs returns only coastal results
- Most of the major errors have been fixed with the patch released in
March 2005
- Now, the concerns turn to the more insipid error: those within the results
|
|
76
|
- Be very skeptical of HAZUS-MH until you have a reason not to be
- With the number of critical errors present in the first iteration of
this release, one has to wonder what errors lie beneath
- No quantification of uncertainty
- It’s just too new…hasn’t been properly vetted by the scientific
community in a variety of situations
|