Thread: [Gpsbabel-misc] Wrong convertion from GPX to Garmin Traning Center (TCX)
Brought to you by:
robertl
From: Thibault R. <tr...@om...> - 2009-12-15 21:14:31
|
Hi all, Following the question of Maarten, here is the "issue" I managed to successfully convert GPX to TCX with gpsbabel few months ago and now impossible to do it again ! When I import the converted file in Garmin Training Center, it says that the file is not correct... But with TCX converter it works... and when I compare, TCX converter adds more info in the file ! Here is all the files : www.omch.ch/gpx-to-tcx.zip Example : GPS BABEL file: <Trackpoint> <Time>2009-12-15T17:01:56Z</Time> <Position> <LatitudeDegrees>46.186984</LatitudeDegrees> <LongitudeDegrees>6.138139</LongitudeDegrees> </Position> <AltitudeMeters>434.170000</AltitudeMeters> <HeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t"> <Value>107</Value> </HeartRateBpm> </Trackpoint> TCX converter file: <Trackpoint> <Time>2009-12-15T17:01:56Z</Time> <Position> <LatitudeDegrees>46.186984</LatitudeDegrees> <LongitudeDegrees>6.138139</LongitudeDegrees> </Position> <AltitudeMeters>434.17</AltitudeMeters> <DistanceMeters>37.71744</DistanceMeters> <HeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t"> <Value>107</Value> </HeartRateBpm> <Cadence>0</Cadence> <SensorState>Absent</SensorState> </Trackpoint> We have : - DistanceMeters - Cadence - SensorState missing in the GPS Babel file... it's probably the problem. and the TCX converter software adds this in the end of the file: <Creator xsi:type="Device_t"> <Name>EDGE305</Name> <UnitId>1111111111</UnitId> <ProductID>450</ProductID> <Version> <VersionMajor>2</VersionMajor> <VersionMinor>90</VersionMinor> <BuildMajor>0</BuildMajor> <BuildMinor>0</BuildMinor> </Version> </Creator> </Course> </Courses> <Author xsi:type="Application_t"> <Name>Garmin Training Center(TM)</Name> <Build> <Version> <VersionMajor>3</VersionMajor> <VersionMinor>2</VersionMinor> <BuildMajor>3</BuildMajor> <BuildMinor>0</BuildMinor> </Version> <Type>Release</Type> <Time>Mar 15 2007, 12:31:45</Time> <Builder>SQA</Builder> </Build> <LangID>IT</LangID> <PartNumber>006-A0119-00</PartNumber> </Author> </TrainingCenterDatabase> So if you have time to kill next Sunday :) Thibault |
From: Robert L. <rob...@gp...> - 2009-12-16 05:50:18
|
On Tue, Dec 15, 2009 at 3:14 PM, Thibault Roulet <tr...@om...> wrote: > Hi all, > Following the question of Maarten, here is the "issue" > > I managed to successfully convert GPX to TCX with gpsbabel few months > ago and now impossible to do it again ! > When I import the converted file in Garmin Training Center, it says that > the file is not correct... > But with TCX converter it works... and when I compare, TCX converter > adds more info in the file ! > "More information" and "more correct" aren't necessarily related. I could encode the color of my socks on any given day into a file. That's more information, but I'd be surprised if any program rejects it as "not correct" because that's not present. > Here is all the files : www.omch.ch/gpx-to-tcx.zip > > Example : > GPS BABEL file: > <Trackpoint> > <Time>2009-12-15T17:01:56Z</Time> > <Position> > <LatitudeDegrees>46.186984</LatitudeDegrees> > <LongitudeDegrees>6.138139</LongitudeDegrees> > </Position> > <AltitudeMeters>434.170000</AltitudeMeters> > <HeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t"> > <Value>107</Value> > </HeartRateBpm> > </Trackpoint> > > TCX converter file: > <Trackpoint> > <Time>2009-12-15T17:01:56Z</Time> > <Position> > <LatitudeDegrees>46.186984</LatitudeDegrees> > <LongitudeDegrees>6.138139</LongitudeDegrees> > </Position> > <AltitudeMeters>434.17</AltitudeMeters> > <DistanceMeters>37.71744</DistanceMeters> > <HeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t"> > <Value>107</Value> > </HeartRateBpm> > <Cadence>0</Cadence> > <SensorState>Absent</SensorState> > </Trackpoint> > > We have : > - DistanceMeters > - Cadence > - SensorState > missing in the GPS Babel file... it's probably the problem. > I haven't looked at the XSD, but those seem "clearly" optional at first blush. DistanceMeters is trivially computable based on successive position fixes. You may or may not have sensors and the absent sensor state clearly means you can't report a sensible Cadence. Can you verify that the absence of these (we can make them up if we don't have them, but that seems kind of dumb) is the deal-breaker? > > and the TCX converter software adds this in the end of the file: > <Creator xsi:type="Device_t"> > <Name>EDGE305</Name> > <UnitId>1111111111</UnitId> > <ProductID>450</ProductID> > <Version> > <VersionMajor>2</VersionMajor> > <VersionMinor>90</VersionMinor> > <BuildMajor>0</BuildMajor> > <BuildMinor>0</BuildMinor> > </Version> > </Creator> > </Course> > </Courses> > <Author xsi:type="Application_t"> > <Name>Garmin Training Center(TM)</Name> > <Build> > <Version> > <VersionMajor>3</VersionMajor> > <VersionMinor>2</VersionMinor> > <BuildMajor>3</BuildMajor> > <BuildMinor>0</BuildMinor> > </Version> > <Type>Release</Type> > <Time>Mar 15 2007, 12:31:45</Time> > <Builder>SQA</Builder> > </Build> > <LangID>IT</LangID> > <PartNumber>006-A0119-00</PartNumber> > </Author> > </TrainingCenterDatabase> > > This entire section (angle bracket balancing aside) seems like busy work. Can you please reduce it to the smallest set of data that we have to forge for this program to work? > So if you have time to kill next Sunday :) > Yeah, right. :-) RJL > Thibault > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Gpsbabel-misc mailing list http://www.gpsbabel.org > Gps...@li... > To unsubscribe, change list options, or see archives, visit: > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc > |
From: Thibault R. <tr...@om...> - 2009-12-16 07:27:59
|
Okay I'll try with blue socks :-) So I will edit the TCX.C file to remove fields one by one and see if the training center is happy with that :) Thibault Robert Lipe a écrit : > > > On Tue, Dec 15, 2009 at 3:14 PM, Thibault Roulet <tr...@om... > <mailto:tr...@om...>> wrote: > > Hi all, > Following the question of Maarten, here is the "issue" > > I managed to successfully convert GPX to TCX with gpsbabel few months > ago and now impossible to do it again ! > When I import the converted file in Garmin Training Center, it > says that > the file is not correct... > But with TCX converter it works... and when I compare, TCX converter > adds more info in the file ! > > > "More information" and "more correct" aren't necessarily related. I > could encode the color of my socks on any given day into a file. > That's more information, but I'd be surprised if any program rejects > it as "not correct" because that's not present. > > > > > Here is all the files : www.omch.ch/gpx-to-tcx.zip > <http://www.omch.ch/gpx-to-tcx.zip> > > Example : > GPS BABEL file: > <Trackpoint> > <Time>2009-12-15T17:01:56Z</Time> > <Position> > <LatitudeDegrees>46.186984</LatitudeDegrees> > <LongitudeDegrees>6.138139</LongitudeDegrees> > </Position> > <AltitudeMeters>434.170000</AltitudeMeters> > <HeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t"> > <Value>107</Value> > </HeartRateBpm> > </Trackpoint> > > TCX converter file: > <Trackpoint> > <Time>2009-12-15T17:01:56Z</Time> > <Position> > <LatitudeDegrees>46.186984</LatitudeDegrees> > <LongitudeDegrees>6.138139</LongitudeDegrees> > </Position> > <AltitudeMeters>434.17</AltitudeMeters> > <DistanceMeters>37.71744</DistanceMeters> > <HeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t"> > <Value>107</Value> > </HeartRateBpm> > <Cadence>0</Cadence> > <SensorState>Absent</SensorState> > </Trackpoint> > > We have : > - DistanceMeters > - Cadence > - SensorState > missing in the GPS Babel file... it's probably the problem. > > > I haven't looked at the XSD, but those seem "clearly" optional at > first blush. DistanceMeters is trivially computable based on > successive position fixes. > > You may or may not have sensors and the absent sensor state clearly > means you can't report a sensible Cadence. Can you verify that the > absence of these (we can make them up if we don't have them, but that > seems kind of dumb) is the deal-breaker? > > > > > > > and the TCX converter software adds this in the end of the file: > <Creator xsi:type="Device_t"> > <Name>EDGE305</Name> > <UnitId>1111111111</UnitId> > <ProductID>450</ProductID> > <Version> > <VersionMajor>2</VersionMajor> > <VersionMinor>90</VersionMinor> > <BuildMajor>0</BuildMajor> > <BuildMinor>0</BuildMinor> > </Version> > </Creator> > </Course> > </Courses> > <Author xsi:type="Application_t"> > <Name>Garmin Training Center(TM)</Name> > <Build> > <Version> > <VersionMajor>3</VersionMajor> > <VersionMinor>2</VersionMinor> > <BuildMajor>3</BuildMajor> > <BuildMinor>0</BuildMinor> > </Version> > <Type>Release</Type> > <Time>Mar 15 2007, 12:31:45</Time> > <Builder>SQA</Builder> > </Build> > <LangID>IT</LangID> > <PartNumber>006-A0119-00</PartNumber> > </Author> > </TrainingCenterDatabase> > > This entire section (angle bracket balancing aside) seems like busy > work. Can you please reduce it to the smallest set of data that we > have to forge for this program to work? > > > > > So if you have time to kill next Sunday :) > > > Yeah, right. :-) > > RJL > > > > > > Thibault > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution > fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Gpsbabel-misc mailing list http://www.gpsbabel.org > Gps...@li... > <mailto:Gps...@li...> > To unsubscribe, change list options, or see archives, visit: > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc > > |
From: Thibault R. <tr...@om...> - 2009-12-25 22:22:42
|
Hi all, I found the problem ! <AverageHeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t"> <Value>142.632</Value> </AverageHeartRateBpm> <MaximumHeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t"> <Value>177.234547</Value> </MaximumHeartRateBpm> These values must be integers ! My god, I tried to remove everything before to test that ! :-) So, in the end you have to round it to <AverageHeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t"> <Value>143</Value> </AverageHeartRateBpm> <MaximumHeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t"> <Value>177</Value> </MaximumHeartRateBpm> and it works ! Thibault On 16.12.2009 08:27, Thibault Roulet wrote: > Okay I'll try with blue socks :-) > > So I will edit the TCX.C file to remove fields one by one and see if the > training center is happy with that :) > > Thibault > > Robert Lipe a écrit : > >> >> On Tue, Dec 15, 2009 at 3:14 PM, Thibault Roulet<tr...@om... >> <mailto:tr...@om...>> wrote: >> >> Hi all, >> Following the question of Maarten, here is the "issue" >> >> I managed to successfully convert GPX to TCX with gpsbabel few months >> ago and now impossible to do it again ! >> When I import the converted file in Garmin Training Center, it >> says that >> the file is not correct... >> But with TCX converter it works... and when I compare, TCX converter >> adds more info in the file ! >> >> >> "More information" and "more correct" aren't necessarily related. I >> could encode the color of my socks on any given day into a file. >> That's more information, but I'd be surprised if any program rejects >> it as "not correct" because that's not present. >> >> >> >> >> Here is all the files : www.omch.ch/gpx-to-tcx.zip >> <http://www.omch.ch/gpx-to-tcx.zip> >> >> Example : >> GPS BABEL file: >> <Trackpoint> >> <Time>2009-12-15T17:01:56Z</Time> >> <Position> >> <LatitudeDegrees>46.186984</LatitudeDegrees> >> <LongitudeDegrees>6.138139</LongitudeDegrees> >> </Position> >> <AltitudeMeters>434.170000</AltitudeMeters> >> <HeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t"> >> <Value>107</Value> >> </HeartRateBpm> >> </Trackpoint> >> >> TCX converter file: >> <Trackpoint> >> <Time>2009-12-15T17:01:56Z</Time> >> <Position> >> <LatitudeDegrees>46.186984</LatitudeDegrees> >> <LongitudeDegrees>6.138139</LongitudeDegrees> >> </Position> >> <AltitudeMeters>434.17</AltitudeMeters> >> <DistanceMeters>37.71744</DistanceMeters> >> <HeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t"> >> <Value>107</Value> >> </HeartRateBpm> >> <Cadence>0</Cadence> >> <SensorState>Absent</SensorState> >> </Trackpoint> >> >> We have : >> - DistanceMeters >> - Cadence >> - SensorState >> missing in the GPS Babel file... it's probably the problem. >> >> >> I haven't looked at the XSD, but those seem "clearly" optional at >> first blush. DistanceMeters is trivially computable based on >> successive position fixes. >> >> You may or may not have sensors and the absent sensor state clearly >> means you can't report a sensible Cadence. Can you verify that the >> absence of these (we can make them up if we don't have them, but that >> seems kind of dumb) is the deal-breaker? >> >> >> >> >> >> >> and the TCX converter software adds this in the end of the file: >> <Creator xsi:type="Device_t"> >> <Name>EDGE305</Name> >> <UnitId>1111111111</UnitId> >> <ProductID>450</ProductID> >> <Version> >> <VersionMajor>2</VersionMajor> >> <VersionMinor>90</VersionMinor> >> <BuildMajor>0</BuildMajor> >> <BuildMinor>0</BuildMinor> >> </Version> >> </Creator> >> </Course> >> </Courses> >> <Author xsi:type="Application_t"> >> <Name>Garmin Training Center(TM)</Name> >> <Build> >> <Version> >> <VersionMajor>3</VersionMajor> >> <VersionMinor>2</VersionMinor> >> <BuildMajor>3</BuildMajor> >> <BuildMinor>0</BuildMinor> >> </Version> >> <Type>Release</Type> >> <Time>Mar 15 2007, 12:31:45</Time> >> <Builder>SQA</Builder> >> </Build> >> <LangID>IT</LangID> >> <PartNumber>006-A0119-00</PartNumber> >> </Author> >> </TrainingCenterDatabase> >> >> This entire section (angle bracket balancing aside) seems like busy >> work. Can you please reduce it to the smallest set of data that we >> have to forge for this program to work? >> >> >> >> >> So if you have time to kill next Sunday :) >> >> >> Yeah, right. :-) >> >> RJL >> >> >> >> >> >> Thibault >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution >> fast and easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> Gpsbabel-misc mailing list http://www.gpsbabel.org >> Gps...@li... >> <mailto:Gps...@li...> >> To unsubscribe, change list options, or see archives, visit: >> https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc >> >> >> > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Gpsbabel-misc mailing list http://www.gpsbabel.org > Gps...@li... > To unsubscribe, change list options, or see archives, visit: > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc > |
From: Robert L. <rob...@gp...> - 2010-01-09 15:10:14
|
Not sure how you got a non-integer max in there, but I've tweaked the code to only write integer values in these two fields. Thanx for the groundwork. RJL On Fri, Dec 25, 2009 at 4:21 PM, Thibault Roulet <tr...@om...> wrote: > Hi all, > > I found the problem ! > > <AverageHeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t"> > <Value>142.632</Value> > </AverageHeartRateBpm> > <MaximumHeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t"> > <Value>177.234547</Value> > </MaximumHeartRateBpm> > > These values must be integers ! > My god, I tried to remove everything before to test that ! :-) > > So, in the end you have to round it to > <AverageHeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t"> > <Value>143</Value> > </AverageHeartRateBpm> > <MaximumHeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t"> > <Value>177</Value> > </MaximumHeartRateBpm> > > and it works ! > > Thibault > > > > > On 16.12.2009 08:27, Thibault Roulet wrote: > >> Okay I'll try with blue socks :-) >> >> So I will edit the TCX.C file to remove fields one by one and see if the >> training center is happy with that :) >> >> Thibault >> >> Robert Lipe a écrit : >> >> >>> >>> On Tue, Dec 15, 2009 at 3:14 PM, Thibault Roulet<tr...@om... >>> <mailto:tr...@om...>> wrote: >>> >>> Hi all, >>> Following the question of Maarten, here is the "issue" >>> >>> I managed to successfully convert GPX to TCX with gpsbabel few months >>> ago and now impossible to do it again ! >>> When I import the converted file in Garmin Training Center, it >>> says that >>> the file is not correct... >>> But with TCX converter it works... and when I compare, TCX converter >>> adds more info in the file ! >>> >>> >>> "More information" and "more correct" aren't necessarily related. I >>> could encode the color of my socks on any given day into a file. >>> That's more information, but I'd be surprised if any program rejects >>> it as "not correct" because that's not present. >>> >>> >>> >>> >>> Here is all the files : www.omch.ch/gpx-to-tcx.zip >>> <http://www.omch.ch/gpx-to-tcx.zip> >>> >>> Example : >>> GPS BABEL file: >>> <Trackpoint> >>> <Time>2009-12-15T17:01:56Z</Time> >>> <Position> >>> <LatitudeDegrees>46.186984</LatitudeDegrees> >>> <LongitudeDegrees>6.138139</LongitudeDegrees> >>> </Position> >>> <AltitudeMeters>434.170000</AltitudeMeters> >>> <HeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t"> >>> <Value>107</Value> >>> </HeartRateBpm> >>> </Trackpoint> >>> >>> TCX converter file: >>> <Trackpoint> >>> <Time>2009-12-15T17:01:56Z</Time> >>> <Position> >>> <LatitudeDegrees>46.186984</LatitudeDegrees> >>> <LongitudeDegrees>6.138139</LongitudeDegrees> >>> </Position> >>> <AltitudeMeters>434.17</AltitudeMeters> >>> <DistanceMeters>37.71744</DistanceMeters> >>> <HeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t"> >>> <Value>107</Value> >>> </HeartRateBpm> >>> <Cadence>0</Cadence> >>> <SensorState>Absent</SensorState> >>> </Trackpoint> >>> >>> We have : >>> - DistanceMeters >>> - Cadence >>> - SensorState >>> missing in the GPS Babel file... it's probably the problem. >>> >>> >>> I haven't looked at the XSD, but those seem "clearly" optional at >>> first blush. DistanceMeters is trivially computable based on >>> successive position fixes. >>> >>> You may or may not have sensors and the absent sensor state clearly >>> means you can't report a sensible Cadence. Can you verify that the >>> absence of these (we can make them up if we don't have them, but that >>> seems kind of dumb) is the deal-breaker? >>> >>> >>> >>> >>> >>> >>> and the TCX converter software adds this in the end of the file: >>> <Creator xsi:type="Device_t"> >>> <Name>EDGE305</Name> >>> <UnitId>1111111111</UnitId> >>> <ProductID>450</ProductID> >>> <Version> >>> <VersionMajor>2</VersionMajor> >>> <VersionMinor>90</VersionMinor> >>> <BuildMajor>0</BuildMajor> >>> <BuildMinor>0</BuildMinor> >>> </Version> >>> </Creator> >>> </Course> >>> </Courses> >>> <Author xsi:type="Application_t"> >>> <Name>Garmin Training Center(TM)</Name> >>> <Build> >>> <Version> >>> <VersionMajor>3</VersionMajor> >>> <VersionMinor>2</VersionMinor> >>> <BuildMajor>3</BuildMajor> >>> <BuildMinor>0</BuildMinor> >>> </Version> >>> <Type>Release</Type> >>> <Time>Mar 15 2007, 12:31:45</Time> >>> <Builder>SQA</Builder> >>> </Build> >>> <LangID>IT</LangID> >>> <PartNumber>006-A0119-00</PartNumber> >>> </Author> >>> </TrainingCenterDatabase> >>> >>> This entire section (angle bracket balancing aside) seems like busy >>> work. Can you please reduce it to the smallest set of data that we >>> have to forge for this program to work? >>> >>> >>> >>> >>> So if you have time to kill next Sunday :) >>> >>> >>> Yeah, right. :-) >>> >>> RJL >>> >>> >>> >>> >>> >>> Thibault >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.Net email is sponsored by the Verizon Developer Community >>> Take advantage of Verizon's best-in-class app development support >>> A streamlined, 14 day to market process makes app distribution >>> fast and easy >>> Join now and get one step closer to millions of Verizon customers >>> http://p.sf.net/sfu/verizon-dev2dev >>> _______________________________________________ >>> Gpsbabel-misc mailing list http://www.gpsbabel.org >>> Gps...@li... >>> <mailto:Gps...@li...> >>> To unsubscribe, change list options, or see archives, visit: >>> https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc >>> >>> >>> >>> >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and >> easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> Gpsbabel-misc mailing list http://www.gpsbabel.org >> Gps...@li... >> To unsubscribe, change list options, or see archives, visit: >> https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc >> >> > |
From: Thibault R. <tr...@om...> - 2010-01-09 18:11:06
|
Thanks to you :-) Thibault Robert Lipe wrote: > Not sure how you got a non-integer max in there, but I've tweaked the > code to only write integer values in these two fields. Thanx for the > groundwork. > > RJL > > On Fri, Dec 25, 2009 at 4:21 PM, Thibault Roulet <tr...@om... > <mailto:tr...@om...>> wrote: > > Hi all, > > I found the problem ! > > <AverageHeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t"> > <Value>142.632</Value> > </AverageHeartRateBpm> > <MaximumHeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t"> > <Value>177.234547</Value> > </MaximumHeartRateBpm> > > These values must be integers ! > My god, I tried to remove everything before to test that ! :-) > > So, in the end you have to round it to > <AverageHeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t"> > <Value>143</Value> > </AverageHeartRateBpm> > <MaximumHeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t"> > <Value>177</Value> > </MaximumHeartRateBpm> > > and it works ! > > Thibault > > > > > On 16.12.2009 08:27, Thibault Roulet wrote: > > Okay I'll try with blue socks :-) > > So I will edit the TCX.C file to remove fields one by one and > see if the > training center is happy with that :) > > Thibault > > Robert Lipe a écrit : > > > > On Tue, Dec 15, 2009 at 3:14 PM, Thibault > Roulet<tr...@om... <mailto:tr...@om...> > <mailto:tr...@om... <mailto:tr...@om...>>> wrote: > > Hi all, > Following the question of Maarten, here is the "issue" > > I managed to successfully convert GPX to TCX with > gpsbabel few months > ago and now impossible to do it again ! > When I import the converted file in Garmin Training > Center, it > says that > the file is not correct... > But with TCX converter it works... and when I compare, > TCX converter > adds more info in the file ! > > > "More information" and "more correct" aren't necessarily > related. I > could encode the color of my socks on any given day into a > file. > That's more information, but I'd be surprised if any > program rejects > it as "not correct" because that's not present. > > > > > Here is all the files : www.omch.ch/gpx-to-tcx.zip > <http://www.omch.ch/gpx-to-tcx.zip> > <http://www.omch.ch/gpx-to-tcx.zip> > > Example : > GPS BABEL file: > <Trackpoint> > <Time>2009-12-15T17:01:56Z</Time> > <Position> > <LatitudeDegrees>46.186984</LatitudeDegrees> > <LongitudeDegrees>6.138139</LongitudeDegrees> > </Position> > <AltitudeMeters>434.170000</AltitudeMeters> > <HeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t"> > <Value>107</Value> > </HeartRateBpm> > </Trackpoint> > > TCX converter file: > <Trackpoint> > <Time>2009-12-15T17:01:56Z</Time> > <Position> > <LatitudeDegrees>46.186984</LatitudeDegrees> > <LongitudeDegrees>6.138139</LongitudeDegrees> > </Position> > <AltitudeMeters>434.17</AltitudeMeters> > <DistanceMeters>37.71744</DistanceMeters> > <HeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t"> > <Value>107</Value> > </HeartRateBpm> > <Cadence>0</Cadence> > <SensorState>Absent</SensorState> > </Trackpoint> > > We have : > - DistanceMeters > - Cadence > - SensorState > missing in the GPS Babel file... it's probably the > problem. > > > I haven't looked at the XSD, but those seem "clearly" > optional at > first blush. DistanceMeters is trivially computable based on > successive position fixes. > > You may or may not have sensors and the absent sensor > state clearly > means you can't report a sensible Cadence. Can you > verify that the > absence of these (we can make them up if we don't have > them, but that > seems kind of dumb) is the deal-breaker? > > > > > > > and the TCX converter software adds this in the end of > the file: > <Creator xsi:type="Device_t"> > <Name>EDGE305</Name> > <UnitId>1111111111</UnitId> > <ProductID>450</ProductID> > <Version> > <VersionMajor>2</VersionMajor> > <VersionMinor>90</VersionMinor> > <BuildMajor>0</BuildMajor> > <BuildMinor>0</BuildMinor> > </Version> > </Creator> > </Course> > </Courses> > <Author xsi:type="Application_t"> > <Name>Garmin Training Center(TM)</Name> > <Build> > <Version> > <VersionMajor>3</VersionMajor> > <VersionMinor>2</VersionMinor> > <BuildMajor>3</BuildMajor> > <BuildMinor>0</BuildMinor> > </Version> > <Type>Release</Type> > <Time>Mar 15 2007, 12:31:45</Time> > <Builder>SQA</Builder> > </Build> > <LangID>IT</LangID> > <PartNumber>006-A0119-00</PartNumber> > </Author> > </TrainingCenterDatabase> > > This entire section (angle bracket balancing aside) seems > like busy > work. Can you please reduce it to the smallest set of > data that we > have to forge for this program to work? > > > > > So if you have time to kill next Sunday :) > > > Yeah, right. :-) > > RJL > > > > > > Thibault > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon > Developer Community > Take advantage of Verizon's best-in-class app > development support > A streamlined, 14 day to market process makes app > distribution > fast and easy > Join now and get one step closer to millions of > Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Gpsbabel-misc mailing list http://www.gpsbabel.org > Gps...@li... > <mailto:Gps...@li...> > <mailto:Gps...@li... > <mailto:Gps...@li...>> > To unsubscribe, change list options, or see archives, > visit: > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc > > > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution > fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Gpsbabel-misc mailing list http://www.gpsbabel.org > Gps...@li... > <mailto:Gps...@li...> > To unsubscribe, change list options, or see archives, visit: > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc > > > |