search

steve8x8 / geotoad

Geocaching query tool written in Ruby
https://buymeacoffee.com/steve8x8
Other
28 stars 8 forks source link

Multiple options in title and automatic filename #293

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
[Please include the relevant parts of your command line, if applicable.
Don't send your password though!]
1. Use the automatic filename feature, and a filter (-T 3.5 for example)

What is the expected output? What do you see instead?
[If possible, include the last ~10--20 lines of verbose output.]
"_T3.5" shows up twice in the generated filename, and "terrain 3.5+" in the 
"title" line present in gpx and html formats

What version of the product are you using? On what operating system?
[Did you check you're using the latest version?]
Everything up to the current SVN (r1524).

Please provide any additional information below.
Some of the filters are run twice, and the corresponding information is added 
to the filename and title strings each time.

As nobody has cared about this: Lowest priority.

Original issue reported on code.google.com by Steve8x8 on 7 Dec 2013 at 9:45

GoogleCodeExporter commented 9 years ago 
I have patched up GeoToad to use a hash for collection of additions to the 
title line, and the default file name - this avoids duplicate entries by design.
I also tried to use ">=" and "<=" but gpsbabel is very unhappy about those - < 
and > would be properly written to GPX output but the first time gpsbabel gets 
its hands on those they are converted back, and a second gpsbabel run fails 
miserably. Not sure whether this is a bug in gpsbabel or my idea of <desc> 
entries is somewhat wrong.
Expect more changes...

Original comment by Steve8x8 on 9 Dec 2013 at 3:19

GoogleCodeExporter commented 9 years ago 
Apparently <desc> elements inside a <wpt> context are handled fine; anything 
outside "might" be non-standard, so it seems to be better to stay on the safe 
(but a bit ugly) side for now.

Original comment by Steve8x8 on 11 Dec 2013 at 12:19

GoogleCodeExporter commented 9 years ago 
Fixed with 3.19.1 - it doesn't make sense to wait for gpsbabel this time.

Original comment by Steve8x8 on 22 Dec 2013 at 1:02