Here is a comparison for those curious:
FILE: 1 TR8272051600742
?ÿ
?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ NGS OPUS SOLUTION REPORT
?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ ========================
?ÿ
All computed coordinate accuracies are listed as peak-to-peak values.
For additional information: https://www.ngs.noaa.gov/OPUS/about.jsp#accuracy
?ÿ
?ÿ?ÿ?ÿ?ÿ?ÿ USER: ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ DATE: December 19, 2018
RINEX FILE: 1___351q.18o?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ TIME: 14:43:10 UTC
?ÿ
?ÿ
?ÿ SOFTWARE: page5?ÿ 1603.24 master93.pl 160321?ÿ?ÿ?ÿ?ÿ?ÿ START: 2018/12/17?ÿ 16:47:00
?ÿEPHEMERIS: igr20321.eph [rapid]?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ STOP: 2018/12/17?ÿ 20:02:00
?ÿ NAV FILE: brdc3510.18n?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ OBS USED:?ÿ 7594 /?ÿ 9208?ÿ?ÿ :?ÿ 82%
?ÿ ANT NAME: TRMR10?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ NONE?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ # FIXED AMB:?ÿ?ÿ?ÿ 51 /?ÿ?ÿ?ÿ 67?ÿ?ÿ :?ÿ 76%
ARP HEIGHT: 1.7942?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ OVERALL RMS: 0.016(m)
?ÿ
?ÿ
?ÿREF FRAME: NAD_83(2011)(EPOCH:2010.0000)?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ IGS08 (EPOCH:2018.9610)
?ÿ
?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ X:?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ -40677.331(m)?ÿ?ÿ 0.011(m) ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ-40678.218(m)?ÿ?ÿ 0.011(m)
?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ Y:?ÿ?ÿ?ÿ?ÿ -4895576.300(m)?ÿ?ÿ 0.018(m)?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ -4895574.922(m)?ÿ?ÿ 0.018(m)
?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ Z:?ÿ?ÿ?ÿ?ÿ?ÿ 4074523.530(m)?ÿ?ÿ 0.019(m)?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ 4074523.430(m)?ÿ?ÿ 0.019(m)
?ÿ
?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ LAT:?ÿ?ÿ 39 57 30.70786?ÿ?ÿ?ÿ?ÿ?ÿ 0.016(m)?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ 39 57 30.73392?ÿ?ÿ?ÿ?ÿ?ÿ 0.016(m)
?ÿ?ÿ?ÿ?ÿ E LON:?ÿ 269 31 26.18569?ÿ?ÿ?ÿ?ÿ?ÿ 0.011(m)?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ 269 31 26.14786?ÿ?ÿ?ÿ?ÿ?ÿ 0.011(m)
?ÿ?ÿ?ÿ?ÿ W LON:?ÿ?ÿ 90 28 33.81431?ÿ?ÿ?ÿ?ÿ?ÿ 0.011(m)?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ 90 28 33.85214?ÿ?ÿ?ÿ?ÿ?ÿ 0.011(m)
?ÿ?ÿ?ÿ EL HGT:?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ 103.315(m)?ÿ?ÿ 0.021(m)?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ 102.200(m)?ÿ?ÿ 0.021(m)
?ÿORTHO HGT:?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ 136.246(m)?ÿ?ÿ 0.028(m) [NAVD88 (Computed using GEOID12B)]
?ÿ
?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ UTM COORDINATES?ÿ?ÿ?ÿ STATE PLANE COORDINATES
?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ UTM (Zone 15)?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ SPC (1202 IL W)
Northing (Y) [meters]?ÿ?ÿ?ÿ?ÿ 4426205.117?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ 365429.312
Easting (X)?ÿ [meters]?ÿ?ÿ?ÿ?ÿ?ÿ 715585.424?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ 673565.307
Convergence?ÿ [degrees]?ÿ?ÿ?ÿ?ÿ 1.62158056?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ -0.19870278
Point Scale?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ 1.00017220?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ 0.99994978
Combined Factor?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ 1.00015599?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ 0.99993357
?ÿ
US NATIONAL GRID DESIGNATOR: 15SYE1558526205(NAD 83)
?ÿ
?ÿ
?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ BASE STATIONS USED
PID?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ DESIGNATION?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ LATITUDE?ÿ?ÿ?ÿ LONGITUDE DISTANCE(m)
DM4120 MOHL MODOT HANNIBAL CORS ARP?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ N394143.571 W0912405.004?ÿ?ÿ 84431.7
DN6079 MOCN MODOT CANTON CORS ARP?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ N400836.688 W0913237.667?ÿ?ÿ 93397.5
DN5826 MOEB MODOT ELSBERRY CORS ARP?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ N391044.087 W0904715.539?ÿ?ÿ 90605.0
?ÿ
?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ NEAREST NGS PUBLISHED CONTROL POINT
KC0041?ÿ?ÿ?ÿ?ÿ?ÿ N 255?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ N395712.000 W0902900.000?ÿ?ÿ?ÿ?ÿ 848.1
?ÿ
This position and the above vector components were computed without any knowledge by the National Geodetic Survey regarding the equipment or field operating procedures used.
?ÿ
RTX:
Post-Processing Service Based on RTX Technology
TrimbleRTX.com
Contributor:?ÿ
Reference Name: 05223510.T02
Upload Date: 01/02/2019 14:13:02 UTC
Report Time Frame:
Start Time: 12/17/2018 16:47:29 UTC
End Time: 12/17/2018 20:02:16 UTC
Observation File Type(s): T02
Observation File(s): 05223510.T02
Antenna:
Name: TRMR10 NONE
Height: 1.794 m
Reference: Bottom of antenna mount
Receiver Name: TRIMBLE R10
Coordinate Systems: NAD83-2011 & ITRF2014
Tectonic Plate: North America
Tectonic Plate Model: MORVEL56
Processing Interval: 10 s
Statistics
# Total Obs # Usable Obs # Used Obs Percent
11688 1168 1169 100
Used Satellites
# Total Satellites: 38
GPS: G01 G03 G08 G10 G11 G12 G14 G15 G18 G20 G21 G22 G24 G25 G26 G27 G31
G32
GLONASS: R01 R07 R08 R09 R10 R11 R16 R21 R22 R23 R24
Galileo: E02 E07 E08 E12 E19 E21 E26 E27 E30
Processing Results
NAD83-2011 at Epoch 2010.0
Coordinate Value ?
X -40677.327 m 0.003 m
Y -4895576.272 m 0.009 m
Z 4074523.547 m 0.007 m
Latitude 39?ø 57' 30.70887" N 0.004 m
Longitude 90?ø 28' 33.81415" W 0.003 m
El. Height 103.304 m 0.011 m
ITRF2014 at Epoch 2018.96
Coordinate Value ?
X -40678.225 m 0.003 m
Y -4895574.914 m 0.009 m
Z 4074523.424 m 0.007 m
Latitude 39?ø 57' 30.73393" N 0.004 m
Longitude 90?ø 28' 33.85248" W 0.003 m
El. Height 102.190 m 0.011 m
Report Information
Trimble RTX Solution ID: 19166033
Solution Type: Static
Software Version: 6.1.4.17185
Creation Date: 01/02/2019 14:13:47 UTC
Disclaimer
Trimble Navigation Limited does not guarantee availability, reliability, and performance of the current RTX Post-Processing service and
accepts no legal liability arising from, or connected to, the use of information on this document or use of this service.
Delta N - 0.013'
Delta E - 0.092'
Delta Z - 0.036'
From where?
Paul in PA
Your mileage may vary, but I pretty much always see about a 0.1'?ÿ from the OPUS 2011 realization and the RTX 2018.
They usually "agree" rather consistently, but RTX seems to obtain better precision when compared to terrestrial data.
This is on a point we set up on before Christmas and I just ran it through RTX since OPUS is down.?ÿ
?ÿ
I assume you are asking where? Near Beardstown, IL
Inverse is just a direct when converted to USFT NAD_83 2011
This is on a point we set up on before Christmas and I just ran it through RTX since OPUS is down.?ÿ
?ÿ
I assume you are asking where? Near Beardstown, IL
Inverse is just a direct when converted to USFT NAD_83 2011
From what CORS plus what ephemeris was used?
Paul in PA
Might want to check your math, using the NAD83 values I get deltas of 0.102'N, 0.013'E, 0.036'EL.
The base stations used for the OPUS are listed in the report above. RTX does not list the stations used in the solution. Same for Ephemeris.?ÿ
I did no manual manipulations, just sent it off to both providers.?ÿ?ÿ
Opus
IGS08?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ ?ÿLat 30.73392", Long 33.85214"?ÿ?ÿ?ÿ?ÿ?ÿ ?ÿNAD83 Lat 30.70786", Long 33.81431"
RTX
ITRF2014?ÿ Lat 30.73393", Long 33.85248"?ÿ?ÿ?ÿ?ÿ?ÿ ?ÿNAD83 Lat 30.70887", Long 33.81415"
?ÿ
The OPUS IGS08 and the RTX ITRF2018 numbers are very, very close, yet the RTX NAD Latitude is about 0.1' north of the OPUS Latitude, almost no difference in the Longitude.
?ÿ
40677.331*39.37/12=133455.543 (OPUS)
40677.327*39.37/12=133455.530 (RTX)
?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ N 0.013
4895576.300*39.37/12=16061569.911 (OPUS)
4895576.272*39.37/12=16061569.819 (RTX)
?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿ ?ÿE?ÿ ?ÿ0.092
These are just the ECEF coordinates - since they are both listed on the report, I grabbed those for comparison. I didn't convert the Lat/Long
But when convert the LAT/LONG?ÿ I agree
RTX
1198912.772?ÿ ?ÿ ?ÿ ?ÿ 0.102
2209855.523
OPUS
1198912.670
2209855.510?ÿ ?ÿ ?ÿ ?ÿ 0.013
I think that Trimble is using the 14-parameter transformation for ITRF to NAD83, whereas NGS uses HTDP (Horizontal Time Dependent Transformation). I just put the RTX ITRF position in for the point and converted it to NAD83 using HTDP and came up with:
Lat: 39?ø57'30.70790" N
Lon: 90?ø28'33.81428" W
This differs from the OPUS solution by only 0.003'.?ÿ
The lack of HTDP in transformations is the biggest problem with finding OPUS replacements, though there are some that do provide HTDP as part of their solution.
?ÿ
Someone commented that RTX did not report orthometric heights. I am relieved to see that it does report ellipsoid heights. I have the capacity, through Star*Net, to compute the orthometric from that.?ÿ ?ÿ
I'm not loving the RTX report formatting. It could use some work. Wouldn't take much effort to improve it a lot. A listing of the CORS employed would be a great addition.?ÿ
I'm not sure that RTX uses CORS stations in the same manner that OPUS does. If I'm not mistaken - and I'm sure Trimble has a white paper on this somewhere - RTX is using Precise Point Positioning. As I understand it, this uses States Space Representation, which is a different processing approach. SSP calculates the error states?ÿ- clock error, orbital error, ionospheric and tropospheric biases - and applies them to the observations taken by a single receiver. OPUS uses observations from multiple receivers to calculate baselines in order to derive a coordinate.
"Trimble is using the 14-parameter transformation for ITRF to NAD83, whereas NGS uses HTDP (Horizontal Time Dependent Transformation)"?ÿ
That makes my head hurt!
Here you go. You can read it and send me the cliff notes in English
https://www.trimble.com/positioning-services/pdf/WhitePaper_RTX_Fast.pdf
?ÿ
RTX and OPUS are both representing Epoch 2010.00. Shawn are you saying that OPUS uses HTDP to derive NAD83 from the IGS?ÿsolution whereas Trimble may be using a fixed 14 parameter transformation? I see that the IGS epoch on the OPUS is 2018.9610. It seems to me that if this is the case it would be necessary to recalculate those 14 parameters on occasion.
Some more...in case anyone is having trouble sleeping
?ÿ
The 14-parameter transformation is a standard seven-parameter Helmert transformation that also adds time to each of the seven parameters. The seven parameters are translation in X, Y, and Z; rotation around X-axis, Y-axis, and Z-axis; and scale. Add velocities to each of those parameters and you have effectively doubled them to 14. This method is an affine transformation, which means that the proportions of the geometry remains the same before and after transformation (a square still looks like a square) even though the position, rotation and size may change. The 14-parameter transformation treats the entire North American plate as homogenous, when in reality points move at different velocities across the plate. HTDP is not affine. The square may not look like a square after an HTDP transformation, because the corners of the square are not moving in the same direction at the same speed. NGS uses the CORS network as a basis for determining how local areas are moving rather than treating them all as a single unit. This produces the most robust transformation of points from ITRF to NAD83, as points in Illinois will not have moved throughout the years the same as points in California or in Florida. HTDP is not easily implemented, certainly not as easy as the more simplistic 14-parameter transformation.?ÿ
RTX and OPUS are both representing Epoch 2010.00. Shawn are you saying that OPUS uses HTDP to derive NAD83 from the IGS?ÿsolution whereas Trimble may be using a fixed 14 parameter transformation? I see that the IGS epoch on the OPUS is 2018.9610. It seems to me that if this is the case it would be necessary to recalculate those 14 parameters on occasion.
It certainly appears to be the case, Lee, that RTX is using the 14-parameter transformation.?ÿ
Part of the problem is that the 14 parameters treat the entire plate as a monolith when in fact points move differently across the continent. But you are correct that the 14 parameters need to be refigured. The current transformation applies the rotations from the center of the Earth. The new 2022 reference frame is based on a rotation point that is not Earth-centered. I suspect that this change to a Euler pole will remove a lot of the disparity in the apparent movements of points on the North American plate.?ÿ
