I think it is more critical to obtain the relationship of the sensors baseline to the axis of the vessel
Yes, that is definitely one thing the client has said is required.
Thanks for taking the time.
I thought maybe the "propagation of errors" formula could be arranged to evaluate how coordinate uncertainty translates into azimuth uncertainty, but I was overthinking I think.
Without baseline processing software, I knew single point positioning of each point would only get me +/- 10mm. However I seem to have managed to overcome the difficulties I was having with GNSS Solutions and will now use that.
What was the GNSS hang up? Just curious. (It’s my only baseline processor at present.)
and it should be easy enough to make 2 observations, even at the obscene 1 hr ea.
i make no accommodation for 64 bit win10. I loaded it and it worked right off. I may not rennet the ins and outs right off, but I never had to abort.
I'm going to step onto the nautical gang plank here and say FWIW, that heading is the direction vessel is pointing, and that's not necessarily the direction the vessel is going.
Too embarrassed to say....well ok...I wasn't including the "n" file...
😕
It's been several years where single point positioning thru CSRS-PPP has been all I've needed - and for that you don't need to supply the "n" file as they use their own precise orbit and clock files.
Your comments encouraged me to have another go, so I appreciate that!
I'm going to step onto the nautical gang plank here and say FWIW, that heading is the direction vessel is pointing, and that's not necessarily the direction the vessel is going.
Yes, I mis-spoke.
?ÿ
glad to year that. I find that with seldom, or infrequent use of GNSS, I’m trial and error for a bit, every time. And in my scenario, OPUS is addictive and my neighborhood is replete with CORS. But when EDM won’t reach, and opus not good enough, GNSS baseline it is.
then there’s the tragic mistake of using grid az instead of geo az because the adjustment was SOC or UTM. There’s few good stories of bad “true north”. So unadjusted, normal section az, from phase differential baseline is pure and unambiguous.
Yes - most surveying mistakes are bad but sending a boat to it's doom with the wrong north is a whole other level of anguish :silly:
Sigh, not my day.?ÿ I took the 10 mm as a sideways error, but if it is the radial error at some confidence, the sideways error would be 7 mm, so was off by sqrt(2).
we had to as-built an antenna array. Deep space monitoring NASA/DoD many dollar antenna. Very accurately and precisely oriented to North by Polaris.
Just not the right north. They built it to grid N, not true N.
@larry-scott Larry can you tell us why Grid North?
JOHN NOLTON
not the correct North. It was a costly mistake.
And adjustment programs often (1989) routinely output only grid and the difference was either not understood, or not correctly outlined in the instructions. They only knew something was wrong when they turned it on.
and gps was not approved for the task, only Polaris.
Yeah, an accident.
Just to wrap things up and prove what a great resource RPLS Today is - here is a thread from 2016, referencing a thread from 2012, that already covered most of my questions.
?ÿ
https://surveyorconnect.com/community/gnss-geodesy/2012-thread-geodetic-north-line/
?ÿ
I find googling?ÿ a topic and adding "RPLS today" to the query, works better than using the built in search function. 🙂 ?ÿ
?ÿ
What you said is really true. I wonder if Google is blocking other search engines... (Pure speculation).
N
Well I assumed the search function within RPLS today is built into the program - not a general search engine as such, but I don't know.
Actually, at the moment, if I use the built in search, no matter what I search, I get 7 pages of Wendell's Geodimeter for sale from 10 years ago! 😆