Additional Raw Data Storage

[Jonsen94]

Hi there,
just wanted to hear your thoughts.

I checked both, the Overland and the Owntracks APIs and found, that they support more data than we currently store.
This includes:

• speed
• moving direction
• elevation accuracy
• estimated activity (ios only)

If I am not mistaken, reitti currently uses kinda simple algorithms for data post-processing (point invalidation via accuracy and estimated speed bounds).
Maybe we could start storing additional data (maybe in a separate table?).
I am currently thinking (even thought I am not familiar with this field) about testing other algorithms for better data processing.

This is partially motivated by my own data having regular issues with invalid points which are not correctly detected.
E.g. while staying at home I sometimes receive points well outside my home and street.

Additionally we could enhance the transportation detection by using the data provided by iOS.
This would have to be implemented in a way working with missing/unavailable data. As not everyone uses the same tools (and thus not all these values are available), we have old data and imports, many of these fields must be seen as optional and only be used to enhance the algorithms output.

What do you think? Did I missing something in the code regarding processing? What do you think generally about storing more raw data? If we do not use it, we don't, but if we don't store it, it's gone forever.