TheNomad

If you create a pocket query, you can then run the preview of the pocket query from a link on your desktop. All you have to do is this: a) Create the pocket query, and give it no schedule (unless you want it delivered to you). On the PQ screen, click "Preview" next to the query - you get a page with the results of that PQ. c) Save this page as a bookmark so you can always get back to it. Or, create a desktop shortcut with this URL as the destination. Voila - a one-click solution!

This is kinda what I'm talking about. Being able to do analysis of geocaches - both archived and active. But - I think I got my answer from Jeremy. So, this thread is done.

Well, I think I stated my willingness to purchase the information in my original post. It seems reasonable that there would be restrictions on the use of the GC data. I'm not looking to supplant GC.COM, only provide features to my users that they want, and that GC.COM doesn't have the time or inclination to provide. I understand that the data is available to me, as a premium member if I'm willing to glean the data from PQ's and by paging through other peoples' found caches manually. I was looking for a solution that wouldn't involve so much manual effort, and would reduce the amount of time I spend clicking on pages on GC.COM and submitting PQ's (thus reducing server load).

That's a shame really. It's a much lower load on a server to download a file than to run PQ's and generate XML. It seems like a win-win situation - I get data, and I don't kill the server. Seems to me a .zip file containing the information I referenced could be a couple of megs or less. I downloaded a zipcode database with 71,000 or so rows in it and the zip file is only 1 MB.

If you're asking specifically about why I'd want archived ones, it's for historical purposes. Example 1: I have found x number of caches. How many of those have been archived? Example 2: Of the caches I've found, which areas had more archived caches, by zipcode. Example 3: How many archived caches are there in Florida, by region. As for why I'd like to have all the rest of the data in a single download, it's for a couple of reasons: Reason 1: Formulating multiple PQ's (many many many PQ's) would be required to accumulate all that data. That has a rather large impact on the GC.COM PQ server and on my mail server. Reason 2: If I went the PQ route, it would involve multiple levels of cleansing to get that stuff - XML parsing to cull out the desired bits. Reason 3: I can't get archived caches by way of a PQ.

Is there a plan in the works to be able to download a .zip file of all caches? I'd be willing to pay extra for such a service/download. I'm not asking about geocachers' stats or anything - I'm purely asking for a download that contains: GC#, Lat (dec), Lon (dec), Name, Type, Diff, Terrain, Hider, Date placed, Status, Type, Size Ideally, it would be updated daily, and contain every cache there ever was (including archived ones).

I've pretty much avoided doing many LC's. I started doing them, but I found that (IMO) many of 'em were not all that innovative (like take a pic of your GPSr with a <insert object here>). However, one of the most challenging finds I've ever had (traditional or locationless) was A Pair of Quintuplets (Multi-Location Virtual). So, to each, their own. I don't personally anticipate doing many other Locationless caches. But, I understand it when I read about other people enjoying doing them. Like I said - that Quintuplets cache was quite challenging to locatate. It added a new dimension to caching. There's nothing like standing in the middle of a street trying desperately to get your digital camera to focus on the numbers in your GPSr at 11:30pm. Not to mention the difficulty in locating a site not on private property. Anyway - as far as locationless caches go - I recommend that one. That's my $0.02 - that and another $1.37 will get you a cup of coffee.

Agreed! In fact, I would pay extra for it...

