I decided to perform a quick test of the M2’s RTK accuracy using NTRIP here in Upstate New York. I have always been a classical post processed GPS (GNSS now) person but decided to test drive the RTK capabilities of the M2 with Harxon GPS500 antenna. I have previously reported static/rapid static post processing results with the same receiver in an earlier post. I utilized 5 NYHARN control monuments and entered in the coordinates (Lat, Long, Ellip Ht) to also test out the Stake Out feature in the ReachView app. There was no scientific approach to each measurement. I simply drove up to each monument, set up rover rod/bi pod, turned on receiver, waited for fix then simply navigated to monument. Set up on monument and averaged between 30 and 60 seconds in measurement mode. Additionally for the last 3 stations that I measured I took a screen shot of my Stake Out screen showing the real time epoch distance to the monument being measured. Here are the DX/DY/DZ values for those 5 NYHARN monuments as compared to the actual NGS Data Sheet published values.
|NYHARN ID||Delta X (m)||Delta Y (m)||Delta Z|
Here are the screen shots of the Stake Out mode for many of the above stations:
Additionally I just performed a quick and dirty test of the new ReachView 3 Beta app for the orthometric vertical real time accuracy utilizing the new coordinate system transformations and geoid models with my android tablet on a high accuracy point at my house that I had previously occupied and adjusted with OPUS Projects with an iGage iG3s receiver. I utilized the WGS84/UTM Zone 18N and NAVD88 Height downloaded models.
Here is the DX DY DZ in RTK: 0.013mm 0.012mm 0.015mm
Conclusion: I am impressed and still need to perform more testing but figured I would share these results for those curious. And this M2 in RTK mode?..”It knows where it is”