Yes as Ronny noted, TA will use the first observation of a point name if you use the option to "store another". So when you try to store additional observations of an existing point name, the errors it shows you will always be compared to the first stored observation. If you choose "average" when storing the same point name, I'm not sure how it is averaging since there's no options. It could be simple average. In TA you can Compute Average through cogo, and there you have the option to use simple or weighted average. Simple will evenly average the position in the center of your different observed locations. Though if you average observations of a point in TA, it could make things trickier in TBC as it'd be seen as a calculation in TBC and it might not get recalculated without deleting the computation value.
TBC has a computation setting for single observation or weighted mean. Choosing single observation will have TBC compute the position using all your observations in a weighted manner, not just using the first observation. If you choose weighted mean setting in TBC, it will only show a weighted mean value in a point derivation report with longer observations and/or a RTK observation from more than 1 base point.
I'm not sure if TBC does a "simple" average of GNSS observations as TA can do. A great way to illustrate how TBC handles multiple GNSS observations to a single point name is to do a point derivation report when selecting a point. It will show the observations relative to the value it calculated. Here's an example, though with a network adjustment, of RTK and total station observation.
On a similar note, it seems that if you have observations of multiple methods (RTK and total station) to a single point name you need to perform a network adjustment in order for TBC to use more than just one data source.
------------------------------
Robert Hoy
------------------------------
Original Message:
Sent: 02-24-2021 09:25
From: Juan Serpas
Subject: How are coordinates derived from several observations on same point
How is the average of the observations is done (simple average of weighted average) in Access and TBC when we
------------------------------
Juan Serpas
Original Message:
Sent: 02-23-2021 20:10
From: Ronny Schneider
Subject: How are coordinates derived from several observations on same point
If you use "store another" it will always store a separate observation.
Just did a quick test in the simulator.
In the CSV file though it only exports the first one.
Test1,367479.776,8110806.825,25.124,
If you import the job into TBC you'll see all of them again.
On the map in Access it'll also just show the first one, but you can review the others and they'll be highlighted as yellow dots.
------------------------------
Ronny Schneider
Original Message:
Sent: 02-23-2021 15:36
From: Juan Serpas
Subject: How are coordinates derived from several observations on same point
We are trying to find out in both cases
------------------------------
Juan Serpas
Original Message:
Sent: 02-23-2021 13:27
From: Robert Hoy
Subject: How are coordinates derived from several observations on same point
Are you referring to results from Trimble Access or TBC?
------------------------------
Robert Hoy
Original Message:
Sent: 02-23-2021 10:06
From: Juan Serpas
Subject: How are coordinates derived from several observations on same point
Does Trimble has any documentation which specifies how coordinates are derived from GNSS observations.
For example, when we observe the same point 2-3 times using 5-sec, topo observations does it compute a Weighted-Mean coordinate when the user selects Store as Another?
What if they choose Store as Check? What happens when they stakeout then store another observation?
------------------------------
Juan Serpas
------------------------------