Part 1: Delineation of Watersheds
Background
A watershed is an area of land that drains all water that
falls within it to a common outlet (USGS, 2016). Watershed boundaries are
areas of raised elevation that separate the flow of water across land
area. Knowing the boundaries of a watershed is important for land and
water management. Watershed maps including watershed boundaries can help
those who work with them pinpoint pollution sources, monitor the amount and
quality of water entering a certain area and much more. A good example is
Adirondack Park, a protected area in northeastern New York. Many portions
of the park are privately owned and used for forestry, agriculture, and
recreation. Understanding the flow of water through this park is helpful
due to its wide variety of uses. The water flow of Adirondack Park will
be determined by performing a watershed delineation of the park area on ArcGIS.
Methods
First data was downloaded from the New York State GIS
Clearinghouse, Cornell University's Geospatial Information Repository, and
ESRI. To prepare the data for the watershed delineation tool, it had to
be processed. The hydrology layer, which includes streams and rivers, was
projected to (UTM) Zone 18N NAD 1983, the same projection as the Adirondack
Park boundary because in order to perform an overlay analysis, all layers need
to be in the same projection. Next, a 20
km buffer was made around the park boundary creating a larger area for clipping
the elevation dataset which will help make smoother watersheds later. The
projected hydrology layer was then clipped to the park boundary, our area of
interest.
The DEM of North America needed for the analysis was
obtained from ArcGIS Online. The DEM was
projected into the same projection as the park boundary and hydrology layer
using a bilinear resampling technique (60 meter cell size), and then clipped to
the buffered park boundary.
Several input datasets were created to perform watershed
delineation including flow direction, filled sinks, water accumulation, source
raster, and stream links. The flow direction raster was created using the
spatial analyst toolbox and the tool ‘flow direction.’ The fill tool was used to fill depressions
impeding water flow and then a flow direction raster was made based on the
filled DEM. With the filled flow direction raster, flow accumulation was
calculated as an integer raster.
A source raster was creating using the Con tool in the
spatial analyst toolbox that served as the input for the watershed delineation.
This raster requires choosing a stream threshold. A stream threshold is the minimum number of
cells flowing into any cell before it is designated as a stream cell. For the first map, 50,000 was chosen. Using the stream link tool, unique
identifiers to each stream reach were assigned in a raster which will show
unique stream links that resemble stream channels. Finally, the Watershed tool created a
watershed map using the flow direction and source raster. For analysis purposes, the watershed raster
was clipped to the park boundary and streams were added to compare watershed
boundaries and stream locations.
For comparison, the
watershed analysis was repeated for a 120 meter cell size and stream thresholds
of 100,000 and 500,000.
Results
![]() |
Figure 1. Watershed analysis using a 60 meter cell size and 50,000 stream threshold. |
Figure 1 shows the final map of 105 different watersheds in
Adirondack Park. Moving from north to
south on the map, there is an increase in the stream outflow from each
watershed (shown by the darker shades of red).
![]() |
Figure 2. Watershed analysis using 120 meter cell size and 50,000 stream threshold. |
Figure 2 shows that the 120 meter cell size DEM decreases
the amount of watersheds shown versus the 60 meter cell size. This is because a bigger cell size means the
processes are run on a more generalized DEM, and so the watershed boundaries
will also become more generalized.
![]() |
Figure 3. Comparison of a 100,000 and 500,000 stream threshold in a watershed analysis. |
Figure 3 shows that when the threshold was changed to
100,000, the number of watersheds decreased to 38 and when the threshold was
increased to 500,000 the number of watersheds decreased to 7. The results vary because as you increase the
threshold for stream initiation, you decrease the number of stream cells. In essence, you are increasing the required
number of cells flowing into another to be considered a stream cell.
Overall, this analysis depends on several factors, and
depending on the values inputted for each factor, the output can show different
results. Two of these factors explored
in this lab were DEM cell size and stream threshold. Care should be taken when creating maps using
tools like watershed delineation so that the final map fulfills its intended purpose
as clearly as possible. For example, a
scientist might want a fine detailed watershed map whereas a poster for the
general public may need to be more generalized.
These are things the map maker must consider when performing a watershed
analysis.
Sources
U.S. Geological Survey. What is a watershed? (2016, December
09). Retrieved from https://water.usgs.gov/edu/watershed.html
New York State GIS Clearinghouse. (2017). Adirondack park boundary
[Shapefile]. Retrieved from http://gis.ny.gov/
Cornell University Geospatial Information Repository. (2017).
Hydrography features of New York state [Shapefile]. Retrieved from http://cugir.mannlib.cornell.edu/index.jsp
Part 2: Finding Areas at Risk of Flooding in a Cloudburst
Background
Recently, the country of Denmark has been subject to
numerous cloudbursts. The
Merriam-Webster dictionary defines a cloudburst as a sudden heavy rainfall
(Merriam-Webster, 2017). One of these
cloudbursts occurred on July 2, 2011 in Copenhagen causing widespread flood
damage. To prevent further damages from
cloudbursts in the future, the Danish government established a Task Force on
Climate Change Adaptation. This task
force utilizes a bluespot map, which identifies low-lying areas that have no
natural drainage. These areas may fill
up and overflow, damaging nearby infrastructure during a cloudburst event. This lab describes a geoprocessing model, a
collection of input data and tools organized as a workflow and run as a single operation,
which finds locations of bluespots and calculates volumes of bluespots and
their capacity to hold sudden influxes of water (ESRI, 2017).
Methods
First, the Cloudburst Models and Data for the project was
downloaded from ArcGIS Online, which contains two geoprocessing models: ‘identify
bluespots’ and ‘identify bluespot fill up values.’ Like part one, the DEM used in this portion had
a buffer zone, in this case 5 km, to ensure that all bluespots and watersheds
were identified correctly because some bluespots and their local watersheds may
lie partly in neighboring municipalities.
First the ‘identify bluespots’ model was utilized. This model found the bluespots on the DEM,
processed this result and the buildings layer, and then selected the buildings
on the map that were within or adjacent to bluespots. This model was premade by
ESRI, so the only necessary steps were to check the model’s inputs and tools
and validate the model before it was run.
This model has several steps to create
the final map of infrastructure affected by bluespots. The first
step of the model is taking the DEM of the Gentofte municipality in Copenhagen,
Denmark and running the fill function to fill all sinks that may occur in the
DEM. Concurrently the same fill function is run, but with a vertical accuracy
input that will give an output raster of filled sinks less than the DEM
vertical accuracy. The two outputs are
then subtracted to find the cell differences for the DEMs and thus create
bluespot depths cell by cell. Then the
Con function performs a true/false test, assigning a 1 (true) value to cells
that are a bluespot and 0 (false) to non-bluespot cells. Then the region group
function assembles all bluespot regions by identifying the cells that had a 1
value assigned to them. These bluespots
were then converted from raster values to polygons, and then the bluespots were
dissolved into one polygon. The dissolved bluespots were made into a temporary
feature layer for selecting buildings affected by bluespots.
The other input
for selecting buildings affected by bluespots was created by taking the
buildings feature class and converting only the buildings in the study area
from polygons to a raster and then back to polygons. These polygons were then made into a
temporary feature layer as well.
Both of the
temporary feature layers were used to select buildings that intersected
bluespots to create the final output of infrastructure affected by bluespots
created by cloudburst events. Out of all
the buildings in Gentofte, approximately 46% were touched by bluespots, meaning
they have some level of flood risk in a cloudburst.
The second model
used was ‘identify bluespot fill up values.’ This model identifies bluespots on
a DEM and calculates how much rainfall is needed to make each bluespot fill up
in a cloudburst. It does this by dividing
the volume of a bluespot by the the area of the watershed. This information can then be used to assign
hazard levels to infrastructure based on how fast bluespots fill up.
To determine buildings within the highest risk
category, a query found the bluespots that fill up with 20 millimeters or less of
rainfall. Then, another query was used
to find the buildings that intersect these bluespots. The same process was used for a fill up value
of up to 40 millimeters to show buildings within the top two risk
categories. These both were mapped in
figure 3.
To understand
the relationship between watersheds and bluespots, the watershed layer was
added to the previous maps. The
watersheds were also symbolized with discrete colors to differentiate between
watersheds. Finally, feature classes of railways and roads were added to the
map with the bluespots. A query found
the bluespots that require 40 millimeters or more to fill up, and then select
by intersection was used to find railways and roads that intersect the selected
bluespots. The final result is a map of
roads and railways that are at relatively low risk for flooding.
Results
![]() |
Figure1. Buildings affected by bluespots in the Gentofte municipality, Denmark. |
Figure 1 shows a map of buildings touched or affected by
bluespots and the corresponding bluespots.
These bluespots are spread out over all of the Gentofte municipality
evenly without clustering. The even dispersion of the bluespots suggests that
all of the Gentofte municipality is at risk for bluespots. This map only shows
buildings affected, but it should be noted that there are other types of
infrastructure affected by bluespots not pictured on the map. In addition, this
model does not address the level of risk to buildings, only that the picture
buildings are at risk. The ‘identify
bluespot fill up values’ model addresses level of risk to buildings and other
attributes of bluespots.
![]() |
Figure 2. Levels of risk for buildings affected by bluespots in Gentofte municipality, Denmark. |
Figure 2 shows the levels of risk for each building in a
bluespot that was found via the ‘identify bluespot fill up values.’ This is visualized using red values for high
risk areas and yellow for lower risk areas. Further analysis was run on this
map to show buildings in both the highest and the top two highest risk
categories and are shown in figure 3.
![]() |
Figure 3. (A) Buildings in the highest risk category of bluespot flooding. (B) Buildings in the two highest risk categories of bluespot flooding. |
Figure 4 shows the bluespots as they relate to
watersheds. This map allows the reader
to examine the relationship between bluespots and the areas that provide the
flow feeding them.
Figure 5 is the final map created in this lab and shows
roads and railways that are at relatively low risk for flooding (it takes more
than 40 millimeters for the bluespots to fill up).
![]() |
Figure 5. Railways and roads at low risk for flooding by bluespots. |
Figure 5 and figure 3 show that with the ‘identify bluespot
fill up values’ model, it is possible to run more complex analyses, such as
finding infrastructure that is at high and low risk for flooding due to
bluespots. It should be noted however that
this model still leaves out many factors, such as the contribution of surplus
runoff to a downstream bluespot and elevation of buildings within a
bluespot.
Discussion
As cloubursts and other large precipitation events become
more common, it is imperative that governments at all levels make an effort to
prepare their jurisdictions for the impacts of these events. This case study of the Gentofte Municipality
of Denmark is a great example of the first step in preparing for hazards:
determining where they occur and the level of impact. With this data, the government can find areas
that need extra precautionary measures taken such as flood insurance, improved
drainage systems, and choosing building sites away from bluespots. The model should be globally applicable as
well because it is based on investigation of the terrain surface and location
of buildings. All one needs to do is make the input layers their own datasets
and run the model. Caution is advised
when looking at the results of these models for a number of reasons. The elevation of the bases of the buildings
varies, so the results may show too many or too few buildings affected by
bluespots. The model also assumes
perfect runoff conditions, but these are rare in real life. Finally, assumptions have been made about the
capacity of the sewer system to handle overflow water, so bluespots may act
differently depending on the cloudburst event.
Overall, these models provide great insights on the behaviors of
bluespots and the likely areas affected as long as caution is taken when
interpreting the results.
Sources
ESRI Learn ArcGIS (2015). Cloudburst models and data
[Geoprocessing Sample]. Retrieved from http://www.arcgis.com/home/group.html?id=6b43edd251e54e0299c68695321b223e&start=1&view=list&sortOrder=asc&sortField=title#content
Merriam-Webster. Cloudburst. (2017, November 01). Retrieved from https://www.merriam-webster.com/dictionary/cloudburst
No comments:
Post a Comment