We've used a couple of their earlier RS+ models at our university for a several years. Overall pleased with them. They delivered the expected level of accuracy under various conditions, good battery life, robust in the hands of clumsy researchers, inexpensive compared to the competition, base-rover configuration works great when outside of the US, etc.
The downsides for us were: (1) only compatible with the Android version of Field Maps (we have a lot of iOS users), and (2) the user experience with getting them setup, configured, and ready-to-use (version 3 of the ReachView app is a definite improvement, however, it still is overly complicated and can lead to a lot of lost time in the field, even with very detailed instructions to follow.)
Our GNSS selection criteria in Higher-Ed are perhaps weighted more towards ease-of-use (also implying ease-of-support) than other sectors, given our constantly changing user base with students graduating and so on. For us, devices like the Bad Elf Flex, though more expensive, have been much easier for folks to adapt to, but they lack the ability to pair into a Base-Rover configuration.
So we are still on the lookout for a "prefect" solution.
Hi @tari ,
We have purchased one unit to test for our utility measurements. One thing to note is that it only works with Android if you want to use it with Collector. Bluetooth for iOS is not supported yet. Native app ReachView works on both via WiFi. I like the device and it is not that complicated to use. The accuracy is according to the manufacturer description (centimeter accuracy) which is more than enough for our projects. However, there is a significant downside which I haven´t figured out yet how to fix. I suspect this downside is not on the RS2 side though.
I have tested RS2 with its native app, ReachView, and our local coordinate system (Iceland) as well as our local geoid model. The values are very accurate and in accordance to the values from the National Land Survey. However, when I did the test at the same locations with Arcgis Collector app, the altitude and ortho height were always varying. Sometimes up to 30 cm which is far from ideal. In both cases, I used same RTK correction via NTRIP. So my guess is that the problem might be in Collector but not in Reach RS2 because the native Reach app showed very good results. I expects the same behavior in FieldMaps as well. I haven´t tested it yet but it is next on my schedule.
Would be nice to hear from you or someone else how successful the Reach integration is for others.
Thanks all for the feedback. I think we might be sticking with R2 since its been around for longer, more support available but thanks for the feedback I may still keep this in mind for future.
ReachView3 is now on the AppStore, so Emlid is compatible with the big "i".
I know... replying to an old thread, but some info is out-of-date, in case this pops up as a search result.
@MikeUnderwood The ReachView 3 app, and earlier versions, have been in the iOS App Store for years. ReachView3 allows to to use an Emlid RS2 GNSS receiver with that specific app.
In the past that hasn't helped with sharing the receiver's location information with other apps, like ArcGIS Field Maps or Survey123. I would be glad to hear that has changed!
Have you had a chance to verify if you can now use an Emild RS2 with ArcGIS Field Maps?
After I read your reply, I remember that the issue was not Reachview in the iOS but the Bluetooth connectivity between Emlid and iOS devices. It simply didn´t work so we had to use Android instead which had no issues in combining Emlid with Arcgis apps. I realized that my earlier response was related to a different thing. Thanks.
I have been working on creating a survey app in collector/field maps using external GPS and thus sending survey data in real time. Before, we used Trimble which required much more work and time to bring the surveyed data to the final destination. So now we can use a GNSS device connected to the Field Maps/Collector and measure in real time. The only issue I have encountered so far is a little difference in Z values when measured in Collector (the ReachView app has no issues though) . Sometimes it is OK and sometimes it differs by up to 10-20 cm. I don´t know if Field Maps has the same problem. I will check it in few weeks. But in general it is very promising and significantly reduces the survey hassle.
Yes, this is accurate. You cannot use bluetooth connectivity between iOS and Emlid devices.
You can use bluetooth connectivity between Android and Emlid devices. I have tested Field Maps and Collector on Android with an Emlid Reach RS2 and it works but I noticed that you have to do some post-processing work on the data after the fact. When you setup your feature class (e.g. points) you must ensure that the GNSS fields exist to capture GPS metadata. When capturing points using the Emlid GPS receiver the elevations that are captured are in ellipsoidal height within the ALTITUDE field. If you want orthometric height you need to convert the ellipsoidal height into orthometric height using a height transformation software. I live in Canada so I use vertical datum CGVD2013 for orthometric heights. To convert my elevation values I use NRCan's GPS-H. I should also mention that I use network corrections (NRTK) for my Emlid GPS receiver.
Hope this helps!