Nate The Surveyor
Well-Known Member
What if we had 3 options, on coord pick.
Now, we have rtk, and ppk. What if we had a 3rd option, avg of rtk, and ppk?
Now, we have rtk, and ppk. What if we had a 3rd option, avg of rtk, and ppk?
Yes the statics are included in the offset point.Do the statistics for the PPK point go to the offset point (error estimates)?
I generally count on my quality control being agreement between my RTK and PPK values. However, I have had two cases recently where they did not agree by as much as several feet. Both times the DPOS choice was the RTK and that did not agree with record dimensions, but I found that the PPK did.
These have been fairly obstructed sites that were a struggle to get a fix.
There are also no statistics given for the PPK solution like there are for the RTK.
I have seen a bad fix last for more than 240 seconds only 1 time in 4 years.
I have seen a bad fix last for more than 240 seconds only 1 time in 4 years.
Hmmm ...do you think Galileo Will help?
Exactly. The issue that most of us have in the deep, dark corners of the world where we take this wonderful little machine, is that many, many times, no matter how long you stay on “one session” the LS just won’t go through all three phases. I know the “directions” say we should do that, but it just doesn’t work some places.Bill, I recommend not accepting an RTK shot that has less than 240 seconds between fixed epochs that agree. I have seen a bad fix last for more than 240 seconds only 1 time in 4 years.
Also I highly recommend taking multiple shots on every corner. It helps identify if you have a bad fix or a blunder. It also helps increase your relative accuracy. It will take more time but I never have to go back and shoot points again.
but when I pick the button under the ppk solution I get this:
The Base/Rover Statistics screen works properly for the PPK solution in the latest build of J-Field when I try it. Are you still on the WinCE OS?
Yes, have not updated yet. With the hiccups some have been reporting, I have hesitated to do so.The Base/Rover Statistics screen works properly for the PPK solution in the latest build of J-Field when I try it. Are you still on the WinCE OS?
When is it appropriate to use the DGPS and standalone options? Let's say I am in dense canopy and only getting an occasional fix that is not enough to verify in a reasonable time frame... I know I should be taking redundant measurements for 10-20 minutes each so that we can get processed results that hopefully match. In situations like this should these difficult shots only accept fixed solutions as well?1136 only has 146 seconds for RTK. That's not using the boundary profile, at least not allowing it to finish. The boundary profile should go for at least 180 seconds, plus another couple of seconds for validation. More in canopy.
Also, do not use accept all (DGPS and Standalone). Use Fixed only.