There is no need to restart the base. Restarting the base was once needed in a localization procedure that corrected an autonomous base position from points with known coordinates. We now have Real Time Position Shift for this instead of using localizations.
Also please post what is not clear in the manual (pages 112 - 120) and I can try to make revisions in the next release of it.
Hi Matt, maybe it's just that the button pushing sequence is easier when separated from the theory and technical explanations. I first shared Shawn Billings writings with folks, which are great for understanding what localizations are and are good for and not. I have a good understanding of what the localization is and what it is and isn't doing. But accomplishing it was a bit murky, not sure I can point to any particular thing but others were having trouble as well. I've had a pretty positive response from my customers (one is laminating the cheat sheet for field crews). I would not want to see less explanation in the manual because it's important folks know more about it than pressing buttons. But, a simple workflow in addition to the long explanation is sometimes useful.
I'm a little confused by your last statement. I thought shift routine was best only used to shift from autonomous to corrected state plane, or differences of only a few meters at most, rather than a local coordinate/state plane conversion?
Which brings up another question; what is proper workflow to tie into old local system, convert those coordinates to state plane, and work the job as state plane from thereon? Would I do a localization and then simply change the design coordinates page from local to state plane?