How to import move with ascent

[isazi]

@remrem with no error from QS?

[Remrem]

@isazi : I just have the message : “Processed 1 file”

[isazi]

@remrem then refresh Suunto App, the activity should get there.

[Mff73]

@remrem said in How to import move with ascent:

@isazi : I just have the message : “Processed 1 file”

if fit file is not “perfect”, following fit sdk rules, it may happen. QS is able to process it, but SA doesn’t accept it, but without an error return (to QS).

[Remrem]

@mff73 said in How to import move with ascent:

@remrem said in How to import move with ascent:

@isazi : I just have the message : “Processed 1 file”

if fit file is not “perfect”, following fit sdk rules, it may happen. QS is able to process it, but SA doesn’t accept it, but without an error return (to QS).

So how do you modify .ift files so that they are accepted?
How complicated it is when before it was so easy with MovesCount! When will a real update of the application be made?

[Mff73]

@remrem said in How to import move with ascent:

@mff73 said in How to import move with ascent:

@remrem said in How to import move with ascent:

@isazi : I just have the message : “Processed 1 file”

if fit file is not “perfect”, following fit sdk rules, it may happen. QS is able to process it, but SA doesn’t accept it, but without an error return (to QS).

So how do you modify .ift files so that they are accepted?
How complicated it is when before it was so easy with MovesCount! When will a real update of the application be made?

Personally, and really personnaly, i modify them manually (decode fit to csv, edit and recode).
it is long and not convenient, but i know what is inside. I was hoping to use other tools like you to crop, change field like altitude, HR, etc…, but export is not perfect as well. So need to also tweak it manually.
It is not really Suunto’s fault, as they seem to follow strictely the fit sdk feature, it is more these softs that not export totally according to this (from my personnal findings).
There are many posts in this forum, requesting crop feature/ascent edit, etc… directly in Suunto’s ecosystem, i would vote for them, but editing fit files : i find it not so easy.

[Remrem]

@mff73 said in How to import move with ascent:

Personally, and really personnaly, i modify them manually (decode fit to csv, edit and recode).
it is long and not convenient, but i know what is inside. I was hoping to use other tools like you to crop, change field like altitude, HR, etc…, but export is not perfect as well. So need to also tweak it manually.
It is not really Suunto’s fault, as they seem to follow strictely the fit sdk feature, it is more these softs that not export totally according to this (from my personnal findings).
There are many posts in this forum, requesting crop feature/ascent edit, etc… directly in Suunto’s ecosystem, i would vote for them, but editing fit files : i find it not so easy.

Thank you for your reply.
I tried to modify them manually but without success.
How do you do ? Do you change every point?

[Mff73]

@Remrem
Download fitsdk from Web, find fitcsv tool in it and read and learn how it works, how fit files are structured.
Decode fit file into csv, find total_ascent message and change value and recode csv to a fit file, and pray .
But not very convenient for sure, and maybe long journey to learn this and discover all issues that may happen after bad file modification.
If someone has a real other working solution, I also take it .

[Brad_Olwin]

@remrem I have had luck with this set of tools. https://www.fitfiletools.com/#/top

[Remrem]

@brad_olwin said in How to import move with ascent:

@remrem I have had luck with this set of tools. https://www.fitfiletools.com/#/top

Thanks for your review.
However in the tools none allows to modify the ascent.

[Remrem]

@mff73 said in How to import move with ascent:

@Remrem
Download fitsdk from Web, find fitcsv tool in it and read and learn how it works, how fit files are structured.
Decode fit file into csv, find total_ascent message and change value and recode csv to a fit file, and pray .
But not very convenient for sure, and maybe long journey to learn this and discover all issues that may happen after bad file modification.
If someone has a real other working solution, I also take it .

Thanks for your response.
Fortunately Garmin is developing tools !!

[Dimitrios Kanellopoulos]

@remrem what do you mean?

[Brad_Olwin]

@remrem said in How to import move with ascent:

@brad_olwin said in How to import move with ascent:

@remrem I have had luck with this set of tools. https://www.fitfiletools.com/#/top

Thanks for your review.
However in the tools none allows to modify the ascent.

How about going into Training Peaks or Strava, correct the elevation with their tools, export the fit file, then you can import via QS as I said, not hard and fast

[Remrem]

@dimitrios-kanellopoulos : That we are reduced to using Garmin software to compensate for the lack of functionality of the Suunto application.

@Brad_Olwin : I’m going to try. Thank you.

[Mff73]

@brad_olwin said in How to import move with ascent:

@remrem said in How to import move with ascent:

@brad_olwin said in How to import move with ascent:

@remrem I have had luck with this set of tools. https://www.fitfiletools.com/#/top

Thanks for your review.
However in the tools none allows to modify the ascent.

How about going into Training Peaks or Strava, correct the elevation with their tools, export the fit file, then you can import via QS as I said, not hard and fast

Hi Brad,
Correcting ascent in Strava is OK, but how to export the fit file with corrected values?
Only option I may find is export original… and GPX.
And original is… Original .

[Mff73]

and tryied TrainingPeaks for elevation correction -> Premium account needed just to correct. No go for me

[margusl]

@mff73 , Runalyze provides number of elevation correction methods and lets you export fit. Though not sure what/if other data from the original would be stripped.

[Mff73]

@margusl said in How to import move with ascent:

@mff73 , Runalyze provides number of elevation correction methods and lets you export fit. Though not sure what/if other data from the original would be stripped.

Thanks, but…
Unless I don’t do it right, RA has effectively lots of altitude corrections, but fit export seems to export original fit file and not one generated with altitude corrections, nor ascent/descent.

[margusl]

@mff73 , oh… that’s somewhat surprising.
But yeah. they apparently don’t do any fit encoding and fit exports are only available for activities that were imported as fit-files (in orther words - only fit-files there are originals). Sorry.

[pilleus]

Go to https://gotoes.org/strava/Combine_GPX_TCX_FIT_Files.php, insert your fit.file and after donating you can edit all data and download the corrected fit.file and upload it via QS into your Suunto app.

I have done this several times with a tcx.file of my Casio and wrong ascent data.