|
|
TPC provides several ways for you to specify which point matches (is related to) another point.
Point label match (default)
This is the default method, in which TPC allows you to record any number of observations to existing survey points.
An example of this would be GNSS observations. The first GNSS observation to a survey point is allowed to compute the position of that point. Additional GNSS observations to that point simply hold the observed data without computing their own position for that point. The additional GNSS observations, are however, included in computing the average position for that survey point.
If your data collector allows redundant observations to existing survey points, TPC will automatically create corresponding redundant GNSS observations when you import that data into TPC.
Point label contains
This method assumes that redundant observations are identified by some matching character or string in their point labels, as in the following examples.
•GNSS point label 100 could have redundant GNSS observations with point labels 100@, 100@1, 100@2 all of which are redundant GNSS observations for point 100. You would just tell TPC that the @ symbol identifies redundant observation points.
•Observed GNSS point G100 would related back to GNSS point 100 if you specified G as the matching string.
This convention allows a GNSS point to be observed any number of times, with each observed position being associated to it.
Point label difference
This method assumes that all your point labels are numbers, or start with numbers and that point labels for additional GNSS observations are incremented by some number offsets as in the following example.
•GNSS point label 100 could have additional GNSS observations with point labels 1100, 2100, 3100 all of which are observed positions for design point 100. You would just tell TPC that the difference of 1000, 2000 or 3000 identifies the GNSS point.
This method allows you to easily report sequences of repeated stakeouts. For example
•On Monday, you use 1000 as the offset for all your GNSS points.
•On Wednesday, when you go back out to re-measure those same points, you use 2000 as the offset.
•On Friday, you would use 3000 as the offset.
Point description contains
This method assumes that existing survey points are identified by some matching character or string in the point descriptions, as in the following examples.
•GNSS point label 100 could have any number of observed points, each with #100 in their point descriptions.
Any character, like # can be used to identify the point labels in the description and other information can be included in the description either before or after the #[design point label].
Sideshot points in a traverse relate back to their control point
This method assumes that traverse control points are the matching points and any sideshots refer back to them.
Related Topics
Averaging GPS/GNSS How TPC Stores GPS/GNSS Data
Editions
Premium, Professional
|
|