lysernix

Utilize scripts and add-ons mentioned for workarounds. I was curious, so I did the math and it looks like the Google licensing model based on 2,000,000 requests per day from Groundspeak, would roughly cost about $2.8 - 5.8 Million per year depending on the API utilized. It then quickly becomes clear why the change was made to a lesser product. You get what you pay for... and going from (free?) to that staggering cost is quite a leap that would require a large re-think on the process. In the mean time a free model becomes a thankful fallback, even if it is vastly inferior. I do like the new CSS that is being used though. But yes... I've been frustrated but at least now I know why.

I came here looking for the answer of this question... how to do it... looked all over, and at least am glad to see that I didn't miss it somewhere. This is a grevious oversight in my opinion and seems like it would be something that could be easily added. There are a couple of situations I wanted to use this: Situation A: Kansas City has a "battleship series" in which a 10x10 grid has been constructed overlaying the Kansas City Metro area and in each 1x1 block there is a cache that contains a hit or miss, and you sink the ships etc. It's actually a lot more complicated than that and an absolute wonder of a series... but that's not the point. I basically was trying to get them all on the map so that I could, if I was in a certain area of Kansas City easily identify when two (or more) of the Battleship series were in close proximity. If I had just been able to search by name within a certain radius I could have created this in one fell swoop - either via pocket query or by how I basically handled it as a workaround: I manually added all 107 of the caches by hand to a bookmark/list. Once the list was created I was able to create a pocket query against that list... then when looking in map view I could add the pocket query filter and uncheck everything else... (as you probably imagine the KC area is littered with caches!). In this way I'm easily able to view the entire series and can identify situations where if I'm in very close proximity to some grid blocks while at others its advantageous to grab them all then. Ok so that one's solved! But could have been a lot easier - they are all named A1: KC Battleship, C5: KC Battleship etc... so the text match on Battleship would have returned all the results I needed... (then could have easily picked out any strays). Situation B: I don't have a workaround for this one (yet!). Some caches / challenges in this area require you to find certain other caches. Specific Example: http://www.geocaching.com/seek/cache_details.aspx?wp=GC3A9Z9 The cache requires: "2) Find FOUR other caches with the following words that STAND ALONE in the Title of them: 1) WILD 2) BLUEBERRY (You may do 2 caches for this word--one with Blue in a Cache Title and one with Berry in a Cache Title 3) RIDES 4) AGAIN" I would like to do this really without it having to be a pocket query. It's not complicated. I simply want 2 criteria: name & location/proximity. I can search for any one of those words and receive thousands of results from around the world... but of course I'm really only interested in those 100mi from me... or in Kansas or Missouri... or in an area code... whatever's easiest. It would even be serviceable if I could simply sort the results by proximity to home location but that doesn't appear to be a sortable column. If it needs to be a pocket query that's fine too. If anyone knows of a workaround for this let me know! And Pioneer Poodle... perhaps my "situation A workaround" might help you in certain situations! And Bhob... yes enhanced all around would be nice... particularly "Placed By: X" "Favorited By: Y" etc... I believe searching by name of cache - which is an option now (and it does do partial matches) is an absolutely essential piece missing from PQ and/or should simply be added to "advanced search".

The website? For me I did it through the app, just went to "Change User" (under menu) and then re-signed in as myself, fixed right-away... and got another confirmation email from Groundspeak about device activation. Funnily though I had the same issue with the Forum for a moment and of course, signing out and re-signing in on the site worked just fine for that!

I had a 3GS (which admittedly was aging) and it worked moderately well with the Geocaching app, but it would kill the battery. Once when I was out hiking in a park on a 5 mile trail it went out on me completely and never responded again until I hooked it back up to power (and when it went out it "said" it was at 50% battery or so). Anyway... it did work moderately well most times. However, due to said incident, and want of a possible better experience I went ahead and upgraded to the 4S. If not for geocaching I'm sure I would still be using the 3GS as for most other purposes it suited just fine. The 4S has been GREAT for caching though! I love it... has yet to let me down at all. One other thing I noticed... I believe on the 3GS it would always say +/- 32ft? Maybe I'm misremembering or that's just what it said some of the time... but the 4S device accuracy is ALWAYS +/- 16ft... and usually it seems to be even more dead on than that.

I have an iPhone 4S, and I previously used the app on a iPhone 3GS... on my apps, when hunting a cache there is a small button that will let you toggle basically if the map points north, or if the map points in the direction you are headed. Very helpful I've found when trying to find some certain caches! I realized this when I once inadvertandly disabled the function... Anyway! A friend of mine has the T-Mobile HTC HD7 Windows Phone, with - what I believe are the latest versions of all software (Mango update, latest GeoCache App version). Is this phone capable of the same function? His map always points north and I checked on it through several menus and wasn't able to get it to work. It seems as though there is a compass function on it because clicking the compass seems to work/rotate as you do... it just won't do it on the map. Any help is greatly appreciated! Thanks.