DECLINED - [BUG] Pocket Query listing Cache Found - not correct

[+gjhimages]

I have download Pocket Queries (500) and found that their are between 7-100 caches that say that I have found them, which is not true. The Queries are loaded into Garmin's BaseCamp so they can be uploaded into my Garmin GPSmap 60Cx. After loading the same query from week to week and noticing that the same caches were shown as found, I loaded the same Pocket Query into Garmin's older software, RoadTrip. But with RoadTrip I find that the same caches are now shown as NOT being found (which is correct). I have checked that only the UNFOUND caches to be download into the Pocket Query.

 

I have looked in the file (TXT format) and can not find anything that shows that I have found the cache. I am wondering if there is something or code in BaseCamp that is showing that I have found the cache.

 

I have sent an email to Garmin, they have stated the following:

 

"I would concentrate on Basecamp as Roadtrip development has been put on

pause for the foreseeable future. Basecamp opens and interprets the

Geocaches based on the <tags> that make up the file. There are

different version of the standards the tags are created with. Its all

XML language. The "<found>" tags in the 4 caches that show up as

found are interpreted by Basecamp as Found, Basecamp might not be able

to recognize the tag at all so it is just assigning it the Found status.

Who ever controls the web page that creates the .gpx file would have to

review the code to find out what the difference is between the 4 caches

and the rest and why the automated web application is creating the

<found> tag differently than the other 24 caches created. You can open

any gpx file in a regular plain text editor like notepad.exe. Just

change the extension on the end of the file to .txt instead of .gpx then

open the file in notepad. You'll see the code or tags associated with

each little piece of data. These are created by a template on the

Geocache website and something within the template needs to be tweaked

but we do not know what the parameters are that Geocache goes by in

order to identify or make any changes. I would say just correct the 4

that are wrong and go have fun Geocaching."

 

Here is the txt file for GC2KMTV (one of the many caches that show I have found - not true):

</wpt>

<wpt lat="45.633767" lon="-122.620783">

<time>2010-12-26T08:00:00Z</time>

<name>GC2KMTV</name>

<desc>White Elephant by GeoReapers, Traditional Cache (1.5/1.5)</desc>

<url>http://www.geocaching.com/seek/cache_details.aspx?guid=aec09cba-bf36-4fe0-83f2-d0bda7126d7b</url>

<urlname>White Elephant</urlname>

<sym>Geocache</sym>

<type>Geocache|Traditional Cache</type>

<Groundspeak:cache id="2021972" available="True" archived="False" xmlns:Groundspeak="http://www.Groundspeak.com/cache/1/0">

<Groundspeak:name>White Elephant</Groundspeak:name>

<Groundspeak:placed_by>GeoReapers</Groundspeak:placed_by>

<Groundspeak:owner id="2833462">GeoReapers</Groundspeak:owner>

<Groundspeak:type>Traditional Cache</Groundspeak:type>

<Groundspeak:container>Regular</Groundspeak:container>

<Groundspeak:difficulty>1.5</Groundspeak:difficulty>

<Groundspeak:terrain>1.5</Groundspeak:terrain>

<Groundspeak:country>United States</Groundspeak:country>

<Groundspeak:state>Washington</Groundspeak:state>

<Groundspeak:short_description html="True"><center><b>A cache located on the beautiful Burnt Bridge Creek

trail.</b></center></Groundspeak:short_description>

<Groundspeak:long_description html="True"><center><img src=

"http://fashionbrandz.com/admin/menu/subcategoryimages/0-elephant-in-a-box1.jpg"

alt="A White Elephant Exchange!" /></center>

This cache was created as a final Christmas Present for the younger

members of the GeoReaper team and is now being released for

everyone else to enjoy. <b><i>There is no parking permitted at the

cache zone</i></b>, so please park by the park and walk to it, if

you are driving (however, we would recommend just walking and

enjoying the trail and enjoying it that way). It is located on a

stretch of a trail that we all often take on our bikes and hope you

enjoy the spot as much as we do. In classic white elephant fashion,

we encourage you to bring a little something random to exchange

with the next cacher that comes along. (<b>Congrats to GeoJerry for

the FTF!!</b> )Please exercise extreme stealth as this is in a very

high muggle traffic area and replace exactly as you have found it."</Groundspeak:long_description>

<Groundspeak:encoded_hints>Trolls</Groundspeak:encoded_hints>

<Groundspeak:logs>

<Groundspeak:log id="182396982">

<Groundspeak:date>2011-08-26T19:00:00Z</Groundspeak:date>

