Today I enjoyed my first successful Hybrid RTK project with DPOS.
I set up a Triumph 1 base with Base Rover Setup broadcasting very low power. I collected five points with raw data. The first point received corrections producing a fixed solution. The remaining four points were standalone. I sent the project to the new DPOS server. The raw data from the collected points were processed with the base data. CORS data wasn't available, but DPOS still processed the on site vectors.
My base position for this project is still based on an autonomous (standalone) position. I calculated a simple translation from the autonomous base position to the known coordinates of my base point, POST. I then applied this translation to all post-processed rover coordinate points: L001, L002, L003, L004 and L005. I then compared the translated coordinates to my known coordinates for the monuments I tied in. The results are as follows in US Survey Feet (Base Line length in parenthesis):
L001 (69' 5 minute observation)
dN +0.0075
dE +0.0036
dU -0.0239
L002 (4825' 5 minute observation)
dN +0.0296
dE -0.0374
dU -0.0447
L003 (13560' 5 minute observation)
dN +0.0192
dE -0.0093
dU +0.0390
L004 (50102' 6 minute observation)
dN +0.0348
dE -0.0457
dU -0.0028
L005 (50102' 15 minute observation)
dN +0.0292
dE +0.0011
dU +0.0939
With comparisons like these, I would find it difficult to say that the Justin engine used by DPOS was in eerror. The coordinates I'm comparing with could be this far from "truth". I would consider these results to be statistically perfect. With this new capability, a user can locate a distant point without the concern for maintaining radio communication. This is fantastic.
There is still more work to be done before release, but these tests untold promise.
I set up a Triumph 1 base with Base Rover Setup broadcasting very low power. I collected five points with raw data. The first point received corrections producing a fixed solution. The remaining four points were standalone. I sent the project to the new DPOS server. The raw data from the collected points were processed with the base data. CORS data wasn't available, but DPOS still processed the on site vectors.
My base position for this project is still based on an autonomous (standalone) position. I calculated a simple translation from the autonomous base position to the known coordinates of my base point, POST. I then applied this translation to all post-processed rover coordinate points: L001, L002, L003, L004 and L005. I then compared the translated coordinates to my known coordinates for the monuments I tied in. The results are as follows in US Survey Feet (Base Line length in parenthesis):
L001 (69' 5 minute observation)
dN +0.0075
dE +0.0036
dU -0.0239
L002 (4825' 5 minute observation)
dN +0.0296
dE -0.0374
dU -0.0447
L003 (13560' 5 minute observation)
dN +0.0192
dE -0.0093
dU +0.0390
L004 (50102' 6 minute observation)
dN +0.0348
dE -0.0457
dU -0.0028
L005 (50102' 15 minute observation)
dN +0.0292
dE +0.0011
dU +0.0939
With comparisons like these, I would find it difficult to say that the Justin engine used by DPOS was in eerror. The coordinates I'm comparing with could be this far from "truth". I would consider these results to be statistically perfect. With this new capability, a user can locate a distant point without the concern for maintaining radio communication. This is fantastic.
There is still more work to be done before release, but these tests untold promise.