TPC stores base and rover points as occupied points and side shots. This allows you to use all of TPC's normal conventions to
•display relationship of rover points to base in a Traverse View
•plot base points and rover points separately using Traverse Drawing Settings
In the traverse shown here, the base point 1107 is followed by 6 RTK (rover) points that originated from the base point.
Each RTK point includes a raw GNSS observation.
Notice that the status bar at the bottom of the view displays Base=1107 when RTK point 202 is highlighted. This confirms the relationship between the RTK point 202 and it's base point 1107.
Relating Raw GNSS Observations to their GNSS Points
Each raw GNSS observation relates that data back to a GNSS point in the survey. In the example shown here, the GNSS points are listed in the Point column. So the raw GNSS data stored with point 202 can be used to
1.compute the position of point the GNSS point 202, if it doesn't already exist
2.add a redundant GNSS observation to the GNSS point 202 if it does already exist
TPC provides a number of ways for you to relate raw GNSS observations to their respective GNSS survey points, depending on your equipment (data collector), work flows and personal preferences.
When you tell TPC to compute GNSS averages, TPC can help you identify any observations that are outliers. You can then choose to reject those observations so they are not used in the average computations. See Accepting and Rejecting GPS/GNSS Observations.