ArcPad Data Collection Part 1
Introduction
In a previous exercise entitled "Geodatabases, Attributes, and Domains," from March 1, 2015, I walked through the proper steps for creating and preparing a geodatabase for field research (click HERE). In this instructional blog, I highlight just how important going through the proper methods of geodatabase construction are to easy, concise, and accurate field measurements. This blog will instruct as to the proper methods of deploying the newly created geodatabase into the field. In this case we are using a Trimble Juno 3 Series Handheld global positioning system (GPS) device (Figure 1).
This device is equipped with two different types of software for data collection. One of these data collection programs is called TerraSync, the native GIS platform for Trimble units (Trimble, 2015). The second program is called ArcPad, one of the many programs in the ArcGIS suite from Esri (Esri, 2015). As ArcPad is part of the ArcGIS suite, it offers seamless integration with ArcGIS for Desktop, ArcGIS for Server, and ArcGIS for Online (Esri, 2015). We will be using ArcPad to record our data while in the field, as we will be able to utilize the power of our already created geodatabase, created in ArcGIS, with all its inherent parameters to quickly and accurately collect data.
The procedures to properly prepare our geodatabase for deployment onto the Trimble Juno units is very brief, though if done incorrectly can lead to issues in the field. For this exercise we were collecting data on the University of Wisconsin-Eau Claire campus (Figure 2).
Methods
The first step to preparing a geodatabase for deployment is to start a new ArcMap session. Open ArcMap and navigate to the folder that the geodatabase has been stored in. The first thing to be done is to add in the point feature class created prior that data points will be created for (Figure 3). NOTE: Failure to do this will result in the basemap image being displayed first and will slow down the map in the field.
In this case we will only be using one feature class for data collection, however, if more were being used then this would be the time to add them. For example, one project I worked on looked at the distribution and amount of invasive strain of reed canary grass on the banks of the Lower Chippewa River. Data collection for this project came in the form of points, lines, and polygons. Points were for very small patches of reed canary grass. Lines were for thin lines of reed canary grass along the banks. Polygons were for larger patches of reed canary grass that required us to dock our canoes and walk around the extent of the polygon. In this case, it was crucial that the proper feature be easily laid out within the ArcPad menu for quick data collection.
The next step is to add the backdrop into the map. For this step, it is necessary to select an image that will not be a large blur when zoomed into the proper level. Personally, I believe that it is also necessary to select an image that allows for some field checking. If in an urban setting, chose an image that allows you to see the study area and pick an area of reference that is discernible on the map. This will allow you to check to see if your data points are being projected properly in the field by seeing where the point is placed on the ArcPad interface in reference to your actual location. Finally, ensure that the image used is zoomed into an area that encompasses the study area, as this level of zoom will be cached and preserved for when the file is opened on ArcPad.
Following this, save the ArcMap file containing the feature class and properly zoomed image. Now we need to check out the data for use on ArcPad. The first step is to go to the Customize menu on ArcMap and select "Extensions" (Figure 4).
Select ArcPad Data Manager in order to check out the extension for use in ArcMap. Then go to Customize again and hover over the Toolbars dropdown menu and select ArcPad Data Manager Toolbar. This will allow for the data to be checked out and made ready for ArcPad. Select the first icon to the right of the "ArcPad Data Manager" text icon. This is the "Get Data for ArcPad" icon (Figure 5).
 |
| Figure 1. This image shows the Trimble Juno 3 Series. This unit was used in the field for data collection. |
This device is equipped with two different types of software for data collection. One of these data collection programs is called TerraSync, the native GIS platform for Trimble units (Trimble, 2015). The second program is called ArcPad, one of the many programs in the ArcGIS suite from Esri (Esri, 2015). As ArcPad is part of the ArcGIS suite, it offers seamless integration with ArcGIS for Desktop, ArcGIS for Server, and ArcGIS for Online (Esri, 2015). We will be using ArcPad to record our data while in the field, as we will be able to utilize the power of our already created geodatabase, created in ArcGIS, with all its inherent parameters to quickly and accurately collect data.
The procedures to properly prepare our geodatabase for deployment onto the Trimble Juno units is very brief, though if done incorrectly can lead to issues in the field. For this exercise we were collecting data on the University of Wisconsin-Eau Claire campus (Figure 2).
 |
