Open GoogleCodeExporter opened 9 years ago
Hi,
Can't see anything wrong with the XML files you attached. They're both valid
XML.
Concerning the problems you reported on this other forum:
* The first problem was that the file was truncated/incomplete. Not sure where
that came from, it might be a bug in the GPX export of OSMTracker, although
that seems unlikely since it never has been reported and the export code hasn't
changed much. It could also be due to a problem when you transferred the file
from your phone.
* The second problem is that the software you import your files on (Basecamp?)
doesn't support the SPEED extension that's attached to each track point.
There's not much we can do about that, either this 3rd party app. needs to
support this extension, or we need to make an option in OSMTracker to not write
the SPEED when exporting GPX files. I'm not ready/willing to develop that, but
I'd happily take a patch.
Cheers,
Nico
Original comment by nicolas@guillaumin.me
on 17 Oct 2013 at 10:31
thanks for the info. basecamp is provided by garmin so there should be
heaps of people using it.
Original comment by gvmalay...@gmail.com
on 17 Oct 2013 at 2:18
just to let u know in http://wiki.openstreetmap.org/wiki/Android, under
"OpenStreetMap editing features" there is an error in the info... it states
that osmtracker cannot upload to OSM.
Original comment by gvmalay...@gmail.com
on 18 Oct 2013 at 3:08
Thanks, I fixed it.
Original comment by nicolas@guillaumin.me
on 18 Oct 2013 at 4:50
Please take note of http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727768,
which is about an import error to pytrainer. The pytrainer dev says:
It seems that despite valid xml format (syntax), gpx file does not
valid provided schemas.
According to 1.1 gpx schema, you can add extend GPX by adding your own
elements from another schema in "extensions" (see
http://www.topografix.com/GPX/1/1/#type_extensionsType), but we miss
the definition of the element provided. For example, pytrainer adds
heartrate data using this feature:
<trkpt lat="43.5407522" lon="-5.6508772">
<ele>14.4000000</ele>
<time>2013-07-17T07:53:19Z</time>
<extensions>
<gpxdata:hr>101</gpxdata:hr>
</extensions>
</trkpt>
Original comment by johan...@rohr.org
on 3 Nov 2013 at 11:42
Original issue reported on code.google.com by
gvmalay...@gmail.com
on 17 Oct 2013 at 3:32Attachments: