Re: [Gpsbabel-misc] return only path, not points in tracks
Brought to you by:
robertl
From: Robert L. <rob...@gp...> - 2008-10-30 03:34:20
|
I don't see a specific logger mentioned here to know if there's "special" data in play, but for normal track data (lat/long/alt/time) GPX is a road very well traveled. RJL On Wed, Oct 29, 2008 at 10:23 PM, Mike Dodge <dmi...@gm...> wrote: > Sure, I can try merging them before turning them into KML files. What > format would you recommend reading them off the loggers as? > Thanks > Mike > > > On Wed, Oct 29, 2008 at 8:32 PM, Robert Lipe <rob...@gp...>wrote: > >> >> >> On Wed, Oct 29, 2008 at 3:55 PM, Mike Dodge <dmi...@gm...> wrote: >> >>> OK, I need to revisit this because I am kind of having the same problem >>> again. I am pulling data off a couple data loggers and sticking it into two >>> KML files. Then I want to combine the files into one, so I use the correct >>> syntax to combine two files into one: >>> C:\dda-gps\GPSBabel>gpsbabel -i kml -f "C:\dda-gps\Temp\output.kml" -f >>> "C:\dda-gps\Temp\output1.kml" -o kml -F "C:\dda-gps\Temp\output3.kml" >>> >> >> Merge them before you get to KML if you can. Reading KML isn't lossless >> for us. >> >> >> >>> >>> Then it made a super huge 5mb+ file. The two source files were 68kb and >>> 466kb. So I looked at the file and the bulk of it was all this extra track >>> data that I have no idea where it got it from. I would not like to have >>> this in my file if at all possible. Here is an example of the extra data I >>> was seeing. >>> >> >> >> That's the trackdata that defaults to 'on'. >> >> See >> http://www.gpsbabel.org/htmldoc-development/fmt_kml.html#fmt_kml_o_trackdata >> >> RJL >> > > |