nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

WebSocket and/or geoid support for Field Maps

GeoguichetGeoguichet

Unfortunately Field Maps is not usable for real and accurate 3D data acquisition or stakeout using precise GNSS because of the lack of precise height management in real time.

It would be useful to support local height systems (geoid) and support of WebSocket to get/handle accurate height from GNSS antenas (e.g. Leica)

Finde mehr Beiträge mit dem Tag

Data collection

Mobile App

Inspections

High accuracy GPS

AR-VR

Status: Öffnen

Kommentare

ColinLawrence

Hi @GeoguichetGeoguichet can you tell us more about your workflow and setup? ie what antenna are you using, geode, coordinate system, etc?

We are currently working on WebSocket support with a handful of vendors. Eventually, we will want to roll this out as the standard over direct bluetooth connection. Hopefully this will help smooth out some of the workflows when operating in both the GPS vendors app and Field Maps.

When it comes to orthometric height support in Field Maps, we still want to accomplish this but do not currently have a timeline.

GeoguichetGeoguichet

Hello. Good news, thanks @ColinLawrence for the fast reply.

We tried with several GNSS receivers, "classic" and low cost.

We wanted to be able (and our customers also) to create data from the field, in 3D, in the official local geographic system. With an accuracy of ~5 cm.

That means not the smartphone or tablet receiver, but with an additonal one.

All data in DB is in local (Swiss CH1903+/LV95 and Bessel Geoid CHGeo2004 [eventually incl. HTRANS in order to have usual height].
We also wish to be able to update data from the field and also from office, so mixed datasets from different heights systems is not a good idea, even if we can "play" with additional attributes to handle temporary field data that has to be transformed afterwards.

And the goal is also to be able to check some heighs or volumes on field (stakeout), that means delayed post-processing server side is not really a solution.

We had to developp an intermediate app to handle NTRIP (for accurate GNSS location) and also transform heights locally.
There are many GNSS tools that work with mock location, but it would be pretty logical if the GIS app could handle local height systems, like ArcGIS Pro on desktop or QField, etc.
Because many low cost "drivers" (eg for ublox chips) cannot handle height transformations at all.

About the GNSS software that is able to handle height transformation, we use for example Leica Zeno Connect: it supports/uses WebSocket and with it, it should be possible to work directly in local height system with Field Maps (even without embbedded orthometric heights support)

Summary:
ArcGIS Enterprise 11.5 in the office
ArcGIS Field Maps on field (or, currently, other tools in order to handle height systems correctly)
Lefebure NTRIP or home made tools in order to handle local corrections, but we would like to work with Leica Zeno Connect
Leica Zeno FLX100+ tilt antenna
CH1903+/LV95 reference system (EPSG 2056)
LHN95 height system (Geoid CHGeo2004) or LN02 usual (~orthometric) height (Geoid CHGeo2004 incl. HTRANS dataset).
Both geoids are available in several formats and may already be used on ESRI desktop tools

We are available for more information, even to provide configuration data/information or perform tests.
Best regards

ColinLawrence

@GeoguichetGeoguichet Thank you, that is helpful context about your workflow! Good news is that Leica and the Zeno app is one of which we are actively working and testing with for potential WebSocket support in Field Maps. Stay tuned!

Nehmen Sie an der Diskussion teil

Melden Sie sich an, um zu posten, Inhalte zu folgen und mehr. Neu hier? Kostenlos registrieren.