{"id":13811,"date":"2023-06-29T11:54:42","date_gmt":"2023-06-29T09:54:42","guid":{"rendered":"https:\/\/www.opengis.ch\/?p=13811"},"modified":"2024-07-07T06:14:43","modified_gmt":"2024-07-07T04:14:43","slug":"qfield-background-tracking","status":"publish","type":"post","link":"https:\/\/www.opengis.ch\/it\/2023\/06\/29\/qfield-background-tracking\/","title":{"rendered":"QField background tracking"},"content":{"rendered":"\n

Years ago, the QField community and its users showed their love for their favourite field app by supporting a successful crowdfunding to improve camera handling.<\/p>\n\n\n\n

Since then, OPENGIS.ch has continued to lead the development of QField with the regular support of sponsors. We couldn\u2019t be prouder of the progress we have made, with plenty of new features added in every major release. This includes major improvements to positioning including location tracking, integration of external GNSS receivers through not only Bluetooth but TCP\/UDP and serial port connections, accuracy indicator and constraints, and most recently sensors reading to list a few.<\/p>\n\n\n\n

We are now calling for the community to help further better QField and unlock an important milestone: background location tracking service<\/strong>.<\/p>\n\n\n\n

\n
Pledge now<\/a><\/div>\n<\/div>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Main goal: background location tracking on Android \u2013 25’000\u20ac<\/h2>\n\n\n\n

Currently, QField requires users to keep their devices\u2019 screen on and have the app in the foreground to keep track of the device\u2019s positioning location. On mobile devices, this can drain batteries faster than many would want to, in environments where charging options are limited.<\/p>\n\n\n\n

This crowdfunding aims at removing this constraint and allow QField – via a background service – to constantly keep tracking location<\/strong> even while the device is suspended (i.e., when the screen is turned off \/ locked). <\/p>\n\n\n\n

To achieve this, a significant amount of work is required as the positioning framework on Android will need to be relocated to a dedicated background service. Recent work we\u2019ve done adding a background service to synchronize captured image attachments in QFieldCloud projects<\/a> armed us with the assurances that we can achieve our goal while giving us an appreciation of the large amount of work needed.<\/p>\n\n\n\n

Some of the benefits<\/em><\/h3>\n\n\n\n

Running out of battery is the nightmare of most field surveyors. By moving location tracking to a background service, users will be able to improve their battery life considerably and keep focusing on their tasks even if it involves switching to a different app.<\/p>\n\n\n\n

Furthermore, while OPENGIS.ch ninjas remain busy squashing reported QField crashes all year long, there will always be unexpected scenarios leading to abrupt app shutdowns, such as third-party apps, systems running out of battery, etc. To address this, the background service framework will also act as a safeguard to avoid location data loss<\/strong> when QField unexpectedly shuts down and offer users means to recover that data upon re-opening QField.<\/p>\n\n\n\n

Stretch goal 1: background navigation audio feedback 5’000\u20ac<\/h2>\n\n\n\n

The second stretch goal builds onto QField\u2019s nice fly-to-point navigation system. If the QField community meets this threshold, a new background navigation audio feedback informing users in the field of their proximity to their target <\/strong>will be implemented. <\/p>\n\n\n\n

The audio feedback will use text-to-speech technology to state the distance to target in meters for a given time or distance interval.<\/p>\n\n\n\n

Stretch goal 2: iOS 15’000\u20ac<\/h2>\n\n\n\n

The main goal will cover the Android implementation only. Due to being a very low level work we will have to replicate the work for each platform we support. If we reach stretch goal 2 we will also implement this for iOS.<\/p>\n\n\n\n

Pledge now:<\/h1>\n\n\n\n