I'll start by saying simply that shift is a lot of fun and very utilitarian. Shift calculates the translation from the current rover position to a known coordinate. For instance, you set up the base using an autonomous position, you then recover a point with known coordinates and you want your survey to relate to this point. Shift allows you to collect a shot on this point then apply the translation to every point within the base session. This means that all points (within the base session) that are observed before shift and all points collected (within the base session) after the shift are translated by the observed difference the known coordinate of a monument and the surveyed rover coordinate of a monument.
In the Collect Action screen press the black button "Point". Select Shift. Select or enter the coordinates of the known point. Press OK. Notice that "Point" now says "Shift". Center the LS on the monument with known coordinates. Press "Start", once the point is collected and accepted, the user is shown the translation amount. Select OK. Press "Shift" and select "Apply Shift". Then switch back to point collection (or line, curve, traj depending on your survey). The bottom of the action screen will now show "SHIFT DETAILS" at the bottom of the screen. This indicates that a shift is in effect so that you won't be inadvertently applying a shift when you did not intend it. It also allows you to see what the shift is.
Shift uses the same "Shift" space in the database that DPOS uses and has all of the same benefits. For instance, shift applies only to a base session, so you can have multiple shifts in a single project (one for each base session - think about each day returning to a job and setting the base in a convenient place then shifting each day's base position to a monument shot with the rover). Shift can be undone and redone. If you have a monument that is only approximate (a leaning post, a damaged monument, etc.) you can shift to it to get your coordinates close, then recover a better monument and shift to the better monument. The new shift applies to the entire base session, so all points collected (including the rough point you shifted originally) will be shifted by the new translation. SWEET! Finally, Shift can be superseded later by DPOS as DPOS will simply Shift the base session from to the post processed coordinates of the base station.
Shift is like localization, but is fast. It only uses ONE point, so it is wise to at least check in to another point. It is, to my knowledge, limited to translating for known coordinate systems and is probably not suited for translating between State Plane and 5000,5000, for example. Perhaps someone from the development team can address this.
In the Collect Action screen press the black button "Point". Select Shift. Select or enter the coordinates of the known point. Press OK. Notice that "Point" now says "Shift". Center the LS on the monument with known coordinates. Press "Start", once the point is collected and accepted, the user is shown the translation amount. Select OK. Press "Shift" and select "Apply Shift". Then switch back to point collection (or line, curve, traj depending on your survey). The bottom of the action screen will now show "SHIFT DETAILS" at the bottom of the screen. This indicates that a shift is in effect so that you won't be inadvertently applying a shift when you did not intend it. It also allows you to see what the shift is.
Shift uses the same "Shift" space in the database that DPOS uses and has all of the same benefits. For instance, shift applies only to a base session, so you can have multiple shifts in a single project (one for each base session - think about each day returning to a job and setting the base in a convenient place then shifting each day's base position to a monument shot with the rover). Shift can be undone and redone. If you have a monument that is only approximate (a leaning post, a damaged monument, etc.) you can shift to it to get your coordinates close, then recover a better monument and shift to the better monument. The new shift applies to the entire base session, so all points collected (including the rough point you shifted originally) will be shifted by the new translation. SWEET! Finally, Shift can be superseded later by DPOS as DPOS will simply Shift the base session from to the post processed coordinates of the base station.
Shift is like localization, but is fast. It only uses ONE point, so it is wise to at least check in to another point. It is, to my knowledge, limited to translating for known coordinate systems and is probably not suited for translating between State Plane and 5000,5000, for example. Perhaps someone from the development team can address this.