Yes. The averaging limits are mainly for points observed multiple times with RTK. In static processing where we are going to adjust the vectors to control, it is mainly a pain in the...neck.

* From the Tools pull-down menu, select Project Management

* Right-click on the project of interest in the displayed list.

* Select Properties at the bottom of the dialog box and change the limits for automatic coordinate averaging to some higher value, say 10 meters.

Note: 10 meters is the largest value SKI-Pro will let you enter. This will give you a check on a bad starting position, but will not display the noise of processing from slightly different reference coordinates.

In a kinematic survey, SKI-Pro treats the trajectory points different than the survey points. The trajectory points are not stored in the database. To get them into the database, perform the following steps:

* Go to the Results page.

* Click on the Points folder in the Results tree view (Don't open the folder as you will only see the surveyed points.), and in the right-hand side of the screen all of the points will appear.

* Click on the first point in the list.

* Hold down the Shift key and click on the last point in the list.

* Hold down the CTRL key and deselect the surveyed points that are already visible.

* Select Copy from the Edit pull-down menu.

* Switch to the View/Edit page.

* Select Paste from the Edit pull-down menu.

Your trajectory points should now appear both in the View/Edit screen as well as the Points screen.

SKI-Pro doesn't write the older formats for backup, so do the following work around:

* After the data has been assigned, you can export it as a RINEX file. The RINEX file will contain site name and antenna height corrections that have been made at the time it was created.

Yes. Do the following steps in the View/Edit screen:

* Right-click on the point and select the Properties option in the pop-up.

* Select the Mean tab.

* In the State column, double-click on Automatic.

* Double-click on Always.

* Repeat for each vector in the mean.

Yes, you can see this on the Data Proc page. In the left portion of the display screen, you will see the Point ID and the Point Class. (If not, you can manipulate the display so that Point Class is displayed).

* The Point Class shown (the CURRENT class) will indicate the coordinate value that will be used if the point is chosen for a reference. If the points have been adjusted, the Adjusted class will be displayed and used as the Reference position.

SKI-Pro assigns the Reference triplet. It is assigned to the base station in an RTK survey, and it is assigned to the known (starting) end of a baseline solution.

* You cannot assign a Reference position.

* You can edit the Reference position. If you edit the reference position, the program will warn you that all points associated with this Reference position will change by the same amount.

Somehow the data has been tagged as kinematic data. One common way this can happen is if the operator forgets to enter a Site ID. In any case, do the following to fix it:

* In the Data Proc page, right-click on the interval with the xxx's.

* Select the Export to RINEX... option.

* Delete the existing data interval by right-clicking on the Point ID (-) and selecting the Delete option.

* Edit the RINEX file as shown below (simply replace the date-time stamp with the Site ID) in the two MARKER lines.

* Also, if there is a 2 in column 29 of the header of the first epoch of data, change it to a 0. (See Tip of the Week for Wed. July 2, 2003).

* Re-import the data from the edited RINEX file.

Example Edited RINEX File Header

90660403_1634100                                            MARKER NAME

90660403_1634100                                            MARKER NUMBER

The kinematic ID above is 9066 (Receiver number), 04 (month), 03 (day), 16 (UTC hour),

34 (minute), and 10 (seconds). There is an implied decimal point in the 100 value for seconds. 100 = 10.0

The kinematic ID is changed to SITE, which is the static station ID.

SITE                                                                        MARKER NAME

SITE                                                                        MARKER NUMBER

The following are my basic steps in dealing with problem vectors in SKI-Pro 2.x. Beyond these steps, it becomes a science project (or a labor of love if you will), and I refer you to the SKI-pro Help items. If these steps don't help, and if you can't just throw the vector out of the network, it may be better to just re-occupy it.

* In the Results page, open the Baselines folder of the processing session containing the unfixed line by clicking on the + sign to the left of the folder.

* Note the position of the baseline in the list and the from and to station names.

* Click on the Logfile icon for the session.

* Right-click on the displayed logfile and make sure that both Satellite information and Cycle slip information are checked.

* Move down in the log file to the solution information for the vector in question. (The position in the logfile will be the same as the position in the baseline folder list, but the from and to stations will be reversed).

* Move down to view the Satellite information section shown below. Note if any satellites have a sizable difference between the L1 and L2 measurements. If so, this satellite should be removed from the processing.

Note: The example shown is not a particularly bad example, and the solution did fix, but with an asterisk. Removing satellite 1 would probably result in a non-asterisk solution.

BL_SI.8    SATELLITE  INFORMATION

---------------------------------

 SV id   L1 phase  L2 phase   L1 code  L2 code

     1       325           317          312         305

    11       245          245          245         245

    14       334          333          335         334

    20       382          382          370         370

    22       125          124          125         124

    25       382          382          370         370

    30       231          231          231         231

* Next, move down to the Cycle slip information section and see if any particular satellite has a number of cycle slips. (Usually this will coincide with the satellite selected in the previous set). If there is a satellite with a large number of cycle slips, or ria (re-initialized ambiguity) slips, this satellite probably should be removed from the processing.

Note: Satellite 1 selected above also has an ria cycle slip.

BL_CS.8    CYCLE  SLIP  INFORMATION

-----------------------------------

Total no of cycle slips: 4

      Time                      time from    SV   freq     slip value  fraction

                                   start (sec)   id               (cycle)   (cycle)

  06/09/2002 17:01:20         560       1       1            21.0     0.234

  06/09/2002 17:02:30         630       1       1            -0.4    -0.406 ria

  06/09/2002 17:15:30        1410      14      1            54.0    -0.010

  06/09/2002 17:15:40        1420      14      2            62.0    -0.029

* Return to the GPS-Proc page, right-click, select Processing Parameters, uncheck and remove the selected satellite(s) and reprocess. If the baseline resolves, you're finished, store the solution. If not, you have some decisions to make. Good luck.

Note: Don't remove too many satellites. I don't recommend less than 5. If you need to go down to 4, watch the PDOP.

If the control value is selected as Local, the processor will ignore it. The processor is working only in WGS 84.

This is common if the control points were imported from an ASCII list.

To correct the problem, right-click on the point name in the processing screen list. Select Edit Point..., click the WGS 84 radio button to the right of the Coordinate Type field in the General tab of the Properties box, and then try the automatic processing again.

SKI-Pro is using the reference position for the RTK base point when it processes to the other point in the project. It is not updating the reference position from the averaged position processed from the CORS because reference is a higher classification and it existed before the average class position. If this reference (or control) position was done with a HERE or SPP function in the field, the resulting position for the other static point on the project will be off by the amount the HERE position was off.

To correct this, go to the View/Edit screen, right-click on the RTK base point, select Delete | Triplets | Reference and then reprocess...

Or (especially if the RTK data is part of the current project)

Right-click on the RTK base point, select properties, and edit the Reference point class position to be same as the Averaged point class position. (You should notice a large difference before editing.)

If the correct antenna type you want to use is contained in the project Antennas tab, simply go to the GPS-Proc tab and right-click on the point ID (not the data interval itself). Select Properties...and click the down-arrow to the right of the Antenna Type: field. Click on the correct antenna in the list and then click the OK button.

If the antenna doesn't exist in the project Antennas tab, go to the SKI-Pro Antenna Management area. Highlight the antenna you want to use and from the Edit pull-down menu, select Copy. Go back to the project Antennas tab and from the Edit pull-down menu, select Paste and then perform the steps in the first paragraph of this section.