I'm developing a geotagging app of sorts that can read GPX files. I've noticed a
couple GPX
exporters (gpsbabel and Garmin's "Bobcat") that will take a tracklog like
"ACTIVE LOG" and
split it into literally hundreds of <trk>s, each containing only one <trkseg>:

<trk><name>ACTIVE LOG</name><trkseg>...</trkseg></trk>
<trk><name>ACTIVE LOG 001</name><trkseg>...</trkseg></trk>
...
<trk><name>ACTIVE LOG 145</name><trkseg>...</trkseg></trk>
<trk><name>ACTIVE LOG 146</name><trkseg>...</trkseg></trk>
...ad infinitum

By my understanding of the format, which is confirmed by other utilities such as
G7ToWin,
a new track log should NOT be created for every single little time the GPS unit
loses signal
or whatnot, especially if the GPS itself does not call it a new track.

Is this a correct understanding? Are there reasons these programs go out of
their way to
turn one tracklog into hundreds named in sequence?

I'm tempted to start a letter writing campaign so that sanity (IMO) may one day
again
prevail, but I'm starting to worry that this strange "feature" is more
widespread than I
imagined, perhaps for some practical reason, and it would be a losing battle.
Has anyone
noticed the general ratio of programs that keep something like Garmin's "ACTIVE
LOG" as
one <trk> with many <trksegs>, versus those that go out of their way to make
sure
there's only one <trkseg> per <trk>?

thanks,
-natevw

ps - sorry for the "get off my yard, you whippersnappers" tone; I was completely
befuddled when I noticed how gpsbabel burst my tidy little GPX world with this
newfangled
idea, and I still have not gotten back into my rocker.