steve8x8 / geotoad

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

No access to true log ID, was: Wrong log id #280

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.download a cache with logs, for example: GC3K37K
2.
3.

What is the expected output? What do you see instead?
[If possible, include the last ~10--20 lines of verbose output.]
I don't really know the rules about the log id, but I tried to import that 
cache (and few others) in a cache manager and it fails to import some logs. I 
reported the bug to that application owner who told me it's a log it problem. 
There are not valid, too high for GC.

What version of the product are you using? On what operating system?
[Did you check you're using the latest version?]
GeoToad 3.17.11

Please provide any additional information below.
N/A

Original issue reported on code.google.com by geocachi...@gmail.com on 21 Sep 2013 at 8:32

Attachments:

GoogleCodeExporter commented 9 years ago
Log id from GCTour vs geotoad:
GCTour
<groundspeak:log id="349237459">
<groundspeak:log id="348633600">
<groundspeak:log id="348613377">
<groundspeak:log id="348432859">
<groundspeak:log id="348184539">
<groundspeak:log id="348165630">
<groundspeak:log id="348047452">

geotoad

<groundspeak:log id="2911440114">
<groundspeak:log id="137106636">
<groundspeak:log id="2601297273">
<groundspeak:log id="2866779195">
<groundspeak:log id="778386452">
<groundspeak:log id="3924716474">
<groundspeak:log id="4103396392">

Original comment by geocachi...@gmail.com on 21 Sep 2013 at 8:53

GoogleCodeExporter commented 9 years ago
This is how a log entry looks in the printable cache details (a.k.a. cdpf.aspx):

                                <dt>
                                    [<img src='../images/logtypes/2.png' alt="Found it" /> Found it]
                                    Thursday, 30 May 2013
                                    by <strong>
                                        shbust</strong> (332
                                    found)
                                </dt>

                                <dd>

                                    yeah<br />shbust</dd>

There is exactly _no way_ to determine the Log ID from this.
This is a very old limitation of GeoToad (another one concerns trackable IDs, 
same problem), and no one has ever found a solution how to fix it without 
completely rewriting GeoToad.
[If you need to include your *own* logs (into an input file for GCStatistic for 
example), there's the -M option to download the _list_ of your logs (they can 
be read without logging in, use wget, curl, ...). They contain the GUID of the 
cache, and can be assigned properly.]

Sorry for the bad news, but this, given the concept of GeoToad, is a clear 
"WontFix".

Original comment by Steve8x8 on 21 Sep 2013 at 1:10

GoogleCodeExporter commented 9 years ago
If we can't have it, would it be possible to leave it empty?
<groundspeak:log id="">

Original comment by geocachi...@gmail.com on 21 Sep 2013 at 1:54

GoogleCodeExporter commented 9 years ago
Pass your gpx file through a sed filter like the following?

sed -e 's~<groundspeak:log id="[0-9]*">~<groundspeak:log id="">~g'

If you don't want to do it by hand each time, create a template and place it in 
templates/ below your config directory.

(Same with "<groundspeak:travelbug id="[0-9]*" ref="TBX[0-9A-Z]*">" etc.)

Original comment by Steve8x8 on 21 Sep 2013 at 3:00

GoogleCodeExporter commented 9 years ago
See issue 58...

Original comment by Steve8x8 on 27 Sep 2013 at 10:12

GoogleCodeExporter commented 9 years ago

Original comment by Steve8x8 on 21 Oct 2013 at 11:00