CORS to BASE, vs BASE to ROVER

[Nate The Surveyor]

I want the freedom, to choose PPK, or RTK, for a rover shot, REGARDLESS of the base origin.

When I use M-Local, for a base origin, it blocks me from choosing, at my will, RTK or PPK. There is no good reason, to LOCK me out of changing from RTK to PPK, on a rover shot, just because I used M-Local to derive the base coord.

This is no good. I have a bad coord in the LS, on a job that is going to court. I have to upload a DESIGN coord, just to have the correct coord, in the field. The PPK, that it chose, is the wrong one.

Thank you,
Nate

 

[Matthew D. Sibole]

Just a work around but switch your base coordinate back to the DPOS solution and pick the RTK/PPK positions you want. After that has been done then switch back to M-Local and it should ask if you want the manually selected coordinate or allow it to pick for you.

 

[Nate The Surveyor]

Ok. Thanks.
These things should be made more user friendly.
I monkeyed with this for a week, on a prev project, that had trajectories. I thought it was locking up, but it runs them real slow.
Also, knowing which iteration (RTK/PPK) is correct, is often not known, until after its in acad, and on the screen.
I'll fix this one. And, keep all this in mind.
Nate

 

[Nate The Surveyor]

I got it right.
I often don't know which iteration is correct, until after its been DPOS ed, and uploaded into Carlson/acad. Then I have to undo and go way back, and re do it. User friendly is necessary, if the javad is to become an industry standard, and used to teach surveying.
Nate