 |
| Figure 1: This map shows the best suitable hunting land, located on publicly managed DNR land, in Sauk County, Wisconsin. The green polygons denote land that matches the specified criteria. |
Goal
Background: The goal of this assignment was to develop a personal spatial question and carry out the correct means to answer that question. The spatial question that this lab seeks to answer is: Where are the best places in Sauk County, Wisconsin to hunt on land open to the public?
Purpose: The purpose of this assignment was to demonstrate knowledge of the skills learned from this course and apply them through various methods.
Methods
Data Collection: To begin the process of determining the best possible public hunting land in Sauk County, data had to be brought in from for streams, bodies of water, Wisconsin Department of Natural Resources (DNR) managed lands, county borders, state border, roads, and cities. Through ArcMap, database connections were made to the Wisconsin DNR Database and the ESRI Database. Through the DNR database the following data was acquired: Streams, DNR Managed Lands, County Borders, State Border. Through the ESRI database the following data was acquired: Bodies of Water, Roads, and Urban Areas. This data was brought into a file geodatabase created for this assignment. Concerns with this data stem from having to use a variety of different feature classes to examine one overall feature, such as the classes for streams and waterbodies.
Data Preparation:
Sauk County: In order to start utilizing the data, Sauk County had to be located and made into its own feature class. This allowed the analyst to use Sauk County to clip the other features to get details within only the target area. To do this, an attribute query was performed to locate Sauk County. Once the county was located, the option to make it into a feature class was chosen. Then, Sauk was projected to the NAD 1983 Wisconsin CRS Sauk (meters) projection to make the feature class more conducive to viewing solely the county.
Roads: To begin using the Roads data it was clipped using the Sauk County polygon. This data was then projected to the NAD 1983 Wisconsin CRS Sauk (meters) projection. This data had many different classes within it, depending on the size of the road. To differentiate between the different classes of roads, they were each given a different symbol, as seen in Figure 1. This class difference led to the need to create buffers based on different criteria to create different sized buffers. [Note: This was not a skill learned in this class, however, I was able to teach myself how to do it and used it for this feature class and for the Streams feature class]. To do this, a new field labelled "Buffer_Field" was added to the attribute table in the form of a Text field. Different values were assigned to this field, for example "0.5 Kilometers". This was added to each different class in order to create different sized buffers based on the size of the road and the perceived distance that a hunter would like to be away from the road in order to reduce the chance of traffic interfering with their hunt. The roads were then buffered by Field, rather than buffered by Distance. A dissolve was also applied to get rid of overlapping lines created by buffering. The resulting feature class was then clipped using Sauk County to get rid of buffers falling outside of the target area. Labels were activated for this data and a mask was applied to the labels to make them more visible on the map.
Urban Areas: To begin using the Urban Areas data it was clipped using the Sauk County polygon. This data was then projected to the NAD 1983 Wisconsin CRS Sauk (meters) projection. A dissolve was applied to remove boundaries between cities like Lake Delton and Wisconsin Dells, and Sauk City and Prairie du Sac, who share borders. Then a buffer was applied around the city to account for anthropogenic influence. The data was clipped again using the Sauk County polygon to remove buffers that extended outside of the county. Labels were activated for this data and a mask was applied to the labels to make them more visible on the map.
DNR Managed Lands: To begin using the DNR Managed Lands data it was clipped using the Sauk County polygon. This data was then projected to the NAD 1983 Wisconsin CRS Sauk (meters) projection. An attribute query was conducted for lands that were fully owned by the Wisconsin DNR or lands that were acquired through easements that allowed for public hunting. The interpretation of this data was assisted by Ann Runyard, GIS Analyst for the Wisconsin DNR. The query left only land that was available for public use of hunting. The data was then compared to the buffered urban class and an erase was applied, then to the buffered roads class and an erase was applied.
Data Utilization:
After all the data was prepared and the necessary feature classes were discerned, the data was finally able to be narrowed down to show only suitable public hunting land that fell within the proximity of a waterbody. To do this, an intersect was applied to show only data that met both of the necessary criteria of falling within the Sauk Water buffer and DNR huntable land. This left the answer to the initial query of the most suitable places to hunt publicly in Sauk County.
Cartographic Preparation: A proper map was created with a map to show location of the county within Wisconsin. A data flow model was also created to show workflow for the project.
Discussion
While I felt that most of this data provided a solid view of the potential lands to hunt in Sauk County, I also feel that more data would have better suited this query. It should be noted that the main focus of this project had deer in mind when the analysis was conducted. I feel that data regarding deer density would have helped show the most suitable land with the most potential for an encounter. There was data regarding deer management zones, but as they are not bound by county boundaries the data regarding density would have been skewed. I also feel that I ran into some issues with the hydrology aspect of this project. There are many different feature classes that deal with streams, rivers, ponds, and lakes, but I could not find one that contained a majority of those, so I had to settle for two feature classes and perform an erase followed by a union. With the streams feature class, lines were shown where lakes were present between an input stream to the lake and a drainage stream. The line between the two is what was erased, leaving only the input stream until the boundary of the lake and the drainage stream from the boundary of the lake. If I had the ability to input real world data gathering measures into my data I would attempt to get an overall idea on how many deer are registered per deer registration station. This would give me a general idea about the number of deer in the area, instead of a large scale classification based on spatially large zones.
Results
This project showed my aptitude to solve a question using applied GIS. It was a comprehensive project showing all that I had learned and gathered from previous coursework. As this is a potential field that I would like to go in to, understanding how to apply various tools and what those tools do is a crucial component to furthering my career.
Sources
Ann Runyard - GIS Analyst, Wisconsin Department of Natural Resources
ESRI Geodatabase
Wisconsin DNR Geodatabase
Data Preparation:
Sauk County: In order to start utilizing the data, Sauk County had to be located and made into its own feature class. This allowed the analyst to use Sauk County to clip the other features to get details within only the target area. To do this, an attribute query was performed to locate Sauk County. Once the county was located, the option to make it into a feature class was chosen. Then, Sauk was projected to the NAD 1983 Wisconsin CRS Sauk (meters) projection to make the feature class more conducive to viewing solely the county.
Roads: To begin using the Roads data it was clipped using the Sauk County polygon. This data was then projected to the NAD 1983 Wisconsin CRS Sauk (meters) projection. This data had many different classes within it, depending on the size of the road. To differentiate between the different classes of roads, they were each given a different symbol, as seen in Figure 1. This class difference led to the need to create buffers based on different criteria to create different sized buffers. [Note: This was not a skill learned in this class, however, I was able to teach myself how to do it and used it for this feature class and for the Streams feature class]. To do this, a new field labelled "Buffer_Field" was added to the attribute table in the form of a Text field. Different values were assigned to this field, for example "0.5 Kilometers". This was added to each different class in order to create different sized buffers based on the size of the road and the perceived distance that a hunter would like to be away from the road in order to reduce the chance of traffic interfering with their hunt. The roads were then buffered by Field, rather than buffered by Distance. A dissolve was also applied to get rid of overlapping lines created by buffering. The resulting feature class was then clipped using Sauk County to get rid of buffers falling outside of the target area. Labels were activated for this data and a mask was applied to the labels to make them more visible on the map.
Urban Areas: To begin using the Urban Areas data it was clipped using the Sauk County polygon. This data was then projected to the NAD 1983 Wisconsin CRS Sauk (meters) projection. A dissolve was applied to remove boundaries between cities like Lake Delton and Wisconsin Dells, and Sauk City and Prairie du Sac, who share borders. Then a buffer was applied around the city to account for anthropogenic influence. The data was clipped again using the Sauk County polygon to remove buffers that extended outside of the county. Labels were activated for this data and a mask was applied to the labels to make them more visible on the map.
Bodies of Water: To begin using the Waterbodies data it was clipped using the Sauk County polygon. This data was then projected to the NAD 1983 Wisconsin CRS Sauk (meters) projection. A buffer was applied to buffer the area around the various bodies of water. This buffer assumed that wildlife would travel a certain distance to drink from a lake, pond, or river. Once the buffer was created and a dissolve was applied, it was clipped with Sauk County again to remove buffers that extended outside of the county. The data was then compared to the buffered urban class and an erase was applied, then to the buffered roads class and an erase was applied. This left waterbodies that were located a certain distance away from anthropogenic influence.
Streams: To begin using the Streams data it was clipped using the Sauk County polygon. This data was then projected to the NAD 1983 Wisconsin CRS Sauk (meters) projection. The data was then compared to the Waterbodies feature class and an "Erase" was applied to the data in order to remove data that was overlayed with lakes or rivers, as they were not properly displayed with a line feature class. This data had many different classes within it, depending on the size of the stream. This led to the need to create buffers based on different criteria to create different sized buffers. To do this, a new field labelled "Buffer_Field" was added to the attribute table in the form of a Text field. Different values were assigned to this field, for example "0.4 Kilometers". This was added to each different class in order to create different sized buffers based on the size of the stream and the perceived distance that animals would travel in order to drink from it. Smaller streams received smaller buffers because they would not supply as much water to the surrounding wildlife, or potentially because they only carried water during precipitation events (intermittent streams). The streams were then buffered by Field, rather than buffered by Distance. Once the buffer was created and a dissolve was applied, it was clipped with Sauk County again to remove buffers that extended outside of the county. The data was then compared to the buffered urban class and an erase was applied, then to the buffered roads class and an erase was applied. This left streams that were located a certain distance away from anthropogenic influence. Finally, a union was applied between the Waterbodies feature class and the Streams feature class in order to derive a new feature class labelled "Sauk Water". This feature class contained all units of water in Sauk County.DNR Managed Lands: To begin using the DNR Managed Lands data it was clipped using the Sauk County polygon. This data was then projected to the NAD 1983 Wisconsin CRS Sauk (meters) projection. An attribute query was conducted for lands that were fully owned by the Wisconsin DNR or lands that were acquired through easements that allowed for public hunting. The interpretation of this data was assisted by Ann Runyard, GIS Analyst for the Wisconsin DNR. The query left only land that was available for public use of hunting. The data was then compared to the buffered urban class and an erase was applied, then to the buffered roads class and an erase was applied.
Data Utilization:
After all the data was prepared and the necessary feature classes were discerned, the data was finally able to be narrowed down to show only suitable public hunting land that fell within the proximity of a waterbody. To do this, an intersect was applied to show only data that met both of the necessary criteria of falling within the Sauk Water buffer and DNR huntable land. This left the answer to the initial query of the most suitable places to hunt publicly in Sauk County.
Cartographic Preparation: A proper map was created with a map to show location of the county within Wisconsin. A data flow model was also created to show workflow for the project.
 |
