Real time position shift

[Darren Clemons]

I haven't, up until last week, utilized the real time position shift function. We have been doing all our jobs on State Plane coordinates for about 6 to 8 years now and more and more go back to one of those jobs or on another job adjoining one we've already did.
It's a very simple, easy process to set up the new base then go find and shoot one good point from the old job and "apply shift" and be right back on the old job.

We had one job yesterday however, where we took a few PPK shots and needed to process those. When we did, the coordinates, of course, just show the "1 local" coordinates which are based off the shift....

What is the simplest and best option for getting the PPK coordinates? Undo the shift, correctly select and pick the RTK or PPK of each individual point and then "apply shift" again?

 

[Matt Johnson]

What is the simplest and best option for getting the PPK coordinates? Undo the shift, correctly select and pick the RTK or PPK of each individual point and then "apply shift" again?

Currently the M-Local auto selects between the RTK/PPK coordinate. When you create a M-Local shift you are prompted to choose between "Auto Select" and "Use Manually Selected" so if you choose "Use Manually Selected" you have some control. If the future I think the plan may be to revisit this issue and improve it.

 

[Darren Clemons]

Currently the M-Local auto selects between the RTK/PPK coordinate. When you create a M-Local shift you are prompted to choose between "Auto Select" and "Use Manually Selected" so if you choose "Use Manually Selected" you have some control. If the future I think the plan may be to revisit this issue and improve it.

Thanks Matt. Yes, it did kind of make it cumbersome when we ran into this situation.
We've been mostly just taking our state plane "old" coordinates, as design points, and after re shooting one point, translating them all. Then doing Dpos and then applying that Dpos to the "design" coordinates (which in several of our cases were true state plane coordinates from an old Opus job) and it shifts them back.....I've seen up to a tenth horizontal at most, a little more in vertical - depending on how old the Opus was and what Geoid it was using.
This way, we're more "current" with moving forward and have everything stored in a Javad job, with Dpos. Otherwise we're kind of going backwards....
May only use real time position shift for things like going back to just remark corners and flag up lines that we've already done....no new plats, etc.