Hurricanes

Hurricane Wilma, a category 3 storm, made landfall on October 19, 2005 at Key West, Florida.  The 8-foot storm surge associated with the hurricane was the source of the most damage to the area.  

This map shows the extent of the flooding due to the storm surge. The highest point in Key West is just over 12 ft. above sea level. 

Key West is a highly populated, developed area.  This graph gives a breakdown of the types of land flooded in the storm surge. 

To restore basic services in the city of Key West, it is important to know where they are located in comparison to the flooded areas.  Clearing roads will give access to hospitals and airports.  Assuming the infrastructure closest to the areas that did not flood is less damaged than areas experiencing a higher water level helps in prioritizing areas to be restored first.

Earthquakes

Earthquakes Part 1:

1.     Opened provided NewMadrid.mxd file in ArcMap.

2.     Turned on Quakes 5 layer.

3.     Turned on Urban Areas layer.

a.     Which major urban area is likely to suffer the most damage in this event?  Memphis, Tennessee

4.     Selected features likely to experience at least intensity VI-related damage.

a.     Select by Location -> Select features in Urban Areas layer that intersect features in New Madrid MMI layer. 91 features selected.

5.     Summarized DESCRIP field for selected features, and added to map as UrbanRisk table. Turned off Quakes 5 layer,

a.     How many urban centers would experience at least a VI level of intensity? 91

6.     Turned on Counties layer.

a.     Added field to attribute table to calculate Area Proportion. Field will represent persons per square meter.

b.     New field: Pop_Density, Type: double.

c.      Field Calculator -> [POP2001]/[Shape_Area]

7.     Overlaid population within MMI zones.

a.     ArcToolbox -> Analysis Tools -> Overlay toolset -> Intersect.

b.     Input features: Counties, New Madrid MMI

c.      Changed output feature class name to CountyMMI.

8.     Adjusted population totals to new areas.

a.     Added new Long Integer field (POP2001ADJ) to attribute table.

b.     Field Calculator -> [Pop_Density]*[Shape_Area]

9.     Summarized population within each of the MMI zones.

a.     Summarized MMI field

b.     Summary statistics: POP2001ADJ field by sum.

c.      Added resulting output table PopMMI to map.

d.     How many people live within the MMI zones? 60,099,857

e.     Created graph of people within each of the MMI zones.

10. Added new field to New Madrid MMI attribute table.

a.     Name: MMI_num, Type: Short Integer

b.     Populated field with numbers corresponding to the Roman numeral values in MMI field.

11. Turned on Interstates layer.

a.     Selected polygons with MMI value of 8 or higher, the intensities in which motor vehicle operation would be disturbed, according to the Modified Mercalli Scale.

b.     Extract toolbox -> Clip

c.      Clipped Interstates layer to selected features in New Madrid MMI.

d.     Output feature class: IstateRisk, added to map

e.     Renamed layer to Interstates at Risk, changed symbol to Highway with line width 1.

12. Turned on Rail layer

a.     Selected polygons on New Madrid MMI layer with MMI of 10 or greater, which are the intensities in which rails would be bent.

b.     Extract toolbox -> Clip

c.      Clipped Rail layer to selected features in New Madrid MMI.

d.     Output feature class: rrRisk, added to map

e.     Renamed layer to Railroads at Risk, changed symbol to railroad

13. Turned on Dams layer

a.     Selected polygons in New Madrid MMI layer that have MMI value greater than or equal to 8.

b.     Select by location -> Select features from Dams layer that are completely within the selected features of the New Madrid MMI layer.

c.      Created layer from selection, and changed name of layer to Dams at Risk.

14. Created deliverable map from output in Step 8 of lab/Step 12 in this process summary. 

15. Saved and closed file.

Earthquakes Part 2:

1.     Opened Northridge1.mxd in ArcMap.

2.     Checked to make sure Spatial Analyst extension was loaded.

a.     Customize Menu -> Extensions -> check Spatial Analyst box -> Close

3.     Turn on Building Status layer.

4.     Symbolized layer

a.     Properties dialog -> Symbology tab -> Categories -> Unique values à click  Add All Values

b.     Changed symbolization symbol to 1.00 point, and no outline.

