{"id":69,"date":"2017-08-18T01:00:58","date_gmt":"2017-08-18T05:00:58","guid":{"rendered":"http:\/\/www.bartondrone.com\/blog\/?p=69"},"modified":"2017-09-02T23:34:07","modified_gmt":"2017-09-03T03:34:07","slug":"reach-rs-accuracy-testing","status":"publish","type":"post","link":"http:\/\/www.bartondrone.com\/blog\/reach-rs-accuracy-testing\/","title":{"rendered":"Reach RS Accuracy Testing underway"},"content":{"rendered":"

\"Reach<\/h2>\n

How accurate is the Reach RS RTK GNSS Receiver?<\/h2>\n

I have been working on getting a good understanding of how to configure and use Reach RS for the past month working to a goal of comparing the Reach RS<\/a> units vs L1 and L2 survey equipment from other manufactures. Ultimately I want to answer that question of how accurate is the Reach RS. \u00a0 Today was the first time we have set up and tested the Reach RS unit for accuracy. \u00a0In essence today was the first real accuracy test of our Reach RS units.<\/p>\n

We set up two units in a Base and Rover configuration using LoRa for correction. \u00a0We set the Base up to use an averaged single position using a 15 minute collection time. \u00a0Future testing will use 30 minutes for the averaged single position. \u00a0We want to use \u00a0a 45+ minute option for the average single position, however the current max is 30 minutes. Our rover is set up to get corrections from the base and set up over a known point. We utilized GPS, GLONAS & SBAS satellites on both base and rover. Once the base set the single solution position we turned on the rover. The rover began dialing in its location with a great AR values quickly. We let the rover get to 999.9 and stay for a couple minutes then turned everything off.<\/p>\n

Examining the data<\/h2>\n

Back at the office we downloaded CORS data plus the base and rover logs. We post processed the base against the CORS then the rover against the solution position from our base.<\/p>\n

A vertical datum conversion on the WGS84 ellipsoid gives us the NAVD88 heigh value. Conversion on the horizontal data to U.S. Survey feet, because thats what we work in. Comparing the post processed results we are \u00b10.111 Northing \u00b10.055 Easting and \u00b10.0570 Height from the coordinates on the survey monument. \u00a0I am very happy with our first test. We will continuing testing on a number of known points. The next phase of this will have us collecting the same locations with Reach RS and other units to compare both to the known points and to each other.<\/p>\n

I will continue to share info as we progress with our testing. I also have a lot of notes for feature request that I need to post. \":slight_smile:\"<\/p>\n

 <\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

How accurate is the Reach RS RTK GNSS Receiver? I have been working on getting a good understanding of how to configure and use Reach RS for the past month working to a goal of comparing the Reach RS units vs L1 and L2 survey equipment from other manufactures. Ultimately I want to answer that […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[4],"tags":[10,6,5,7],"yoast_head":"\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\t\n