The Traverse View can display and manage GNSS data along with terrestrial data. The example shown here is an RTK NTRIP import.
Having the GNSS data readily available in the Traverse View will help you review and evaluate GNSS data you have collected and help you make decisions on how to get the best possible results from it.
As a rule, you will create GNSS traverses by importing GNSS data.
When you import GNSS data, TPC automatically creates a traverse to hold the raw GNSS data and formats the Traverse View to display that data. That traverse also is assigned Traverse Drawing Settings to draw the GNSS points.
When you collect GNSS data, like RTK points, TPC stores the geodetic position and ellipse height along with statistical data like RMS, PDOP and sample size. This data is imported into the traverse as raw GNSS data. Each traverse point stores one GNSS observation.
TPC can average multiple GNSS observations for the same point, providing better accuracy which is helpful for control points. See Averaging GPS/GNSS.
Individual observations can be accepted or rejected on import, any time average GNSS positions are computed or directly from the Traverse View. See Accepting and Rejecting GPS/GNSS Observations.
RTK Base and Rover Point Types
When you use RTK (Real Time Kinematics) for collecting GNSS points, you have one or more base stations, which can be physical or virtual, and RTK vectors to each rover point measured.
TPC treats these RTK base points like occupied points and any RTK points derived from then like side shots.
In the Traverse View shown above, the base point 1107 has 5 RTK points derived from it.
Depending on your field data collection procedures, you may have collected GNSS points in specific sequences to pick up features like curbs, edge of pavement, building foundations, etc. If you separate these points into traverses using Point Codes, TPC retains the collected point sequence in the resulting traverses. See Creating Traverses From Point Codes.