ESPM 4295 -GIS in Environmental Science and Management

Week 1 - Introduction and Course Mechanics

Read the Semester Project Description, to get an idea of what we're heading for over the next 15 weeks, and look at the Rainfall Mitigation description and the Metropolitan Council Summary for additional motivating information.

This course is split in two periods. We develop skills during the first seven weeks, focusing primarily on two practice areas in the northern part of the St Paul Campus (map here). The remainder of the semester focuses on an analysis for two project watersheds (map here).

This week, you should create a practice geodatabase in NAD83(CORS96) UTM Zone 15 coordinates. The purpose is to dust off elementary digitizing and geodatabase creation skills, in case they're rusty. We also want you to get familiar with the image data on the class L drive (see a description in the rightmost column), and our practice areas.

Create a feature data set and three feature classes, shown on the practice map here, and as described in the following paragraphs:

Open ArcGIS Pro and display an image of the St. Paul campus (see the Resources column, to the right, for where to find the image), and digitize features on the St. Paul Campus for:

1) the water tower next to Green Hall, into a point feature class

2) a "Trees study area" outline into a line feature class, as shown on the practice map, here, and

3) The "Landcover" practice area boundary, a polygon feature class, shown on the practice map, here.

Create a map with an image background, your three digitized layers, your name, a title, scale bar, and north arrow, and export as a pdf. Remember, you can get an image background from the ArcGIS standard backgrounds, or from the class images, described in the Resources column for this week, at the far right.

A note on software.  You should use ArcGIS Pro, even if you learned ArcMap in a previous course. You may have trouble moving back and forth between Map and Pro versions of Arc, so best to avoid that trouble entirely. It is best to stay with just one version of the software.

If you cannot create a geodatabase, or are a bit fuzzy on digitizing or creating a map in ArcGIS Pro, then you should review the intro materials in the resources column at right. If after viewing you still have questions, talk to Paul and Andy. We'll expect you to be able to create geodatabase layers and digitize into them quickly and easily for next week's exercise. 

One final note for this week, in this and all assignments and conduct, your expected understand and follow the Student Code of Conduct and Academic Integrity. Read it and let the instructors know if you don't understand any parts.

Deadlines for the current week's work are listed in this column.  Turn assignments in on the Course Canvas Site, unless specified otherwise. Some activities are due in the same week as assigned, but typically assignments are due the Monday of the week after being introduced.

All assignments due on Canvas, unless specified otherwise

Prior to class Next Monday, before the start of class, turn in:

1. A pdf map that includes these features, plus an image background, name, title, scalebar, north arrow, and legend.

Next Monday before class is a hard deadline, you should turn in what you have. This class moves at a fast pace, and you can't be neglecting new work.  Once the deadline has passed, you will receive a 50% deduction from your graded score, and after the next class meeting, zero points. Unless noted otherwise, this will be our policy for assignments. If you're traveling out of town for another committment, pre-clear tardy submissions.

Rules to follow when turning things in:

• Submit maps as pdfs
• Submit data as geodatabases (GDB extension), compressed in  .zip or similar formats. 
• Submit written documents as MS Word files or pdfs
• Include your initials at the start of your files, and a W# where # is the week at the end of the filename.  For example, I might name my map "pvb_practicemap_W1.pdf", my geodatabase "pvb_practice_data_W1.gdb" and my zip file "pvb_practice_W1.zip".

Failure to follow this naming convention for compressed and component files may result in a deduction.

When you turn in vector data layers, make sure you don't have extraneous columns in the table.  The data may come with "extra" columns, or you may be generating intermediate columns through processing. Keep only those needed for the primary purpose of your data.

Introductory Slides

Semester Project "Big Picture" Overview (refer to this throughout semester)

Data and photos available for this class on the class L drive, ESPM4295W directory, in the CampusImages folder.  The L:\ drive is accessible from the computers in 35 Skok Hall, under the CFANS\LABS\ESPM4295W directory. For this class we'll refer to the subdirectory as the L Drive or as CLD for "Course Lab Drive"

