I've been using files collected with the R8-3 for submission to OPUS, but need to submit some files collected with the R10 and I'm not 100% certain of the measure up point on the receiver used with the NGS model. Anybody know for sure? Not having much luck finding it on the NGS site. Thought there might be past thread on it but no luck in finding it.
TIA, Willy
Just because I'm paranoid, doesn't mean they aren't out to get me.
Bottom of the receiver. If you're using the QR add 5cm - so the R10 on a 2m fixed height with the quick release is 2.050m.
There was a similar discussion
https://surveyorconnect.com/community/threads/height-values-with-trimble-r10.331242/#post-435570
Thanks guys.
Just because I'm paranoid, doesn't mean they aren't out to get me.
Also remember if you are using the slant measurement to side of the GPS head to calculate the correct height to the bottom of the antenna. Should have all the info on the https://www.ngs.noaa.gov/ANTCAL/&apos ;">NGS antenna data or from the manufacture site to use Pythagorean theorem. It is only a little difference, but isn't that our job?
Scotland, post: 452150, member: 559 wrote: Also remember if you are using the slant measurement to side of the GPS head to calculate the correct height to the bottom of the antenna. Should have all the info on the https://www.ngs.noaa.gov/ANTCAL/&apos ;">NGS antenna data or from the manufacture site to use Pythagorean theorem. It is only a little difference, but isn't that our job?
Thank you Scotland!
Funny timing. I just got done breaking down a 5 hour observation done last week into 1/2 hour segments to submit each separately using the OPUS-RS utility. I'd had some problems with freezing/thawing causing some drift over the point I was observing and wanted to parse out the later affected data. While the horizontal positions only varied by a couple hundreths, the ortho heights ranged from 489.29' to 489.49', or in other words a couple of tenths, all using the same CORS. The quality of the data was excellent. I don't generally get too worked up about the elevations with the type of utility work I'm doing, but given the range in the results, I'm not sure I need to worry about going that extra step of reducing the measure ups.
Just because I'm paranoid, doesn't mean they aren't out to get me.
Williwaw, post: 452156, member: 7066 wrote: Thank you Scotland!
Funny timing. I just got done breaking down a 5 hour observation done last week into 1/2 hour segments to submit each separately using the OPUS-RS utility. I'd had some problems with freezing/thawing causing some drift over the point I was observing and wanted to parse out the later affected data. While the horizontal positions only varied by a couple hundreths, the ortho heights ranged from 489.29' to 489.49', or in other words a couple of tenths, all using the same CORS. The quality of the data was excellent. I don't generally get too worked up about the elevations with the type of utility work I'm doing, but given the range in the results, I'm not sure I need to worry about going that extra step of reducing the measure ups.
As I understand it TBC will take care of that, if you let it know where you measure it to and use the Processing Services pull down.
Williwaw, post: 452133, member: 7066 wrote: ...I'm not 100% certain of the measure up point on the receiver used with the NGS model. Anybody know for sure? Not having much luck finding it on the NGS site.
From the NGS AntCal site, see Trimble antenna model TRMR10.
https://www.ngs.noaa.gov/ANTCAL/
Current NGS/IGS policy is to use a non-detachable point for the ARP.
I just submitted two OPUS files through a TBC job, downloaded the receiver file then sent it to OPUS two different times. The only change I made was to change which measure point I used. One to the lever arm, one to the bottom of antenna. I did no calculations or changes except when I sent it in with the lever arm, then I put in my measurement, Trimble converted everything for me and I got the same number from OPUS for the elevation for each submittal within .001m. If you have TBC it speeds up the process by using the processing services pull down menu.
The options for an OPUS submittal are:
Bottom of antenna mount
Bottom of quick release
Lever of R10 extension
Bottom of V10
Lever of V10 extension
Antenna phase center
You should specify that those are TBC options, in all cases it will convert to the ARP, which is what OPUS REQUIRES. But it is a great feature that TBC will do that.
I wish OPUS would have an option to read the antenna type and HI from the rinex file.
I would think that if you have an R10 you probably have TBC, not sure how to use one without it, everything is so integrated.
I don't know for sure what TBC does to the .T02 file, since I don't send OPUS rinex files I would think TBC doesn't convert it before it sends them, maybe it does, when you get the OPUS report back it does show a rinex file that was used, so it's possible TBC is doing that behind the scenes.
When you measure the HI in the field, just be sure you correctly pick the measure point when you start the base, if you measure the lever arm be sure to pick that on the list of choices and from there it's a seamless process, it takes very little of your time to send it to OPUS.
They incorporated the RINEX conversion utility into TBC about the same time they put in the Processing Services. Now if they'd just add a decimate tool...
Lee D, post: 452399, member: 7971 wrote: They incorporated the RINEX conversion utility into TBC about the same time they put in the Processing Services. Now if they'd just add a decimate tool...
It's a hands off service, no touching!!;)