Trimble Business Center

 View Only

 TBC v2025.20 GVX Export Reporting Unexpected

John Garrison's profile image
John Garrison posted 03-17-2026 07:58

I’m working with a set of vectors exported from TBC v2025.20.  Most are tied to Trimble R10, R12, and R12i rovers using 2-meter fixed-height carbon fiber rods, measured as 2.000 m to the bottom of the quick-release.

In TBC, everything appears correct, and when exporting to TDEF the heights are properly corrected and stored as APC values.  However, when exporting to GVX, the <ARP_HEIGHT> is reported as exactly 2.000 instead of 2.05.

I’m seeing the same behavior on base setups as well.  Heights measured to the lever of the R10 extension are exported to GVX as the uncorrected lever values, rather than being adjusted to the ARP.

Based on the NGS GNSS Vector Exchange (GVX) specification, <ARP_HEIGHT> should represent the vertical distance from the ground mark to the Antenna Reference Point (ARP).  That makes me think I may be overlooking a setting in TBC, or possibly misunderstanding how GVX handles antenna height conversions.

Any insight would be appreciated.

Thanks,

Ronny Schneider's profile image
Ronny Schneider posted 03-17-2026 16:12

From my understanding the vector in the GVX is ground bound, between the survey marks themselves.

If you change in TBC the information about using the quick release it doesn't change the antenna part in the GVX, but it changes the "ELLIPSOIDAL_HEIGHT", "GEOCENTRIC_COORDINATES" and "GNSS_VECTOR - ECEF_DELTAS" values for this point by exactly this amount.

The antenna height is just an information, and TBC removes the information about the quick release, since it's not mentioned in the NGS antenna specifications.