trip recording - the smart way (like Garmin does) about osmand

[sonora]

We must be aware that many such (often post-processing) algotithms are usually targeted at fitting the geometric shape of a track with fewer points than their raw data has as e.g. recorded at fixed time intervals.

But this also removes other information(!), which may not be desired, e.g. time, speed, altitude, cadence etc.data, which was contained in points the geo- simplification removes or manipulates.

So what kind of track sinplification makes sense for you depends on your actual purpose and use case.

[albansuser]

Exacttly. Just saying that "the smart way" is not necessarily "smart" for all use cases.

And perhaps optimizations like this should even be a post-processing option you can apply to a track once it's been saved, there may be little benefit enforcing a decision before recording.

I agree. No sense in unnecessarily increasing the processor load while recording, especially if external sensors are being used. Then there's also data loss.

I can't think of any benefits of such real time "optimization".

[nosorozec]

Thanks for all the comments.
I agree that this is best dona as post-process optimization.

[albansuser]

"if you are moving the same direction (straight line) they record less information but when you start turning there is a lot more points in the log."

Am curious as to the practical advantages of such a feature?

Thanks

[pebogufi]

@albansuser
Have a look at
https://en.m.wikipedia.org/wiki/Ramer%E2%80%93Douglas%E2%80%93Peucker_algorithm

[Sonwon1]

We must be aware that many such (often post-processing) algotithms are usually targeted at fitting the geometric shape of a track with fewer points than their raw data has as e.g. recorded at a fixed tome interval.

But this also removes other information(!), which may not be desired, e.g. time, speed, altitude, cadence etc.data, which was contained in points the geo- simplification removes or manipulates.

So what kind of track sinplification makes sense for you depends on your actual purpose and use case.

It could be an option letting the user decide which is more useful for their usage.

[sonora]

Exacttly. Just saying that "the smart way" is not necessarily "smart" for all use cases.

And perhaps optimizations like this should even be a post-processing option you can apply to a track once it's been saved, there may be little benefit enforcing a decision before recording.