c.      Under Advanced, chose Symbol Levels, and checked box to Draw This Layer using given symbol levels. Rearranged symbol levels.

5.     Create Building Damage Density map.

a.     ArcToolbox -> Spatial Analyst Toolbox -> Density -> Kernel Density

b.     Input point or polyline features: Building Status, Output raster: MyData\DmgPattern, Search Radius: 500, Population field: NONE, Output Cell Size: 100, Area Units: Sq. KM.

c.      Turned off Building Status and MMI layers.

d.     Under Color Selector properties for DmgPattern, checked box for Color is Null.

e.     Adjusted transparency to DmgPattern to 15%.

f.      Saved raster as layer file.  Added new file to map and removed original raster file.

g.     Renamed DmgPattern to Building Damage Density

6.     Turned on Geology layer.  Looked for correlation between damage concentration and rock unit. Turned off Geology layer.

7.     Turned on Liquefaction layer, and compared relationship between building damage pattern and liquefaction potential. Turned off Liquefaction layer.

8.     Turned on Stations layer to compare building damage to peak ground acceleration and peak ground velocity.

a.     For PGA:

                                               i.     ArcToolbox -> Spatial Analyst -> Interpolation Toolset -> Spline.

                                              ii.     Input point features: Stations, Z value field: PGA, Output raster: \MyData\PGA, Spline type: tension, Weight: 4, Points: 12, Output cell size: 100.

                                            iii.     Symbolized layer with 45% transparency and a yellow->red color ramp.

                                            iv.     Compare building damage pattern against PGA.

b.     For PGV:

                                               i.     Interpolated again, except used PGV for Z value field, and named output raster PGV.

                                              ii.     Symbolized layer with 45% transparency and yellow->red color ramp.

                                            iii.     Compared building damage pattern against PGV.

9.     Created deliverable for this portion of lab.

10. Saved file and exited ArcMap.

Earthquakes Part 3:

1.     Opened Northridge2.mxd in ArcMap

2.     File menu -> Add Data -> Add XY data -> Add NorthridgeAfter.csv file in data file.

a.     Lon is X field, Lat is Y field

b.     Spatial Reference Properties: WGS 1984.prj

c.      NorthridgeAfter.csv Events is added to map. Exported this data to NorthridgeAfter.shp in MyData folder. (Exported all features, in the same coordinate system as the data frame).

d.     Changed symbolization to a Dark Navy symbol, renamed layer to Northridge Aftershocks.

3.     Selected main shock. Created new layer from selection, and changed symbolization to a red triangle size 18 point.

4.     Cleared selection of main shock. Created new selection by attribute for all aftershocks of magnitude 3 or greater.

a.     Symbolized layer with graduated colors based on magnitude and a green->yellow->red color ramp.

b.     Only needed three classes.  Set number of decimal places to 1.

c.      Changed symbol levels to draw according to specified levels.

5.     Created deliverable for this portion of lab.

6.     Saved file and exited ArcMap.

Earthquakes Part 4:

1.     Opened Northridge2.mxd in ArcMap.

2.     Summarized aftershocks by magnitude over time.

a.     Earthquakes layer Attribute table à Summarized DaysAfter field, including maximum magnitude of aftershocks.

b.     Output table saved as Aftershocks.dbf, and added to map.

3.     Created and exported to JPG graphs of the amount of aftershocks.

a.     Aftershocks table -> Options menu -> Create Graph

                                               i.     Type: vertical bar, Layer/Table: Aftershocks, Value field: Count_DaysAfter, X field: None, Add to Legend: unchecked

4.     Created and exported to JPG graphs of the maximum magnitude of aftershocks.

a.     Aftershocks table -> Options menu -> Create Graph

                                               i.     Value field: Maximum_magnitude.

5.     Tried to create final map…had trouble with changing symbol drawing order.

Final Project

Slide by Slide summary
Powerpoint presentation

Semester Finished!  Whew!

Final Project

Google Maps

I had a tough time selecting a location for my wind farm because I got sidetracked and drawn into reading about the politics of constructing them, but this is really outside the scope of the lab.