The CampusImages folder contains  various high-resolution, drone-based images of the St Paul Campus. You'll be using these extensively over the course of the semester.

Each student is also assigned a L:\home\{your id} directory.
This directory is for all your class work.  The Course Lab Drives are "read only" so you will copy all needed material to L:\home\{your id} for class work.

Note that you should not access files directly on the L drive via ArcGIS. Copy them to your desktop or local drive first. You may get away with using the L drive directly, but your project is more likely to freeze, crash, or lose data, and at times it will be excrutiatingly slow - particularly during peak use. Do yourself a favor and get in the habit of copying data to your desktop when you start, and back to the L when you finish.

ArcGIS Software Access
Software are available in the 35 Skok Hall lab.  You can also access ArcGIS:

Via the web (click blue-colored text for a link to a quicksheet)
Accessing via the the web - Mac or PC

but you also need to read this, about using Citrix

If you have access to a sufficiently powerful computer, and permission to load software, you can download and install ArcGIS on the desktop

If you use ArcGIS on non-lab computers, then you'll need to either copy the data back and forth, either using a USB, or a cloud drive, or for Citrix (and perhaps also your private computer) using a VPN and mapping the CFANS lab drive

You'll need to compress geodatabases before turning them in, here is a video:
How to Zip/Unzip

ArcGIS Pro Refresher

