I got the same problem in the beginning. I also thought I already had agreed to the license agreement, but there was something more to agree to. Look around on gc.com and you will find a box that you have to cross in somewhere.
Forum: General Topics

Look at this example from the man-file: $ geo-count Jeremy geo-count: Could not determine the user account number for 'Jeremy' $ geo-count -s 3 363 3 366 0 0 $
Forum: General Topics

I have found a funny behaviour of geo-newest Look at this: $ geo-newest -r 100km -n 100 -I unfound -s sweden N63 E17 BayofOmne 62.96145 18.39080 Geocache-unfound-regular AngeCampingPonderosa 62.51645 15.61790 Geocache-unfound-regular But $ geo-newest -r 100km -I unfound -s sweden N63 E17 <nothing> Meaning I need to put a high number to the -n option to make it work together
Forum: General Topics

Try this: geo-gid -H. GC10D4Q geo-html2gpx -b GC10D4Q.html > GC10D4Q.gpx In the output gpx file at least I get things like &amp;amp; And things like &amp;#229; Which should have been &amp; and &#229; That is, the ampersand is converted to &amp; If I postprocess with the following, the gpx files turn out right: sed -e 's/&amp;nbsp;/ /g' -e 's/&amp;amp
Forum: General Topics

Sweden seems to be left out of the suite. The following patch fixes it: --- ./geo-newest.sh.~1~ 2007-10-24 18:20:48.000000000 +0200 +++ ./geo-newest.sh 2009-06-28 10:02:00.000000000 +0200 @@ -292,6 +292,7 @@ western\ cape) id=152;; yukon\ territory) id=74;; +.se|se|sweden|sverige) cid=10;; .uk|uk|.gb|gb|united\ kingdom|great\ britain) cid=11;; .af|af|afg|a
Forum: General Topics