Shut down my L1/L2 receiver down at 5:08 local time and set up on my OPUS-RS point to locate a concrete monument, pipe in a tree/stone row, a go West traverse point and shoot the location of where a concrete monument used to be. As I am picking up the farm owner walks up and I take him into the swampy area to show him there is no concrete monument to be found. He swears it was there and I am not particularly worried because at the intersection of two stone rows is a 4'x2.5' rock that has not moved in 200+ years. This is 90 acre farm survey (compass and perches description) with 1 lot deep subdivisions on 3 sides, so there are a lot of reasons to agree with everyone else. Goal one is to monument the easterly frontage, a 5 acre parcel to north owned by a brother, concrete monuments at rear, nada along road, a 4 acre field exception to south, 1894, and a 70'x150' lot in the middle excepted out in 3 parcels (last in 1897). So far I've located 4 concrete monuments, some corner and line pipes and 2 set stones besides the big one. More set stones, line and corner pipes to come. Goal 2 is the West lines, with either the farm or abutting lots crossing a considerable creek. There is considerable terrain and wooded areas exceed farmable area.
Today's job was to GPS 7 points tying in open traverses to abutting lot frontage areas and to jump a swampy area without clearing a traverse line. The OPUS base point at the farm group ran 3 hr. and 12 min while I reconned rear lot lines and jumped 3 ProMark 2s around 5 points, the last L1 jump was to a pipe under canopy, let that cook for 2.5 hours. The OPUS-RS point in the open field ran for 1 hr. 21 minutes while I was in and out to the missing concrete monument. Right now I have 7 monuments, tied in only by GPS. An unshot pipe is about 60' West of my go West traverse point and from there I am heading into the woods towards the creek. On the South side I have multiple traverse points to jog around the field to the woods and creek. My aim is to get into the woods and pull any traverse points in the fields. Lime was applied Thursday and the clover is greening up in a hurry. I don't want to be driving over a man's livelihood or ruining his equipment. Until I get into the woods I do not know if I will close my traverse along the West line, or jump the creek and the lots and traverse up the road. Before then I will add 2, maybe 3, GPS points along that road. It is much easier to get somewhere when you know exactly where you are going.
Anyway this thread was supposed to be about OPUS and OPUS-RS. My OPUS base point came back less than 3 minutes after submitting. OPUS used 2 out of the 3 nearest CORS , Lat 0.002m, Lon 0.003m, 83% of observations used and 95% fixed ambiguities. Not much more you can do, so we are good to go. What came next was a surprise, as I was really not expecting an OPUS-RS solution 2 hours after GPS midnight, but come it did 4 minutes after the OPUS. OPUS-RS did not use any of the OPUS CORS. What I got was Lat & Lon 0.005, 88% of observations used from get this, 5 New York State CORS, 1 from Connecticut, 1 from South Jersey, 1 from Delaware and the only PA CORS was in Towanda, farther away than any of the other 8. I will resubmit it on Monday, just to see how much it may move, but all I can say tonight, OOPS, this morning is WOW!
Paul, very happy in PA
I resubmitted today because I realized I had input wrong antenna height last night.
Never before saw an zero estimated error?
FILE: P858086A.16O OP1459103762284
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: March 27, 2016
RINEX FILE: p858086q.16o TIME: 18:36:31 UTC
SOFTWARE: page5 1209.04 master90.pl 022814 START: 2016/03/26 16:18:00
EPHEMERIS: igr18896.eph [rapid] STOP: 2016/03/26 19:30:00
NAV FILE: brdc0860.16n OBS USED: 6666 / 8029 : 83%
ANT NAME: ASH700700.B NONE # FIXED AMB: 62 / 65 : 95%
ARP HEIGHT: 2.08 OVERALL RMS: 0.017(m)
REF FRAME: NAD_83(2011)(EPOCH:2010.0000) IGS08 (EPOCH:2016.2343)
X: 1233663.539(m) 0.001(m) 1233662.678(m) 0.001(m)
Y: -4668346.409(m) 0.004(m) -4668344.979(m) 0.004(m)
Z: 4153499.032(m) 0.005(m) 4153498.989(m) 0.005(m)
LAT: 40 53 31.33469 0.002(m) 40 53 31.36764 0.002(m)
E LON: 284 48 9.63174 0.000(m) 284 48 9.61179 0.000(m)
W LON: 75 11 50.36826 0.000(m) 75 11 50.38821 0.000(m)
EL HGT: 201.438(m) 0.006(m) 200.199(m) 0.006(m)
ORTHO HGT: 234.934(m) 0.016(m) [NAVD88 (Computed using GEOID12B)]
UTM COORDINATES STATE PLANE COORDINATES
UTM (Zone 18) SPC (3702 PA S)
Northing (Y) [meters] 4526791.041 176183.619
Easting (X) [meters] 483377.652 815087.594
Convergence [degrees] -0.12917598 1.65615837
Point Scale 0.99960340 0.99998912
Combined Factor 0.99957182 0.99995752
US NATIONAL GRID DESIGNATOR: 18TVL8337726791(NAD 83)
BASE STATIONS USED
PID DESIGNATION LATITUDE LONGITUDE DISTANCE(m)
DJ8947 PAMS STROUDSBURG CORS ARP N405944.024 W0751503.835 12355.7
DL6296 LUMT LEHIGH UNIVERSITY CORS ARP N403605.748 W0752127.133 34977.7
DK4430 NJHC HUNTERDON COUNTY CORS ARP N403005.804 W0745404.015 50066.1
NEAREST NGS PUBLISHED CONTROL POINT
KV1433 570=88 DLWRR N405258. W0751105. 1478.3
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.
Paul in PA
Paul in PA, post: 364346, member: 236 wrote: I resubmitted today because I realized I had input wrong antenna height last night.
Never before saw an zero estimated error?
FILE: P858086A.16O OP1459103762284
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: March 27, 2016
RINEX FILE: p858086q.16o TIME: 18:36:31 UTCSOFTWARE: page5 1209.04 master90.pl 022814 START: 2016/03/26 16:18:00
EPHEMERIS: igr18896.eph [rapid] STOP: 2016/03/26 19:30:00
NAV FILE: brdc0860.16n OBS USED: 6666 / 8029 : 83%
ANT NAME: ASH700700.B NONE # FIXED AMB: 62 / 65 : 95%
ARP HEIGHT: 2.08 OVERALL RMS: 0.017(m)REF FRAME: NAD_83(2011)(EPOCH:2010.0000) IGS08 (EPOCH:2016.2343)
X: 1233663.539(m) 0.001(m) 1233662.678(m) 0.001(m)
Y: -4668346.409(m) 0.004(m) -4668344.979(m) 0.004(m)
Z: 4153499.032(m) 0.005(m) 4153498.989(m) 0.005(m)
LAT: 40 53 31.33469 0.002(m) 40 53 31.36764 0.002(m)
E LON: 284 48 9.63174 0.000(m) 284 48 9.61179 0.000(m)
W LON: 75 11 50.36826 0.000(m) 75 11 50.38821 0.000(m)
EL HGT: 201.438(m) 0.006(m) 200.199(m) 0.006(m)
ORTHO HGT: 234.934(m) 0.016(m) [NAVD88 (Computed using GEOID12B)]
UTM COORDINATES STATE PLANE COORDINATES
UTM (Zone 18) SPC (3702 PA S)
Northing (Y) [meters] 4526791.041 176183.619
Easting (X) [meters] 483377.652 815087.594
Convergence [degrees] -0.12917598 1.65615837
Point Scale 0.99960340 0.99998912
Combined Factor 0.99957182 0.99995752
US NATIONAL GRID DESIGNATOR: 18TVL8337726791(NAD 83)BASE STATIONS USED
PID DESIGNATION LATITUDE LONGITUDE DISTANCE(m)
DJ8947 PAMS STROUDSBURG CORS ARP N405944.024 W0751503.835 12355.7
DL6296 LUMT LEHIGH UNIVERSITY CORS ARP N403605.748 W0752127.133 34977.7
DK4430 NJHC HUNTERDON COUNTY CORS ARP N403005.804 W0745404.015 50066.1
NEAREST NGS PUBLISHED CONTROL POINT
KV1433 570=88 DLWRR N405258. W0751105. 1478.3
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.Paul in PA
Ya mean zero "peak-peak."
It happens from time to time, but NOT very often.
Sure looks a KEEPER.
Loyal
If you roll 3 dice, about one time in 36 they will all come up with the same number. The pk-pk values in the report are somewhat analogous, being expressed in millimeter increments. If the rms spread of random errors is a very few mm, than it isn't surprising that sometimes they all fall in the same increment.