Review materials from FRNM3131 (note, data referred to is in the 3131 course files, but you shouldn't need them for understanding the mechanics):

• Review this Video, if need be, for starting ArcGIS Pro, creating a new project
• Here is a short excerpt from Lab 1 in the 3131 course, on creating a Geodatabase, and importing data into it
• Review video here on creating a geodatabase
• Review video on creating a feature dataset
• Review  videos on digitizing points
• Review video here on digitizing polygons

Week 2 - Digitize trees and write an introduction of your final report

Task 1 - Digitize the tree canopy for the "Trees" practice area

Display and view the photos available for this class on the class L drive, ESPM4295W directory, in the CampusImages folder. Your goal is to digitize the canopy outline of all the individual trees, based on the images. 

Only digitize trees within the "trees" practice area, shown on last week's practice area map.

Manually interpret individual tree crowns based on the various leaf-on and leaf-off images. It is best to use the most recent image, but we won't use the 2018 data as our primary image because of snow and obstruction. You can use leaf-off images to somewhat identify the crowns and to separate evergreen from deciduous trees, but leaf-on images provide the best source for crown edges.

Note that you should do your best job of interpreting the individual trees, even where they grow in clumps. Do not be too meticulous in digitizing tree crowns. Something like 8 to 12 vertices should be acceptable for most normal, "rounded" crown boundaries. Use autocomplete digitizing or split polygon digitizing as appropriate on clumps. Remember that individual crowns cannot overlap.

Also note that tree crowns cannot overlap with buildings.  It is probably best to digitize crowns rather coarsely where they overlap buildings, as we will later be digitizing building outlines, and can use these to erase the overlapping tree portions.

You should create a text attribute named something like TreeType with the values "conifer" or "deciduous" assigned as appropriate for each polygon.

Also note that the various annual and seasonal images don't register perfectly, one to another. They fit in one part of the campus, while not so well in others. Features digitized on one image don't fall exactly on top of the same feature in another. How should you adjust/account for this? Perhaps pick one image as a base, and manually adjust locations to the base while digitizing.

Task 2 - Begin your semester-long report by writing a polished draft of the introduction. This should be two or four pages at 1.5 line spacing, not counting figures. It should describe:

• the problem you're addressing,  
• why we're interested in doing this, 
• a description and map/figure of the study area (remember, the two large watersheds, NOT the practice areas), and
• the general approach you'll be using. 

Your description should be written as if you were working over the entire two watershed analysis are, and not just your practice areas.  We want to build the report in pieces over the course of the semester. If your graphics and text refer to the practice areas as your study area, you'll cause yourself more work, in that you'll have to re-write sections and create new figures for your final report. The two-watershed, whole analysis area is shown in the project description, provided last week.  You can include graphics in this introduction and in the methods section you write in a few weeks that include examples from the Trees and Landcover practice/skills areas. You should be clear to describe them as examples from a sub-area of your overall study area.

You should write in the present or past tense when describing general problems or conditions (e.g., "managing rainfall runoff is one of the most common and expensive problems in developed areas,"  and the past tense when you're describing the data development and analysis of your project (e.g., we used several images as data sources). Although you haven't done the work yet, when we get to those parts, write as if you've already completed your analysis, even though you haven't started yet. You'll slowly build the report, an assignment at a time, so you'll add to the introduction in future labs, and add methods, results and recommendations later. 

Look at the information on rainwater and runoff provided in the first week for motivation, and the example reports in this week's resources columns for example introductions. 

I'll expect you will have gone through the write-read-revise cycle several times, to make sure it is clear, concise, complete, well organized, and grammatically and factually correct. Read the materials in this week's resources column on general writing guidelines. 

By next Monday, before the start of class, turn in: 

1. A pdf map of the tree crowns, colored by TreeType, with an image background, and your trees practice area boundary, and the usual map elements (title, name, legend, scalebar, etc.) 
   
   
2. A draft introduction for your final report.

• You should use a 11 or 12 point font,
• Have 1" margins all around,
• Two to four pages not counting figures, 1.5 line spacing, section and subsection titles on their own line (e.g., "Introduction"  or "Study Area") and you should bold, italisize, and increase font size to set off titles if you wish. 
• All figures should be numbered sequentially, e.g., Figure 1, Figure 2, have a descriptive caption, and be referenced in the narrative. You should at least have a study area figure, with the analysis watershed outlines and an image background. See the resources column at right.
• All tables should also be numbered sequentially. 
• Maps should have north arrows, scale bars, a descriptive title, and legend, in fonts that are no smaller than 9 point when displayed on a page.

Week 2 Slides, digitizing tips, writing assignment

Editing, see the intro videos provided in Week 1 on creating a geodatabase and digitizing points and polygons, and these below, excerpted and modified from FNRM3131 for more efficient digitizing:

• polygon snapping 
• split polygons
• merge polygons
• autocomplete polygons
• clip digitizing
• using transparent and hatch fills
• adding a field to a table
• manually selecting and assigning a field value into a table
• deleting fields

Additional information for your report: 

Read the "Guidelines for Your Report" and the "Writing Hints" pdfs in the CLD\Writing directory, as you'll be submitting several reports in this class. 

Additional tools that might be useful for your report:

• MS Windows Snip image from screen for figures 
• ArcGIS Pro Export image from data frame for figures
• Using Draw.io to create a flowchart of your workflow

Examples of professionally written reports - good examples of proper tone, grammer, and level of detail:

1: Browns Creek
2: NPS Pollinator Survey
3: NPS Kettle Ponds
4: Dall Sheep Survey
5: Grand Sable Netting
 

You should create a study area figure in your draft introduction, using the full watershed outlines in the StudyShds shapefil provided in the L: drive, respective class directories, in the Data subdirectory.

Week 3 - Project Geodatabase Creation, Digitizing, Topology 

Monday:
Create a Geodatabase with topology for your project area, containing the layers listed below. Review topology editing/digitizing in ArcGIS pro as needed (videos on right).

Your geodatabase should have a feature data set that includes:
1) A "Landcover" polygon layer recording surface cover, separating impervious surfaces (e.g., roads, sidewalks, parking lots, paved plazas) from pervious areas (grass, flower beds, non-compacted dirt, forested areas, shrubs). Include a text attributes for this layer named material, specifying pervious or impervious surfaces. 

2) A "Buildings" polygon layer to hold all building footprints, with an attribute for the name (text), and roof type (with flat or pitched values).

3) A "Tree Canopy" data layer, imported from last week's digitizing. Note that you do not have to digitize trees for the entire landcover area, just use those for the smaller trees area you digitized last week. Import those data into your geodatabase if you digitized them as a shapefile, or into another geodatabase.

4) A "Boundary" layer encompassing your landcover/building "practice" study area - you should import the boundary layer you digitized in week 1.