As someone with a college vocabulary and someone with children (ages 3, 8 and 11) let me just say that there's no way in he11 that I'd let my children (any of them) read or participate in forums - whether they are geocaching forums or kiddie forums - I exercise my parental responsibility in a way that I see fit. So, as it relates to this thread - AFAIC, you can let loose with all the misspelled or properly spelled curse words - it doesn't matter to me. Nor do any curse words offend me. As a matter of fact, it's pretty dang hard to offend me. If we need a kiddie-friendly forum, I'm all for someone else (that is, not me and not geocaching.com) shelling out the cash to create a new kiddie-friendly forum (with their own server, their own bandwidth and their own programming talent). Otherwise, I consider this to be an adult forum where adults can express their views as they see fit. Finally - IMHO, too many people spend too many cycles trying to censor people from expressing their opinion. I say - let it loose. Let it all out. I'm a responsible parent. I don't let my kids surf the net any more than I let them flip through cable channels. We don't need censors. We need responsible parents. We need parents who monitor and censor (if desired) the content that kids consume. Let me decide whether my 11yr old will go to a page with WTF on it. Let me decide what stations are ok for my 3yr old to listen to on the radio. Let me decide what channels my 8yr old can watch. And, as a responsible adult, I also want to have a place where I can type "Holy 5h1t" without worrying that some irresponsible adult will allow his 6yr old to read it. That's my $0.02 - that another $1.36 will get you a cup of coffee. This product is meant for educational purposes only. Any resemblance to real persons, living or dead is purely coincidental. Void where prohibited. Some assembly required. List each check separately by bank number. Batteries not included. Contents may settle during shipment. Use only as directed. No other warranty expressed or implied. Do not use while operating a motor vehicle or heavy equipment. Postage will be paid by addressee. Subject to approval. This is not an offer to sell securities. Apply only to affected area. May be too intense for some viewers. Do not stamp. Use other side for additional listings. For recreational use only. Do not disturb. All models over 18 years of age. If condition persists, consult your physician. No user-serviceable parts inside. Freshest if eaten before date on carton. Subject to change without notice. Times approximate. Simulated picture. No postage necessary if mailed in the United States. Breaking seal constitutes acceptance of agreement. For off-road use only. As seen on TV. One size fits all. Many suitcases look alike. Contains a substantial amount of non-tobacco ingredients. Colors may, in time, fade. We have sent the forms which seem to be right for you. Slippery when wet. For office use only. Not affiliated with the American Red Cross. Drop in any mailbox. Edited for television. Keep cool; process promptly. Post office will not deliver without postage. List was current at time of printing. Return to sender, no forwarding order on file, unable to forward. Not responsible for direct, indirect, incidental or consequential damages resulting from any defect, error or failure to perform. At participating locations only. Not the Beatles. Penalty for private use. See label for sequence. Substantial penalty for early withdrawal. Do not write below this line. Falling rock. Lost ticket pays maximum rate. Your cancelled check is your receipt. Add toner. Place stamp here. Avoid contact with skin. Sanitized for your protection. Be sure each item is properly endorsed. Sign here without admitting guilt. Slightly higher west of the Mississippi. Employees and their families are not eligible. Beware of dog. Contestants have been briefed on some questions before the show. Limited time offer, call now to insure prompt delivery. You must be present to win. No passes accepted for this engagement. No purchase necessary. Processed at location stamped in code at top of carton. Shading within a garment may occur. Use only in well-ventilated area. Keep away from fire or flame. Replace with same type. Approved for veterans. Booths for two or more. Check here if tax deductible. Some equipment shown is optional. Price does not include taxes. No Canadian coins. Not recommended for children. Prerecorded for this time zone. Reproduction strictly prohibited. No solicitors. No alcohol, dogs, or horses. No anchovies unless otherwise specified. Restaurant package, not for resale. List at least two alternate dates. First pull up, then pull down. Call toll free before digging. Driver does not carry cash. Some of the trademarks mentioned in this product appear for identification purposes only. Record additional transactions on back of previous stub. Decision of judges is final. This supersedes all previous notices.

