This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Creating a course from GPX file- timing issues

Former Member over 6 years ago

I'm using firmware 6.44.
I noticed yesterday that if I create a course from ride history on my garmin the timing ahead/behind works fine.
If I load a gpx file with timestamps in to the new files folder, I can navigate the course but I don't get time ahead or behind.
I opened the fit file created by my garmin and the issue appears to be in the header data. My garmin creates a field of "Course Capabilities" which is set to 515. This somehow prevents the use of course timing.
If I delete this entry then the course file works ok.
I'm not sure when this bug was introduced as I don't use courses all that often

0 aweatherall over 6 years ago

Can you provide a sample GPX file that you see this with?

0 aweatherall over 6 years ago

Where are you getting the GPX files from? Is there a reason you are using GPX versus TCX?

0 aweatherall over 6 years ago

What tool/site was used to produce the GPX file. The header in the file instructs the Edge to process it that way.

0 Former Member over 6 years ago

It is a 3rd party strava segment app simply called strava segments (I don't have a link at the moment)
What is it specifically that you see in the GPX header that does this?

0 aweatherall over 6 years ago

There is nothing wrong with the GPX file. I tried the same file on the 520 and 1000 and both units created a FIT file with course capabilities of 768 and not 515 as produced on the 1030. This looks like a bug on the 1030. I have submitted it to Garmin.

0 Former Member over 6 years ago

Thanks Alan.
Just as an aside is there a list of what how the course capabilities perform? ie what is 768 vs 515?
I had some old course files with capabilities set to 3 so when I changed the 515 to 3 and reversed from csv to fit they worked

0 aweatherall over 6 years ago

From the profile information for the FITSDK. I'm not sure if these values are used as described below by the Edge. There maybe other settings on the unit that control the behavior.
[TABLE="border: 0, cellpadding: 0, cellspacing: 0"]
[TR]
[TD="width: 149"]course_capabilities[/TD]
[TD="width: 77"]uint32z[/TD]
[TD="width: 293"] [/TD]
[TD="width: 89"] [/TD]
[/TR]
[TR]
[TD="width: 149"] [/TD]
[TD] [/TD]
[TD="width: 293"]processed[/TD]
[TD]0x00000001[/TD]
[/TR]
[TR]
[TD="width: 149"] [/TD]
[TD] [/TD]
[TD="width: 293"]valid[/TD]
[TD]0x00000002[/TD]
[/TR]
[TR]
[TD="width: 149"] [/TD]
[TD] [/TD]
[TD="width: 293"]time[/TD]
[TD]0x00000004[/TD]
[/TR]
[TR]
[TD="width: 149"] [/TD]
[TD] [/TD]
[TD="width: 293"]distance[/TD]
[TD]0x00000008[/TD]
[/TR]
[TR]
[TD="width: 149"] [/TD]
[TD] [/TD]
[TD="width: 293"]position[/TD]
[TD]0x00000010[/TD]
[/TR]
[TR]
[TD="width: 149"] [/TD]
[TD] [/TD]
[TD="width: 293"]heart_rate[/TD]
[TD]0x00000020[/TD]
[/TR]
[TR]
[TD="width: 149"] [/TD]
[TD] [/TD]
[TD="width: 293"]power[/TD]
[TD]0x00000040[/TD]
[/TR]
[TR]
[TD="width: 149"] [/TD]
[TD] [/TD]
[TD="width: 293"]cadence[/TD]
[TD]0x00000080[/TD]
[/TR]
[TR]
[TD="width: 149"] [/TD]
[TD] [/TD]
[TD="width: 293"]training[/TD]
[TD]0x00000100[/TD]
[/TR]
[TR]
[TD="width: 149"] [/TD]
[TD] [/TD]
[TD="width: 293"]navigation[/TD]
[TD]0x00000200[/TD]
[/TR]
[TR]
[TD="width: 149"] [/TD]
[TD] [/TD]
[TD="width: 293"]bikeway[/TD]
[TD]0x00000400[/TD]
[/TR]
[/TABLE]

0 Former Member over 6 years ago

Thanks Alan.
I feel like I was both lazy and dumb for that. Lazy for not looking and dumb because I wouldn't have immediately converted to hex.