ntrip6 , the geofences hack you are referring to with input is something QField has also supported for years. The relevant variables to build the default value expression are listed in QField’s documentation site here (Positioning (GNSS) - QField Ecosystem Documentation). That’s however a limited workaround and doesn’t offer any visual indication prior to getting to a feature form, which is partly why I’m excited about upcoming QField 3.4’s geofencing functionality.
Imported from GitHub comment by @nirvn on 2024-08-31T02:32:14Z