Monday, May 16, 2016

Lab 4: Personal Final Project

Goal:
As the final lab of the semester and the GIS 1 class in whole, we were tasked with applying all the skills we learned over the semester to each create our own final project. The final project would involve answering a question each of us formulated by looking at several collections of data provided to us. Using data provided from the Wisconsin DNR, I was able to gather data on reported invasive plant species locations within state forests. However, this data was largely limited to only the state forests of Wisconsin, while the nearby county forests remained largely unsurveyed. From this, I determined my research question. What areas of county forests were vulnerable to infestation from nearby state forests? The goal of the question was to identify these vulnerable areas in relation to the nearby infested areas so they could be properly monitored. This data would ideally be available to anyone on the state or county level that was interested in the preservation of natural biodiversity in these forests. Hopefully, the local DNR could use it to effectively survey and mange the local county forests.

Data and Source:
All of the data used in this lab was provided by the Wisconsin DNR. The data used includes a state forest feature class, a county forest feature class, a roads feature class, the reported invasive plant species locations within state forests, and the surrounding county and state lines. The problem with much of this data is that its to focused to be viewed at a statewide level. In order for an accurate and visible map to be generated, the map needed to focus on one specific county. Additionally, this specific county needed to county both designated state and county forests, which counties within Wisconsin didn't have. For this reason, Jackson County of Wisconsin was selected to be the area of interests. Additionally, estimating area for the infected locations presented difficulties, as these points lacked true values for the area infested, opting for rough ranges and estimates of area. Because of this, a 100 meter buffer was performed on the reported invasive plant locations to estimate area.

Methods:
In order for the any of the data to be used, it first needed to be cut to the Jackson County borders. This was done for the county forests, state forests, roads, and invasive species locations (SF Invasive) in order to create a focus area and to speed up load times. Afterwards, a 100 meter buffer was performed on the SF Invasive feature class to estimate the area infected. This buffer was intersected with the state forests feature class. Afterwards, the dissolve tool was used to remove internal boundaries, creating a feature class showing the area with reported invasive plant species in state forests. Additionally, the total area infested 100 meter buffer was also intersected with the county forests, as several of the locations reported did in fact lie beyond the boundaries of state forests and within the boundaries of the county forests. From this intersect, a feature class was created showing the county forests that were already reported as infected.
From previous knowledge of invasive species, it was believed that roads could assist in unintentional transportation. In order to verify this, a spacial query was performed to see if a significant portion of reported locations lay within 100 meters of roads. Indeed, a significant portion did. Because of this, it was necessary to take roads into consideration. A two mile buffer was performed on the SF Invasive feature class in order to create a logical range outside of the state forests where more invasive plants may exist. The resulting feature class was run through the buffer tool to decrease processing time. Then, the two mile buffer was intersected with a 100 meter buffer of the road feature class, as it was previously determined that a majority of invasive species locations lay within 100 meters of a road. This was then intersected with the county forests feature class to create a logical search area within county forests. The county area already known to be infected was erased from this using the erase tool, creating the final resulting area within county forests that was suspect of infection and should be checked.
With this completed, a map of Jackson County was created in order to highlight these suspect areas, showing them in relation to the county forests, state forests, roads, and the areas already known to be infected. A smaller reference map was also created to show Jackson County in relation to the rest of the state of Wisconsin. Furthermore, a data flow model was created showing the full process, minus the original clipping to scale, used to create the feature classes present in the final product.













Results:The resulting map shows that much of the county forest areas should in fact be surveyed for invasive plant species. According to the map, all of the area around the roads leading into the eastern county forest from the west should be surveyed, as well as as the areas around the roads leading into the central county forest from the north, east, and west. Small patches of these areas already show infestation. This is relatively unsurprising, given the presence of invasive plant species throughout the state forests of Jackson county.









































Post-Project Evaluation:
Overall, I believe that this project served as an excellent way to creatively put together all of the GIS information and map building skills learned over the course of the semester. It provides a fairly accurate visual representation of the suspected presence of invasive plant species within state and county forests. If asked to repeat this project, I would wish to perform it with all the counties from which information was readily made available, as the project was limited in scope in order to prevent it from becoming overwhelming for a single individual. Additionally I faced challenges in creating realistic representations of areas already infected and for creating a reasonable search window for the areas suspect of infection. This is due to the fact that the area infected was based on an estimate I largely estimated and the 2 mile search window was arbitrarily decided after several buffers were performed. If this project were to be performed in the future, I would prefer to gather accurate area measurements for areas infested with invasive species and not have to base it around a estimated buffer performed on a series of roughly 850 points.

