Geotrace in background

[seewhy]

Hi @Florian_May
Apologies if this sounds critical, but is this a correct interpretation of the question and/or background capture of geotraces? I ask because of my previous requests along this line (sorry for the unintended pun!)...

My interpretation (and probably yours) is that @noman.s2325 wants to be able to set a geotrace running within a form and then continue collecting data in the same form. In which case it's very similar to:

Parallel collection of Geotrace while collecting other information

Dear all, One aspect that a recent client wanted was the collection of the route travelled (Geotrace) on a public transport vehicle while documenting the stops and the commuters alighting/boarding (looped queries) until the end of the journey. Currently we do this with two phones. However, it would be nice to be able to document the actual route the surveyor used while doing the entire survey. Thus I perceive the flow as follows: Select route; Start "background" automated geotrace; Start loo…

and

Record a geoline in the background

What is the general goal of the feature? I'd like to be able to kick off a 'trace' at the beginning of a form or group and for it to collect location points automatically in the background while being able to complete the rest of the form. This would then be saved in a field (in a format that can be converted to a 'track' - maybe just lat/long pairs). If its possible to set the time interval that would be a good way of reducing battery load (i.e. turn gps on and off between points if necessary…

and of course, your (fantastic) master plan:

Entity-based data capture workflow "Site-based survey with opportunistic encounters"

1. What is the general goal of the feature? In a nutshell: For longitudinal ODK Collect projects, allow one parent form to run in the background while filling in the other child forms. Allow recording a geotrace in the backgrounded parent form while filling in other forms (with their own geo widgets). Allow several projects in ODK Collect, each with their own modes (longitudinal or opportunistic). In long form: This is a write-up of a typical workflow that might work better as an entity-bas…

I think that the support for background geotrace is actually enabling ODK to continue capturing locations whilst the screen is locked or another app is active?

So perhaps the three of us are confusing the word background? Maybe @seadowg can clarify as he implemented the feature...

Maybe we really mean parallel recording, not background recording?

The only way I have managed to achieve this "function" to date is to run a GPS track in a navigation app (e.g. Oruxmaps or Viewranger) then added a question at the end to upload a file into the form (you need to stop recording the track in the other app and export as gpx or kml). This is a bit onerous for enumerators who are not fully committed to the nuances of collecting data.

I have another project that needs this functionality, which is why I was delving into the topic!