We have a Height Modernization Survey Station at the office known as "SHOP" (PID AB4093).
The position according to the current NGS datasheet is:
40°49'11.44909"N 096°43'36.33890"W NAD83(2011) 352.16m Ortho height NAVD88.
On November 19 & 20, I did two static sessions of three hours each using the Trimble R8 and Sokkia GSR2700ISX receivers. The data was sent to OPUS with the following solutions.
Trimble R8: 40°49'11.44920"N 096°43'36.33911"W 352.136m
Sokkia GSR2700ISX: 40°49'11.44921"N 096°43'36.33899W 352.178m
In terms of ground distance, the Trimble and Sokkia differ by 0.0010' (feet) in latitude and 0.0092' (feet) in longitude.
The Trimble R8 differs from the NGS published position by 0.0111' (feet) in latitude and 0.0162' (feet) in longitude.
The Sokkia GSR2700ISX differs from the NGS published position by 0.0121' (feet) in latitude and 0.0069' (feet) in longitude.
Looks to me like you'd better go back to the drawing board and start over. Kind of sloppy don't you think?! 🙂 😉
One of the old school engineers here was questioning the accuracy of using GPS. This pretty much silenced him. 🙂
WD
What will really amaze you is to send the R8 data to the Trimble online RTX processor. This is a Precise Point Position solution, using no nearby CORS. I have used it in a production mode with 45 minute sessions with great results (cm level).
I am currently doing some more testing to see how well it works with 30 minute, 45 minute, 60 minute data sets. So far I have done the 30 minute tests, and found that it mostly works (it is GPS and Glonass data), but not always, occasionally it fails to get a solution. I have been collecting hourly files on my pedestal since last night, and will send a bunch of those when done.
They recommend 60 minutes minimum, but I have had no problems so far with 45 minutes.