David M. Simolo
Well-Known Member
Up until about 3-4 weeks ago when I would do an M-Local it would display and utilize all of the surveyed points in the M-Local datum. It seems as though since then it only "shifts" the points that are collected after creating the M-Local relationship. The most apparent reason I know this is the first thing we do when we do a base-rover setup is to set a point. That point will be the last point we locate at the end of the session after point-staking it. Now if I do an M-Local during the course of that setup the initial point will be off by the amount of shifting that M-Local applied. Am I correct in this observation? Am I missing something like a setting that may have changed?
Once I return to the office and do a CORS-Base-Rover processing this all gets resolved in the new solutions for the points.
I am keeping current with the pre-release versions of the software.
Once I return to the office and do a CORS-Base-Rover processing this all gets resolved in the new solutions for the points.
I am keeping current with the pre-release versions of the software.