Nate The Surveyor
Well-Known Member
We have 2 processed base lines to consider.
1.) CORS to Base.
2.) Base to Rover.
In base to Rover, we have Two options.
a.) RTK
b.) PPK (In my head, that is a form of Static)
Then, you can have Cors to Rover Processing. If you like. That too is good.
This works just fine.
But, if you use M-Local, it messes up the above sequence.
Every sideshot from a given base, are called M-Local. No longer can you choose
RTK, PPK, or Cors to Rover.
IF you set your base up for a SHORT time, (On a point with a known SPC Coordinate) Do an M-Local, then, set 2 corners, and your base is only up for 45 mins to an hr, then you can have a problem. You do not want to hold a Poor Base, from Cors.
You do want to HOLD the M-Local coord, for base.
I am not sure of what is the BEST way to fix this.
Another corollary of this, is the ability to "Lock" coordinates. If I work a day on a job, put it down for a week, do other things, come back, and work on it again, I can potentially mess up my coordinates, by pressing one of those buttons, "Yes for all".
When, I had already carefully picked through, and selected PPK for some, RTK for some, etc. I'd like to be able to pick and lock these, both individually, and by DAY. So, I work a day, make all my selections, while I still remember what was going on. And, I can lock them as I go. Then, after all of them are happy, I can lock that day. 2 Locks. If you want to change a "Locked Point" it simply give you a warning, "Previously Locked Point, Override lock?" Y/N And, you can override, and change an individual point.
Another thing, sort of related, is the ability to make _AVG points, and SKIP the previously averaged points.
Sorry, put so many issues together like this, but they are things that can improve things.
Thanks for all you do.
Nate
1.) CORS to Base.
2.) Base to Rover.
In base to Rover, we have Two options.
a.) RTK
b.) PPK (In my head, that is a form of Static)
Then, you can have Cors to Rover Processing. If you like. That too is good.
This works just fine.
But, if you use M-Local, it messes up the above sequence.
Every sideshot from a given base, are called M-Local. No longer can you choose
RTK, PPK, or Cors to Rover.
IF you set your base up for a SHORT time, (On a point with a known SPC Coordinate) Do an M-Local, then, set 2 corners, and your base is only up for 45 mins to an hr, then you can have a problem. You do not want to hold a Poor Base, from Cors.
You do want to HOLD the M-Local coord, for base.
I am not sure of what is the BEST way to fix this.
Another corollary of this, is the ability to "Lock" coordinates. If I work a day on a job, put it down for a week, do other things, come back, and work on it again, I can potentially mess up my coordinates, by pressing one of those buttons, "Yes for all".
When, I had already carefully picked through, and selected PPK for some, RTK for some, etc. I'd like to be able to pick and lock these, both individually, and by DAY. So, I work a day, make all my selections, while I still remember what was going on. And, I can lock them as I go. Then, after all of them are happy, I can lock that day. 2 Locks. If you want to change a "Locked Point" it simply give you a warning, "Previously Locked Point, Override lock?" Y/N And, you can override, and change an individual point.
Another thing, sort of related, is the ability to make _AVG points, and SKIP the previously averaged points.
Sorry, put so many issues together like this, but they are things that can improve things.
Thanks for all you do.
Nate