Hi, and welcome.
The interaction of all those options is gnarly. You're turning on track,
but since you have no timestamps, we can't really write a gx:Track that's
useful to Earth so we end up trying hard to leave you with something. The
result is a duplicate.
As you have no times, don't turn on track and you won't get the dupes.
On Mon, Feb 20, 2012 at 10:41 AM, Brett Russ <icycle@...> wrote:
> I'm converting National Geographic 3.x TPO files to KML. I made a simple
> repro: drew a short track in the Topo SW, save .tpo file (attached; not
> sure if attachments are welcome/stripped), and use gpsbabel 1.4.3 (Win XP)
> to convert to KML using these args:
> gpsbabel -D2 -w -r -t -i tpo3 -f test.tpo -o
> -F test.kml
> I also tried with lines=0, points=0, and some other variations. End
> result is always 2 duplicate tracks in the KML:
> To rule out a Windows app issue, I compiled the 1.4.3 source under Ubuntu
> and saw the same behavior.
> I saw this previous post about a similar issue:
> which was fixed in 1.4.3. I verified the source shows it's fixed, so mine
> must be a new issue.
> As a side note, I notice that I don't see any track in Google Earth
> (126.96.36.19901) unless I set track=1, which is odd because the default is
> track=0 for the tpo conversion. In other words, just setting lines=1
> doesn't make a track line.
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> Gpsbabel-misc mailing list http://www.gpsbabel.org
> To unsubscribe, change list options, or see archives, visit: