Nate The Surveyor
Well-Known Member
Add a chime or noise at the end of every iteration of RTPK.
Add a white button that shows total time of fixed solutions, that are in agreement, with each other (I'm told 6 minutes fixed, in agreement, is gold) maybe a graphic, showing total time per point, (temporary points in RTPK, that is)
RTPK * (star on screen) should be color coded, so that we can differentiate fixed and floats. And a distance to the closest epoch, from rtk. This is not always the lead rtk point. This can indicate that we are on the correct init point.
I'm sometimes on a point for 30-40 minutes, or more. I'll store multiple shots, until I achieve a level of comfort, with the point.
Ability to change from rtk to RTPK should be allowed any time, not just when both are present and available.
I'm sometimes on a point 2 or 3 minutes before I get any rtk clicks. I need to be able to tell if it moves, in the iterations of RTPK, independent of RTK. In fact, I need to be able to see what is happening, ie qc the RTPK. (See above)
I need to be able to SELECT all shots, or points where rtk, and RTPK are in disagreement by more than a specified value. (0.08' or such like)
I hope I'm not making a mosquito (nuisance) of myself. I'm posting alot lately. I'm experiencing dead afternoons, and only working mornings, because of some sort of bad satellite issues beginning at around 12:30, to 4:00 PM. I've ordered a T-3, and I'm hoping that will help with dead afternoon syndrome.
I hope adding a T3 will help. Then, I'll be needing the LS upgrade.
Building software seems like a never-ending task.
If I could write software, I'd....
Have calluses on my fingertips.
Nate
Add a white button that shows total time of fixed solutions, that are in agreement, with each other (I'm told 6 minutes fixed, in agreement, is gold) maybe a graphic, showing total time per point, (temporary points in RTPK, that is)
RTPK * (star on screen) should be color coded, so that we can differentiate fixed and floats. And a distance to the closest epoch, from rtk. This is not always the lead rtk point. This can indicate that we are on the correct init point.
I'm sometimes on a point for 30-40 minutes, or more. I'll store multiple shots, until I achieve a level of comfort, with the point.
Ability to change from rtk to RTPK should be allowed any time, not just when both are present and available.
I'm sometimes on a point 2 or 3 minutes before I get any rtk clicks. I need to be able to tell if it moves, in the iterations of RTPK, independent of RTK. In fact, I need to be able to see what is happening, ie qc the RTPK. (See above)
I need to be able to SELECT all shots, or points where rtk, and RTPK are in disagreement by more than a specified value. (0.08' or such like)
I hope I'm not making a mosquito (nuisance) of myself. I'm posting alot lately. I'm experiencing dead afternoons, and only working mornings, because of some sort of bad satellite issues beginning at around 12:30, to 4:00 PM. I've ordered a T-3, and I'm hoping that will help with dead afternoon syndrome.
I hope adding a T3 will help. Then, I'll be needing the LS upgrade.
Building software seems like a never-ending task.
If I could write software, I'd....
Have calluses on my fingertips.
Nate