Introduction
This
week we were tasked with mapping features at the Eau Claire priory for the
purpose of future planning. A long term goal for the Priory includes student
housing, outdoor adventure center, as well as other multipurpose buildings. We
were tasked with mapping features that may be of interest for future planners.
There
are many methods to going about mapping an area, for this exercise we decided
to use the Trimble Junos. These devices have ArcPad loaded so we can deploy a
Geodatabse from ArcMap into the device. Then we can use the device to collect
points in the field and eventually bring the data back into ArcMap after point
collection had finished.
Figure 1: Trimble Juno 3D. We used the 3B edition, but they are essentially the same for our purposes. |
Study
Area
As
mentioned earlier, we were once again at the UWEC Priory. The Priory is an area
filled with many small hills and deep (for Wisconsin) gorges. It currently
houses the children’s center and has a few buildings on the property.
Figure 2: Aerial photo of our study area at the UWEC Priory. |
Methods
To
begin this exercise we had to load a geodatabse onto our Trimble units. After
checking out the Juno from our geospatial faciliatator, we started building a
geodatabse in ArcCatalog. We decided we wanted to map a number of features
along the trails at the Priory. We chose to map the benches, invasive species,
and erosional areas. To make the mapping process easier we decided to set
domains for each of these features. This would allow us to classify the
features as we went along without typing out the long details. For example,
with erosion we set domains of Low, Moderate, and Severe occurrences. Now while
in the field, we could just select one of the domains from a dropdown menu.
After
creating the same criteria for the other two features, we deployed the data to
our Juno units and went into the field. As we walked the trails we kept our
eyes open for our desired features. When we stumbled upon a feature we would
discuss exactly how to classify the feature. We would normally come to a
consensus then record the data in the Juno. Unfortunately, something went wrong
with our deployment and we were not able to access the dropdown menu as we thought
we would. This meant we had to write out our desired attributes for each
feature occurrence. Also, my GPS unit was having a hard time taking points and
doing the point averaging so my data was basically useless.
When
we returned to the lab, we began uploading our data that we collected. My data
was obviously pretty unusable so I had to copy the data from my group member,
Zach. From here we can begin to make maps of the feature data we collected.
Results/Discussion
Figure 3: Map of all the feautre data collected with Trimble units. The repetative key is a product of our flawed data collection methods |
Overall
this was a good exercise in how we can use geospatial tools to map an area for
potential future land use planning.