Cache O'Plenty

Here's an idea - just look at the back of each of the State Quarters and do a cache at each of the represented items. And for those that have just the state outline or a generic item, then go to the State Capitol. Looks from your list that you like history of some kind. Every state has a historic element of some kind. Surprised you couldn't come up with something for one of your neighboring states - Virgina. Seems I remember that something in history happened there.

I see no problems here. There are many modes of transportation that don't involve parking right next to GZ. Lots of folks bike to caches. Or walk. The limited hours will impact some folks but that's just part of the challenge. We have one near here that it's in a drive-in theater that's only open on Tuesdays and Thursdays for a swap meet (free parking then). Or at night, of course. And we have a Mystery Cache that is only available on Sundays (in fact, it's called Only On Sunday). Since it's a Multi, I do hope that all of the stages are available at the same time and not spread over the week! Be sure to include the hours of availability in your cache page.

BTW - is this one multi or seven traditionals leading to a bonus "unknown" cache. A multi is only logged once versus the seven traditionals and the unknown being logged separately. And, yes, contact your reviewer ahead of time if you want them published after a certain time on a certain day. There is no guarantee that it will happen at the exact time you want. Reviewers do not have a system where they can set a delayed publish command so, if they have other commitments, they may not be able to do what you need. The other option is to hand out the coordinates. However, if they aren't published, then the attendees won't be able to see your cache pages.

In the meantime, put it on your Watchlist so you'll get any logs that may be generated.

Do you want just the archived caches or all finds? Premium members can already do that with their "My Finds" pocket query. It's just imported into GoogleEarth and they are all displayed. If just the archived caches are wanted, then it just filtered using GSAK or some other third party software.

FYI - If you are using the .kml add-on, the caches in GoogleEarth will only show an approximate location. This is by design so you can't circumvent the PQ process. However, if you import a PQ .gpx file into GoogleEarth, it will show the correct location (subject to the accuracy of the coordinates portrayed in GE).

If they are very near the cache in question, wave your GPS and ask "Did you find it?".

Admit it - everyone that saw this post went and checked their own stats.... I did also. 85 found and only 6 of them have been archived. That over 5 years of caching. Yep, did the DC Mall in May of '09. One of my favorite ones was the one at Grand Canyon, 10 feet from the edge. I don't have much of an acrophobia problem but the other half does. Needless to say, I did that one solo. And I only have 21 left within my home area - 30 mile radius. Will have to start focusing more on those. Personally, I would like virtuals to come back but that's another story (thread).

Yes, they had some issues with PQs yesterday. Check the Get Satisfaction topic on the update. It's located in the right-hand column. Much, if not all, of the problems have been resolved. And, yes, you can e-mail GS to ask for a reset.

The FindStatsGen3 macro for use with GSAK has all kinds of options concerning stats. It also has at least two functions involving notes. I haven't investigated those too much so I don't know if that will do what you want but it's worth a shot.

Same here. Red X is on mine as well. And the download worked fine. Do your other PQs download OK? The size of the file might be the culprit. If your My Finds is large (mine is 2.07 MB) your browser may have some limit. My regular PQs are <1.0 MB each. I also had an issue once when I downloaded the file and tried to open it before it had completely downloaded. Got an error then that it was corrupted. So, I just wait a bit to make sure it completes the task. Now no problems.

Well, exceptions have been made. I know because I received two. One due to fences and highways that cannot be crossed. The other was just what you are describing, a steep cliff. Mine were really quite separated at over 480 feet apart but still did violate the rule (err... guideline). Maybe you didn't convey the cliff element of the obstruction. It's not really clear from the maps. Perhaps a picture or two from one cache to the other showing the cliff in the way! Or, you could make the three caches into a multi. Then you don't need to worry about the distances (only within the multi). All three would still have to be further from existing caches by the 528' rule though.

And, remember, the errors only are additive if they are off in the same direction! It's entirely possible that they could be offsetting each other. The 28 ft. is the max normally encountered. Now, in this parking lot, are there overhead power lines? Or is there a block wall or building adjoin GZ? Those could throw both units into a tizzy.

The limit is 528 ft (0.1 mi) for "do it yourself". Beyond that requires a reviewer to do it. However, this function was intended to allow correction of input errors or to adjust the positioning of a cache a small distance. Although it does allow you to move a cache up to that distance, anything more than a few feet or so actually becomes a new caching experience and should be done by archiving the old cache and creating a new one. But if you are merely moving it from one tree to the next, you can do it yourself as mentioned above.

We have a number of "bag" caches here in the dry areas. But, usually, the bag is wrapped with camo tape to create a pocket. The camo tape only adds a small amount of thickness to the bag and greatly increases it's resistance to the elements. The ziplock part of the bag has to be of higher quality or the log will get wet/dust/etc. The cache site has to be protected from the sun and the occasional rains (winter).

You could make it a three tier series with two groups of three traditionals, each of which could have codes that when put together will give them the two second level caches. That's your eight caches. Then, if you want, you could add the final, top level cache as a bonus. The coordinates for that one would be in the two second level caches (longitude in one and latitude in the other).

Even the best models won't give you the same degree of accuracy that you will get out in the open. But they will be better. Until then here's what I found to help (I cached DC a while ago and had little trouble, even for the few just north of the mall). Get as far away from the buildings as possible (i.e. in the middle of the street if you dare) and walk the center line. Watch the needle until it points at 3 o'clock or 9 o'clock and note the distance. Then pace it off toward the building. After that, it's the geosenses that will help you.

I have the nuvi 660. To do what you want to accomplish (get the coordinates back!), I would copy the file "Current.gpx" from the nuvi's "\gpx" folder to my PC. Then, with GSAK (and, I presume any other software that can read .gpx files) I would upload the "current.gpx" file and get the coordinates that way (they are listed as Latitude and Longitude field names).

It's a system generated Bookmark List with special properties. You can't recreate a new one. At least, not that I'm aware of. Someone a few weeks ago did that and now doesn't have that capability anymore. He was directed to contact Groundspeak to try to fix it.

Wheelchair height is about 4.5' off the ground or so - that's a 1.0 if the wheelchair can get to GZ. I'm shorter than average, and I know it. So, if I can reach it unassisted (up to 7'0", it's a 1.5 (wheelchair plus). I carry a TOTT in the car that helps me compensate. With that, I can reach most any cache that's 10' or less. If I can add a rock, stump, pail, fence rail to the mix, I can increase that to 12' or so. These make the T about a 2.0. Anything above that is 2.5 or greater.

If it's in bushes, I pull out some of the trash. If anyone asks what I'm doing, I ask if they'd like to help.... They usually leave.....

Just because the CO checked the box doesn't give me a warm feeling that EVERY aspect of the guidelines were reviewed by the CO and that he remembers every one of them when he checked it. I mean, how many people actually read those "I agree" statements that come with software. Some are quite extensive. I believe the checkbox is there to give Groundspeak some leverage of denial when issues arise about violations of posting guidelines and allows them the ability to Archive, modify, disable cache listings that do. And, given the number of LPCs that are placed that we KNOW do not have "adequate permission", why would you assume that those with No Trespassing signs do have that permission? I would skip the cache. Depending on mood, I might post a NA or, at least, a "Note".

Well, you can always use: 1. Tying your shoes over and over again. 2. Use the GPS as a cell phone. 3. Drop your keys. 4. Work on your bike at GZ while looking. 5. If a bench or retaining wall is nearby, sit and read the paper/book/anything. 6. Ignore the muggles and just keep looking - just don't pull the cache out if you find it until you are "muggle safe".

Problem here is that everyone is different in how they use the site and what their priorities are. For example, of the main sections in the right column, I don't need both the Hello section AND the Stat Bar. And, I really don't need to know my GPS units! I don't use Twitter so push it down. So, leave the Hello section and follow that with: 1. Field Notes - Yes, that is used quite often now that I have my smartphone working! 2. Pocket Queries - a must 3. Bookmarks - Somewhat often 4. Your Inventory - good reminder that I have TBs/Geocoins to drop off Everything else can be "below the fold". I haven't looked into "saved GPX files" yet so.... Best option is for the user to be able to define the "Order of Appearance" of the sections. I almost never use the search functions, or the map functions. I don't use the route functions either.

Isn't that the same thing as "scraping"? As I understand the problem, it has nothing to do with bandwidth or other transmission loads. It has to do with the Terms of Use clause. I think the following clause is the guide here. 5. Access and Interference Much of the information on the Site is updated on a real time basis and is proprietary or is licensed to Groundspeak by our users or third parties. You agree that you will not use any robot, spider, scraper or other automated means to access the Site for any purpose without our express written permission. Additionally, you agree that you will not: (a) take any action that imposes, or may impose in our sole discretion an unreasonable or disproportionately large load on our infrastructure; or ( interfere or attempt to interfere with the proper working of the Site or any activities conducted on the Site or other measures we may use to prevent or restrict access to the Site. It's the part BEFORE the word "additionally".