Goal: To create a
geodatabase in order to set up ArcMap with the Trimble Juno GPS. The basemap of
UWEC will be applied to the points, lines, and polygons collected via the
Trimble. This lab teaches the basics of the Trimble Juno GPS and ArcPad as well
as the ability to transfer data onto the ArcGIS program.
Methods:
Tasks for Objective
One: Create a geodatabase and deploy
the geodatabase for ArcPad to the Trimble Juno for field data collection.
Create a file geodatabase within ArcMap. Within that
geodatabase, I created new feature classes in the categories of points, lines,
and polygons to be able to account for the various GPS units I would plot in
the field. This process requires establishing a coordinate system for each feature
class. Additionally, I uploaded the main campus building file as well as the
rasterdataset from the class folder. In order to differentiate the feature
classes, I established unique symbols for the various features.
Tasks for Objective
Two:
To set up ArcMap to be compatible with the Juno, I needed to
turn on the ArcPad Data Manager through the customize menu. Through accessing
this manager, I clicked the ‘Get Data’ button to begin the process of allowing
ArcPad and ArcMap to work together. Most of the settings on the Action Menu
within the wizard are able to be set to default, but I changed all of the
layers to ‘check out’ and the CampusImage was linked to JPG2000. Finally, I
created a place to store the data. From there I used the deployment option to
create the ArcPad data.
Tasks for Objective
Three: Deploy data to Juno
In order to transfer the data on the computer to the Juno
device, I needed to connect the device to the computer using a USB cable. Following
that step, I cut the lab file from the hard drive onto the Trimble Juno drive. From
here, I was able to look within the GPS unit to find the map from the computer.
I did such by opening the ArcPad application and opened up the document I had
previously saved in ArcMap. To become comfortable with the application before I
went out in the field, I explored ArcPad and re-established which features had
which symbols.
Tasks for Objective
Four: Become familiar with the basics
of the Trimble Juno GPS and ArcPad through an instructor led demo.
This objective was really to establish the core knowledge in
order to collect the proper data. As a class, we went outside and
differentiated between the ‘add a GPS Vertex’ and ‘add a GPS Vertex
Continuously’.
Tasks for Objective
Five: Collect point, line, and
polygon features in the field using ArcPad on the Trimble Juno GPS
For this portion, I went outside to the campus mall in order
to collect the points on the Juno GPS. To maintain the most accurate feature
data, I chose to use the ‘add a GPS Vertex’. I took three points for three different light
posts and three points for three different trees. I took two points on either
side of the footbridge to create a line feature. For my polygons, I used at
least three points to create four polygons of various grass areas. After
collecting my data, I saved the map and closed the program.
Tasks for Objective
Six: Check the collected data back
into ArcGIS from the field.
This objective required me to reconnect the Juno to the
computer. Before the data could be transferred, I needed to paste the data from
the Juno back into my lab folder. After opening the .mxd folder I needed to
‘check in’ to the ArcPad data manager toolbar. This required me to click the
green plus sign and ‘check’ all of the points, lines, and polygons, and select
‘check in’. Once I completed this, I created a clean map of all of my data as
well as a legend, title, north arrow, scale, source, and the author name.
Results:
Once all of the data was added to ArcMap, I noticed that
there were some errors regarding the positioning of GPS in relation to the
topographic map of the UWEC Campus. All of the points, lines, and polygons were
shifted in regards to the topographic and aerial map. This shows the gap for
error that needs to be accounted for when using the Juno Trimble. The
footbridge, especially, shows that even in my attempt to make the line as
straight as possible, GPS units in the price of hundreds to a couple thousand
are not perfect. Additionally, the precise shape for the polygons and the line
is skewed because many more points would have needed to be recorded in order to
get the most accurate coordinates.
Sources:
·
GPS data:
collected by Emily Moothart
·
Topographic
Base Map: UWEC Server, W:\geog\LidarData\EauClaireCity_3in_2013\MrSids
folder
·
Aerial
Map: GIS Online, UWECCampusBaseMap