5) Layer topology, with, topological restrictions as:

• Land Cover and Buildings must not overlap,
• Land Cover polygons must not have gaps (except the holes created by Buildings) 
• Trees and buildings must not overlap
• All layers must be contained within your Study Area Boundary

Start Digitizing All Layers in the "Landcover/Buildings" Practice Area. Digitize landcover for at least 50% of your practice area, and all building for that same 50% area, and test the topology rules. Use primarily the 2017 images, but as needed reference the 2015 through 2018 leaf on and leaf off images to locate building edges as best you can.

By next Monday before the start of class, turn in:

1) Your geodatabase with your trees layer, your practice landcover area boundary layer, the 50% digitized landcover and buildings layers, and completely specified topology rules.

Remember to use our standard naming convention (initials on the front, week on the back of the name), and zip up your data into an archive.

2) You should also turn in a pdf map that shows at least 50% your landcover and buildings, with the usual map elements.

As noted above, you should create maps in a form that will be easily integrated into your written report. Think about the size and shape of the map when used as a figure, and font sizes, symbology, and the arrangement of map elements when created for that.

Week 3 Slides, geodatabase, digitizing and topology 

Below are more videos on topology, the first a bit repetitive from what's been provided, but 2nd and third videos below help with the actual mechanics of creating topology and fixing topological errors in ArcGIS: 

-Topology concepts, 
-Create topology, 
-Fixing topological errors 

Week 4 - Complete digitizing, edit and fix topology.

Complete digitizing for buildings and landcover for the practice  area. 

Complete  cleaning the topology for the practice area, verify and fix topology for landcover/buildings, keeping the data logically consistent across layers, and complete the building roof type and landcover type and maximum infiltration attributes. Your data should be topologically "clean," with all "real" errors fixed, before you turn it in, but if it isn't, turn in progress by the deadline.

Create a map  showing your landcover  data layer, and display the "clean" topology, after checking for and fixing any topological errors. Be sure to include the topology and participating data layers in your PDF map, and that only the "faux" errors appear in your topology.

Create a map of your canopy and buildings for the "landcover" practice area, with an image background. Canopy should be colored by type (conifers one color, deciduous trees another), and buildings should be colored by roof type (flat roofs one color, pitched roofs another).

Note that the canopy may not overlap buildings, so you should use the ArcGIS Erase tool to remove any parts of trees that overlap buildings.

Next Monday, before the start of class turn in:

1) A pdf map with landcover and your clean topology, with all errors fixed. Include the topology in the legend and on the map..

2) a PDF map of the tree canopy and buildings.

Observe the usual map requirements.

Your rules specify that the buildings layer must not overlap with trees. You can enforce this with the Erase tool, by first digitizing all the buildings, then erasing the trees with the building footprints. 

See this video and read the documentation on the Erase tool.

Week 5 - Condition soils data, complete database, start methods section for report

