Appendix J

GPS and Criterion Surveying

GPS

1. Using the gps software (Pfinder, CMT, etc.) scroll to data dictionary or feature list or whatever name that refers to the preplanned feature and attribute format.

2. Type in the features and their corresponding attributes for the format you want to use in the field. Depending on the software used, one can specify which attribute values can be entered in the field or in the office. The Pfinder uses filters to accomplish the result. Pfinder allows the user to enable the filter each time an attribute is entered. The CMT does not have the ability to perform that task.

3. Transferring the data to the GPS unit to use in the field is accomplished by first, setting the PC and GPS unit to data transfer mode. All data transfer is initiated from the PC. Connect cables from PC to the unit, attaching them the correct com ports. Incorrect port attachment will result in no data transfer. Also, if other configuration parameters (Baud rate, etc.) are not equal between the unit and PC, there will be no transfer. Those values can be changed in the respective configuration setup menus. The data dictionary can also be created on the GPS unit itself, but only the CMT can perform that procedure. Transfer from the GPS unit to the PC can also be done using the same method. Again, the transfer must be initiated from the PC.

2. The general setup of the unit can be achieved within the unit itself. Scroll to any setup screens to alter variables such as PDOP, settle time, logging mode, etc. Most of the parameters will not need changing. But, refer to the respective manuals to familiarize yourself with correct procedures in making adjustments.

3. In the field, do not expect quick signal reception because the canopy cover can do some signal deflections and breakage. Below is the procedure for field data capture for the three GPS units used:

1. START UP. Scroll to AUTOEXEC.S and select RUN.

2. Select DATA CAPTURE from Main menu.

3. SELECT or CREATE file.

4. Select [FILE NAME], once you are at desired position.

5. Enter data into GPS Unit at appropriate attributes.

6. END. Press SH2 then OFF.

1. START UP. Push bottom button.

2. Select DATA CAPTURE from Main menu.

** Push middle button to select.

3. SELECT FEATURE. [FILE NAME].

4. Enter data into GPS Unit using arrow keys.

5. Push ESC to retreat back to the Main menu.

6. END. Hold bottom button down for 5 sec. to turn off.

1. START UP. Push ON button.

2. Select SETUP. SETUP RECEIVER.

3. Push F1(ON), to turn Receiver on.

4. Enter Lats and Longs of position.

5. PGDN to enter next screen. Enter EL.MASK, VDOP, HDOP.

** ESC to Main menu.

6. Select GPS JOBS. Select or Create JOB.

7. Enter information in JOB DEFINITION screen.

**FEATURE LIST---[FILE NAME]

8. Select POSition(F1). Select FEATure(F3).

9. Select LIST. Select FEATURE-NAME(F5).

10. Enter data values for appropriate attributes.

11. Press STORE(F4).

12. END. ESC to Main menu. Select OFF.

4. Some helpful hints: When recording static points, set the static session for at least 2 minutes and more if you are in thick canopy cover. In the CMT, set the settle time to about 3-5 sec. It will save time when satellite reception is lost. At least 4 satellites are needed for precise location and storing of data. Therefore, it some time useful to set your PDOP to a higher setting. The precision may be reduced, but you will get some data. Do not attempt to record data if the PDOP graph readings are too high(from quickplan). PDOP of 5 or higher is not a good time to use the unit. Exception is if canopy cover is zero.

2. Downloading can be initiated within the BBS itself and sometimes it must be initiated with the modem software. The CMT BBS is one that uses that procedure.

3. Differential correction is explained in the user manual, but is easy to perform. Make sure files are in chronological order (if more than one file is used for correction), or it will fail to correct.

The Technical Use of the Criterion Survey Laser

The laser while developed for timber cruising is very useful as a road survey instrument. It can accurately measure horizontal distance, slope distance, azimuth and percent slope. The laser also gives one the power to store the data in the field, this reduces the human error involved in the relay of data from the instrument operator to the notetaker. This also becomes rather enjoyable when working in wet weather. This, however does not mean that the laser is waterproof, it can withstand a rain storm, but do not throw it in a stream.

• The word "TREE" should be displayed

1. Use the up and down arrows to Navigate; Go until you find SURVEY and hit enter
2. Then scroll until you find UNIT SURVEY and hit enter

• This will be displayed:

1. When done move the arrow key down for the next menu. (If this does not work push enter then the down arrow)
2. Scroll down to the screen:

