Forgot your password?
PDA Database Backup Utility
Data Verification Procedures (QC_Tool)
Data Preparation and Verification
Overview
Major data issues are often associated with relational key values whereas minor data issues are usually associated with missing data, incomplete data or blank records. Incorrect key values cause data processing errors and need to be resolved prior to processing. Tabular data should also be checked for incomplete field entries, spelling issues, and inconsistent entries.
PUID or SUID keys consist of the following structure:
YYYYMMDDUUUS**P
Y = Full Year, M =Padded Month, D = Padded Day, U = Unit ID, S =
Session ID, **P = Point or Survey ID
Note: Point or Survey ID's and have their
values padded to three digits once converted to ObsID or SurvID's.
Step 1: Converting Data Packages
Data packages that have been downloaded from the handheld are in a Access 95 version and need to be converted to an Access 2002 format prior to running data verification procedures.
a. Select the following menu item, browse to sampledata_unit.mdb.
b. Save renamed copy in same directory as sampledata_unit-2002.mdb.
Step 2: Importing Quality Control Elements
a. Open the sampledata_unit-2002.mdb
file, select the following
menu item, browse to your QC_Tool.mdb file.
Step 3: Select Quality Control Elements
Select each of the following tabs: Tables, Queries, Forms, Modules
and click "Select All" in each. After the last tab click "OK".
Step 4: Run Analysis
After importing the Quality Control tool elements, select Forms from the Objects list. Open the "Start" form and click the Import Rapix button. Note: This step will import the rapix.dbf file from the same directory as your data package that downloaded from the GPS unit. This .dbf file must be called "rapix.dbf" and must be located in the same directory. This step only needs to be done one time and will only import replicants of rapix table if clicked more than once.
The next step is to select the Photo Syntax that is being used for your photos. The current values are:
- Nikon - "DSCN" (Default)
- Canon - "IMG_"
- Pentax - "IMGP"
- Olympus - "P000"
Once completed, click the "Process Report" button.
The Start form also displays information on the current version of your application. Users connect to the Internet can use the "View updates" link to access the latest application updates on this site.
Step 5: Review Analysis
Review the Quality Control Tool results, note comments
and make the necessary corrections within your tables. These changes
will consist of reviewing the PUID/PointID and SUID/SurvID fields for
inconsistencies noted above. Once corrected, close this form and open
the Start form again. Click the "Process Report" button again and
verify all errors have been eliminated and/or documented. Repeat this
process until all corrections have been completed. This form can be
accessed directly by selecting the Report form in Access.
If the data packages contain photos, review for photo quality issues.
The photoviewer form may run slowly depending on the size of your
photos and your computer. We recommend limiting photo sizes to less
than 1.2 mb each.
Note: Isolating photos in a sub-directory will hide the photos from
this tool and will speed up the opening of the form.
Here are some tips in making data corrections:
- When making data corrections, please place a note in the comment field and type in your name next to the associated comment. This will allow us to track changes if we have questions later.
- Check table for erroneous values that contain unusual characters such as "" or blank records that appear to be incomplete entries and eliminate these records. These records will be identified within the form by the "Keys containing invalid ANSI symbols identified" section.
- Offending records can be isolated by replicating the table and renaming this duplicate table to table-name_FIX. Remove the good records from this new copy and then delete the bad records from the original table.
- Deletion of records can sometimes result in the creation of orphaned records since there is often a heirarchical relationship between tables. When in doubt check with us prior to making major record deletions or forward the package onto RAP for verification.
- Missing PointID's or SurvID's can sometimes be identified by their associated PUID or SUID terminal values and updated. See the upper right window in the Report form for suggested "Correct values".
- Extra rapix.dbf waypoint values can cause some processing errors with earlier versions of VB Rapix and should be deleted or clipped using ArcView or ArcGIS by the project data manager prior to importation. Waypoint values containing text MUST be removed prior to processing with VB Rapix. This no longer applies, pyRapix will accept all GPS points into the Master Shapefile. Those points in the shapefile that do not have a RAPIXID must be removed manually in GIS software.
- Waypoints over 501 will display #ERROR in RAPIX Status since
these are predetermined locations or location where no GPS reception
was available. Please contact RAP to arrange a method for creating
locations for these points.
- View the "Photo Checker" tab and review the photos. Missing thumbnails that indicate "No photo" (see below), but have an associated photo number indicated below should be reviewed by checking the data package directory and verifing the photo exists. If the photo is missing please locate and update, or open the PHOTO table and eliminate associated photo number.
Once the package has been reviewed, please change the name to one of
the following :
- VERIFIED_sample-data_2002.mdb: Data has been completely verified and is ready for processing.
- ISSUES_sample-data_2002.mdb: Data contains data that has been isolated and should be corrected prior to processing. Example: Records that have been isolated due to lack of associated waypoint data or missing associated photos. This data can be processed but may result in the loss of records, i.e. - non-resolved problematic records have been isolated in "_FIX" tables and these have not been fixed prior to importation to the main RADB database.
- ERRORS_sample-data_2002.mdb: Data contains major errors and needs to be corrected by crew members prior to processing. Example: Non-resolvable key issues.
Application Troubleshooting
Problems encountered by this tool are due to version incompatibility issues or unexpected data issues that cannot be properly analyzed by the tool's forms and queries. Here are some noted alerts and solutions.
Broken OWC10.DLL reference information alert.
Issue
This error periodically arises when converting and exchanging Access
databases between computers that have differences with their Visual
Basic .dll libraries. The solution to this incompatibility
issue has not been adequately identified by Microsoft or other online
forums.
Solution
- After receiving the error above, click "OK" to the dialog error.
- Press Alt+F11 to call up the Microsoft Visual Basic editor from within Microsoft Access.
- Select Tools>References from the editor menu.
- Check off the following box.
- Close windows and resume the opening of the Start form, click the "View Report" button.
"Invalid Procedure Call" warning alert
Issue
This error is generated by a query used by one of the
subforms in the "Report" form when it cannot complete a
group-by function. After clicking "OK" the Report
form will often display a subform that appears to be blanked out.
Solution
This problem is caused by unusual data types in one of the
keys or point fields. Close the
report and review the tables for unusual records that have bad
characters, blank key values. Open the Start form
again and click "View Report". Repeat this process
until problem is corrected or submit the data package RAP HQ.
