| QUOTE (DSDhams @ July 13, 2013 07:19 am) |
| Is this a case of waiting and seeing if this get resolved? |
Yes.
As an aside, I have not had a problem with the API with my usual cache update routines (I update about 10,000 caches weekly) because I never stopped using PQ's. Maybe I'm just lucky, but I would argue that using PQ's and refreshing or getting caches only when necessary (e.g. for a trip to a one time area, or to positively identify caches that have been archived) is the best approach for three reasons:
1) You can fully automated the downloading and loading of multiple PQ's using a simple macro and Goecaching.com API>Download Pocket Queires. Once you have things set up, it's no more work than GetGeocahes (and may be less work),
2) With the API being overloaded at gc.com, you can avoid most (if not all) of the problems with the API (as I said, I've yet to hit the problems others describe), and
3) Using PQ's instead of intensive Get Geocaches or Refresh Geocaches reduces the demand on the GSAK API server and, if enough users rely on PQ's, it will help resolve the overload problem!
If anyone wants to go in this direction, I'd be happy to outline my setup in more detail.