Condition your soils data, following instructions here: Soils data 
You need to add a column for maximum infiltriation (see early weeks' resources for adding fields if need be). Values and how to assign polygons to categories is described in the handout. Read the instructions and modify the soils data so that it is useful for your analysis, and clip it for your landcover/buildings practice area.

Start on the Methods section for your final report,  describing data creation.  This should be four to six pages of 1.5 spaced text, in addition to several figures, including figures containing digitized layers, one for the landcover, one for soils, one combining buildings and canopy, and one for topology. You may use the maps you've already produced for previous assignments, as appropriate, but your methods section should describe these are examples; don't refer to your practice area as the entire study area, otherwisw you will have to rewrite these sections or redo these figures later (remember, we'll be doing an analysis for a larger study area as the focus of our report, and want to be able to use these graphics in that final report).

Next Monday, before the start of class turn in:

A pdf map of soils data, colored by infiltration rate, for the entire study area.

You should also start on the methods section of your report, due Monday after next. 

Slides for Soil Data

(to do) Review on selecting and calculating fields for vectore layers

Clip function

Dissolve function

Important! As noted in the more detailed materials earlier, DO NOT write your methods as an overtly sequential description, and DO NOT frequently refer to specific ArcGIS Pro tools. As in the examples, professional reports rarely include this level of detail or form in their methods. 

Week 6 - Complete 2nd report draft, and delineate watersheds

2nd report draft:

• Edit/improve your introduction according to feedback you received on your last draft, and
• Complete  the Methods section for your final report that covers data development.

Create watersheds for the two pourpoints the practice data, and create a pdf map of your watersheds. Your watersheds should look like those in the figure here.

YOU DON'T NEED TO DO THE DEM FILL STEP WHILE CALCULTING WATERSHEDS in this exercise, the DEM has already been conditioned for you.

Creating watersheds was covered in FNRM3131/5131, taken by most folks in this course, so we'll provide a reduced set of instructions. See the videos and pdfs in this week's resouces section that cover the steps.

The flowpaths might not intersect the provided pourpoints, but only run near.  You should use the the SNAP POURPOINT function, with a snap distance of less than 5 meters, for this exercise.  

Create and turn in a PDF map of your watersheds as semi-transparent overlays, and easily seen watershed boundaries, also include your surface flowlines, and a title, name, and other basic map elements. 

Next Monday, before class,
turn in:

1. Report 2nd draft, and
   
   
2. A pdf map of your watersheds, that includes the watershed boundaries, stream lines, and an image background,
   
   
3. Your completed geodatabase, that includes all your final layers, including buildings, canopy, landcover, soils, and watersheds.

Watershed Slides

Most of you should have had exposure to the concept of watershed delineation based on a raster DEM.  Here is an excerpt from the "GIS Fundamentals" textbook explaining the general idea, for review: Watershed Background

Below are a video and instructions  excerpted from FNRM3131/5131.  The students in that class are provided a "well-behaved" DEM, that has been pre-processed to work. You'll need to substitute your different input files and other parameters, but these provide an example of the workflow in ArcGIS Pro.

Creating watershed instructions, excerpted from 3131/5131, here using the tools:

• Flow direction
• Flow accumulation
• Snap pour points (snap distance less than 5 m)
• Watersheds

You DON'T NEED TO USE the FILL function on your DEM, included in some of the descriptive materials. The DEM has already been filled for you.  

Video for Watershed Creation

Video for creating vector streamlines from flow accumulation layer. This may require use of the tools

• Raster Reclassify
• Raster to polylines

Also note that the watershed tool sometimes returns incomplete watersheds. This is because the D8 algorithm only allows water to drain one of eight directions, and in nearly flat terrain you can get divergent flow where you shouldn't. Sometimes this results in a cell near your flow channel with a slightly off direction, creating a second watershed upstream that doesn't drain into your pourpoint, at lease as represted by your DEM.  Look to see if this is the case, all of your watersheds should be fairly large. In addition, the streams layer will often show a stream ending, without connecting to another stream, in your FAC-based stream network. Visually check all your output watersheds, and redo, moving the pourpoint slightly if needed. 

Week 7 - Project Roadmap, and familiarize yourself with the new, mostly complete data

Monday and Wednesday in Class - we'll discuss the overall project, analysis, and output. Participation IS Mandatory

Carefully re-read the semester project description provided in the first week, and develop a draft flowchart of analysis. You need to think about  the spatial operations and order in which they'll be applied, represented by a box and arrows diagram you'll apply. 

Re-read the project description before class, and come prepared to ask questions about anything that's not clear.

We will provide you with campus wide data very similar to those you have been developing. All work from here forward will be using these campus-wide data, and NOT those that you have developed.  The data are available on the class lab drive.

You may have to modify the data layers a bit for your analysis, e.g., re-calculate the watersheds, move the drain pour-points, and modify a few attributes, but these are relatively minor.

Your task is to estimate the runoff as described in the semester project document, for various storms under current landscape conditions, and after modifying tree canopy, landcover, buildings, and underground storage to mitigate rainstorms.

We will discuss an example flowchart, and provide a refresher on the raster calculator, raster to vector conversion, and some background for the specific problem.

You will have to add details to the flowchart, or create an alternative detailed one to estimate base runoff estimates for various storms.

Complete the flowcharting exercise.

Wednesday - Analysis and Tools

You need to create two intermediate layers for this week,  processing you'll need for your analysis.

First, clip the soils to only the watershed study areas, and select/assign or otherwise recode the soils data based on absorption, to create a column that has maximum absorption, in meters. Use the maximum infiltration values that are listed in the summary section of the project description, linked in the first week's materials.

Second, use the selection/edit or other tools to recode the canopy layer to create a canopy interception layer, with vector polygons or raster cells with a value that stores the interception level, in meters.

Before the start of class on Monday, next week

• Turn in your flowchart exercise - first draft of your detailed flowchart, as a pdf

Also turn in the following pdf maps, based on the two watershed, analysis area data provided on the L:\ESPMx295\Data\ drive, in the ProjectData20 geodatabase

• A canopy interception map, displaying/colored by interception values in meters for the conifer and deciduous, tall and short classes.
• A soils infiltration map, displaying/colored by absorption values in meters for the various soil types

Week's slides 

Using Draw.io to create a flowchart

Finding tools in ArcGIS Pro

Example flowchart graphic (vector analysis, then raster)

Alternative flowchart graphic (all vector)

Week 8 - Net Interception layer, surface infiltration layer

More Tools: 
We'll review these tools in class, and describe how we might use them in a workflow to solve your primary analysis:

• Union (in addition to last week)
• Selection/reclass
• Dissolve
• Polygon to raster
• Raster calculator

You should review the general information in the resources on how to use the tools.

We need to modify the canopy interception layer so that we have zero values for interception where there isn't any canopy.

We also need to combine the landcover, buildings, and soils layer so that we have a maximum soil infiltration layer that shows zero infiltration for the impervious landcovers (roads, sidewallks) and buildings.

By next Monday, before class, turn in:

1. Map of modified canopy that includes zero net interception in areas without trees, a
2. Map of maximum soil infiltration that combines landcover, buildings, and soils data to show maximum infiltration across the surface.

Week's slides: (modify for new Calculate Net Rainfall and Maximum Infiltration Layer

Week 9 - 

More Tools, Calculating Net Runoff for 2.5 cm Rainfall

We'll introduce the general steps needed to create a net runoff layer. Most of the work will be with tools you already know, but we will introduce a few new tools:

• Zonal statistics for Raster
• Summary Statistics for Vector

 By next Monday, before class, turn in two maps and a spreadsheet:

1. Map of your rainfall polygon layer,
2. Map of net runoff for a 2.5cm rainfall event, with watershed boundaries shown on the map, and
3. A spreadsheet with a row for each watershed, with columns of your average interception in cm, average infiltration in cm, and summed agregate runoff, in cubic meters, for each of the target watersheds.

Week's slides, Reclassification and Summary by Zones, here

Example here of how to summarize across an arc vectory polygon layer/table

Week 10 - Calculate Runoff for 5 cm Rainfall, an Introduction to Model Builder (optional for undergrads)

Apply your analysis workflow to estimate runoff for the 5 cm rainfall event, analagous to what you produced last week, just at a higher rain level. Create a map layer and table, produce pdfs, and turn these in.

Optional Activity: Read and practice the Model Builder Exercise.  Then create a model that calculates your watersheds, with the pourpoint layer, snap distance, and output layer as parameters for the model.  Turn in a screen capture of the model builder canvas (paste into a document, and export as a pdf), and a zipped toolbox containing the model.

By Monday, turn in: 

1) Map of 5 cm net interception (including zero areas),

2) maximum infiltration, and