| Figure 2. This image shows the projected study area for the ArcPad Data Collection exercise. |
Methods
The first step to preparing a geodatabase for deployment is to start a new ArcMap session. Open ArcMap and navigate to the folder that the geodatabase has been stored in. The first thing to be done is to add in the point feature class created prior that data points will be created for (Figure 3). NOTE: Failure to do this will result in the basemap image being displayed first and will slow down the map in the field.
 |
| Figure 3. This figure shows what the table of contents for a newly opened ArcMap file, after the point file for data has been dropped in first (Trimble, 2015). |
In this case we will only be using one feature class for data collection, however, if more were being used then this would be the time to add them. For example, one project I worked on looked at the distribution and amount of invasive strain of reed canary grass on the banks of the Lower Chippewa River. Data collection for this project came in the form of points, lines, and polygons. Points were for very small patches of reed canary grass. Lines were for thin lines of reed canary grass along the banks. Polygons were for larger patches of reed canary grass that required us to dock our canoes and walk around the extent of the polygon. In this case, it was crucial that the proper feature be easily laid out within the ArcPad menu for quick data collection.
The next step is to add the backdrop into the map. For this step, it is necessary to select an image that will not be a large blur when zoomed into the proper level. Personally, I believe that it is also necessary to select an image that allows for some field checking. If in an urban setting, chose an image that allows you to see the study area and pick an area of reference that is discernible on the map. This will allow you to check to see if your data points are being projected properly in the field by seeing where the point is placed on the ArcPad interface in reference to your actual location. Finally, ensure that the image used is zoomed into an area that encompasses the study area, as this level of zoom will be cached and preserved for when the file is opened on ArcPad.
Following this, save the ArcMap file containing the feature class and properly zoomed image. Now we need to check out the data for use on ArcPad. The first step is to go to the Customize menu on ArcMap and select "Extensions" (Figure 4).
 |
| Figure 4. This image shows where the Extensions option can be found within the ArcMap toolbar. |
 |
| Figure 5. This shows the ArcPad Data Manager Toolbar and all of its options (Esri, 2015). |
Click "Next" on the initial page. Select Action menu and choose "Checkout all Geodatabase Layers" (Figures 6-8). Unfortunately, when creating this blog, I did not have access to a version of ArcMap with the ArcPad Data Manager as I was using a remotely sourced desktop version of ArcMap. However, I will be using images from a previous student, Lee Fox, who took this course in spring 2014.
The next step is to specify a name for the folder that will be created for the data. Under the "Specify a name for the folder that will be created to store the data" list the name of the folder, paying attention to not include spaces in the folder name (Figure 7). Make sure that under "Where do you want this folder to be stored?:" that the ArcMap file that you have saved is the one selected.
After clicking next to get to the next window the final option is to ensure that the "Create the ArcPad data on this computer now" option is selected and then select "Finish" (Figure 8). If the process is successful a screen will appear after the process has finished stating that the operation was successful.
Once the folder containing the deployable data has been created make sure to copy it in case the data is compromised in any way. This will ensure that the original data is unaltered and will be immediately redeployable in need be. Make sure the Trimble Juno unit is connected to the computer, copy the folder again, and paste it onto the SD drive of the Trimble Juno.
Once you return from the field all that needs to be done is the data needs to be copied from its location on the SD and back into the folder created in the previous process as the checkout folder. Make sure the proper extension (ArcPad Data Manager) is turned on as before and use the tool "Get Data from ArcPad" (Figure 5).
Results
Using the Trimble Juno 3 Series in the field we were able to gather results for Surface Temperature, 2 Meter Temperature, Wind Chill, Wind Speed, Humidity, Dew Point, and Ground Cover. This data was collected over 16 points. The results were used to create two sample maps (Figure 9 and Figure 10).
Conclusion
Proper movement of a geodatabase to ArcPad for deployment can make or break a data collection outing. If the geodatabase is not moved over properly it can slow down the entire process and make field collection of data very problematic and slow. Properly moving it over, however, will usually result in a streamlined method of data collection that allows for quick response time from the software and easy recording practices. This will allow the next step of the exercise, collecting significantly more data points, to be done in an easy and streamlined manner. The geodatabase used in this exercise was selected for deployment for the entire class in order to provide a standardized method of data collection. This will allow all the data to be merged in a quick and easy manner after the data collection process has been conducted.
 |
