Geocaching Australia

Only 2 minor changes to work with the latest changes to the secondary site.<br>
Just to clarify a few things, CacheMonkey doesnt download each cache page to get all the info it needs, it only downloads the list pages and then the .LOC file for each page. So it can get 300 caches with about 30 requests to the GC.com servers. It doesnt use the Logs or even look at the main pages at all. This would take CONSIDERBALY longer and piss Jeremy off CONSIDERABLY more!
<br>
The new GPX import will miss most of the caches you have found as it uses the logs to gather this info, and you only get 1 page worth of logs a GPX file. Anyone have any suggestions on this one, im stumped! The only solution would be to download the GPX file for caches you havent or have found and import them seperately.
<p>
Get the new release at the usual spot. http://members.ozemail.com.au/~bmcgill7 ... monkey.jar
<p>
GeoMonkey Brad.

Sounds like the same sort of thing a user would do manually. Where does it pick up the found caches, I couldn't see that in the loc file.

Just tried it Brad - Those <strike>tags</strike> are back on the unavailable caches again ..

I'm afraid I just get No Protocol : default ASPX and then it just stops

GMJ3191

Working well for me. A few niggles in quote handling on the cache names and distance&bearing not being populated.
<p>
This was from a 250 mile radius query from my home coordinates(Brisbane) resulting in 113 caches.

Premium mebership allows you to download up to 5 different GPX queries, so I get one for all caches, another for not-found caches etc, so no problem there for me.

Nice work Brad!
CacheMonkey is now GC.com change proof for me.

EcoDave

CacheMonkey wrote:The new GPX import will miss most of the caches you have found as it uses the logs to gather this info, and you only get 1 page worth of logs a GPX file. Anyone have any suggestions on this one, im stumped! The only solution would be to download the GPX file for caches you havent or have found and import them seperately.

Brad,
<br><br>
If I open a GPX file in EasyGPS, it does correctly indicate which caches have been found, not found and hidden and probably doesn't do it using the attached log files as even caches I found ages ago are correctly recorded... I assume that there must therefore be an indicator attached to the cache somehow which indicates its status... Not sure if there's a symbol embedded in the file format which you could use????
<br><br>
Otherwise, I'm glad to see the GPX import feature... and will let you know of any problems I encounter...
<br><br>
Thanks for the good work as usual...

Anyone else having trouble with CacheMonkey's File/Options/Export-Upload function? I'm finding that checking the Found/Not Found/Hidden/Unavailable boxes doesn't result in the relevant caches in the list being selected. In Not Found for one state, for example, out of 291 possibles, only six get selected, while only one of 57 Founds gets selected. They are all correctly identified in the Status column. Am I missing something or is this one of the casualties of the recent secondary site changes that is still broken?

Could someone please post the location of the latest version of Cachemonkey. The website does not seem to be being kept up to date. The link above seems to be a listing of source files only.

Could it be Maccamob that the list limiters is set to 100 days or similar and so you are only downloading from the caches placed in the last 100 days and not the full list?
Thats what happened to me anyway.

Cheers Jeff

Cachemonkey is available here http://geomonkeys.com/main/CacheMonkey/cachemonkey.html

Thanks, but that is not the latest version.

Geoff - download the full 2.0 Beta version from the link in Sparkky's post, then replace the .jar file with the one from the link in Cachemonkey's post at the top to get the latest 2.0.3 version.

Beaut, thanks Macca. I have been trying to get this going for weeks.

Geoff

I am still seeing the strike /strike tags around the names of disabled caches. Is it just me. I believe this was fixed once.

Is everybody getting quotes and other punctuation in the cache names coming through looking like HTML or is it just me?

" looks like &QUOT