file import_network error : 6

63 views
Skip to first unread message

Bernard Rybicki

unread,
Sep 21, 2025, 2:48:53 PMSep 21
to golden-cheetah-users
Hi All,
many trouble this time with GC.
during import of a Garmin fit file, I have this error message :
Copie d'écran_20250921_203946.png
I think this is a problem with elevation data.
and, associated with that, the running power estimation is not provided because it is estimated with speed and elevation features.
Is it an issue with my fit file.
the last fit file import dated yesterday had no problem.
Bernard.

Nigel Laws

unread,
Sep 21, 2025, 4:27:52 PMSep 21
to golden-cheetah-users
I have never seen this error message previously, but it appeared today for the first time for me too.

The "Fit" file was imported eventually and all my elevation data is "weird" but the a power estimation i showing, but I notice my "Elevation Gain" shows "0" and "VAM" is also showing "0" which is odd as I was "flying" up the hills today because of the backwinds and should have been higher than normal. Everything yesterday was perfect and today was exactly the same rroute.

I shall try reimporting the file tomorrow if I get chance.

Rather than wait till tomorrow, just reimported the "Fit" file and it has imported all elevation data and VAM as it should be. So is it an issue where a server is or was down that Golden Cheetah gets elevation information from rather than useing what is recorded in the "Fit" file????

Ale Martinez

unread,
Sep 21, 2025, 5:13:13 PMSep 21
to golden-cheetah-users
El domingo, 21 de septiembre de 2025 a la(s) 5:27:52 p.m. UTC-3, laws...@gmail.com escribió:
I have never seen this error message previously, but it appeared today for the first time for me too.

The "Fit" file was imported eventually and all my elevation data is "weird" but the a power estimation i showing, but I notice my "Elevation Gain" shows "0" and "VAM" is also showing "0" which is odd as I was "flying" up the hills today because of the backwinds and should have been higher than normal. Everything yesterday was perfect and today was exactly the same rroute.

I shall try reimporting the file tomorrow if I get chance.

Rather than wait till tomorrow, just reimported the "Fit" file and it has imported all elevation data and VAM as it should be. So is it an issue where a server is or was down that Golden Cheetah gets elevation information from rather than useing what is recorded in the "Fit" file????

GoldenCheetah default behavior is to import elevation data from the imported file without connecting to an external server, If you are seen the error above is because YOU have enabled the Fix Elevation data processor to run automatically on import, this is not enabled by defautl, it is not recommended, and it is a bad idea IMHO.

Nigel Laws

unread,
Sep 22, 2025, 3:49:55 AMSep 22
to golden-cheetah-users
Quiet interestingly, "Fix Elevation" was enabled, I don't know how. But about a day before, "Golden Cheetah" started acting odd by just "Hanging" and I found when it eventually started, all my "perspectives" had gone so I have had to rebuild them best I can from memory. Then I found it would not save "Notes" for an activity as they would be missing when I restarted "Golden Cheetah" but, sometimes would show under "Activity" but not in the "Notes" related to the activity, it would be just blank.

But, it seems to be working OK this morning. This is "Build 5005"

Bernard Rybicki

unread,
Sep 22, 2025, 12:09:35 PMSep 22
to golden-cheetah-users
Hi,
I deleted my GC file and imported again my  original garmin fit file.
All is ok.
This error is surely a network issue with the server that is connected with the recalculation of elevation data.
I had by myself enable the automatic fix elevation data at import 
I disable it
I confirm that was a bad idea, prefer to fix elevation data manually only when is is necessary.
I've seen also the following :
original garmin fit file had no GPS errors at import.
After fix elevation data, GC indicated GPS errors (around 2000).
So ,i think that if elevation data are not very important, it is better not to fix elevation data.
Bernard
Reply all
Reply to author
Forward
0 new messages