or something like the command failing if you specify both waypoints and tracks at the same time but the layer has no waypoints - i.e.
Trying to use ogr2ogr produces ugly output, has annoying command line behaviour (IIRC needing '-overwrite' to overwrite an existing file but the command fails when -overwrite is used but it's a new file.
#Gpsbabel gpx option how to#
This work may be complete but I couldn't see how to write a new format for GPSBabel very easily (even if the current google_maps thing does a certain amount it's geojson->gpx not an export option for us). Unfortunately it seems GPSBabel is going through the transition to Qt framework.
#Gpsbabel gpx option plus#
I thought about supporting GeoJSON natively in Viking but that's a lot of coding effort, but could be plus point for Viking.Īlternatively putting in GeoJSON support into GPSBabel would help lots of other people. I've being thinking of adding in GeoJSON support some how but haven't found a simple/clean way to do. Trouble is what happens if include an option for GeoJSON, depending on how it's implemented. Putting it into a single export UI is probably very hard. The main sticking points are GPSMapper and GPSPoints - stuff that I expect hardly any one uses - but the capability is built into Viking. I only added a KML option here because it's probably quite popular than the rest of the formats, but I'd happily relegate it into a GPSBabel option. It may not be conceptually clean but I think it's more user friendly for the presumed majority that use GPX - because it's the mostly widely supported type. I think it is really useful to have GPX as the primary export option since it is the de facto standard. I'd just to say that I agree with Greg here. >export to some other format, with a dialog to choose it > Basically I'm saying that logically I see options as >you can just hit return once the file is specified that's ok. So I think export to GPX should be able to >My opinion is that GPX is the one true format, and the others are useful > file format known by gpsbabel or viking. > dialog would certainly be better, allowing export to GPX, KML and any other From the simple user point of view, a single "Export" I also realized that this is one more "export" For example, allowing such "export" feature