Beginning with TPC Desktop 2024, when you take multiple GPS/GNSS observations of a survey point, TPC can average those observations to improve the accuracy of that point's position.
GNSS Averages Sneak Peek (3:45) - See how to average mutliple GNSS observations in TPC and improve the accuracy of those survey points.
Example
In the example shown here, 2 observations were made for point 201, a day apart.
The two observations are averaged to compute the position of the point, displayed as the AVG (Average).
NGS User Guidelines
In their User Guidelines, NGS says "RT positioning of important data points cannot be done reliably without some form of redundancy". They provide guidelines on how to create these redundant observations.
TPC provides a number of options for specifying redundant GNSS observations. The method you choose will depend on your equipment (data collector), work flows and personal preferences.
If a GNSS project is imported multiple times, TPC looks for GNSS observations with matching date/time stamps and although they get imported into a traverse, they are not treated as redundant observations of that survey point.
As you work on a project, you may need to collect more points and end up exporting the project multiple times to TPC. TPC accounts for this by ignoring observations with a duplicate time stamp.
TPC also looks for GNSS points with multiple observations when importing GNSS data. If it finds one or more imported points with multiple observations, it displays the GNSS Averages dialog, allowing you to reject any outlying observations, update existing survey points with the computed averages, report the averages or export them to a CSV file.
From the GNSS Averages dialog, you can use the Summary button to report how averages are computed for GNSS survey points with multiple GNSS observations.
From the GNSS Averages dialog, you can use the Export CSV button to write a CSV file with the data used to compute average positions for GNSS survey points with multiple GNSS observations.