On Sun, Oct 24, 2010 at 5:03 PM, tsteven4
gpsbabel remembers the
xsi_schema_location from a read and uses it on a write, but
does not remember the gpx version. gpx.c has a comment:
It reads schema loc to handle additional extension schemas.
Version was to be triggered by the option on the GPX writer.
gpsbabel -i gpx -f reference/expertgps.gpx -o gpx -F
Yes, converting 1.1 to 1.0 generally doesn't work.
Also, it appears the
static variable gpx_version is never used. It is set in
gpx.c and the related file garmin_device_xml.h.
It was an idea that I started but didn't finish.
I realize that I could
have forced the output version by using the gpxver option,
gpsbabel -i gpx -f reference/expertgps.gpx -o
gpx,gpxver="1.1" -F xx.gpx
However, this would the user to know the input file gpx
In the wild, GPX 1.1 is still relatively rare, probably
because of its incompatibilities with 1.0.
The mixing of 1.0 and 1.1 is full of all kinds of hazards
that I just don't have my head around. If you have merge
files of different GPX versions and both use extensions (the
extension scheme is different for 1.0 and 1.1) what's a
sensible thing to output? Converting unknown extensions is
Is any bug tracking
system other than this mailing list in use for gpsbabel?
This is it. When we had a bug tracking system, it was
consistently filled with nonsense. You've seen the
consistently poor reports we get on the list; the bug tracker
was far worse.