Did I just get lucky?
I haven't run that many OPUS so far this year. NGS must have just cleaned up the coords on the CORS or something. This is one of the best OPUS solutions I've ever got.
FILE: 54411911.DAT OP1375307496155
NGS OPUS SOLUTION REPORT
========================
All computed coordinate accuracies are listed as peak-to-peak values.
For additional information: http://www.ngs.noaa.gov/OPUS/about.jsp#accuracy
USER: [email protected] DATE: July 31, 2013
RINEX FILE: 5441191a.13o TIME: 21:58:06 UTC
SOFTWARE: page5 1209.04 master52.pl 072313 START: 2013/07/10 00:12:00
EPHEMERIS: igs17483.eph [precise] STOP: 2013/07/10 20:11:00
NAV FILE: brdc1910.13n OBS USED: 48994 / 49521 : 99%
ANT NAME: TRM33429.00+GP NONE # FIXED AMB: 146 / 147 : 99%
ARP HEIGHT: 1.679 OVERALL RMS: 0.010(m)
REF FRAME: NAD_83(2011)(EPOCH:2010.0000) IGS08 (EPOCH:2013.5217)
X: -1798203.308(m) 0.001(m) -1798204.130(m) 0.001(m)
Y: -4580537.244(m) 0.005(m) -4580535.949(m) 0.005(m)
Z: 4047017.479(m) 0.002(m) 4047017.402(m) 0.002(m)
LAT: 39 37 24.47567 0.003(m) 39 37 24.49246 0.003(m)
E LON: 248 33 58.61223 0.002(m) 248 33 58.56032 0.002(m)
W LON: 111 26 1.38777 0.002(m) 111 26 1.43968 0.002(m)
EL HGT: 1796.982(m) 0.003(m) 1796.236(m) 0.003(m)
ORTHO HGT: 1813.791(m) 0.017(m) [NAVD88 (Computed using GEOID12A)]
UTM COORDINATES STATE PLANE COORDINATES
UTM (Zone 12) SPC (4302 UT C)
Northing (Y) [meters] 4386056.782 2143230.590
Easting (X) [meters] 462775.279 505690.433
Convergence [degrees] -0.27660280 0.04245830
Point Scale 0.99961706 0.99990560
Combined Factor 0.99933533 0.99962379
US NATIONAL GRID DESIGNATOR: 12SVJ6277586056(NAD 83)
BASE STATIONS USED
PID DESIGNATION LATITUDE LONGITUDE DISTANCE(m)
DH7098 P086 KENNECOTT1UT2005 CORS ARP N403855.643 W1121655.412 134895.5
AJ2124 PUC1 CARBON COUNTY COU CORS ARP N393557.066 W1104831.329 53756.1
AJ8478 MYT2 MYTON 2 CORS ARP N400609.568 W1100254.602 129949.9
NEAREST NGS PUBLISHED CONTROL POINT
KN0181 T 42 N393724. W1112531. 723.9
That is a great solution. We collected data this week with Trimble 4700 receivers for OPUS post processing as we have in the past. When we submit, it comes back with nothing as the file cannot be read. If we use an R6 or R8 it works fine. Did Trimble hammer us again with a timed clock as they did with post processing in TGO to force us to TBC? Anyone else having OPUS issues this week?
That's a 4700 file but about 3 weeks ago. I sure hope they ain't going to quit working as I don't have anything else.
>...This is one of the best OPUS solutions I've ever got...
20 hours of data and a precise ephemeris. A good part of the observation before the sun came up probably helped, too.
Was the unit set up outside of LR Day, Inc. world headquarters?
This is my geodetic corner record documentation. This one for section corner put back from some survey ties from 1987 in a guys front yard. I wouldn't call it the best observation conditions. The house was about 30 feet north, quite a few trees about but not real close. Power lines above and large tress SE across the street would have messed with signals up to maybe 25 degrees. The tripod was in the lawn but I set it as good as I could.
Usually my solutions are messed up more than that because the CORS coordinates are not precisely good with each other. Generally there is about 3 times this much error baked into the cake to begin with.
Sister OPUS files
Better than normal but not as lucky. So the good solution was probably just luck. I'm going to use it though, and these tie outs also. Seems OPUS picked different CORS.
FILE: 54421911.DAT OP1375312379870
NGS OPUS SOLUTION REPORT
========================
All computed coordinate accuracies are listed as peak-to-peak values.
For additional information: http://www.ngs.noaa.gov/OPUS/about.jsp#accuracy
USER: [email protected] DATE: July 31, 2013
RINEX FILE: 5442191n.13o TIME: 23:19:36 UTC
SOFTWARE: page5 1209.04 master12.pl 072313 START: 2013/07/10 13:58:00
EPHEMERIS: igs17483.eph [precise] STOP: 2013/07/10 20:03:00
NAV FILE: brdc1910.13n OBS USED: 15150 / 15277 : 99%
ANT NAME: TRM41249.00 NONE # FIXED AMB: 56 / 56 : 100%
ARP HEIGHT: 1.277 OVERALL RMS: 0.010(m)
REF FRAME: NAD_83(2011)(EPOCH:2010.0000) IGS08 (EPOCH:2013.5225)
X: -1797438.609(m) 0.004(m) -1797439.431(m) 0.004(m)
Y: -4580851.873(m) 0.005(m) -4580850.578(m) 0.005(m)
Z: 4047026.056(m) 0.007(m) 4047025.979(m) 0.007(m)
LAT: 39 37 24.41076 0.006(m) 39 37 24.42755 0.006(m)
E LON: 248 34 33.26805 0.002(m) 248 34 33.21615 0.002(m)
W LON: 111 25 26.73195 0.002(m) 111 25 26.78385 0.002(m)
EL HGT: 1812.850(m) 0.008(m) 1812.103(m) 0.008(m)
ORTHO HGT: 1829.614(m) 0.021(m) [NAVD88 (Computed using GEOID12A)]
UTM COORDINATES STATE PLANE COORDINATES
UTM (Zone 12) SPC (4302 UT C)
Northing (Y) [meters] 4386050.837 2143229.245
Easting (X) [meters] 463601.495 506516.908
Convergence [degrees] -0.27046322 0.04862491
Point Scale 0.99961631 0.99990560
Combined Factor 0.99933209 0.99962130
US NATIONAL GRID DESIGNATOR: 12SVJ6360186050(NAD 83)
BASE STATIONS USED
PID DESIGNATION LATITUDE LONGITUDE DISTANCE(m)
AF9633 RBUT RED BUTTE CORS ARP N404651.807 W1114831.490 132679.4
AJ8478 MYT2 MYTON 2 CORS ARP N400609.568 W1100254.602 129199.8
DH3864 P105 DELTAMUNI_UT2004 CORS ARP N392315.140 W1123014.669 96531.4
NEAREST NGS PUBLISHED CONTROL POINT
KN0181 T 42 N393724. W1112531. 102.4
FILE: 54421901.DAT OP1375312310798
NGS OPUS SOLUTION REPORT
========================
All computed coordinate accuracies are listed as peak-to-peak values.
For additional information: http://www.ngs.noaa.gov/OPUS/about.jsp#accuracy
USER: [email protected] DATE: July 31, 2013
RINEX FILE: 5442190v.13o TIME: 23:18:06 UTC
SOFTWARE: page5 1209.04 master50.pl 072313 START: 2013/07/09 21:07:00
EPHEMERIS: igs17482.eph [precise] STOP: 2013/07/10 13:29:00
NAV FILE: brdc1900.13n OBS USED: 37537 / 38451 : 98%
ANT NAME: TRM41249.00 NONE # FIXED AMB: 141 / 144 : 98%
ARP HEIGHT: 1.493 OVERALL RMS: 0.013(m)
REF FRAME: NAD_83(2011)(EPOCH:2010.0000) IGS08 (EPOCH:2013.5212)
X: -1797936.446(m) 0.005(m) -1797937.268(m) 0.005(m)
Y: -4581728.605(m) 0.008(m) -4581727.310(m) 0.008(m)
Z: 4045816.141(m) 0.001(m) 4045816.064(m) 0.001(m)
LAT: 39 36 33.57062 0.005(m) 39 36 33.58740 0.005(m)
E LON: 248 34 27.26705 0.005(m) 248 34 27.21516 0.005(m)
W LON: 111 25 32.73295 0.005(m) 111 25 32.78484 0.005(m)
EL HGT: 1810.143(m) 0.008(m) 1809.397(m) 0.008(m)
ORTHO HGT: 1826.941(m) 0.021(m) [NAVD88 (Computed using GEOID12A)]
UTM COORDINATES STATE PLANE COORDINATES
UTM (Zone 12) SPC (4302 UT C)
Northing (Y) [meters] 4384484.176 2141661.317
Easting (X) [meters] 463450.999 506375.097
Convergence [degrees] -0.27144549 0.04755710
Point Scale 0.99961645 0.99990654
Combined Factor 0.99933265 0.99962266
US NATIONAL GRID DESIGNATOR: 12SVJ6345084484(NAD 83)
BASE STATIONS USED
PID DESIGNATION LATITUDE LONGITUDE DISTANCE(m)
DH7098 P086 KENNECOTT1UT2005 CORS ARP N403855.643 W1121655.412 136589.2
AJ2124 PUC1 CARBON COUNTY COU CORS ARP N393557.066 W1104831.329 53022.1
AF9633 RBUT RED BUTTE CORS ARP N404651.807 W1114831.490 134165.9
I ran some GPS Sessions two weeks ago. I still haven't been able ot get OPUS to process the data. I keep getting the message that there are no base stations withing 250km of my points. I get the aborting message. I must have broken it here in Georgia. i was able to process through Trimble and get my ccords.