geo-*- Rick Richardson's Linux Tools for Geocaching

Re: BUG: gc.com changed the login page.

rickrich — Wed, 09 May 2012 19:02:23 -0400

$ geo-nearest
GC1NPYG 44.94743 -93.48930 Geocache-regular
GC10G15 44.94527 -93.49463 Geocache-regular
GC2DW82 44.94292 -93.49548 Geocache-regular
GC13EDN 44.94143 -93.49095 Geocache-ifound-regular
GC1FFA8 44.95327 -93.48798 Geocache-ifound-regular
GC244BC 44.95000 -93.50000 Geocache-unknown
GCX22E 44.94592 -93.48125 Geocache-regular
GC3A7WM 44.95240 -93.49893 Geocache-ifound-regular
GC1R0VT 44.94355 -93.48213 Geocache-ifound-regular
GC10Y5N 44.94802 -93.48007 Geocache-regular
GC2W0G8 44.94262 -93.50030 Geocache-ifound-regular
GC10WZE 44.94020 -93.48235 Geocache-regular
GC10WWJ 44.94688 -93.47720 Geocache-regular
GCH4FC 44.94342 -93.47842 Geocache-regular
GC38HVF 44.94142 -93.50213 Geocache-ifound-regular
GC24BBM 44.93963 -93.48228 Geocache-ifound-unknown
GCQVJA 44.94453 -93.47708 Geocache-regular
GC1JGZQ 44.93605 -93.49830 Geocache-regular
GCRRPX 44.94202 -93.47497 Geocache-regular
GC1GX3E 44.94387 -93.47353 Geocache-regular

Works here.

BUG: gc.com changed the login page.

happyhibo — Wed, 09 May 2012 08:24:16 -0400

Hello,

When I try to use any of these tools I get this message:

BUG: gc.com changed the login page.

In the morning it works fine.
Just now comes the error.

Have GC.COm change the Page?

Cu HH

Re: geo-nearest: curl: returned /dev/null for '/tmp/geo-login.html' [solved; put CURL_OPTS="--sslv3" in ~/.georc]

rickrich — Sat, 05 May 2012 18:14:57 -0400

DATE FORMATS
        Geocaching.com date formats that are compatible:

            GC Format   Example     Compatible
            YYYY-MM-DD  2011-07-13  yes
            YYYY/MM/DD  2011/07/13  yes
            MM/DD/YYYY  07/13/2011  yes
            DD/MM/YYYY  13/07/2011  yes if DATEFMT=1 in $HOME/.georc
            DD/Mmm/YYYY 13/Jul/2001 no
            Mmm/DD/YYYY Jul/13/2011 no
            DD Mmm YY   13 Jul 11   yes (english only)

Re: geo-nearest: curl: returned /dev/null for '/tmp/geo-login.html'

benbergman — Sat, 05 May 2012 17:45:13 -0400

I may have spoken too soon. I'm trying to run this:

