Hi,
can you define 'strange offset' in this context? Like a more or less constant offset or changing? In the ellipsoidal height or MSL height? And in which scale? Like cm, m or where?
The ellipsoidal height should be more or less identical. MSL can vary based on the used geoid - if you have geoid with higher resolution for your area (so not the global one but local to UK) it will differ from the global.
Also - what's the caster URL you're using? If this is a none-public URL feel free to shoot it via a private message. The mountpoint may also contain further information on the stream settings - and we can check if there is a config difference compared to Trimble VRS network (which is the foundation of TCH).
------------------------------
Nico Becke
------------------------------
Original Message:
Sent: 05-21-2021 01:19
From: David Brooks
Subject: Why is the Geoid menu visible if collecting raw GNSS (WGS84)?
Okay thanks for that info. Im finding a strange Z offset between control points surveyed by Trimble Catalyst and same poitns sureyed by Leica using Smartnet. I'm just checking that the GNSS Output system and datum are the same across the platforms.
------------------------------
David Brooks
------------------------------
Original Message:
Sent: 05-17-2021 23:00
From: Nico Becke
Subject: Why is the Geoid menu visible if collecting raw GNSS (WGS84)?
Hi David,
the 'GNSS Output' configures your horizontal datum; the vertical datum is independent from this in TMM.
So technically you can't deselect the geoid in TMM as most workflows require a geoid.
If you select 'Same as source' it means TMM does not apply any horizontal datum transformation - but we still apply a geoid afterwards.
Never the less TMM/ GCP provide both MSL and ellipsoid height - you can verify this in the export of GCP:

So there is no need to remeasure points - at least from what I've seen above. If points have been collected with GCP the export does contain both heights.
Cheers
Nico
------------------------------
Nico Becke