Need some help using GNSS Solutions v3.1
I got some kinematic data & base data.
I am able to process it without any problems.
My question is what column do I look at to determine accuracy of
the kinematic point -
Points Tab - Surv_Hor_Conf, Surv_Height_Conf
Vector Tab - Proc_Length_Conf, Proc_DX_Conf,Proc_DY_Conf, Proc_DZ_Conf
Shouldn't the 2 be related?
I am getting points that have an error of 34 in Surv_Hor_Conf/Surv_Height_Conf but confidence level that are less than 1cm in the vector results.
Typically I don't fret too much about statistics for kinematic work. I'm more interested in fixed vs. float. If it's fixed I expect something in the neighborhood of 1cm 68% of the time with 2cm at 95% and the occasional outliers at 3cm.
Without redundancy I don't put much stock in statistics on short occupations.
are you running two bases by chance?
I only ask because I found a glitch with GNSS that doesn't like slant heights coming from a base station. seems to work fine with vertical heights though. The glitch causes a real blow up with multiple vectors to the same point. much like what you are describing. I think I found a work around by manually converting the slant to a vertical and inputing it. Curiously the glitch seems to be fine with a vector going to a station with a slant height, but blows up with a vector coming from a station with a slant height.
Thank you Shawn.
Will do what you suggested. The conversion is just a simple trigonometric function - using the radius of the antenna right?
Slant Height vs Vertical Height
Slant height us to a defined point on the antenna perimeter.
Vertical height is to the base of the female 5/8" threads.
There is a small vertical offset to be included in the calculations. See your particular antenna data.
Paul in PA
Slant Height vs Vertical Height
:good:
I just looked. I'm running v3.71. Version 3.8 is available. You might see if the issues you're seeing are corrected in the newer version. I'm hoping mine are...