Thread: [Gpsbabel-code] Geocaching filter?
Brought to you by:
robertl
From: Jani F. <j.f...@gm...> - 2011-10-05 05:34:53
|
Hi all, This is my first post. First I'd like to thank for this great software I've been using a few months now for geocaching. Would it be possible to implement a new filter, that filters waypoints (including or excluding) based on geocache type, difficulty or terrain ratings? Jani |
From: Robert L. <rob...@gp...> - 2011-10-05 13:30:44
|
On Wed, Oct 5, 2011 at 12:34 AM, Jani Frilander <j.f...@gm...>wrote: > Hi all, > > This is my first post. First I'd like to thank for this great software I've > been using a few months now for geocaching. > You're welcome. > Would it be possible to implement a new filter, that filters waypoints > (including or excluding) based on geocache type, difficulty or terrain > ratings? > It'd be possible, but that doesn't make it a good idea. Frankly, there are way better ways to accomplish the same thing that are actually meant for that kind of thing and that can provide a reasonable user interface for doing it. Between tools like GSAK and Maccaching and the geo.rkkda.com suit and geotoad and my personal favorite, just plain ordering up a pocket query with the "right" data to start with, there's just no reason to drive that nail with this wrench. RJL |
From: Jani F. <j.f...@gm...> - 2011-10-05 15:40:43
|
2011/10/5 Robert Lipe <rob...@gp...>: > > > On Wed, Oct 5, 2011 at 12:34 AM, Jani Frilander <j.f...@gm...> > wrote: >> >> Would it be possible to implement a new filter, that filters waypoints >> (including or excluding) based on geocache type, difficulty or terrain >> ratings? > > It'd be possible, but that doesn't make it a good idea. Frankly, there are > way better ways to accomplish the same thing that are actually meant for > that kind of thing and that can provide a reasonable user interface for > doing it. I realized that a little late when I allready had posted my question. I examined the source and founds out it would require changes in the way gpx files are handled, just a simple filter isn't enough. > Between tools like GSAK and Maccaching and the geo.rkkda.com suit and > geotoad and my personal favorite, just plain ordering up a pocket query with > the "right" data to start with, there's just no reason to drive that nail > with this wrench. > RJL > Actually I'm using gpxfilter and gpxrewrite from Tyler Akins GPX Tools package. The reason I asked my question was they sometimes segfaulted, but found a way to work it out. Of course pocket queries were the best, but I decided not to renew my membership until I get a new job. Jani |
From: Robert L. <rob...@gp...> - 2011-10-05 15:54:04
|
On Wed, Oct 5, 2011 at 10:40 AM, Jani Frilander <j.f...@gm...>wrote: > 2011/10/5 Robert Lipe <rob...@gp...>: > > > > > > On Wed, Oct 5, 2011 at 12:34 AM, Jani Frilander <j.f...@gm...> > > wrote: > >> > >> Would it be possible to implement a new filter, that filters waypoints > >> (including or excluding) based on geocache type, difficulty or terrain > >> ratings? > > > > It'd be possible, but that doesn't make it a good idea. Frankly, there > are > > way better ways to accomplish the same thing that are actually meant for > > that kind of thing and that can provide a reasonable user interface for > > doing it. > > I realized that a little late when I allready had posted my question. > I examined the source and founds out it would require changes in the way > gpx files are handled, just a simple filter isn't enough. > Since I've already said it's a bad idea, it seems silly to engage in an "is too" conversation, but it could totally be a filter in our architecture with zero changes to the GPX reader or writer. > > > Between tools like GSAK and Maccaching and the geo.rkkda.com suit and > > geotoad and my personal favorite, just plain ordering up a pocket query > with > > the "right" data to start with, there's just no reason to drive that nail > > with this wrench. > > RJL > > > Actually I'm using gpxfilter and gpxrewrite from Tyler Akins GPX Tools > package. The reason I asked my question was they sometimes segfaulted, > > I hadn't even heard of those. If you can't fix them, send a failing test case to the author. There are lots of subtle, data-specific opportunities to drop things on the floor but if you can put a breaking test case in the hands of whomever supports that, that's a long way toward getting it fixed. RJL |