| Figure 2: Data flow model for the assignment. This shows the work flow carried out in order to achieve the desired output data. |
Discussion
While I felt that most of this data provided a solid view of the potential lands to hunt in Sauk County, I also feel that more data would have better suited this query. It should be noted that the main focus of this project had deer in mind when the analysis was conducted. I feel that data regarding deer density would have helped show the most suitable land with the most potential for an encounter. There was data regarding deer management zones, but as they are not bound by county boundaries the data regarding density would have been skewed. I also feel that I ran into some issues with the hydrology aspect of this project. There are many different feature classes that deal with streams, rivers, ponds, and lakes, but I could not find one that contained a majority of those, so I had to settle for two feature classes and perform an erase followed by a union. With the streams feature class, lines were shown where lakes were present between an input stream to the lake and a drainage stream. The line between the two is what was erased, leaving only the input stream until the boundary of the lake and the drainage stream from the boundary of the lake. If I had the ability to input real world data gathering measures into my data I would attempt to get an overall idea on how many deer are registered per deer registration station. This would give me a general idea about the number of deer in the area, instead of a large scale classification based on spatially large zones.
Results
This project showed my aptitude to solve a question using applied GIS. It was a comprehensive project showing all that I had learned and gathered from previous coursework. As this is a potential field that I would like to go in to, understanding how to apply various tools and what those tools do is a crucial component to furthering my career.
Sources
Ann Runyard - GIS Analyst, Wisconsin Department of Natural Resources
ESRI Geodatabase
Wisconsin DNR Geodatabase
No comments:
Post a Comment