Frederic

Ovahead, Your issue seems to be different, let alone that you are trying to import a crp file and not a fit file. 10:14:30 [main - 1] 1 Importing tours... 10:14:30 [Importing tours - 49] 2 0.158 s ∙[Import failed] C:\Users\frederic\Downloads\080522.crp 10:14:31 [main - 1] 3 Imported in 1.544 s Can you create an issue here please ? Thanks

Pascal, After more investigation, I have fixed an issue in MT that will be in the next release. With this fix, your file FIT NOT OK.fit imports correctly as you can see in my attached screenshot. Frederic

Pascal, After more investigation, I have fixed an issue in MT that will be in the next release. With this fix, your file FIT NOT OK.fit imports correctly as you can see in my attached screenshot. Frederic

I would recommend to create a feature request on GitHub as I don't believe this is possible to do such a thing in MT as of today.

Frans, I have now investigated the altitude discrepancy and indeed, when I import in MT, I see a value of 2095m. However, when I change the DP value to 70m, then I read an elevation gain value of 1460m, which seems more close to the actual value you mentioned in your original post (1600m) Looking at your tour's altitude graph, it seems to me that there are a lot of little up & downs (see my attached screenshot) that might be the cause of the high original value of 2095m and hence why the DP algorithm...

Ok, good to know you haven't pressed the button. There are definitely pauses but it seems that some are not "complete" and hence the error message. I will try to see if those pauses were triggered by the device (auto-pauses?)

Frans, First of all, congratulation on summiting Ben Nevis, that looks like a great hike on a legendary mountain :-) Thanks for the clarification. I only had the time to investigate today the discrepancy in the distance and here are my findings. You can find attached a comparison of distance values where I used MT, CalTopo and GoldenCheetah and as you can see all the distance are roughly 24km. Therefore, I would be tempted to think that the question about the discrepancy should be asked to Strava...

Frans, I don't fully understand your issue. Are you saying that you are seeing distance/altitude differences when importing files from Strava to MT or from MT to Strava ? As for the distance, it seems like Strava computes using its own algorithm, which can explain the discrepancies, more info here Frederic