| Figure 6. This image shows the second window where the data is initially checked in (Fox, 2014). Select the Action menu and select "Checkout all Geodatabase Layers." |
 |
| Figure 7. This image shows the Select Output Options menu within the Get Data From ArcPad menu (Fox, 2014). |
 |
| Figure 8. This figure shows the final screen that needs to be input in the the Get Data From ArcPad wizard (Fox, 2014). Selecting finish will start the process of making the data ready for deployment. |
Once you return from the field all that needs to be done is the data needs to be copied from its location on the SD and back into the folder created in the previous process as the checkout folder. Make sure the proper extension (ArcPad Data Manager) is turned on as before and use the tool "Get Data from ArcPad" (Figure 5).
Results
Using the Trimble Juno 3 Series in the field we were able to gather results for Surface Temperature, 2 Meter Temperature, Wind Chill, Wind Speed, Humidity, Dew Point, and Ground Cover. This data was collected over 16 points. The results were used to create two sample maps (Figure 9 and Figure 10).
 |
| Figure 9. This image shows the map created from the temperature taken at the surface. Darker blue represents colder areas while darker green represents warmer areas. The warmest areas are located located over blacktop. |
 |
| Figure 10. This image shows the wind speed over areas of campus. Areas of dark green represent lower wind speeds while dark red represents higher wind speeds. |
Conclusion
Proper movement of a geodatabase to ArcPad for deployment can make or break a data collection outing. If the geodatabase is not moved over properly it can slow down the entire process and make field collection of data very problematic and slow. Properly moving it over, however, will usually result in a streamlined method of data collection that allows for quick response time from the software and easy recording practices. This will allow the next step of the exercise, collecting significantly more data points, to be done in an easy and streamlined manner. The geodatabase used in this exercise was selected for deployment for the entire class in order to provide a standardized method of data collection. This will allow all the data to be merged in a quick and easy manner after the data collection process has been conducted.
References Cited
Esri. (2015). ArcPad - Mobile Data Collection & Field Mapping Software. Retrieved March 7, 2015, from http://www.esri.com/software/arcgis/arcpad
Esri. (2015). ArcPad - Mobile Data Collection & Field Mapping Software. Retrieved March 7, 2015, from http://www.esri.com/software/arcgis/arcpad
Esri. (2015). ArcPad User Guide. Retrieved March 7, 2015, from http://webhelp.esri.com/arcpad/8.0/userguide/index.htm#arcpad_data_manager/concept_datamanager.htm
Fox, L. (2014, March 3). Field Activity #7: ArcPad Data Collection. Retrieved March 8, 2015 from http://uwecleefoxmethods.blogspot.com/2014/03/field-activity-8-arcpad-data-collection.html
Trimble. (2015). Trimble – Juno 3 Series Handheld | Trimble Agriculture. Retrieved March 7, 2015, from http://www.trimble.com/Agriculture/juno-3.aspx
Fox, L. (2014, March 3). Field Activity #7: ArcPad Data Collection. Retrieved March 8, 2015 from http://uwecleefoxmethods.blogspot.com/2014/03/field-activity-8-arcpad-data-collection.html
Trimble. (2015). Trimble – Juno 3 Series Handheld | Trimble Agriculture. Retrieved March 7, 2015, from http://www.trimble.com/Agriculture/juno-3.aspx
Trimble. (2015). TerraSync. Retrieved March 7, 2015, from http://www.trimble.com/mappingGIS/TerraSync.aspx
No comments:
Post a Comment