will do and thanks :) i would like to get involved myself but my pythin skills aren't up to much right now
On 03/24/2012 04:30 PM, David García Granda wrote: > Hi Lauren, > > Thank you for your interest and feedback. > >> hope this is the right place to be filing bug reports >> >> i am running 1.9.2-dev on debian wheezy 64bit >> >> i have a garmin forerunner 205 >> >> i use garmin-tools to export the tracks as .gmn files >> >> i then use garmin_gpx to convert into .gpx files >> >> when i try to import one of these .gpx files the date / time of the run >> is incorrect >> >> what i have discovered is that garmin_gpx writes the following at the >> head of each file: >> >> <?xml version="1.0" encoding="UTF-8"?> >> <gpx version="1.1" >> creator="Garmin Forerunner Tools - http://garmintools.googlecode.com"; >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >> xmlns:gpxtpx="http://www.garmin.com/xmlschemas/TrackPointExtension/v1"; >> xmlns="http://www.topografix.com/GPX/1/1"; >> xsi:schemaLocation="http://www.topografix.com/GPX/1/1 >> http://www.topografix.com/GPX/1/1/gpx.xsd >> http://www.garmin.com/xmlschemas/TrackPointExtension/v1 >> http://www8.garmin.com/xmlschemas/TrackPointExtensionv1.xsd";> >> <time>2012-01-14T10:26:28Z</time> >> <bounds minlat="-34.101196" minlon="18.472706" maxlat="-34.094719" >> maxlon="18.479521" /> >> <trk> >> <trkseg> >> >> the important data point here is the<time></time> entry - it is set to >> the date / time of the gpx export NOT the date / time of the run >> >> it appears as though pytrainer's gpx import uses the first<time> tag to >> determine the date/time of the activity even though it is not contained >> within a<trkseg> >> >> i believe this to be an error in how pytrainer imports gpx files >> >> i could not find any reference to the<time> tag in the head section >> when i looked in the gpx file standard but even so i would think >> pytrainer should only look for the first<time> tag *within* the >> <trkseg> sections >> >> if i am misunderstanding the gpx spec and laying the problem at >> pytrainer when it should be the garmin_tools issue to fix please forgive me > > Unfortunately setting import datetime info in time tag seems an issue > related to garmintools (http://code.google.com/p/garmintools/) so the > best option would be to file a bug there. > > Anyway you are right that maybe pytrainer should check if reference > provided in time tag is contained (or may match) in time tag for any > trackseg (or trackpoint) in the provided file. We definitely have room > for improvement. Do you Lauren mind raising a ticket in trac > (http://sourceforge.net/apps/trac/pytrainer/)? > > Thanks! > > David ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Pytrainer-devel mailing list Pytrainer-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytrainer-devel