3) Net runoff

and

4) Table showing net runoff by watershed

Model Builder resources from ESRI:
-QUICK TOUR
-GETTING STARTED BUILDING MODELS
-MODEL BUILDER 101

Week 11 -  Discuss strategies for mitigation, create "new" forest canopy

Digitize points, buffer, as described in class this week, clip/union with the original trees layer combine  to create a modified canopy layer that is part of your 2.5 cm mitigation recommendations.

Create a map that shows the new trees layer, highlighting what you added/changed compared to the old layer (you can do this by displaying the old layer on top of the new layer, in a different shade).

Before class on Monday next week, turn in:

1. A modified canopy layer towards mitigation of a 2.5 cm rainfall events.
2. Optionally, a graphic showing your Model Builder model for calculating watersheds, as a pdf, and a zipped copy of your Model Builder model within it's toolbox.

Week's Slides, Buffering and strategies for "Creating" new canopy, and calculating rainfall mitigation needs.

Buffer function

Singlepart to multipart

Erase function

Document describing strategies and examples for mitigation planning

Week 12 - Pervious pavement, Rain Gardens, Green Roofs for 2.5 cm Rainfall Mitigation, start Report Draft 3

• Weighted flow accumulation

Complete the mitigation modifications for your 2.5 cm rainfall runoff. 

