Latest Contributions by Jean-YvesLauture

Hello Scott,  Please note that any ESTIMATED accuracy reported by any GNSS receiver remains an estimated accuracy. It is not the absolute truth and should be an indication of how well the receiver is more or less behaving in a specific environment.  Different manufacturers will handle estimated accuracies in different ways in their algorithms. Therefore, I suggest you take your receiver on a survey monument, first in clear view of the sky, and compare estimated accuracy vs true location. If you can repeat the same in “non-ideal” conditions (light canopy, or light or moderate urban canyon) then you’ll have a clear picture of how the receiver’s estimated accuracy compares to the reality.  Last, also note that, as a rule of thumb (and this is valid for any GNSS receiver), vertical accuracy is usually 1 to 3 times less the horizontal accuracy. For example, if you are getting 2cm accuracy horizontally, your vertical might be anywhere from 2 to 6cm.  Best of luck, JY  ... View more

Hello Ewout,  Please contact me directly at info@eos-gnss.com.  Thank you,  JY  ... View more

Thank you Miaogeng for the update. Great job.  ... View more

Hello Field Worker, Back to you with some news: the technical team at Esri was able to reproduce this bug also. They are currently working in a fix for this problem in Collector. Although we do not want to speak on their behalf (and just to give you an idea of the timeline), they anticipate a release in April. With the current world situation affecting all of us, they may face some delay but they are doing their best as usual.  We will post here again once released.  Stay safe.  JY  ... View more

Hello FW, Thank you for the extra info.  We are also seeing something there after our technicians’ tests today and are able to duplicate some behaviour. We are in contact with the Esri team on this. Can you please send an email to support@eos-gnss.com as our technicians might have some more questions for you. Please reference your GeoNet name “Field Worker” when writing.  (We will also post the outcome here for the community once problem solved.) ... View more

Hello FW,  We will try to duplicate this behavior and get back to you soon. Can you tell me which version of Collector you are using? Also, can you confirm that this behavior started after your last Collector update?  JY ... View more

We ran the test in "disconnected" on Collector Android beta with full GNSS metadata from our Arrow receivers and could not duplicate the problem that you are facing.  At one point in time, please do not hesitate to reach out so the Eos technical team can try to debug with you.  JY ... View more

Our technical team is doing testing now with the Android beta. In connected, so far so good. They are continuing today and tomorrow in disconnected. Issue might be with syncing.  Stay tuned.  ... View more

Dear Ron,  Would it be possible to fill-out the support contact form on our website? Eos Technical Support Request for Arrow GNSS Receiver Support  Info that we would need are: 1) What version number of Android Collector beta are you using? 2) Confirm that for both iOS and Android you were completely in disconnected environment (we would have to run a similar test in house by simulating disconnected environment). Are you facing the same issue in connected environment? 3) One of our technicians would invite you to a test map and see if you are facing the same problem. We could also run a vice-versa of this test where you could invite us to your map.  The above would be good starting steps to diagnose the problems you are facing.  Waiting to hear from you.  Best Regards,  Jean-Yves  ... View more

David,  this might help you: https://www.fgdc.gov/standards/projects/FGDC-standards-projects/accuracy/part3/chapter3  JY  ... View more

This is correct. GNSS receivers usually output estimated accuracies in rms. If you need 95% confidence, the best is to enable the 95% confidence level in Collector in the settings. This won’t give you exactly what you are looking for, but at least you will be recording with 95% confidence but with rms values saved.  Record GPS metadata—Collector for ArcGIS (Classic) | ArcGIS  See the note below... Good luck. ... View more

Elevations can be a pain to understand. Here is an article that might help a bit: https://eos-gnss.com/elevation-for-beginners  (This is expressed in very simple terms, and trust me, there’s much more to it). In your case, the Geoid12B or the new Geoid18 model is not applied to your ellipsoidal height to get your elevations in the NAVD88 vertical datum (that are shown in your benchmark spec sheet). In ArcGIS, since this is not done in the field, you can convert your Z value back in the office in ArcGIS. You can search here on GeoNet for references on how to do this. Just search for GEOID12B topics for example. Then, your values should match.  ... View more

Don,  Assuming your R2 is outputting coordinates in Nad83 2011, have you compared ellipsoidal height (HAE) of the R2 vs the ellipsoidal height of your benchmark? (It would be height in NAVD88 + undulation = HAE.  If they match, then it would mean that your R2 is not applying the Geoid12B (or new GEOID18) model to give you orthometric height in the NAVD88 vertical datum. It might be using a coarse grid for MSL (Mean Sea Level). I would recommend debugging this by first comparing ellipsoidal heights.  ... View more

Eos Positioning Systems offers a laser mapping solution built for Collector on iOS. It was developed by Eos for its user community of Arrow receivers and uses mainly the TruPulse 200x from LTI (because of its iOS compatibility). There is no manual data entry, except for the standard Distance/Azimuth/Inclination method where a manual input of azimuth is required (since the Trupulse 200X does not feature a built-in compass).  There are two other methods: Range/Range Intersect and Range/Backsight using the TruAngle encoder for azimuth as can be seen in the following link: Laser Mapping | Eos Positioning Systems  A couple of case studies for users who are interested (one of them published in ArcNews Summer 2019): Seattle Zoo Builds Basemap Around Lions, Tigers, and Bears  Arrow Gold for Construction: DDSI Increases Profit w/ RTK Laser Mapping  Hope this helps. ... View more

Hello Tirrell, Re- “is the Z data limited to elevation only, or is there a way to apply it to feature collected in this scenario” Not sure what you mean exactly, but to add to the very good points Lance and Ken mentioned, there is one thing to note on how the new Collector for iOS  (19.1.0  released on June 24, not Collector Classic) works with elevations. The Z-value Is now available in the point geometry itself along with the x, y. With the Arrow receivers, this is where the orthometric height is stored as you collect your points and if you have defined high-accuracy GNSS metadata fields in your map, the ellipsoidal height is stored in the ESRIGNSS_ALTITUDE field.  Here is an article that shows how to set it up: How to Record Orthometric Heights in Collector v18.1.0 (Aurora) with Your Eos Arrow GNSS Receiver | Eos Positioning Syst…  Just in case you have not done so yet, I really recommend setting your high-accuracy GNSS metadata fields in Collector. Here is how to (webinar from Esri Water):  How to Get Started with Collector for ArcGIS | Web Maps, Arrow & More  and a quick guide:  How to Record GPS and GNSS Metadata in Collector for ArcGIS  Good luck...  ... View more