Add a setting to choose which fields are exported into TXT files

[GrazianoCapelli]

We would add a new custom setting (below the "Export tracks in TXT" one) to choose which data fields are exported in TXT files.

The setting should show a checkbox list (a static one should be fine) where the user can select/deselect the fields. It should not be possible to change the order of them. As default we should keep checked all the fields that v3.2.2 saves in TXT files.

At this time the following fields are saved into TXT files:

type, date time, latitude, longitude, accuracy(m), altitude(m), geoid_height(m), speed(m/s), bearing(deg), sat_used, sat_inview, name, desc

I think that we could make the following selectable checkbox list:

• Type
• Date and time
• Latitude, Longitude
• Accuracy
• Altitude
• Geoid height
• Speed
• Bearing
• Satellites used
• Satellites in view
• Name
• Description

In the future we would add some new fields (read for example the issue #193): the plan is to add the new fields to the list and leave them unchecked by default.

Here a task list:

• [ ] Make a custom preference "Fields to export in TXT files" that opens a checkable list of fields. The preference should be added to preference screen. I think that to be complete we should include the Type and the Coordinates, but they should be not deselectable
• [ ] Write the fields list into preference summary, separated with a comma
• [ ] Use the stored preference keys in the Exporter to write (or not) the fields into TXT files during the exportation
• [ ] Upload the new strings in Crowdin for translation and proofreading

[Sauhard74]

can i work on this issue , I have experience in building both native and web apps and have worked on similar features I think I can contribute

[GrazianoCapelli]

Ok! I edited the header comment adding a brief task list. I'll do the last task in the list when we finished other tasks. If you think that you are comfortable with them (or you would like to do some of them) I can assign the issue to you.

[Sauhard74]

i can proceed with the entire list and have no issue working on it you can assign it to me

[GaneshVasireddy]

As default we should keep checked all the fields saved into the TABLE TRACKS v3 (the table used by the GPS Logger v3.2.2).

So if I’m not mistaken, there are nearly 40 fields being saved in the Tracks table. Should I display all those 40 fields in the checkable list ? @GrazianoCapelli can you please confirm the fields that needs to be shown in the checkable list.

[GrazianoCapelli]

So if I’m not mistaken, there are nearly 40 fields being saved in the Tracks table. Should I display all those 40 fields in the checkable list ? @GrazianoCapelli can you please confirm the fields that needs to be shown in the checkable list.

@VasireddyGanesh good question, Trying to be more specific I updated the header message including the list of fields to be included to the checklist. Currently we have 12 items.