Is it just me, or is anyone else having serious height problems (~0.15 m) when submitting R8 GNSS data to OPUS recently?
Sometimes I get a message back saying that the antenna name doesn't match, other times no such message. In any case, the heights are NOT correct. But, the peak-to-peak, etc are OK. I believe this started about the time they switched to the new models?
John,
This might shed some light on things. Here is the NGS ANTINFO data for the VARIOUS Trimble R8 GNSS calibrations:
TRMR8_GNSS NONE Integrated GPS L1/L2+L2C/L5 GLO L1/L2 TR NGS ( 4) 11/03/25
0.6 -0.2 83.7
0.0 0.1 0.1 0.1 -0.2 -0.7 -1.3 -1.6 -1.6 -1.3
-0.8 -0.4 -0.4 -0.6 -0.6 -0.2 0.8 2.0 2.5
-0.7 -0.3 72.1
0.0 -0.0 -0.1 -0.3 -0.4 -0.5 -0.7 -1.0 -1.2 -1.3
-0.9 -0.1 1.0 1.8 1.9 1.0 -0.5 -1.6 -0.8
TRMR8_GNSS3 NONE Integrated GPS L1/L2+L2C/L5 GLO L1/L2 TR NGS ( 5) 11/03/25
0.9 -0.4 84.7
0.0 0.1 0.2 0.2 -0.0 -0.5 -1.0 -1.4 -1.5 -1.2
-0.8 -0.4 -0.3 -0.5 -0.6 -0.2 0.7 1.9 2.5
-0.9 -0.4 73.4
0.0 -0.0 -0.1 -0.2 -0.3 -0.4 -0.6 -0.8 -1.1 -1.2
-0.9 -0.2 0.8 1.5 1.5 0.8 -0.4 -1.1 0.2
TRM_R8_GNSS NONE Integrated Antenna (R8) Model 2 NGS ( 2) 06/05/22
0.9 0.0 103.9
0.0 0.6 1.6 2.9 4.2 5.5 6.7 7.5 7.9 8.0
7.6 6.8 5.5 3.8 1.6 -0.9 -3.5 0.0 0.0
-2.0 -0.4 80.8
0.0 -1.0 -1.4 -1.2 -0.7 -0.3 0.1 0.2 0.1 -0.2
-0.6 -1.2 -1.7 -2.3 -2.9 -3.2 -3.0 0.0 0.0
I suspect that there may be some confusion depending on software...
🙂
Loyal
Thanks, Loyal. I have been trying to figure out what could cause 15 cm, since the ARP heights in those models are somewhat less. I have seen it now in several different points. After the first one I sent an email, but got no response.
Loyal: I believe they use several machines for processing OPUS, correct? Maybe the machines do not have the same files, that could be the reason for the sometimes return of "antenna type unrecognized".
Have you tried using Trimble's integrated data processing function within Trimble Business Center (it works with a basic installation/no key required). It will automatically convert your DAT/T01/T02 files into RINEX, detect the type, ARP offset based on OPUS's ARP and keyed-in antenna height. You can designate a point ID - and receive back an XML file that you can simply drag/drop into your project in TBC, which will then transform the base position and all relative vectors.
It was (and IS) my understanding that OPUS ignores all that receiver, antenna, "HI" stuff in the RINEX Header, and that's why we have to select the Antenna Model, and enter the GRP-to-ARP height when we submit.
I often see the "receiver model" or "antenna model" NOT RECOGNIZED message when running TEQC, but that shouldn't freakout OPUS (I wouldn't think anyway).
I dunno, something is screwy though.
Loyal
Thomas: I don't use OPUS for anything other than a sanity check. But, I was curious as to why no one else has seen this.
Thomas
How about a hint on what drop down menu to find the automated OPUS routine. I have browsed around but haven't found it yet. Didn't see anything in "help" either.
TCC > Trimble Access Services > Data Processing.
Thanks Thomas
That works pretty slick.
Thank you Thomas
One of the processing options is the Canadian Precise Point Positioning Service. Unfortunately the emailed returns do not neatly import into TBC as does the OPUS xml.
A caveat - some corporate networks may block xml files sent as attachments. Ours does as I discovered today. You may have to get IT to give permission for xml attachments from NGS.
No problem! ...and yes - the XML format alters the reference/point ID, but this can be altered in Wordpad farily quickly. For the trade-off in manually converting and calculating the ARP, antenna offset, etc. - this is a pretty cool service. It can only get better from here!