This evening, I'm getting the same error over and over when I try to access the site. It took a while before I was able to get into the Forums. Anyway, here is the full text of the error: I get this in several places - notably going to my cache page, or trying to load forums. Server Error in '/' Application. -------------------------------------------------------------------------------- Unable to make the session state request to the session state server. Please ensure that the ASP.NET State service is started and that the client and server ports are the same. If the server is on a remote machine, please ensure that it accepts remote requests by checking the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\aspnet_state\Parameters\AllowRemoteConnection. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Web.HttpException: Unable to make the session state request to the session state server. Please ensure that the ASP.NET State service is started and that the client and server ports are the same. If the server is on a remote machine, please ensure that it accepts remote requests by checking the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\aspnet_state\Parameters\AllowRemoteConnection. Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [HttpException (0x80072740): Unable to make the session state request to the session state server. Please ensure that the ASP.NET State service is started and that the client and server ports are the same. If the server is on a remote machine, please ensure that it accepts remote requests by checking the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\aspnet_state\Parameters\AllowRemoteConnection.] System.Web.SessionState.OutOfProcStateClientManager.MakeRequest(StateProtocolVerb verb, String id, StateProtocolExclusive exclusiveAccess, Int32 timeout, Int32 lockCookie, Byte[] buf, Int32 cb, Int32 networkTimeout, SessionNDMakeRequestResults& results) +512 System.Web.SessionState.OutOfProcStateClientManager.DoGet(String id, StateProtocolExclusive exclusiveAccess) +53 System.Web.SessionState.OutOfProcStateClientManager.GetExclusive(String id) +7 System.Web.SessionState.OutOfProcStateClientManager.System.Web.SessionState.IStateClientManager.BeginGetExclusive(String id, AsyncCallback cb, Object state) +6 System.Web.SessionState.SessionStateModule.GetSessionStateItem() +67 System.Web.SessionState.SessionStateModule.BeginAcquireState(Object source, EventArgs e, AsyncCallback cb, Object extraData) +275 System.Web.AsyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute() +66 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +173 -------------------------------------------------------------------------------- Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET Version:1.1.4322.573

One of the things I'd be willing to pay for as part of this is a starter data-drop, and then access to specific URL's that more humanely allow gleaning data from the site. As an example of the former, I would gladly pay for a CD that contained all the relevant information about every cache in the system - no, not every log or anything like thiat - I mean the GC#, guid, date placed, lat/long, type, container type, status (active, archived, temporarily offline), etc. This would let me pre-populate my database with all the caches out there as a starting point. As an example of the latter, being provided with either specific URL's, an RSS feed, or files that can be FTP'd - the caches placed/updated (status update) within the last 24 hours. This would let me keep my database up to date. Having access to this data would allow me to generate code that would, for example: a- List caches along I-4 from Orlando to Tampa within 1 mile of the interstate. b- Build trip-based cache lists that aren't point-of-origin based. c- Build stats that are geographically broken down by state, zip code, etc. Stuff I'm willing to let my CPU churn and do, but may be of less interest to the general population of cachers (and therefore shouldn't be part of the GC.COM website. That's my opion - and we all know about opinions...

From my standpoint, I'd rather that there were simple(ish) URL's I could submit that would return data about another cacher (with their explicit permission of course) that would eliminate the adornment html and such, and simply list out the GC#, Lat/Long, Date found, Diff/Terr, and a few other goodies in a format easy to parse. I'm quite happy harvesting the information and using my own database storage and my own CPU for computing stats. I would just like a mechanism for extracting the data that doesn't have a huge cost on either the PQ server, or the web server. I don't care whether any particular person wants a stats page or doesn't want one. I know that I have some users that do want to have a stats page, and I'm happy to code it up. I just don't want to execute some kind of long-running query that will tax the system. Then, if you don't want to see your stats or have 'em computed - well, they won't be. Full stop. But, I can satisfy the users that do.

Here in the Orlando area, I've been hiding similar ones that have been dubbed "Nano-caches" for about six months or so. You can get 'em for $1 each. Just load this page and search for DT03050. For shock value, I created a log with 24 lines that fits into the smaller inner pill container. It's worked so well that I've never had any soaked-log problems.

First, thanks much for making the My cache page more usable. My TB list was getting huge - especially with the ones that are "creative" with fonts. Feedback is important in these things, so I'll make it short and sweet! 1) I agree that the current My Caches is not nearly as helpful as the old one. Before, I had a simple half page. Now, it's three pages long. I really think we need a My Caches tab. 2) Under Geocaches - I agree - the full log is way TMI - abbreviation of the logs to 80 or so characters should be sufficient. That way, we can get more than 15. 3) I'm personally thrilled with having the TB's split out. It's just what I wanted. Thanks again. 4) On the Quick View, I suggest having a link to PQ's (for members) because we use those a lot. In all - I'm much happier with the new layout. Thanks for the good work.

