PeterNoG

TrailGators is correct, but why limit your PQ to 300 when you can get 500.

Don't select a day for the PQ to run until after you have previewed the search results. Once you are happy with the results, then select a day to run it.

When you ignore a cache, you can exclude ignored caches from a pocket query. When you do a search and filter out caches that you have found, you also filters out caches that you own and caches that you are ignoring. There are a couple of local caches that I am ignoring because they have been disabled for a few months and I hate seeing them on my "closest to home" search because they are currently unfindable. I do have those caches on my watchlist, so that when something happens with the cache, I will know about it.

I assume that you klm is in your Places folder in Google Earth. At the bottom of the Places window, there is either a right arrow or two vertical bars (play tour) and a square (stop tour). Just press the square to stop your tour.

I often had a problem with single cache GPX's. I would save several then load them all into GSAK at the same time. Quite often a GPX would get corrupted in the download and then it takes forvever to figure out which ones loded OK, which one was corrupted and which one had not loaded. Now, instead of Saving an individual GPX, I just Open it. I have not had a problem with this method.

If you have the info in GSAK (from multiple "date" PQs), you can to filter by direction (ie. SE & S today, W tomorrow) or you can get very exact filters with the "arc/poly" tab in GSAK filters.

Maybe this human is just too slow because I have dial-up. I often have multiple pages open but only once in three years have I been throttled.

The only true constant is the GC number (which is based on when the 'page' was created). Your old GC number from '03 could have any date placed (as long as it's not in the future). The same goes for a brand new GC number. In my test for caches along a route, the first 500 GC numbers (regardless of date placed) were included in the PQ. That doesn't explain Markwell's Earthcache anomoly. No earthcache were included in my PQ; four were missed.

I thought I would try to duplicate Markwell's experiment. I had I route that had over 500 caches. I split the route into two parts and got 806 caches. When I tried sorting by date placed, the split was close but not exact (5 caches screwed up the split.) Resorting by GC number gave a perfect split. GC3EF to GCYP53 were included in the single 500 cache (red in pic below) query. GCYP6E to GC15942 were the extra 306 caches (yellow in pic) that were skipped.

Just under the last cache on any search page, you can click to change from kilometers to miles or vica versa.

nevermind

Someone didn't read the cache description. That's no reason to create a new catagory.

Here's a few hints that may help: Make sure that the caches that you are seeking have been found recently by other cachers. Find a few Traditional caches before trying Multi or Mystery. Make sure that your GPSr is set to WGS84 datum. Make sure that your GPSr does not "Lock on Road". Once your GPSr gets you to within 10 feet of GroundZero, put your GPSr away and observe/search.

There has NOT been a recent change that affected the TBs/Geocoins. Once activated, they appear in the dropdown list until you drop them somewhere else (I use an archived cache for my collection) or move them to an unknown location. Moving to Unknown Location will be quite teadious if you have 200; you have to do them individuallly. You can drop them all in a cache very easily.

1. We often search without reading the description, so your warnings would not help us. 2. We would not search very long if 3. Location. Location. Location. Is this really a place that you want to bring geocachers to?

Most consecutive days without a find: 34, from 7/17/2005 to 8/19/2005 - I suffered a partial tear of the Achilles Heel while caching on June 15th, but we still found one cache on the 16th before taking a break. Most consecutive days with finds: 32, from 5/19/2007 to 6/19/2007 June/07 was a really good month with these records also: Most finds in a day: 23, on 6/17/2007 Best weekend caching: 24 finds, on Saturday 6/16/2007 & Sunday 6/17/2007 Best week caching: 58 finds, from Monday 6/4/2007 to Sunday 6/10/2007 Most finds in a calendar month: 142, in Jun 2007 Fastest 100 finds: 14 days from 6/6/2007 to 6/19/2007

The problem with an automatic proximity check is that someone could zero in on the final coords of a multi or mystery without finding all the stages of the multi or without solving the mystery cache.

The OP's cache that was placed on the 5th, was approved on the 7th and there were 2 reviewer notes before publication. Sounds like pretty good service.

I don't think any wild cards are allowed but there is a 3 character minimum for keyword searches.

GSAK is great for slicing and dicing a PQ (or several PQs) anyway that you want. Then it will create a GPX that can be opened in GE.

Since the total is less than 500, on your Croatian PQ, while pressing Ctrl, click on Slovenia as well. Both counties would be included in the same PQ.

No

I'm sure that thishad been said before: It should disappear when there is an "Attended" log.

It should disappear 30 days after you logged that you "will attend".

Although GPXs are best for accuracy, live Network KML is often quite helpful. When you do get it working, under Properties - Refresh set it to View Based Refresh "On Request" so that you don't use up you views every time you move the camera.