ArcPad Data Collection

Introduction

            Our final exercise of the semester involved creating a database in ArcPad for deployment in the field.  Using the ArcPad software, we were able to create pre-designated data fields and import them onto a Juno GPS.  Creating a database prior to gathering data in the field, allows the user to limit his/her input, therefore reducing the potential for error. This practice should be considered standard procedure when embarking in any geospatial field activity.

Study Area

            The study area for this exercise was once again the 112 acre plot of land known as the Priory (figure 1).

Figure 1. Priory study area located south of UWEC Campus 

 

Methods

            We began this activity by creating a geodatabase within ArcMap including our three desired fields, benches, erosion, and invasive species. For each of the fields we created a domain to describe attributes of the data being collected.  For example, benches may fall under one of three values, usable, needs repair, and unusable.  A description is provided with each of the values to define our interpretation of the feature.  In the case of erosion, a coded value signifying severe levels of erosion would describe that feature as having exposed bedrock, outcropping, wasting, or colluvium debris.

            After the database has been created, a project was made within ArcMap. It was important to classify the three fields using a distinct symbol that can be recognized in the field. A projected raster background image was also included in the project to spot our visual location on the GPS unit. Using the ArcPad Data Manager, we prepared our database to be imported as an ArcPad project. Once this was complete, we were able to transfer our ArcPad map (.apm) file onto the the GPS device.  We used the Juno 3B Trimble model for field data collection (figure 2).



Figure 2: The Juno 3B Trimble GPS unit used during the data collection portion of this activity

 

            Once all of the data is transferred to the Juno, we were able to collect our points in the field.  The intuitive design of the Juno allows the user to simply select the feature being recorded, and the location data is automatically stored for the previously defined projection. When selecting the feature, the display will ask how to classify it according to the set domain.  After marking the features, the unit automatically saves them to your .apm file and they are ready to be uploaded.

            Uploading the data is quite easy. Simply use the ArcPad Data Manage and select ‘get from ArcPad’. The software wizard will prompt you to select your file and it will then upload the data. The map I created below shows where each feature is located as well as its condition (figure 3).

Figure 3: The point locations of the three feature, benches (star), erosion (diamond), and Buckthorn (bolt).

Conclusion

            Although we only used a week to cover this lesson, I can see its potential in creating an organized and thorough database.  It’s important to begin any field activity from the ground up instead of collecting data on the fly.  This procedure will help organize your data from the get go while reducing the amount of error that may occur during the data collection phase of the project. I look forward to getting more hands on experience with ArcPad and the Juno devices in future projects.