One thing that would be really helpful for fieldwork with QField is the ability to designate layers as ‘geofences’:
i.e. a hazard point layer is included in the Qfield project, alert the user when they get within xx meters of a hazard.
or a polygon layer is included in the project representing restricted/no-go areas. Qfield app alerts the user when they enter the area.
Imported from GitHub discussion by @timbo-barnes on 2022-11-30T00:41:09Z
Thanks for the suggestion. This feature is unlikely to be developed in QField without financial support for it, if you are interested please drop us an email on info at opengis.ch.
In the meantime, I believe with some ninja skills in QGIS expressions you can make the screen to blink and flash whenever the condition you mentioned is satisfied.
Imported from GitHub comment by @suricactus on 2022-12-04T11:27:39Z
Geofencing has been implemented and will be available in the next version of QField (3.4). The PRs covering the implementation is Implementation of geofencing functionality by nirvn · Pull Request #5409 · opengisch/QField · GitHub . The implementation includes a visual warnings when entering / leaving a geofenced area as well as a digitizing prohibition when in or out of geofenced areas. Pretty exciting functionality!
Imported from GitHub comment by @nirvn on 2024-08-31T02:28:43Z
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
