I use an external GPS antennae Leica GG04plus (Leica Zeno GG04 plus Smartantenne für hohe Präzision an jedem Einsatzort | Leica Geosystems) with ZenoConnect app (for connecting external antennae and receiving NTRIP correction data from RTK servers) on an iOS tablet (iPad).
However, QField on iOS only offers configuring TCP/UDP connections for NMEA streams besides the internal antennae.
According to ZenoConnect documentation, corrected, high precision location data should be seamlessly provided via iOS “LocationManager” without further configuration; however when choosing internal antennae in QField (with ZenoConnect up and running and RTK servers configured and serving correction data as can be observed in ZenoConnect), QField only shows low-precision location data.
How do I access high-precision location data from ZenoConnect within QField?
Mobile
- Device: iPad
- QField version: 3.0.5
I just noticed that there is a similar question here: iOS App does show accuracy only with 5m, although 10cm RTK accuracy in device · opengisch/QField · Discussion #4577 · GitHub
I contacted Leica support. However, they always stated that it would “just work”:
Trotzdem schonmal kurz zu Ihrer Frage: Zeno Connect leitet die Korrekturdaten als NMEA in die Drittsoftware.
Welche NMEA-Messages rausgehen sollen, kann in Zeno Connect unter Einstellungen → NMEA-Messages definiert werden.
Weitere Informationen finden Sie im angehängten Dokument ab S. 18.
And attached this document, but the section regarding “streaming NMEA messages” seems to only deal with output to COM ports, no mention of how (TCP/UDP ports?) the third party app (QField in this case) would have access to the stream and no mention of iOS specifics:
Zeno_Quick_Start_Tutorial_-_Zeno_Connect_and_Zeno_Tools_en.pdf
In the ZenoConnect datasheet, it is simply stated that “On Android and iOS3, the accurate position will be provided via the location manager with no further setup required.”; I interpreted that as ZenoConnect substituting its high-precision location data for the datat given by internal device receiver, but it does not seem to work.
On Android I know how to configure Developer mode to make ZenoConnect the source for LocationData.
Imported from GitHub discussion by @w0pr on 2023-11-08T10:03:12Z