We've separated localization and Base Shift in the newest version. Now localization will only be used for creating the transformation parameters: translation N, E, U, rotation around the axes N, E, U (think of an airplane, pitch roll and yaw), and scale, to go from one coordinate system to another. This could be for creating a local system (5k,5k) or for determining the difference between some geodetic coordinate system (known) and some unknown coordinate system (5k, 5k).
M-local is in the points screen. After a point is collected, it can be translated to another coordinate. Think of the reverse shift we have now. You set up the base on a temporary point (roof of car) and you tie into a known point, then shift translates the base and all points observed from that base to the target point. The target could be a design point or an entered value. We've offered single point shift for a while now and many of you are using it. Now you will be able to have Multiple point shift. Just keep adding points to the shift. The only thing being applied is translation (similar to how CORS processing in DPOS has worked).
Today and Saturday I tested something pretty amazing, in my opinion. I set up the base with an autonomous position, I then went to a physical city control monument that was beyond radio range. I collected raw data on the point. I returned to the base, downloaded the short file and processed the base and rover data to determine the vector from base to known point. I then performed a shift holding the known coordinates of the monument. This shifted the base and all rover points from the base. I then restarted the base, careful to recall the new shifted position of the base and completed my work. The great thing was that I didn't need to actually have a real time position on the monument, but I was able to process the vector in the field using the internet on my phone to send the data to DPOS, once the vector was returned it was as if I had a real time position and I was able to use that vector in the field for additional work, just as if I actually had a real time position on it.
M-Local will be a powerful tool. I may never worry about setting the base on a physical control point again. If you tie in several points, I think you may actually have a stronger solution for the base than centering a tribrach over a point. M-Local also supports fixing vertical or horizontal or both to known points. This will be useful for holding benchmarks for vertical translation. Also the shift can be constantly refined, selecting and de-selecting point combinations as necessary.
M-local is in the points screen. After a point is collected, it can be translated to another coordinate. Think of the reverse shift we have now. You set up the base on a temporary point (roof of car) and you tie into a known point, then shift translates the base and all points observed from that base to the target point. The target could be a design point or an entered value. We've offered single point shift for a while now and many of you are using it. Now you will be able to have Multiple point shift. Just keep adding points to the shift. The only thing being applied is translation (similar to how CORS processing in DPOS has worked).
Today and Saturday I tested something pretty amazing, in my opinion. I set up the base with an autonomous position, I then went to a physical city control monument that was beyond radio range. I collected raw data on the point. I returned to the base, downloaded the short file and processed the base and rover data to determine the vector from base to known point. I then performed a shift holding the known coordinates of the monument. This shifted the base and all rover points from the base. I then restarted the base, careful to recall the new shifted position of the base and completed my work. The great thing was that I didn't need to actually have a real time position on the monument, but I was able to process the vector in the field using the internet on my phone to send the data to DPOS, once the vector was returned it was as if I had a real time position and I was able to use that vector in the field for additional work, just as if I actually had a real time position on it.
M-Local will be a powerful tool. I may never worry about setting the base on a physical control point again. If you tie in several points, I think you may actually have a stronger solution for the base than centering a tribrach over a point. M-Local also supports fixing vertical or horizontal or both to known points. This will be useful for holding benchmarks for vertical translation. Also the shift can be constantly refined, selecting and de-selecting point combinations as necessary.
