How to import move with ascent
-
Hello, I cannot correct the registration errors on my watch.
I have several moves, with inconsistent elevation values.I tried to correct the moves by uploading the .fit file with the application. Then as indicated in this forum, I tried to modify it with Land, Iphigénie, VisoRando. Then re-import it via SportTracker.
But each time the move does not contain a difference in height.
Thanks in advance.
Have a good day. -
@remrem you can import FIT files using quantified-self.io
-
Thank you for your reply.
I have connected quantified-self.io to my Suunto account.
Next, I tried to edit the inconsistent value of a move’s ascension and re-import a modified .fit file.
This without results in the Suunto app.It’s really heavy this lack of functionality of the Suunto app!
-
@remrem I meant you can use QS to import FIT files to SA, but you need to edit the FIT file somewhere else.
-
@isazi said in How to import move with ascent:
@remrem I meant you can use QS to import FIT files to SA, but you need to edit the FIT file somewhere else.
Yes. Of course. That’s what I did…
-
@remrem if you want you can post here the file and I (or someone else) can try.
-
@isazi I think it takes a long time to sync all the moves.
It is not finished because the moves appear gradually in Quantified Self. -
@remrem it does take time to sync past moves, but you don’t really have to do it if you just want to upload something to SA. Just connect QS to Suunto, have your edited FIT file (using what you said before “Land, Iphigénie, VisoRando”), and click here
you can then select the file on your computer and the activity will end up on Suunto App.
-
@isazi : Hello,
I modified the .fit file.
I then imported it into QS.
But no activity is added to my account.Thanks.
-
@remrem with no error from QS?
-
@isazi : I just have the message : “Processed 1 file”
-
@remrem then refresh Suunto App, the activity should get there.
-
@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).
-
@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?
-
@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. -
@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? -
@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. -
@remrem I have had luck with this set of tools. https://www.fitfiletools.com/#/top
-
@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. -
@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 !!