I'd create a puzzle cache as the Bonus cache. The reason I'd choose a puzzle cache is because the coordinates don't have to be correct - the only way you get the corrected coordinates is to take a pic doing CITO at your other cache. Then, post the pic. You send the offset to the coordinates which takes 'em to a bonus cache that they can claim. So, no double-claimed cache, no feathers ruffled. That's just my opinion - and we all know about opinions...

On March 19th, I'll be 32!!! Holy crap. The gray is starting to show!

I worked with this for the first time last night, and I noticed something. It completely ignores your credentials and thus doesn't allow you to eliminate caches you found.

I had two of my bugs get "stolen" and placed in a TB graveyard by some jerk. The reason was that the TB SN was visible in the photos I took of the bugs. After I learned a bit, I had corrected the photos. But apparently, he had gleaned the numbers long before. I wouldn't have made that mistake if I had understood the security of the bug number. Also, I'd recommend a change for TB numbers (I know, this has been batted around before so save the flames... ) but there should be two numbers - one on one side, one on the other. It takes both to log the bug. For example: Side 1 - 231443 Side 2 - AX15Q Kinda like a checksum - having one doesn't do you any good without the other, and it would prevent newbies from the same fate that befell my two bugs. That's my 2/100 of a $.

Funny enough, I raced out last night to be FTF on a new cache that was just posted. I got to the site (Slim Bob Arrives in Winta Paark) and started the hunt. The coordinates stuck me in the middle of a usually busy four-lane road (but it wasn't bad at midnight). Anyway, I poked around these little road-side reflectors and such for about 30 minutes to no avail. As usual, I posted my DNF. Well, apparently, the coordinates are actually nowhere near the cache - something must have happened when she entered the coordinates. But, the bottom line is - because of the feedback to the owner of the cache, it was temporarily disabled immediately so that it can be fixed. IMO, that's what logging DNF's is about. I searched, I didn't find it - I logged a DNF. The owner of the cache used the feedback to correct the coordinates.

I was caching in a park somewhere in the San Jose area. The entrance to the park has these HUGE powerlines running through it. Just massive. Anyway, when I was about 6' from the cache, I saw it - and started to reach for it when - BAM - two kids (14ish and 18ish) with a dog walked right up to me and asked me what I was doing. My answer? "I'm measuring electromagnetic frequencies in this area to see if they are high enough to hurt small animals." They beat a hasty retreat.

I've got a cemetery multi-cache called the Cemetery Gauntlet here in the greater Orlando area. None of the caches themselves are in a cemetery, but each stage has you go to a headstone to collect birth and death dates. The final stage uses all the dates as a "what happened in this year" google-quest. Anyway, it's been well received, but I didn't hide any of the micros inside the gounds of any cemetery, and the final stage is in a park across from a cemetery. I personally love cemeteries, and I love showing people the wide variety of cemeteries in the Orlando area. Clearly, we don't want people dumping flowers out looking for a cache - that's where care and permission are important (and also why my caches are all outside the cemeteries). That my 2/100 of a $1.

I too had many logs enter the ether yesterday. I finally gave up, and chose to log them this morning. I got everything from "Service not Available" to DNS errors. Talk about issues - holy crap. Anyway - I hope that these issues get resolved soon. There's nothing like composing a detailed description of a caching experience (like I did) only to have it disappear down the bit bucket.

The one time I was busted by a "muggle" with cache in hand, my statement was "I'm taking electromagnetic readings". The cache was in a park that had HUGE power lines running through it. It seemed plausable to me, and they seemed to ignore the large ammo can in my possession. In heavy traffic areas, I do tend to take the cache far away from the hide area to go through it. Otherwise, if I have no trade items, I will take out the log, move far away to sign, and then move back to replace it. My biggest fear is compromising the hide.

I hid one members only cache, and changed it within a week to a standard cache. I didn't realize at the time how polarized this issue is in the caching community, so I decided not to ever hide another MOC. About the only good reason I can think of for an MOC is as a members-only FTF leg up. But otherwise, I don't think it's worth it to hide an MOC. I'd rather get the traffic to my cache than only have one hit a month or so on it. That's my $0.02. That and another $1.73 will get you a cup of coffee.

Similar to the Nanocaches I've placed in the Orlando area. You can find 'em here: IMSPlus Load that page, and search for "DT03050".