<Groundspeak:type>Found it</Groundspeak:type>

<Groundspeak:finder id="3450891">h2owarrior</Groundspeak:finder>

<Groundspeak:text encoded="False">Quick run down the path and find. Let a trackable. TFTC!</Groundspeak:text>

</Groundspeak:log>

<Groundspeak:log id="181776027">

<Groundspeak:date>2011-08-21T19:00:00Z</Groundspeak:date>

<Groundspeak:type>Found it</Groundspeak:type>

<Groundspeak:finder id="4395346">lostinwashington</Groundspeak:finder>

<Groundspeak:text encoded="False">A good hide right in the middle of it all. tftc</Groundspeak:text>

</Groundspeak:log>

<Groundspeak:log id="177054159">

<Groundspeak:date>2011-08-02T07:00:00Z</Groundspeak:date>

<Groundspeak:type>Found it</Groundspeak:type>

<Groundspeak:finder id="2261559">sujojeepers</Groundspeak:finder>

<Groundspeak:text encoded="False">Fun find! Took card game, left a dinosaur. Thanks!</Groundspeak:text>

</Groundspeak:log>

<Groundspeak:log id="176254470">

<Groundspeak:date>2011-07-30T19:00:00Z</Groundspeak:date>

<Groundspeak:type>Found it</Groundspeak:type>

<Groundspeak:finder id="4430829">northwesttreehugger</Groundspeak:finder>

<Groundspeak:text encoded="False">Wow i can't believe this cache has not been found in a month. Great cache and a great location to bike bike on the Burnt creek trail.</Groundspeak:text>

</Groundspeak:log>

<Groundspeak:log id="169360201">

<Groundspeak:date>2011-06-27T17:42:18Z</Groundspeak:date>

<Groundspeak:type>Found it</Groundspeak:type>

<Groundspeak:finder id="3305246">gummibjorn</Groundspeak:finder>

<Groundspeak:text encoded="False">Cool container reapers

Out grabbing a few with klien

Before he leaves </Groundspeak:text>

</Groundspeak:log>

</Groundspeak:logs>

<Groundspeak:travelbugs>

<Groundspeak:travelbug id="2725918" ref="TB3C9AR">

<Groundspeak:name>Cachekinz</Groundspeak:name>

</Groundspeak:travelbug>

</Groundspeak:travelbugs>

</Groundspeak:cache>

 

Thanks for looking into this,

Gary

gjhimages

[Moun10Bike]

I spoofed your login and downloaded the single PQ that you have available for downloading on your profile ("Gresham"). I imported that into my copy of BaseCamp running on my Windows PC and all of the caches show as unfound. I'm inclined to think that the issue lies with your Mac version of BaseCamp.

[+webscouter.]

I have download Pocket Queries (500) and found that their are between 7-100 caches that say that I have found them, which is not true. The Queries are loaded into Garmin's BaseCamp so they can be uploaded into my Garmin GPSmap 60Cx. After loading the same query from week to week and noticing that the same caches were shown as found, I loaded the same Pocket Query into Garmin's older software, RoadTrip. But with RoadTrip I find that the same caches are now shown as NOT being found (which is correct). I have checked that only the UNFOUND caches to be download into the Pocket Query.

 

I have looked in the file (TXT format) and can not find anything that shows that I have found the cache. I am wondering if there is something or code in BaseCamp that is showing that I have found the cache.

 

I have sent an email to Garmin, they have stated the following:

 

"I would concentrate on Basecamp as Roadtrip development has been put on

pause for the foreseeable future. Basecamp opens and interprets the

Geocaches based on the <tags> that make up the file. There are

different version of the standards the tags are created with. Its all

XML language. The "<found>" tags in the 4 caches that show up as

found are interpreted by Basecamp as Found, Basecamp might not be able

to recognize the tag at all so it is just assigning it the Found status.

Who ever controls the web page that creates the .gpx file would have to

review the code to find out what the difference is between the 4 caches

and the rest and why the automated web application is creating the

<found> tag differently than the other 24 caches created. .......

 

Thanks for looking into this,

Gary

gjhimages

 

In the email from Garmin they said they change the unrecognized tag to found. That seems like a strange default behavior to me. Most people get GPX files of caches they want to find, not ones they have already found. (Except for the MyFinds PQ)

 

This is most definitely a Garmin issue IMHO.

[+gjhimages]

Really appreciate Groundspeak looking into this and revealing that there appears to be a bug in Garmin software.

Thanks again,

Gary

gjhimages