Tweedledum & Tweedledee

It sounds like 8 was a popular number. Most teams submitting had 8 just not the same 8.

The Atlanta one was: GC21QTD. You can find the rest pretty easy from there.

I can answer part of that for you. They were posting virtual caches in areas that were possible locations of the balloons. FTF hounds like myself jumped at the opportunity to be a FTF'er at such a cache and dashed off to the coords to search for the balloons. Sadly though, there were no balloons in Atlanta. Actually there was a balloon in Centennial Park. (DARPA's site now reveals all balloon locations.) I see that now... Darn.

I can answer part of that for you. They were posting virtual caches in areas that were possible locations of the balloons. FTF hounds like myself jumped at the opportunity to be a FTF'er at such a cache and dashed off to the coords to search for the balloons. Sadly though, there were no balloons in Atlanta.

To have cache not show on your search results all you do is add them to your ignore list. This can be done by selecting "ignore listing" on the right hand side of the cache that you want to ignore. As for features that you can now take advantage of I'm not too sure what to tell you. Most of the features a best used when you have the ability to send the data strait to a GPSr device. An example of this would be the pocket queries; they can be used even if you can't send the data to GPSr or PDA, but are most useful for that purpose.

The scenario is that I am looking up caches in the geocaching.com maps. After I pick a point and identify the caches and get a list below the map, I then check mark some then select the bookmark button at the bottom. It then list the caches that I selected and then I select the click to confirm button. After selecting that I get this: It doesn't matter which caches are selected. I tried only pick one then picking a different one, so it's not a particular cache causing this.

My opinion is the scenario should play out like this: Log a DNF. Take a picture of what you found and where you found it. If the cache owner confirms that what you found was the cache then they can decide if appropriate for you to change the log to a found. This is the way I have seen it handled in the past and seems to work.

This would be a question for Garmin since they are the ones that programed the plugin. As for an educated guess I would say yes. The plugin is written in java and as long as your browser supports it then it shouldn't matter the operating system.

The only way to run a pocket query is to goto the My Pocket Queries page.

why would ANYONE complain about having the hint on there GPS? You think they want to print the hint and carry paper or there palm? If they don't want hint, don't look at it! Help me understand this.... Some people want more of a challenge. We typically won't look at a hint until we have given it our best search. Others wont take anything with them but the coords. This is why the hint is at the bottom of the page and encrypted with a code. If everyone wanted to see the hint right off then it would be decrypted and right under the name.

It does load similar to the way a .loc is loaded, but the communicator plugin is not limiting the possibilities of a hint in the description. So all it would take is changing the code on geocaching.com, but I think having the hint right in the description would cause more people complaining that not having it.

On the bug's page, goto the "edit this item" link on the right and bug image is the second line.

It's a problem everywhere, and there is nothing that can be done about it. Yes, adding the below picture to your cache page might make you feel better, but it's not going to stop everyone from leaving pointless items.

GPSbabel would be another solution, and the test output is formated fairly nicely. I don't think that using text docs on an Ipod will be a very user friendly way of doing things, but I guess it works!

Even though the solution has been pointed out, I still think this is an interesting idea. I don't think, however, that it would be as simple as adding a check box called "I'm using a polygon instead of a line." And for that reason I don't think its going to happen, but it is a good idea.

Just realized you might mean a picture from on your computer. The answer to that is you can't. You will need to host it somewhere on the web then post as I did the logo.

Do you mean like this: Just click the button on the tool bar that looks like a tree.

Well if you do make a pocket query of a list of bookmarked caches you can view them in google maps. Now as to why all the options are missing when you try to make a pocket query of a bookmark list, that is because you don't need to define what caches you want on the pocket query page since you have done that by making a bookmark list.

This thread seems to be dropping off the page and the problem hasn't been fixed. I think it should be a simple fix. Here's the code from geocaching.com: function getWptData() { var lat = 33.820283; var lng = -84.728183; var elv = 0; var name = 'GC1397T'; var descr = 'Blessed are the Meek #8 - Relocate'; var type = 'Geocache|' var sym = 'Geocache'; waypoint = new Garmin.WayPoint(lat, lng, elv, name, descr); var factory = new Garmin.GpsDataFactory(); var gpx = factory.produceGpxString(null, [waypoint]); I think this is how it should be: function getWptData() { var lat = 33.820283; var lng = -84.728183; var elv = 0; var name = 'GC1397T'; var descr = 'Blessed are the Meek #8 - Relocate'; var type = 'Geocache'; var sym = 'Geocache'; waypoint = new Garmin.WayPoint(lat, lng, elv, name, descr, sym, type); var factory = new Garmin.GpsDataFactory(); var gpx = factory.produceGpxString(null, [waypoint]); Note the subtle changes made: 1)"|" removed in var type= line 2)";" added in var type = line 3)", sym, type" added in the line where the wapoint is created

Actually now that I have been looking over the code on the Geocaching website I found the correct line in question. Here's from the geocaching website: waypoint = new Garmin.WayPoint(lat, lng, elv, name, descr); Here's the API information: initialize void initialize(lat, lng, elev, name, desc, sym, type) So the problem IS with the website coding they simply left off the sym (symbol) and so it defaults to the blue flag on color units and a pixel on non color units.

I will need to look into the Api but it seems like such a basic thing to be able to control what icon the waypoint gets. From what Raine posted - I would conclude that the interface does not support setting the icon. Constructor Summary Garmin.MapIcons() Icons used to mark waypoints and POIs on Google maps. Setting the icon is in the Garmin Communicator API, so it seems the fault in the wrong icon goes back to this websites scripting.

Well.. has anyone contacted Garmin as to what can be done about the icon? I doubt if anything can be done. Not all GPS units have the geocaching icon. It looks like it's defaulting to a generic icon, so it can be used on the greatest number of units. The problem that people are having with the icon is that it's not the closed chest, which is what Garmin GPSr use for their Goecaching mode. If you don't have a Garmin then this feature doesn't work for you anyways and most people have a geocaching compatible GPSr (that has the geocaching mode).

How long has this been going on for? I have noticed that there has been times when our owner note emails have been delayed for up to two days, but eventually we have gotten them all. It doesn't happen very often, but it also happens with other notifications.