M-Local shift

[Mark Wheeler]

Currently using LS+ as Rover, LS as base. The base/rover connection is not the same as if using a T-2 or T-3. Linking the files is more complicated. In the LS base a raw file is created along with the session. Typically collect the point on the RTN and use that as an initial Base coordinate and collect RTN points (or RTPK points) on the other LS+. Then after post processing the Raw base file I adjust the collected points in Cad by the Base shift. This process works but would prefer to shift the collected points in the LS. Using this process, though I cannot find M-Local on the J Field screen. Is there a means to shift the RTK points on the LS rover without doing the file transfers and linking?

 

[Adam Plumley]

If you recover the base, attach gnss file, then recover the DPOS session then when it is sent to DPOS it will shift the base and the rover points. You don't have to do that in CAD. If you want to shift your design points in J-Field use cogo and shifts. Tap the little triangle that says DPOS and it will populate the DPOS shift. Then you can shift them.

 

[Mark Wheeler]

Thanks Adam. So as of now there is no way shift survey points in the LS other than the above procedure?

 

[Shawn Billings]

Thanks Adam. So as of now there is no way shift survey points in the LS other than the above procedure?

M Local is the way to shift survey points. Highlight the source point being translated (usually a base point, but it could be a rover point if the rover point was on a known coordinate). Click the chart button below the DPOS button. At the bottom right corner of the screen, you should see a button with two green planes. If you don't see it click on the button at the top left that shows ABS/Known/Auto. Cycle through them until you see the two green planes button. This is the M-Local button. Once selected you will be prompted to give a point or coordinate for the destination of this point. Once selected and okay'ed the point will translate, along with the base point (if it's a rover point) and all rover points collected from that base point. Points observed from other base sessions will not move, nor will any design points. In this regard, it works very much like DPOS in how it translates. Note this is only for small translations such as you might encounter in translating from an autonomous position to a CORS position (a few meters). It is not intended for large translations such as State Plane to 5,000/5,000.