geo-nearest -H html -n1000 && geo-html2gpx -b -l 5 html/*.html > geo-nearest_1000_2012-05-05.gpx

but I'm getting a bunch of these:

...
date: invalid date '12am 27/Apr/2012'
date: invalid date '12am 14/Apr/2012'
date: invalid date '12am 14/Feb/2011'
date: invalid date '12am 21/Apr/2012'
date: invalid date '12am 28/Jan/2011'
date: invalid date '12am 05/Apr/2012'
date: invalid date '12am 10/Mar/2012'
...

No HTML files seem to be created. Any thoughts on this one? I predict a date format is setup wrong, but I don't know where to look for this.

EDIT: I just tried running the above command with -n10 instead of 1000 and it does end up outputting HTML files and the combined GPX. I'm still not sure what is up with the date errors, but it at least looks like I've got my gpx file.

Re: geo-nearest: curl: returned /dev/null for '/tmp/geo-login.html'

benbergman — Sat, 05 May 2012 17:09:44 -0400

That fixed it! Thanks a lot, rickrich!

Re: geo-nearest: curl: returned /dev/null for '/tmp/geo-login.html'

rickrich — Sat, 05 May 2012 15:18:11 -0400

Its a bug in the newe(r|st) curl. Put this in your ~/.georc:

CURL_OPTS="--sslv3"

Ref: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/595415/comments/8

Re: geo-nearest: curl: returned /dev/null for '/tmp/geo-login.html'

rickrich — Sat, 05 May 2012 14:42:05 -0400

It is your curl version and SSL. Maybe the certs aren't right?

geo-nearest: curl: returned /dev/null for '/tmp/geo-login.html' [solved; put CURL_OPTS="--sslv3" in ~/.georc]

benbergman — Sat, 05 May 2012 12:14:59 -0400

When I try to use any of these tools I get this message:

geo-nearest: curl: returned /dev/null for '/tmp/geo-login.html'

With -D1

$ geo-nearest -D1
geo-nearest: curl https://www.geocaching.com/login/default.aspx
geo-nearest: curl https://www.geocaching.com/login/default.aspx
geo-nearest: curl: returned /dev/null for '/tmp/geo-login.html'

I have tried with multiple gc.com accounts. I used these tools successfully at work, but I can't seem to get them working on my home computer. At work I use Ubuntu and at home I use Arch Linux. I did not find anything when I searched the forum. Any help is much appreciated. These tools are exactly what I've been looking for, so I am excited to start using them.

OsmaRender maps abandoned

Steve8x8 — Mon, 02 Apr 2012 06:11:41 -0400

At some point in the past few weeks, OsmaRender maps (geo-map type 21) have become unavailable, and OSM forums suggest they won't come back.
Currently, www.openstreetmap.org offers four map layers:
- Standard (= Mapnik)
- Cycle Map
- Transport Map
- MapQuest Open
of which only the Standard one is supported (as type 20) by geo-map.

The transition from Mapnik tiles to other map tiles is easy:
Mapnik: http://$x.tile.openstreetmap.org/$zoom/$column/$row.png
CycleMap: http://$x.tile.opencyclemap.org/cycle/$zoom/$column/$row.png
TransportMap: http://$x.tile2.opencyclemap.org/transport/$zoom/$column/$row.png
MapQuestOpen: http://otile$y.mqcdn.com/tiles/1.0.0/osm/$zoom/$column/$row.png
(with x={a,b,c}, y={1,2,3,4}, all tiles being 256x256 in size)

but I don't know whether there's an export URL.
(The interface says "standard layer", which may suggest there isn't. At least not on the main site.)

BTW, exported images seem to be returned from parent.tile.openstreetmap.org now,
but URLs like
http://parent.tile.openstreetmap.org/cgi-bin/export?bbox=13,52,14,53&scale=1000000&format=png and
http://tile.openstreetmap.org/cgi-bin/export?bbox=13,52,14,53&scale=1000000&format=png
seem to be equivalent (still).

Re: Problem with geo-demand using GC code

rickrich — Sat, 11 Feb 2012 07:50:58 -0500

From the Changelog:

2012-02-11      Rick Richardson 
        * geo-demand: GC codes are gc1234 *and* gc12345

Problem with geo-demand using GC code [solved]

cor9957 — Sat, 11 Feb 2012 05:41:51 -0500

Hi,

I'm probably missing something very simple but I have no idea what, maybe somebody can point my in the right direction.
This command works just fine: "geo-demand -n 400 -q notfound,active,traditional,multi,earth" but when I add a GC code at the end of the command like this "geo-demand -n 400 -q notfound,active,traditional,multi,earth GC1FT3E" the command is accepted without an error, but the PQ is not created.
When I look at the PQ page I see the previous PQ's that geo-demand created, but not the one with the GC code at the end.

Thank for any help you can give me.

Cor.

Re: hash2sdt()

rickrich — Tue, 07 Feb 2012 07:38:02 -0500

hash2sdt() is only used for *archived* caches. Loc format is used for regular caches.

hash2sdt()

Steve8x8 — Tue, 07 Feb 2012 04:57:52 -0500

Hi Rick,

nice to see that GeoToad's S/D/T decoding algorithm has found its way into geo-* after about a year ;) Let's hope the guys at GroundSpeak won't find out too fast...

Cheers, S

Re: \x13 characters

rickrich — Sat, 04 Feb 2012 15:13:59 -0500

From the Changelog:

2012-02-04      Rick Richardson 
        * geo-html2gpx: remove ^Q/^S characters

\x13 characters [solved]

z00k — Sat, 04 Feb 2012 14:05:03 -0500

I don't know whether this is actually a bug (i.e. what the gpx specification says) but my Garmin device has a problem with the character \x13 which occurs for example in GC1KVEK (it seems to just ignore the file from the respective cache on). So I have a script to remove these. Perhaps geo-gpx2html might already do that.

In the cache in question, the character occurs in an html comment, so another option (in the particular case) would be to strip comments.

Re: BUG: gc.com changed the login page

rickrich — Wed, 01 Feb 2012 07:51:09 -0500

From the Changelog:

2012-02-01      Rick Richardson 
        * geo-common-gc, et al: Make login case insignificant

Re: BUG: gc.com changed the login page

marikanders — Wed, 01 Feb 2012 02:32:13 -0500

OK, found it.
The user name is case sensitive.
You must enter the user name in the geo-* tools exactly as it is displayed at geocaching.com
Alternativly, change one line in the geo-* tools:
if ! grep -q "You are logged in as <[^>]*>$_username<" $LOGINPAGE; then
to
if ! grep -iq "You are logged in as <[^>]*>$_username<" $LOGINPAGE; then

Re: BUG: gc.com changed the login page

marikanders — Tue, 31 Jan 2012 10:11:36 -0500

I have two accounts at geocaching.com
The exact same operation, geo-pqdownload, works for one of them but gives
the "BUG: gc.com changed the login page" error for the other.
Comparing the /tmp/geo-login.html files for the two cases I can see that
the only differences are the __VIEWSTATE, the uid and the X value in the
URL for the ads.groundspeak.com iframe.

Re: BUG: gc.com changed the login page

rickrich — Sun, 22 Jan 2012 08:27:24 -0500

$ geo-nearest -D1
geo-nearest: curl https://www.geocaching.com/login/default.aspx
geo-nearest: curl https://www.geocaching.com/login/default.aspx
geo-nearest: 0: curl http://www.geocaching.com/seek/nearest.aspx?origin_lat=44.947500&origin_long=-93.491083 #list
Total Records: 10659
GC1NPYG 44.94743 -93.48930 Geocache-regular
GC10G15 44.94527 -93.49463 Geocache-regular
GC2DW82 44.94292 -93.49548 Geocache-regular
GC13EDN 44.94143 -93.49095 Geocache-ifound-regular
GC1FFA8 44.95327 -93.48798 Geocache-ifound-regular
GC244BC 44.95000 -93.50000 Geocache-unknown
GCX22E 44.94592 -93.48125 Geocache-regular
GC3A7WM 44.95240 -93.49893 Geocache-ifound-regular
GC1R0VT 44.94355 -93.48213 Geocache-ifound-regular
GC10Y5N 44.94802 -93.48007 Geocache-regular
GC2W0G8 44.94262 -93.50030 Geocache-ifound-regular
GC10WZE 44.94020 -93.48235 Geocache-regular
GC10WWJ 44.94688 -93.47720 Geocache-regular
GCH4FC 44.94342 -93.47842 Geocache-regular
GC38HVF 44.94142 -93.50213 Geocache-ifound-regular
GC24BBM 44.93963 -93.48228 Geocache-ifound-unknown
GCQVJA 44.94453 -93.47708 Geocache-regular
GC1JGZQ 44.93605 -93.49830 Geocache-regular
GCRRPX 44.94202 -93.47497 Geocache-regular
GC1GX3E 44.94387 -93.47353 Geocache-regular

Works here.

Please put "/tmp/geo-login.html" somewhere on the web so I can access it.

Re: BUG: gc.com changed the login page

thehodapp — Sun, 22 Jan 2012 04:28:14 -0500

I'm having the same problem. To be fair, I just installed the tools. What might be causing this problem?

Re: geo-demand how to limit to one state with coordinates? [solved]

jerry — Sun, 15 Jan 2012 00:20:38 -0500

Thank you!

Re: geo-demand how to limit to one state with coordinates?

rickrich — Wed, 11 Jan 2012 10:07:27 -0500

From the Changelog:

2012-01-11      Rick Richardson 
        * geo-demand: Add state using lat lon; e.g. geo-demand mn n43.6 w92

geo-demand how to limit to one state with coordinates? [solved]

jerry — Wed, 11 Jan 2012 04:38:40 -0500

I live right on a state line.

When I run

geo-demand lat lon  (or more simply, just geo-demand)

It of course creates a pq with the 500 nearest caches, with no regard to the state, expected and desired behavior in most cases.

But, if I try to run

geo-demand state

It returns caches in the state, but by date order (so it returns the 500 oldest caches in the state). Expected and desired behavior in most cases.

I don't see any way to create a lat/lon (or home based) pq that is limited to one state?

Running

geo-demand lat long state

just dumps the help screen.

Is there a way to do this?

Re: BUG: gc.com changed the login page

rickrich — Mon, 09 Jan 2012 10:26:37 -0500

Works here.

Premium:

$ geo-nearest
GC1NPYG 44.94743 -93.48930 Geocache-regular
...

Basic:

$ geo-nearest -udyl1231 -pPASSWORD
geo-nearest: Basic Member: pay the $30/yr fee for Premium Member!
geo-nearest: Basic Member: doing it the REAL SLOW way!!!
GC1NPYG 44.94743 -93.48930 Geocache-regular
...

BUG: gc.com changed the login page [solved]

gewoon_wij — Mon, 09 Jan 2012 09:55:19 -0500

Hi,

When I try to use any command, the text: "BUG: gc.com changed the login page" appears... Is it so that GC.COM changed the login page yesterday??

Bastiaan

Re: Error when encountering a premium-only cach with geo-nearest and basic membership

rickrich — Sat, 07 Jan 2012 12:37:08 -0500

From the Changelog:

2012-01-07      Rick Richardson 
        * geo-common-gc: remove soc's from basic member

NOTE: --nocheck-order is WRONG!!!!

Error when encountering a premium-only cach with geo-nearest and basic membership [solved]

divan90 — Sat, 07 Jan 2012 05:59:42 -0500

Hi,

geo-nearest fails for me when it happens to find a premium-only cache while I have only a basic account (yet). The error occurs in line 1400 of geo-common-gc, when trying to join the .csv and .xtra file. This is because the premium-only cache only turns up in $CSVFILE (as a line like GC2AA34 0.000 0.000 ...) and not in $XTRAFILE, which causes join to complain and the script to abort.

I have a quick workaround attached, which simply tells join to ignore unmatched lines. However, I believe it were possible to filter those caches out some time before. I just don't quite understand the code there yet to attempt it by myself.

There's one additional complication here, though: geo-nearest fails reliably as described when issuing the same query (same location) again and again. However, it happened to me that a subsequent query didn't fail (reliably if repeated), when in between the querys I either issued a query for another location, or just opened the failing premium-only cache in a browser (URL like http://www.geocaching.com/seek/cache_details.aspx?wp=GC2AA34). Don't know how to make sense of that.

--- upstream/geo-12-01-06-02-37-49/geo-common-gc	2011-12-27 01:47:45.000000000 +0100
+++ geo/geo-common-gc	2012-01-07 11:07:52.025671512 +0100
@@ -1397,7 +1397,7 @@
     # Convert CSV into CSV with puzzles...
     csv2csv $GEOMYSTERY < $CSVFILE2 > $CSVFILE
 
-    join -t '	' $CSVFILE $XTRAFILE > $JOINFILE
+    join --nocheck-order -t '	' $CSVFILE $XTRAFILE > $JOINFILE
     if [ $? != 0 ]; then
 	cp $CSVFILE /tmp/geo.err.csv
 	cp $XTRAFILE /tmp/geo.err.xtra

Edit: Output of geo-nearest attached. There are three caches in geo.err.csv that don't show up in geo.err.xtra. geo-nearest was calles as

geo-nearest -H "$DIR/html" -s -n50 52.523369 13.475888

missing dependency in Makefile [solved]

divan90 — Thu, 05 Jan 2012 10:16:32 -0500

Hi,

after I changed a source line in geo-common-gc (line 1400, to try if the tab in "join -d '\t'" was the reason for my join error), the geo-correct-coords executable script didn't get updated as expected by running make (geo-correct-coords.sh includes geo-common-gc). Also, it didn't get removed bt make clean.

Fix:

--- geo-11-12-26-18-48-32/Makefile	2011-12-19 17:33:19.000000000 +0100
+++ geo/Makefile	2012-01-05 16:07:50.782465359 +0100
@@ -309,6 +309,7 @@
 oc-nearest: geo-common geo-common-oc geo-common-gpsdrive Makefile
 oc-newest: geo-common geo-common-oc geo-common-gpsdrive Makefile
 ll2maidenhead: geo-common Makefile
+geo-correct-coords: geo-common geo-common-gc
 
 geo-images: images Makefile
 	find images -type f | sed '/CVS/d' | \
@@ -344,6 +345,7 @@
 	rm -f ll2maidenhead
 	rm -f geo-cs-html2db
 	rm -f geo-demand-cs geo-newest-cs
+	rm -f geo-correct-coords
 	rm -f *.tar.gz
 	rm -f Readme
 	rm -f tomtom-*.png

Using procmail to grab notifications and parse gc code

turner.curtis — Mon, 02 Jan 2012 20:08:59 -0500

Hey guys,

Never realized there was a forum here. Well on to the subject at hand... A fellow caching friend and I have created some scripts to use procmail to snatch incoming publish notifications and send to a php script which parses the gc code and hand off to a modified shell script of Rick's to grab the cache page info which it then hands back to the php script to send the modified notification onward.

If anyone is interested in the procmail recipe, our php or modified script of Rick's let me know and I will post a tarball.

@Rick thanks for all the time and effort you put in to creating such useful scripts and publishing them for us to molest.

Re: geo-html2gpx does not demask

rickrich — Sat, 17 Dec 2011 14:41:47 -0500

From the ChangeLog:

2011-12-17      Rick Richardson 
        * geo-html2gpx: terr (GC.com 09/15/11 update)
        * geo-html2gpx: unescape hex &xHH; (GC.com 09/15/11 update)
        * geo-html2gpx: JSON format account id
        * geo-html2gpx: logdate's in JSON format