Re: [Gpsbabel-code] Re: [Gpsbabel-code] Re: [Gpsbabel-code] replacement for capabilities page

[Robert L. <rob...@us...>]

> To me this whole thing is somewhat confusing. We (in my opinion) need a
> clear system that allows the user to specify what (in terms of
> waypoints/tracks/routes)
> a) should be read
> b) how it should be transformed/translated (e.g. route(s)->waypoints)
> c) should be written

We've had some thrash on this in the past - and we have some modules that
never did catch up to the new thinking here, but the guiding principle 
is:

A) Usually read everything (wpts, routes, tracks) you can.  Major exception
   is the serial code where reading everything is prohibitively slow, so
   we read only what was specified.
B) Write everything you can.  Ditto on the serial thing.


> Example: I have a gpx file that contains some waypoints and some tracks. Now
> I want to write the waypoints to a cotoGPS (or whatever) file. How would I
> do this? Reading the docs I believe this should be the default (processing
> waypoints), but from the code I wrote I belive gpsbabel is going to dump
> everything into the target file.

That actually is what _most_ people want to happen most of the time.
When we didn't do this, there was an endless amount of whining.

> - The -t and -r options should be dumped.

Wait for your serial garmin unit to transfer 10,000 trackpoints when
you just wanted to read the 5 waypoints and see if you agree. :-)

RJL