|
As you work on a project, you may need to collect more points and end up exporting and importing the project into TPC multiple times. As a result, an individual GNSS observation can be imported multiple times.
Beginning with TPC 2026 Release 2, each time TPC imports a GNSS CSV file, it looks for a matching GNSS observations it has already read. It identifies these by the date/time the observation started. If TPC sees an existing GNSS observation with a matching date time, it does not create a new survey point for it.
Prior to TPC 2026 Release 2, you could insure observations were correctly imported by selecting an existing point option for the import. See Importing Matching Points.
Details
If you turn on [X] Details in the Import Settings dialog, TPC reports when it finds an existing, matching GNSS observation based on the date/time as follows.
In the example shown here, existing survey point 403 was imported again, and the match identified by date/time.
Found existing survey point 403 (matching label and GNSS date/time)
Keeping existing survey point
403 Desc:rs4 Attr/Code:FPK
Lat=43.9837921dN, Lng=124.0976658dW, Ht=-34.26
Y=136704.337 X=7255351.466 Z=46.40
Origin: Global
Antenna ht=6.31 Feet
Solution=FIX
RMS: Y=0.034 X=0.034 Z=0.048 Horiz=0.048 Feet
PDOP=1.20 GDOP=1.40
Start Time=2026-02-19 14:27:07.6 UTC-08:00 End=2026-02-19 14:27:37.6 UTC-08:00
GNSS Averaging
If TPC imports a GNSS observation with the same date/time stamp more than once, it accounts for this by using just one observations with that date/time stamp.
See Averaging GPS/GNSS.
Related Topics
Using GPS/GNSS GPS/GNSS Data Importing GNSS CSV Exporting GNSS CSV Averaging GPS/GNSS
Editions
Premium, Professional
|