Assignment 3: Site suitability analysis for wind power subsidies
ESM 263 (Frew), Winter 2019
Due at 2019-02-18 08:00 (Monday)
NOTE: This is a complicated assignment!
(The next one will be even more so.) Read it through, carefully, all the way to the end,
before you start working on it!
Work through tutorials.
Perform a suitability analysis, and produce a model and
Design a map to communicate your results.
Submit your work to course website.
This assignment is worth 15 points—5 points each for
your map, model, and data, awarded according to the evaluation rubric.
The Energy Division from the Planning & Development office
of Santa Barbara County seeks your advice on wind energy. They
have received a grant to seed small-scale wind energy production
by subsidizing WES 250
kW turbines for installation within mainland Santa Barbara
County. These turbines operate at 30 to 50 meters in height, and
require minimum wind speeds of 6 m sec-1 for optimal
power generation (roughly, 300 W m-2 in wind power
density). They want a ranked list of 10 potential sites, each with
at least 4 contiguous hectares, that meet their suitability
requirements, written as follows:
Wind: Sites must have sufficient wind to power our
Roads: Sites must be within 7.5 km of a major road.
Airports: Sites cannot be within 7.5 km of an airport.
Urban: Sites cannot be within 1 mile of an existing
urban area, nor projected growth areas.
Fire: Sites cannot be within fire hazard zones.
Public: Sites cannot be on state or federal lands
designated as parks or other public use.
The data for this assignment can be downloaded
The following data come from a variety of sources, and are
available in the HW3.gdb geodatabase. Except
where indicated, we've projected these data into NAD83
California (Teale) Albers and clipped them to the Santa Barbara
Airports: Airport boundaries. Source: ESRI Data and
CenterLines2008: Street centerlines data in the
original FIPS V projection and not clipped. We filtered these
data for "major" roads such that all features have SPEED_LIM
>= 35. Source: Santa Barbara County GIS (SBCGIS),
County: Mainland Santa Barbara county line. Source:
FireLRA: Recommended Fire Hazard Severity Zones in
Local Responsibility Areas. We filtered these data such that all
features have HAZ_CODE = 3. Source: Fire and
Resource Assessment Program (FRAP),
FireSRA: Adopted Fire Hazard Severity Zones in State
Responsibility Areas. These data are not filtered; they include
multiple zone types. Assume "fire hazard zones" are zones where
HAZ_CODE = 3. Source: FRAP, 2007.
Parcels: Parcels in the original FIPS V projection
and not clipped. We've already filtered these data to contain
only features where NONTAXCODE = US (federal) or NONTAXCODE
= ST (state). Assume that "designated as parks or other
public use" are parcels where USECODE starts with
a 6, 7, or 8 (e.g., 6xxx, 7xxx, or 8xxx.) Source: SBCGIS, 2009.
Urban2001: Urban areas from 2001. Source: ESRI Data
and Maps 2004.
Urban2020: Urban growth projections for 2020. Source:
California Digital Atlas (Cal-Atlas),
Note: In 2002, NREL produced the California data
in cooperation with the California Energy Commission. These
original raster data used a 200m cell resolution. NREL has
only published these data in vector format, so we've
rasterized the published data to simulate their original
data using a cell size of 200m.
Remember, once you've added a layer to ArcMap,
you can view its metadata by right-clicking on the layer in the
table of contents and selecting Data→View Item Description....
If this doesn't work, navigate to the data layer in
ArcCatalog, right-click on it, and select Item Description
Task 1: Tutorials
Work through Law & Collins Chapters 8 (Classifying features)
and 18d (Running tools in a model).
Optionally, you may work through the ArcGIS
Spatial Analyst tutorial. It walks through a
suitability analysis using Model Builder in "Exercise 3: Finding a
site for a new school."
Task 2: Suitability analysis
Use Model Builder and ArcToolbox to implement a binary model
that produces a suitability raster where each cell indicates
whether that area satisfies all the provided constraints. Use
the masking technique for your rasters—that is, 1 = "included in
solution" and NoData = "excluded from solution."
Figures 1–6a show the specific ArcToolbox tools and data flow
necessary at each step to implement your model. These figures
are separate for clarity purposes only. You will implement
all steps together in a single model.
When working in Model Builder, you should build
your model using an iterative process; i.e., one tool at a
Find the tool you need in ArcToolbox.
Drag the tool into your model to add it (Yellow box).
Rename the tool's output data as appropriate (Green
Drag any data you need for the tool into your model (Blue
Connect the tool to the required input data as appropriate.
Configure the tool as appropriate.
Run the tool.
Mark the output data with "Add to display" to view in
ArcMap. Did it work as expected?
Repeat until all steps are in your model.
Once your suitability raster is ready, your final step is to
interpret your results by identifying the 10 most suitable
sites, ranked by most contiguous area.
Task 3: Map results
Design a map that communicates your results, and clearly
identifies your 10 most suitable sites.
Task 4: Turn in your work
You will upload three files: your map, your model, and
your results data:
Map: Export your map as a PNG image (use options of
300dpi and 8-bit color palette), and name it HW3Lastname.png
Organize and name your processes and data
to clearly describe your model. Ensure that your model
properties and current/scratch workspaces are set as
specified, and that all input data are obtained from HW3.gdb
(otherwise we won't be able to run your model ourselves).
Rename your toolbox HW3Lastname.tbx
and make sure it contains a single, run-ready model.
A good way to check that your model is "run-ready" is to
let a classmate try to run a copy of it in their own
Create a new File Geodatabase (using
the Create File GDB tool) to hold your results
data. Name it Results.gdb
Export your suitability raster into
your Results.gdb geodatabase as a raster
named Suitable. You needn't include any
attributes for these data—the raster itself is sufficient.
(The Example.gdb geodatabase in HW3_example.7z
shows how to do this.)
Use ArcCatalog to enter appropriate
metadata for the Summary (Purpose), Description
(Abstract), and Credits fields in the Overview→Item
Create a 7-Zip file of your geodatabase
In Windows Explorer, right-click on your Results.gdb
folder, then select 7-Zip→Add to "Results.7z"