Sources:
Data Source: Wisconsin DNR

Hupy, C. (2016). Lab 4: Mini-Final Project. Eau Claire, Wisconsin.


Friday, May 6, 2016

Lab 3: Vector Analysis with ArcGIS

Goal:
The goals of this specific lab were to introduce various geoprocessing tools and to create a map based on a given scenario using the data we were given along with various geoprocessing tools such as overlay, buffer, erase, and dissolve. The use of python code was introduced as well, demonstrating another way for the tools to be operated.
Background:
The scenario given was as follows. The DNR had issued the task of determining suitable bear habitat from within a study area contained in Marquette County, Michigan. Not only did the habitat need to fit the criteria necessary for it to be considered suitable for bears, it also needed to be contained within the DNR's preexisting management areas and exist at least five kilometers beyond any urban or built up areas within the county. All of the data was downloaded from the State of Michigan Open GIS Database, including the landcover, DNR management areas, and streams data.
Methods:
In order for the bear locations file to be analyzed within ArcGIS, the locations needed to be added as a XY theme event, as bear locations originally existed as an Excel Table File. This was done by choosing "File, Add Data, Add XY Data" from the main menu, and selecting the bear locations excel table and matching the XY coordinate fields within the table with the XY coordinate selectors. The coordinate system was set to the NAD 1983 HARN Michigan GeoRef (Meters) in order to eliminate distortion within the final product. This was then exported as its own feature class to save these modifications. This, along with the streams, landcover, study area, and DNR management areas was added to an empty map document.
A special query was performed to check for the importance of streams within bear habitat. A special query was performed to check if reported bear locations were near streams. A spatial query showed that a significant and majority portion of bear locations were within 500 meters of streams. As of such, this area was considered important to our final product. To determine what landcover bears primarily were found within, an intersect was performed with the bear locations and landcover feature classes. The resulting feature class was summarized based on the minor type field to determine what three landcover types bear were most prevalent within. The Mixed Forest Land, Forested Wetlands, and Evergreen Forest Land types were determined to be the most bear prevalent of the minor types. With this information, a query was performed to select these specific areas from the landcover feature class. A layer was created from this selection.
Since the area within 500 meters of streams was shown to contain a significant number of bear locations, a buffer tool was performed on the streams feature class of the area within 500 meters of streams. The output of this operation, along with the selection from the landcover feature class, was input into the intersect tool to create the proper bear habitat feature class. A dissolve tool was run on the bear habitat in order to clean up the internal boundaries. In order to make sure the bear habitat was within the DNR Management Zones, an intersect tool was run with the bear habitat and the DNR Management feature classes, with the output feature class being run through the dissolve tool to remove the internal management zone boundaries.
The final criteria for the management areas involved them being five kilometers or further from Urban or built up areas. Another query was performed to select the necessary areas from the greater landcover feature class, with the selection being added as its own layer. The selection was then run through the buffer tool to create the area five kilometers around all urban areas. This buffer feature class and the bear habitat within the DNR management zones was then run through the erase tool, with the input feature being the current habitat management area and the erase feature being the urban area buffer.
A cartographically pleasing map was created to show the final Bear Habitat Management Area in relation to the overall bear habitat outside of the management zones, including what was within urban areas, all bear locations, and the entire area of study. A data flow model was also constructed to show the entire string of tools used to arrive at the final map results. In addition, some of the previous steps in the process were performed with python in order to familiarize us with python coding, the results of which can be seen below.
Results:
























 The map shows that although there is much viable bear habitat, bears tend to cluster to the to the west of the central longitude of the study and to the north of the central latitude of the study. However, the only viable DNR management areas lie along the central longitude of the study area, both from west to east. Much of the management area to the east if far from any reported bear locations, and many of the bear locations within the center of the study area falling too close to urban areas. I would recommend the DNR expands its area of management to the far northwestern corner of the map, in which many bears exist far away from the urban areas to the southeast.




Sources:

Hupy, C. (2016). Lab 3: Vector Analysis with ArcGIS. Eau Claire, Wisconsin.

In State of Michigan Open GIS Data. Retrieved May 6, 2016, from http://gis.Michigan.opendata.ArcGIS.com/

DNR Management Units sub-link: http:www.dnr.state.mi.us/spatialdatalibrary/metadata/wildlife_mgmt._units.htm

Landcover sub-link: http://www.mcgi.state.mi.us/mgdl/nlcd/metadata/nlcdshp.html

Streams sub-link: http://www.mcgi.state.mi.us/mgdl/framework/metadata/Marquette.html