March 2023 Newsletter - HERE, HERE!

by Nikolas Smilovsky February 28, 2023

Datums: WGS84 vs NAD83

Are you a Bad Elf Flex user switching between the standard and extreme modes? If so, you're probably collecting coordinates in differing datums and need a way to transform points between them.

American users connected to a RTK network via NTRIP for survey-grade accuracy will almost always be collecting points in the NAD83(2011) datum, while essentially every other latitude-longitude coordinate pair will be in the WGS84 datum. How to deal with this? We recommend using the horizontal time displacement tool available from the NGS. Just convert your coordinates to a .csv file, choose the input and output datum, input the desired epoch date, which is always 2010 for NAD83(2011), and the date of the point collection for WGS84. Calculate the shift, and add the resulting points to your GIS.

• WGS84 and NAD83(2011) are the two most common datums used by Bad Elf Flex users
• Difference is approximately 1-3 meters
• Use the NGS HTDP tool to convert between the two

Useful Links

1. Bad Elf Flex: How to switch between standard and extreme modes
2. NGS Horizontal Time Displacement Tool
3. NGS Coordinate Conversion and Transformation Tool (NCAT)

Bad Elf Flex Custom Esri ArcGIS Fields for Field Maps and QuickCapture

Do you collect elevation data or laser offset measurements in Esri's ArcGIS Field Maps or QuickCapture field data collection apps? Bad Elf Flex users now have the ability to automatically save valuable metadata to ArcGIS Field Maps and QuickCapture to improve quality control and assist in potential troubleshooting of their data. Whether you need more advanced details saved from your laser rangefinder offset points like feature height or tilt, or you're a surveyor needing the complete data lineage for survey-grade orthometric heights, or you simply want to track the datum and correction source for your field data collection efforts, we have you covered.

• Add Bad Elf custom metadata fields for ArcGIS by:
  • Using the ArcGIS Pro toolbox
  • Copying our ArcGIS Online Ortho Everywhere layer
  • Manually adding fields according to documentation
• Fields are filled whenever point is collected on the Bad Elf Flex or companion app with an ArcGIS feature open
• Fields include:
  • Datum
  • Orthometric height components
  • Antenna height
  • Laser rangefinder offset metadata
  • And more

Useful Links

1. Bad Elf Flex: How to add custom fields to ArcGIS Field Maps and QuickCapture
2. Ortho Everywhere
3. Adding Custom Field Attributes to ArcGIS Feature Classes
4. Updating Firmware Using a USB Drive
5. ArcGIS Online Ortho Everywhere Layer

Ortho Everywhere Tool

So you collect elevation data in Esri's ArcGIS Field Maps or QuickCapture field data collection apps? Our new Ortho Everywhere feature is for you!

ArcGIS Field maps and QuickCapture automatically apply the EGM96 geoid, which is relatively low accuracy with SBAS and useless when used with survey grade RTK corrected points that use the NAD83(2011) datum. Bad Elf solves this problem with our Ortho Everywhere checklist that allows ArcGIS users to overwrite elevation data with the high accuracy USGG2012 and GEOID18 geoid models used with the WGS84 and NAD83(2011) datums respectively.

Now whenever a form is open in Field Maps before submitting, just collect a point on the Flex or the companion app, and we will overwrite the point's EGM96 Z-value in the point’s geometry with the high accuracy geoid, as well as any custom Bad Elf metadata fields in the feature layer.

• The Bad Elf Flex can overwrite elevations on ArcGIS with more accurate geoids
• The Bad Elf Flex can overwrite Bad Elf custom metadata fields in ArcGIS

Useful Links

1. Bad Elf Flex: How to add custom fields to ArcGIS Field Maps and QuickCapture
2. Ortho Everywhere
3. Adding Custom Field Attributes to ArcGIS Feature Classes

Tilt Filtered Points

Just wait, we have more. Are you also a Bad Elf Flex user looking to enforce data integrity when collecting the location of assets in the field, whether it's receiver tilt, GNSS accuracy, or correction fix type? When using a Flex mounted on a 2 meter pole, each degree of tilt is equivalent to an error of nearly 4 centimeters, or nearly an inch and a half. Accuracy and correction type can vary drastically depending on environmental conditions.

To solve this problem, the Bad Elf Flex app now has a feature in the data collection checklist that requires the user to keep the GNSS unit within a specified threshold of tilt, GNSS fix, and accuracy. Check out our video for more information.

• Filtered Points with accuracy requirements including:
  • Tilt
  • Accuracy
  • GNSS fix type
• ArcGIS Field Maps and QuickCapture integration

Useful Links

1. Bad Elf Flex: How to add custom fields to ArcGIS Field Maps and QuickCapture
2. Anatomy of a Flex

Bad Elf's Quote Corner

"Last Month, Larry talked about how Bad Elf focuses on our customers and their learning. Learning is a two-way street, and we know we can learn from our customers. So, while we offer webinars and training to help you to use our products effectively, our products only deliver utility if we first learn what you need. We value tools that streamline workflows and focus on doing the right things. At the end of the day, we strive to make new customers, not just new products." - John Cunningham, Bad Elf CEO

Share:

---

Leave a comment

Comments will be approved before showing up.

Name *

Email *

Comment *