Turn in Next Monday, Before Class: 

1) Data tables that include the runoff for the 2.5 cm rainfall mitigation, and the 
completed table for costs, and

2) map showing the rain gardens, new pervious surfaces, green roof, and underground storage you added for the 2.5 cm mitigation

Week's slides here

Model builder exercise 2 for 5295 students, 4295 students may do this as an extra credit exercise.

Week 13 -  Finish Report Draft 3 

This draft should include:

1) revised introduction and methods sections, based on previous grading/comments. You should include a detailed flowchart in an appendix, not in your methods section. You may find it helpful in your discussion to include a very generalized flowchart in your methods section, showing the main branches of analysis.

2) results section describing your findings for the base case rainfall for both 2.5 and 5 cm rains, and the mitigation for the 2.5 cm rains if you've completed it.  The results section should include the runoff volume and a cost tables for your the mitigation activities, in the format specified in the project description.

Your results section should also include maps of your estimated runoff, and for the mitigation, map(s) that show your feature modifications (new canopy, raingardens, previoius pavement, green roofs, underground storage).

Remember that the target audience is the set of administrators in charge of the University physical environment and stormwater management. They don't know anything about GIS software, or GIS theory, or any jargon on geospatial analysis terms. You need to provide enough detail so that an intelligent non-expert will understand what you did, and be convinced that your methods are sound and your reccomendations are valid.

Turn in next Monday, before class:

• Report Draft 3

Week 14 - Continue Analysis Under Modifications

Project work, modifications and analysis to mitigate runoff for prescribed rainfall amounts

• Not a dang thing

No class final; all assignments due by Wednesday, December 18, 11:59 pm

You should turn in three final geodatabases:

1) A geodatabase with the word "Current" in the name that contains data used for calculating your "current condition" runoff for 2.5 cm and 5 cm storms. These are the base final data, as provided, with any modifications to the main data layers.  The geodatabase should also include your final "surplus water" layer, that is, the layer that you summed by watershed to get the total runoff volume for the study areas. 

2) A geodatabase with "2p5cm" in the name, that includes the modified layers used to obtain your 2.5 cm mitigation of runoff. You should include both the original and modified layers for a 1" storm only, that is, the original canopy layer and the canopy layer with added trees for a 1" storm, and NOT the canopy layers  or any other layers for a 2" storm.  If you did not need to modify a layer to reach the 1" threshold (e.g., no green roofs required for buildings), then just include the original layer (e.g., the original buildings).
Include any of the modified layers from: a) canopy, b) rain gardens/surface storage, c)perviousness, d) buildings (with green roofs attributed), e) subsurface storage entry points.

3) Same as 2, except for the 5 cm rainfall, with "5cm" in the name of the geodatabase. DO NOT include any of the modified layers from the 2.5 cm analysis, but DO include your original data layers and any modified data layers needed to meet the 5 cm requirements.

Your final report should include the information provided in previous drafts, plus a description/discussion of the changes for reducing runoff to zero under the different rainfall amounts. This should include appropriate maps/figures.

Wednesday, Dec. 18th, by 11:59 p.m., turn in your final report, via Canvas, and your copy your final data to the 4295Share\yournamefinaldata subdirectory