Nate The Surveyor
Well-Known Member
I've been using Javad gear now for about 5 years.
In the bad places we go, I believe RTPK is going to replace RTK, for solid answers.
Mr. Matt Johnston asked me in another thread, about how I would suggest that we evaluate RTPK .
Well, this so deeply affects us, that I thought it deserves a thread of its own.
I'd like to propose that we first consider some of rtpk's limitations. One is it requires communication base to rover. Sometimes in these holes, com's are intermittent or poor. This can interfere.
Also, as it is now, if you sit on a place for an extended time period, (say 10 minutes) the whole thing restarts, from zero, and goes to 10 minutes and restarts. Each of these 10 minute periods is repeated, and after each one, scored. It's scored for separation. (Time separation) and ellipse size and shape. After hitting store, the RTPK software uses a weighted average, and averages these 10 minute sessions into one master coord. It may work better to use 6 minute sessions, or some other number.
It should then store this RTPK as a piggy back coord, as it now does.
DPOS should mimic this process, so that if some of the data is MISSING, from the RTPK solution, that it is put back via DPOS. Or, DPOS could be allowed via a form of post processed RTPK, after the base is downloaded to the rover.
This mechanism would allow extended RTPK sessions, post processed RTPK, where signals were low, intermittent, or altogether missing.
Post Processed RTPK, should be allowed, without shutting down the base, but it would only be for selected points, or points with poor or missing base data.
Via Bluetooth.
I want to thank the whole team that's making all this wonderful stuff happen. I especially want to pay respects to Mr Ashjaee's vision to allow us, the users of this equipment to make suggestions, and comments on the development, and mechanisms that we use to perform land surveying. I realize I am using equipment, that I only understand in a limited fashion. So, some of my ideas are not implementable.
That's ok. The whole idea is to get good data fast. And to build an invincible survey machine.
Also, someday, we want automated rod height, even if rod height is changed during an observation.
Someday? Yes. It will become commonplace.
Now, where is my T-3?
Nate
In the bad places we go, I believe RTPK is going to replace RTK, for solid answers.
Mr. Matt Johnston asked me in another thread, about how I would suggest that we evaluate RTPK .
Well, this so deeply affects us, that I thought it deserves a thread of its own.
I'd like to propose that we first consider some of rtpk's limitations. One is it requires communication base to rover. Sometimes in these holes, com's are intermittent or poor. This can interfere.
Also, as it is now, if you sit on a place for an extended time period, (say 10 minutes) the whole thing restarts, from zero, and goes to 10 minutes and restarts. Each of these 10 minute periods is repeated, and after each one, scored. It's scored for separation. (Time separation) and ellipse size and shape. After hitting store, the RTPK software uses a weighted average, and averages these 10 minute sessions into one master coord. It may work better to use 6 minute sessions, or some other number.
It should then store this RTPK as a piggy back coord, as it now does.
DPOS should mimic this process, so that if some of the data is MISSING, from the RTPK solution, that it is put back via DPOS. Or, DPOS could be allowed via a form of post processed RTPK, after the base is downloaded to the rover.
This mechanism would allow extended RTPK sessions, post processed RTPK, where signals were low, intermittent, or altogether missing.
Post Processed RTPK, should be allowed, without shutting down the base, but it would only be for selected points, or points with poor or missing base data.
Via Bluetooth.
I want to thank the whole team that's making all this wonderful stuff happen. I especially want to pay respects to Mr Ashjaee's vision to allow us, the users of this equipment to make suggestions, and comments on the development, and mechanisms that we use to perform land surveying. I realize I am using equipment, that I only understand in a limited fashion. So, some of my ideas are not implementable.
That's ok. The whole idea is to get good data fast. And to build an invincible survey machine.
Also, someday, we want automated rod height, even if rod height is changed during an observation.
Someday? Yes. It will become commonplace.
Now, where is my T-3?
Nate