There is many things to do now. For example, allowing such export feature
at the File-Export level. I also realized that this is one more export
sub-menu entry. From the simple user point of view, a single Export
dialog would certainly be better, allowing export to GPX, KML and any other
file format known by gpsbabel or viking.
My opinion is that GPX is the one true format, and the others are useful
but can also be distracting. So I think export to GPX should be able to
happen with no adtitional barriers. Perhaps if gpx is preselected so
you can just hit return once the file is specified that's ok.
Basically I'm saying that logically I see options as
export as gpx
export to some other format, with a dialog to choose it
I'd just to say that I agree with Greg here.
I think it is really useful to have GPX as the primary export option since it
is the de facto standard.
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 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.
The main sticking points are GPSMapper and GPSPoints - stuff that I expect
hardly any one uses - but the capability is built into Viking. Putting it into
a single export UI is probably very hard.
I'd be tempted with:
Export-GPX
Export-Other-GPSMapper
Export-Other-GPSPoint
Export-With GPSBabel...
Trouble is what happens if include an option for GeoJSON, depending on how it's
implemented.
I've being thinking of adding in GeoJSON support some how but haven't found a
simple/clean way to do.
I thought about supporting GeoJSON natively in Viking but that's a lot of
coding effort, but could be plus point for Viking.
Alternatively putting in GeoJSON support into GPSBabel would help lots of other
people. Unfortunately it seems GPSBabel is going through the transition to Qt
framework. 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).
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. 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. need to tailor the options exactly depending on what
input you give it)
I haven't investigated MapBox's togeojson (a node.js thing) yet, because I've
yet to install it on my system...
--
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231iu=/4140/ostg.clktrk
___
Viking-devel mailing list
Viking-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/viking-devel
Viking home page: http://viking.sf.net/
