Is there a minimum session length that AS 2.5 requires to process a static vector?
I was tying a subdivision to league corner (1 hour sessions) and just to see if would work I took 2 five minute sessions on a large water meter box AS 2.5 ignored them.
I believe that in the settings you will find a minimum vector time span. I think it defaults to five minutes in which case it probably caused the data to be ignored...just change the setting to something smaller
Shawn
Thanks I found it.
Hi:
A general rule of thumb we recommend for static vector observation times is:
10 minutes+2minutes*distance(km)
So for a 10 km baseline, approximately
30 minutes
--this time would increase somewhat under certain conditions such as obstructions at the ROVER, high ionospheric activity (on long baselines), etc as stated in the product manuals.
With shorter observation times, Solutions may or may not be able to fix the ambiguities.
Minimally constrained and constrained network adjustments with independent vectors are good tools to help verify the quality of the GPS vectors.
Br,
Richard
Thales Navigation Technical Support