Wind Speed:
The location I picked is offshore, about 6 miles North of Rogers City, Michigan on Lake Huron.  Wind speed ranges between 6.5-7 m/s, which is sufficient.  I picked an offshore location because wind speeds are more constant there than on land.


Ornithology:
I had trouble assessing this factor in particular when picking my site.  I believe the major cause for concern in this location is migration of ducks, but there is a great deal of bird migration over the Great Lakes in general.  With the information I could readily access (and understand...), I can't say I know enough to be able to really analyze my chosen site in regard to the ornithology.


Noise:
The British Wind Energy Association (http://www.bwea.com) reported that the sound from a wind farm 350 meters away (a typical setback distance) was less than that of an automobile moving at 65 km/h a hundred meters away. Noise should not be a problem for communities on land.


Shadow Flicker:
The wind mills shouldn't cast a shadow on land, making this a non-issue for humans.


Shipping Impact:
Depending on the size of the farm (number of wind mills), it should be outside of major shipping paths.


Landscape and Visual Impact:
Lake Huron is on the more shallow end of the Great Lakes spectrum, making constructing a farm more monetarily feasible here than in the other lakes.  Also, at 6 miles distance from the nearest large city, the wind farm should not be visible or just barely visible.  I opted to locate the farm offshore, but closer to habitation areas so the infrastructure to carry the energy produced could be readily and economically constructed and utilized, and also so public opposition to wind farms near protected nature areas like State Parks could be minimized.

Geodatabases and Modeling Tools

Exercise 1: Creating a Project Database

1.    Opened ArcCatalog, and looked through the data included in the Organize folder from LearnArcGIS10.exe.

2.    Right clicked the Organize folder in ArcCatalog, clicked New -> File Geodatabase.

3.    Replaced the default name for the geodatabase with Flood.gdb.

4.    Checked environment settings.

a.     Output Coordinates: Same as Input

b.    Processing Extent: Default

c.     Geodatabase Advanced: Output XY Domain is Same as Input

5.    In Catalog tree, right clicked Flood.gdb. Import -> Feature Class (multiple)

6.    Navigated through folders and added: CountyBoundary.shp, MajorRoads.shp, SB_Floodzones.shp, and CityLimits and Schools feature classes.

7.    Right clicked Flood.gdb. Import -> Feature Class (single).

8.    Added CensusBlocks.shp, and entered Demographics for the Output Feature Class name.

9.    In the Field Map tree, deleted MALES (long), FEMALES (long), and MED_AGE (double) fields.  Clicked to add the Demographics feature class to Flood.gdb.

10. Right clicked Flood.gdb. New -> Feature Dataset.

11. Named the dataset Municipal.

12. Imported coordinate system from Parcels feature class. Import -> Organize\City.gdb -> Parcels -> Add. Accepted default value for XY Tolerance.

13. Right clicked the Municipal feature dataset. Import -> Feature Class (multiple).

14. Added Parcels, landuse, and polygon feature class.

15. Right clicked Flood.gdb. New -> Feature Class.

16. Named new feature class Emergency. Alias: Emergency Facilities.

17. Specified geometry type as point feature class.

18. Imported coordinate system from FireDepts.shp.

19. Created attribute fields in new Emergency feature class to match the attribute fields of the data.

20. Right clicked Emergency. Load -> Load Data.

21. Added FireDepts.shp, Hospitals.shp, and PoliceDepts.shp.

22. “Load all of the source data” is selected.

23. Right clicked Flood.gdb. Import -> Table (single.) Added SchoolBuildings table.

24. In Catalog tree, expanded City.gdb. Right clicked PlaceNames and copied. Right clicked Flood.gdb, and pasted file.

25. Right clicked Flood.gdb. Import -> Raster Datasets. Added raster_aerial.tif.

26. Created thumbnails. Took screenshot of thumbnails for lab.

27. Closed ArcCatalog.

STEP 11b:

Exercise 2: Assess Fire Damage

1.    Opened Assessement.mxd from LearnArcGIS10\Model\Fireassessment folder.

2.    Set default geodatabase to Fire.gdb.

3.    Geoprocessing menu -> Search for Tools -> buffer

4.    Clicked on Buffer (Analysis)

a.     Input Features: Creeks

b.    Output Feature Class: Fire.gdb

c.     Name: Creeks_Buffer

d.    Distance: 200

e.    Distance units: Meters

5.    Creeks_Buffer layer appears.

6.    Search for Tools -> clip

7.    Parameters:

a.     Input Features: Creeks_Buffer

b.    Clip Features: FirePerimeter

c.     Output Feature Class: Fire.gdb\Creeks_Buffer_Clip

8.    Opened attribute table.  Right clicked the Shape_Area field -> Statistics.  Examined Sum under Statistics for the total area of burned riparian areas.

9.    Geoprocessing Menu -> Intersect

10. Input features: FirePerimeter, and Vegetation. Named output FirePerimeter_Intersect.

11. FirePerimeter_Intersect layer is added to map.

12. Selection menu -> Select by Attributes.

13. In FirePerimeter_Intersect layer, BurnDay = 1 AND Type = Forest

14. Right click the SHAPE_Area field in FirePerimeter_Intersect attribute table. Statistics -> get SUM.

15. Repeat process for features burned on Day 2.

16. Layer Properties for FirePerimeter_Intersect -> Symbology tab -> Import

17. Choose Vegetation from drop-down box.  Selected Type in the Value field. 

18. Under Display tab in Layer Properties, entered 35 for transparency value.

19. Saved work, exited ArcMap.

STEP 9c:

Exercise 3: Build and Use a Simple Model

1.    Opened Assessment2.mxd from Model\FireAssessment2 folder.

2.    Displayed catalog window. Set the default geodatabase to Fire.gdb.

3.    Scrolled down the tree and expanded Toolboxes.  Right clicked My Toolboxes. New -> Toolbox.  Name: FireTools.

4.    Right clicked FireTools toolbox. New -> Model.

5.    Model menu -> Model Properties.

6.    Replaced text in Label field with Assessment.  Added description to Description box.

7.    Checked box next to “Store relative path names (instead of absolute paths)”.

8.    Dragged Buffer tool into Model Builder window.  Double clicked Buffer tool, and entered parameters

a.     Input features: Creeks

b.    Output feature class: Output1

c.     Distance: Linear Unit =200 meters

9.    Dragged Clip tool into Model Builder.  Drew connecting arrow from Output1 element to Clip tool.

10. Double clicked the Clip tool.  Entered parameters:

a.     Input features: Output1

b.    Clip features: FirePerimeter

c.     Output feature class: Output1_Clip

11. Clicked AutoLayout button.  Clicked the select tool and clicked in the white space in the Model Builder to deselect any elements.

12. Clicked the Run button.  Dragged Output1 and Output1_Clip into map display area.

13. Saved and exited ArcMap.

STEP 9:

Exercise 4: Work with an Existing Model           

1.    Opened Timber.mxd from Model\LeasesCD folder.

2.    Turned on LeaseC and LeaseD layers, and zoomed to extent of StandsCD layer.

3.    Made Tongass.gdb the default geodatabase.

4.    Expanded the LeaseTools toolbox in the catalog window.  Right clicked TimberCD model and chose Edit.

5.    Reset paths to output elements in model.

6.    Zoomed in on the last process in the model.  Right clicked the final element and choose Add to Display.  Double clicked the Clip tool, and changed the output feature class name to FinalC.

7.    Ran the model.  FinalC layer was added to map.

8.    Returned to the model.  Edited the final process by double clicking on the Clip tool.  Changed Clip Features to LeaseD, and changed name of output feature class to FinalD. 

9.    Deleted disconnected LeaseC element from model.  Clicked AutoLayout button.

10. Ran only the last process in the model.  FinalD layer was added to map.

11. Selection menu -> Select by Attributes. In FinalC layer, selected features with N_Distance AND S_Distance = 0.

12. Opened FinalC attribute table. Clicked Show Selected Records button.  Right clicked the StandValue field name -> Field Calculator.

13. In Field Calculator, entered expression:

a.     [ValuePerMeter]*[Shape_Area]/1000000

14. Right clicked the StandValue field -> Statistics.

15. Repeated process for FinalD.

16. Opened model builder window again.  Model menu -> Delete Intermediate Data.

17. Saved model, closed window.  Saved map, closed ArcMap.

STEP 13: