Customize track summary layout, hide unneeded data?

[ghost]

Opening a new feature request on this as suggested in #1297

Since we already have a way to customize recording layout where i can hide gain/loss data for example, would it be possible to customize track summary layout as well?

My desire to hide certain data originally came from my Pixel 5's barometric sensor messing up OpenTracks' gain/loss values, but being able to edit the summary layout would be otherwise welcome as well, and it would make sense because there already is partial layout customization support.

[dennisguse]

Similar to #1297 (comment)

Now I have a problem :)
If the sensor is broken, it doesn't make any sense to collect the data, right?
So, now we have the situation that there is a broken GPS (abs. elevation) and a broken barometer (rel. elevation/ gain).

And for both the solution would be to just not store the data, because it is useless anyhow.
So, technically speaking we would solve #1297 and #1309, if we would just not collect (barometer) or not store (GPS; elevation) the data.

Technically both is it not complicated.
Question is: how to implement the settings properly?
Any suggestions?

[ghost]

Regarding gain/loss data, in my personal opinion it would be acceptable to add a toggle to record said data (and use barometric sensor), possibly with a mention that this data may be inaccurate on some phones. This way users with "compatible" devices could make use of it (it seems not everyone is affected by this bad inaccuracy?) while others, like me, could just toggle gain/loss recording off, potentially saving a bit of battery in addition to screen real estate.

As to altitude, i have found this information to be fairly accurate and useful in some situations, but it isn't essential to me. I mostly use OpenTracks for speed, distance and heart rate, and the average values of these (edit: GPX tracks too of course). But others may want altitude/gain/loss values too, since we all have our own use cases.

Removing these would likely be simple, but would it be too complicated to add a toggle for one of these or both?

[dennisguse]

Rather simple for both, just at different places in our code.

[ghost]

I'm generally in favor of options as long as they don't add irrelevant clutter to an app. In this case i think the toggle(s) would be a good compromise between hiding data that is useless to some and altogether removing a feature that may be useful to others. I do consider recording/showing altitude values a "basic" feature of any outdoor/track recording/activity tracker app, so i wouldn't outright remove it either. Just my take.

[dennisguse]

My proposal was to not collect/ store the data and make this configurable.