No matter what the post processed solution says, I’ll agree with Nate and take a verified, validated, double checked and triple checked rtk shot any day of the week and twice on Thursday over any static result. I ,of course, don’t mean just any RTK shot, but a properly time separated and collected Javad LS RTK shot.
What Nate’s describing is far from a “lucky” RTK shot. It’s “hands on”, boots on the ground, physical checking of our data. That’s what many of us have to do on almost every “tough” RTK point. Store the point, store the point again, maybe an hour or two later or the next day if necessary, stake back to the point - when they’re ALL checking within 0.04’ or better there’s no need for any type of post processing software as far as I’m concerned. I want to physically see that I can repeat that coordinate. That’s what Matthew’s original post proves. Even as great as the PPK ability is, it CAN give false positives. It’s value to us from its very beginning has been as mostly an aid for verification - not as a stand alone guarantee. It can be used certainly when no RTK whatsoever is able to be collected, but a minimum of two matching sets of data must be acquired.
No matter the software or algorithms used for any static solution there’s nothing better that multiple matching visual RTK shots.