-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug] Receiving SRTM heights breaks the heart rate recording. #96
Comments
Just in case, I will add information, a workaround for the problem until it is fixed in gpsprune, for those users who are faced with the same problem (for example, all users of the TomTom line of watches, who can now receive their tracks from the watch only using a PC) . You can add height to a track and save the heart rate in various software (osmand; qgis, etc.), but this is not so convenient/long. The easiest option but privacy may suffer, although the source code is open and there is a nice privacy policy, everything seems to be acceptable
https://gpx.studio/ |
Thanks for the bug report, and yes I agree it can be a bit confusing. The problem here is not specifically the SRTM lookup, it's the fact that this function adds the altitude field to a point which didn't have an altitude before. It behaves the same if you manually add an altitude to this point too. Until GpsPrune has a more complete understanding of all the possible gpx extensions which could be in use, it doesn't have a way to work out where to insert the missing |
I have a watch that writes metrics: GPS and heart rate (but not altitude).
Reproducing the problem when GPSPrune removes (apparently unintentionally) the pulse from the gpx track.
If you do not use the function in gpsprune (obtaining heights from SRTM), then after editing the track, for example, gluing, etc. and after saving the track, the new track saves your heart rate.
So I conclude that it is the 'get height from SRTM' function that removes the heart rate from the track, it shouldn't be that way. Please correct.
The text was updated successfully, but these errors were encountered: