James Barnett

What is the processing difference between using Rinex and T04?

Discussion created by James Barnett on Oct 11, 2019
Latest reply on Oct 21, 2019 by James Barnett

When I process a static directly through the Trimble Processor website I get different results than converting to a RINEX and sending it to OPUS. Why is the processing handled differently?

 

RINEX FILE

FILE: 03252810.19o OP1570811342514

 

                              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: jbarnett@ceieng.com                     DATE: October 11, 2019

RINEX FILE: 0325281r.19o                            TIME: 16:49:58 UTC

 

 

  SOFTWARE: page5  1801.18 master44.pl 160321      START: 2019/10/08  17:25:00

 EPHEMERIS: igr20742.eph [rapid]                    STOP: 2019/10/09  00:56:00

  NAV FILE: brdc2810.19n                        OBS USED:  3200 /  3377   :  95%

  ANT NAME: TRMR10-2        NONE             # FIXED AMB:    10 /    16   :  63%

ARP HEIGHT: 2.05                             OVERALL RMS: 0.014(m)

 

 

 REF FRAME: NAD_83(2011)(EPOCH:2010.0000)              ITRF2014 (EPOCH:2019.7694)

     

         X:      -799130.708(m)   0.513(m)           -799131.550(m)   0.513(m)

         Y:     -5492605.799(m)   0.267(m)          -5492604.333(m)   0.267(m)

         Z:      3132114.000(m)   0.272(m)           3132113.798(m)   0.272(m)

 

       LAT:   29 36  3.82637      0.122(m)        29 36  3.84199      0.122(m)

     E LON:  261 43 19.20180      0.544(m)       261 43 19.16299      0.544(m)

     W LON:   98 16 40.79820      0.544(m)        98 16 40.83701      0.544(m)

    EL HGT:          231.086(m)   0.336(m)               229.831(m)   0.336(m)

 ORTHO HGT:          256.851(m)   0.339(m) [NAVD88 (Computed using GEOID18)]

 

 

DIRECT PROCESSING FROM T04

 FILE: 60001 TR4070254409681

 

                              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: jbarnett@ceieng.com                     DATE: October 11, 2019

RINEX FILE: 6000281r.19o                            TIME: 16:22:36 UTC

 

 

  SOFTWARE: page5  1801.18 master60.pl 160321      START: 2019/10/08  17:25:00

 EPHEMERIS: igr20742.eph [rapid]                    STOP: 2019/10/09  00:56:00

  NAV FILE: brdc2810.19n                        OBS USED: 16327 / 17598   :  93%

  ANT NAME: TRMR10-2        NONE             # FIXED AMB:    90 /    99   :  91%

ARP HEIGHT: 2.05                             OVERALL RMS: 0.018(m)

 

 

 REF FRAME: NAD_83(2011)(EPOCH:2010.0000)              ITRF2014 (EPOCH:2019.7696)

     

         X:      -799130.655(m)   0.011(m)           -799131.497(m)   0.011(m)

         Y:     -5492605.860(m)   0.020(m)          -5492604.394(m)   0.020(m)

         Z:      3132114.060(m)   0.006(m)           3132113.858(m)   0.006(m)

 

       LAT:   29 36  3.82723      0.011(m)        29 36  3.84286      0.011(m)

     E LON:  261 43 19.20407      0.008(m)       261 43 19.16526      0.008(m)

     W LON:   98 16 40.79593      0.008(m)        98 16 40.83474      0.008(m)

    EL HGT:          231.162(m)   0.019(m)               229.906(m)   0.019(m)

 ORTHO HGT:          256.927(m)   0.048(m) [NAVD88 (Computed using GEOID18)]

Outcomes