1. Make sure that the asterisks is on the "SIDE" (like above in #6; If not push the orange "SIDE" key; which is also the #5 key) scroll down once to:\

1. (Take a reading at eye level to approximately the same height on your partner or tree) Take first reading to the Left. To do this, push the button on the hand trigger and hold it in. The longer you hold the more accurate reading.
2. HIT ENTER (this will save that reading, hit clear to reshoot)
3. SCROLL until you find:

1. Push the orange "SIDE" key (which is also the #5 key)
2. Take a shot to the right like done in #7.
3. HIT ENTER
4. Then down arrow until you get to the display as in step 10. Move the asterisks to the FS by pushing the INLINE button.
5. Use the down arrow once to:

1. Take a front shot to your next survey point.
2. Repeat steps 6 to 16.

Criterion to Pt2Pt to Terrain Models in RoadEng (5/98)

This is to help you with the downloading of data from the Criterion 400 into a program called Pt2Pt and then into the Terrain Model in RoadEng. You may want to look at "Converting Criterion Data to Terrain Models in RoadEng" that was done by the class of 1997 (I think?). There is also a Readme.doc file that comes with Pt2Pt that was really useful for me if you have any problems. I found out a little more about the Pt2Pt program that may help you in the whole process. If you can not find this Pt2Pt software from previous classes it can be downloaded easily from the Softree ftp site at ftp://ftp.softree.com. If you need to talk to someone you can call (206) 628-6454 and get on the technical support line. You should get a hold of Craig Spears. Well here it is and I hope that this makes your life easier.

First of all, always start with a forward shot (FS) with the Criterion. If you don’t you will mess up the numbering convention later when you bring it into RoadEng. (I learned the hard way.)

Make sure that the cable is plugged into the computer and into the battery. The battery also needs to be attached to the Criterion. Open up the Pt2Pt program and scroll over to the "Transfer" pull down menu. The Criterion needs to be turned ON. Input the proper Serial Port and it will download until it says, "download complete." You will then have a root filename (or you will have to save it) with the extension of ".S1" Rename if needed to something that you will remember and that will not be confusing later on.

If your data is not on the Pt2Pt screen you can load it by going over to the "Load" pull down menu. Input the correct pathname or just press the down arrow key were you will find it in the directory. Once the file has been specified, scroll down and make sure that the comma field is selected. Then you will be able to load the file up. Now scroll over to the "Map" pull down menu and hit ENTER. Hit the right arrow key to select all of the data. (This is where you edit the junk files out.) The screen should have four columns: Input Record Fields, From, To, and New Output Record Fields. There should be a zero (0) highlighted in the To column. The Input column should look something like:

Converting Criterion Data to Terrain Models in RoadEng

Notes to make life easier.

If GPS coordinates are taken, take them at the first point (Pt 1) of the given traverse. This allows for easier calculation of coordinate offsets when importing traverses into the RoadEng TERRAIN module.

Ensure that the person running the Criterion really knows how to use it. In particular, the operator should be able to recognize (by sound) when a particular sensor (usually compass) does not take a reading and how to get that reading for the data shot. This will ensure that there are no holes in your data.

If the declination is set in the Criterion, make sure that it is consistent for all traverses and that all traverses are surveyed with it set. I recommend that no declination be set in the Criterion and that rotation of the traverses is performed when importing into RoadEng.

Downloading Criterion Data

The PT2PT program provides a simple method of downloading data from the criterion. If a copy of PT2PT cannot be found, contact the Criterion people and ask them to e-mail you a copy.

Within the PT2PT program, the TRANSFER pull-down menu provides a function to download criterion data. Make sure that the criterion download cable is plugged into the battery and the appropriate serial port and that the criterion is turned on.

When setting up the download, you will choose a port and a download root filename. Regardless of the number of surveys in the criterion, this filename will be given to them all. The only difference will be the extension, which will be .S1, .S2, .S3 and so on up to .S20. All surveys in the criterion will be downloaded every time you download. It is important that, immediately following the download, these files are renamed (file manager) to something that indicates what they contain. This saves a lot of confusion later during conversion and use. The best way to keep track of the surveys is to give each a unique UNIT number when initializing the criterion for each survey. This number should be recorded somewhere with comments as to what it pertains to. Then the traverse can be identified by this number in the downloaded file.

Converting Criterion (.S*) Files for Use in Road Eng

The PT2PT program provides a function for converting Criterion files for use in RoadEng. It is easier to just convert the files manually using Excel so that is the process I will describe here. If you are interested in using PT2PT, you can find info on the process in the readme.txt file that accompanies PT2PT.

To access the files, open them as comma delimited text files in Excel. The files will look like the following (without the descriptive part above). I have provided a description of each column that is relevant to the conversion (but is not part of the file!). The "junk" columns are exactly that as far as this process is concerned.

After accessing the files, simply delete the columns described as junk. The file should now look like the following table and is now in the appropriate format for import into RoadEng except that it needs to be checked and corrected if necessary (see next section).

After removing the "junk" files, the file must be checked to ensure that each line includes data. Scroll through the data set and ensure that each column of each line contains data. Caution: Do not change the From/To Numbering at all. For lines that are not complete:

Foreshot (FS) Lines:

Sideshot (SD) Lines:

Importing Criterion .POL Files into RoadEng

After creating the corrected .POL files, the next step is to import the traverses into the TERRAIN module of RoadEng. There are two approaches to this: simple and not as simple. If the actual coordinates and elevation of the traverses is not important to the task at hand, use the simple method. In othere words, if you simply desire that each point on the traverse is relative to the others and are not concerned with how it relates to the real world, use the simple method. If actual coordinates and elevations are desired, use the not so simple method.

Simple Method

You should now have an imported traverse with side shots (shown as dots) and proper rotation. Save this as a .TER file. Refer to later sections for development of terrain models.

All of the steps in this method are the same as above except for Step 7.

7. To put the traverse in real world coordinates and elevations, there are two situations. The first situation is when the coordinates/elevation you have are for the first point in the traverse. The second situation is when the coordinates/elevation are for any other point on the traverse.

7.a. One - Coordinate/elevation for first traverse point.

In the case that you have coordinates/elevation for the first traverse point, simply enter these coordinates in the appropriate X and Y offset entry boxes. In the Z box, enter the actual elevation minus 100 ft (because RoadEng automatically puts the first point at 100 ft elevation).

You should now have an imported traverse with side shots (shown as dots), proper rotation, and proper coordinates/elevation. Save this as a .TER file. Refer to later sections for development of terrain models.

7.b. Two - Coordinate/elevation for other point on traverse.

In this case, the traverse should be imported by the simple method initially. After importing, look at the point on the traverse at which you have real-world coordinates and write down the coordinates that RoadEng has assigned to it including elevation.

After obtaining these coordinates, clear the traverse without saving.

To calculate the coordinate offsets, subtract the RoadEng-assigned value from the real-world value (keep track of minus signs). These calculated values are the appropriate offsets to use in the Coordinate Shift entry boxes. Continue importing as usual using these values.

You should now have an imported traverse with side shots (shown as dots), proper rotation, and proper coordinates/elevation. Save this as a .TER file. Refer to later sections for development of terrain models.

Development of Terrain Models

In general, this portion of the handbook is not designed to teach you how to use RoadEng so for normal operations, consult the RoadEng manual. But, here’s a trick for working around some RoadEng limitations.

With large datasets, RoadEng is sometimes unable to develop the terrain model because of a limitation with the number of features. This is usually because it counts each side shot as a separate feature.

To get around this in the TERRIN module, Save As the imported traverse w/side shots (but no terrain model) as an AutoCAD Format (*.dxf) file. Do not modify the default save options.

After saving as a .DXF file, then import the file as a DXF Import File. Under options, enable the checkbox "combine isolated point entities into features". This will cause the sideshots to be considered a signle feature.

Save this as a .TER file. You should now be able to perform all terrain model functions on this consolidated file and all of your features such as coordinates, etc should still be correct.

2. Upload the data, by choosing UPLOAD from the menu.

3. Set the Data Collector to ASCII coordinates. Choose Upload From Existing Print File.

4. Find .PRN file that you want for the conversion.

5. Choose Export File from the menu. Choose ASCII. Give the file a name. The format can be changed if needed. Hit GO and Exit.

6. Edit the exported ASCII file. The first column of each line must be deleted and replaced by either a CL or a SS. These refer to Center line and Sideshot respectively. Refer to the .PRN file to associate the numerical numbers with the CL/SS characters.

7. In the terrain module in ROADENG choose import feature set from the menu. Choose ASCII Road C/L coordinates and then the SS coordinates. Choose your file.

8. Choose export feature from the menu. Export the features to the traverse document. Be sure to have the cross-hairs on the Plan view of the terrain module are on the traverse and not the Side shots or the export will not be complete. The end result will be a .DB1 file that can then be made into a .MAP file.