Hi-Accuracy Storage of Coordinates with Web mercator basemaps and NAD83(2011) augmentation Not Possible

241
1
2 weeks ago
Status: Open
Labels (2)
JoelCusick1
New Contributor III

Currently, when using a hi-precision bluetooth receiver (Trimble R1/R12i and Leica GG04 Basic Plus) on Android OS 13 with Mock Location ON and a real-time stream based on (NAD83(2011) - EPSG:6318) GCS, it is not possible to store features accurately online when the QuickCapture project map is based on Web Mercator (EPSG 3857).

A description of a series of tests on survey control conducted recently are attached which I hope provide the level of detail so your team can best figure a way forward to allow hi-accuracy storage of solutions meeting manufacturer specifications.

FieldMaps when setup properly on Android (Mock location off) both Trimble Mobile Manager and Leica Zeno Connect pass through the NAD83(2011) augmentation stream allowing a user with hi-accuracy receivers to store data in AGOL meeting specifications.   My tests reveal the same workflow with Quick Capture (mock location off on Android), induces an error on stored positions.

Eliminating this datum shift would allow the user community to use QuickCapture to store high accuracy positions, which are not possible on phones/tablets today and allow users to leverage the large market of hi-precision bluetooth receivers on the market today.  QuickCapture is an incredible app but we think it should offer the same capacity as Field Maps - use for hi-accuracy receivers based on a GNSS output other than "WGS84"

Here is the screenshot of Test results (Figure 4 in attachment) using the Trimble R1, Trimble R12i and Leica GG04 Basic Plus.

JoelCusick1_0-1713120704806.png

@Hi-Accuracy Storage of Coordinates with Web mercat... - Survey123 Ideas Esri Community

@Mapping and GIS Solutions Community (trimble.com) Android Device S123 not using mock locations from Trimble Mobile Manager 

1 Comment
MarikaVertzonis

This is really great research Joel, and the QuickCapture/Survey123 team appreciates you sharing this detail. In short, we know we are stuck in the current releases of the two apps, to not being able to support projected maps. But we are enthused that with the next generation of the apps we will have the full use of the Maps SDK, and will be able to do so, just like in Field Maps. 

Your testing environment and setup is outstanding so I am keen to follow up with you directly to see if you would be willing to test both possible workarounds, and of course prototype implementations when they are ready.