Skip to content

Creates zones of shared risk, correct building location and elevation, and conduct economic assessment for efficient defense against storm surges

License

Notifications You must be signed in to change notification settings

rajaoberison/SeaWallToolBox

Repository files navigation

This is still a work in progress. I started working on this as part of the Geospatial Software Design class at Yale FES. My submission at the time is in the pdf document.

-! This is an older version of the tool. -!
-! The updated version is not public yet -!

SeaWall ToolBox

WHAT and WHY

Coastal areas are annually exposed to risk of flooding from storm surges. With the expected increase on storm intensity due to climate change, more and more properties are at risk. This tool will allow you to identify areas at risk and get insights on the efficiency of their protection.

WHAT you’ll NEED

High resolution elevation data (ideally Lidar). Geospatial data (shapefile) of the properties and their economic values. Expert knowledge of the storm surges on the locality of interest.


HOW it WORKS

Within a specific coastline there are main entry points where the storm surges can come in. Each entry point will affect the decision in the design, nature, and feasibility of the seawall to be established. One of the main challenge in coastal defense is the identification of these entry points and consequently the delimitation of the coastal segment for each seawall.

Sea water flooding

As storm surge intensify, longer walls are needed. The ability to predict identify potential water entry during the design of the wall is therefore crucial as the storm intensity are expected to increase in the future.

Given these challenges, 3 main questions are to be answered prior to a seawall construction:

  • How many segments are there within the study area?
  • What and how much are the capital in harms’ way for each segment?
  • Which of the segments are worth protecting economically and ecologically?

Which requires the availability of these information:

  • Elevation data of the region
  • Spatial data of property values (natural, public, and private capital)
  • Economic model of damages and cost of seawall construction


1. How many segments?

Segments location and length depend on the scenario (defined by the expert) in the design of the seawall.

Two elevation values need to be identified in order to determine the segments:

  • Mean High Water (which under US Law is where wall should be built)
  • Local storm surge level potential within the timeframe

Then for each of the two elevation values, contour lines will be created and seawall segments are where they are the closest to each other (i.e. where the elevation gradient is highest and sea water split in two directions)



2. What capitals are in harms’ way?

When the segments is delimited, they will be connected with their corresponding storm surge line: which will produce a polygon, a region of interest for each segment.

Anything within that region will be in harms’ way.

With the spatial data of the properties available, ArcGIS’s Select by Location tool can highlight these at risk capitals. The tool will automatically do that for the user.





3. How much are the potential damages?

For the selected properties, average elevation can be calculated using Zonal Statistics as Table, and then damages from storm can be calculated.

This tool will use a simple Total Benefit Analysis for the wall by calculating total annual benefits/damages for each segment and the benefits per segment length units. These damages are caluculated based on the percent of damage given the average elevation of the property and the user-defined storm surge level.

Wall considered feasible are the ones providing economic value.





Here is a short video on how it works: https://youtu.be/8dYU8tFJRV4.

About

Creates zones of shared risk, correct building location and elevation, and conduct economic assessment for efficient defense against storm surges

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages