Difference between revisions of "Pocket queries"

From GeoWiki
Jump to: navigation, search
(Caches Along A Route)
(Caches Along A Route)
Line 70: Line 70:
== Caches Along A Route ==
== Caches Along A Route ==
A new addition to GC.com is the ability to generate Pocket Queries along a predefined route.
A new addition to GC.com is the ability to generate Pocket Queries along a predefined [[Route]].
Visit [[Caches Along A Route]]
Visit [[Caches Along A Route]]

Revision as of 20:51, 26 July 2006

This page contains information specific to Geocaching.com.

Geocaching.com Premium members have the ability to create Pocket queries. A Pocket Query allows you to have a list of caches from a customized search, generate a GPX waypoint file and/or eBook.

A useful tutorial for creating Pocket queries is at Markwells Pocket Queries for Geocaching.com. A recent addition has been the ability to filter on cache attributes.

File Types

What formats does Groundspeak provide this data in?

  • The first is a LOC file (a file with the extension LOC on the end). This is currently the default file type that Geocaching.com uses when exporting information from the website into a format that can be directly loaded to your GPS. All you need is some software that can read LOC files and a cable from your computer to your GPS.
  • The second is a GPX file. This is similar to a LOC file, but the file contains much more information, including some information about the logs on the cache, whether or not there's a travel bug, etc. GPX files can also be run with the most current versions of EasyGPS or ExpertGPS, but there's also an abundance of new software being written by cachers to interpret these files. GSAK is the ideal software for the job.
  • The third format is a eBook Format file. This is particularly useful for those cachers that have Palm Pilots or other hand-held computers. It contains the information about the cache that you normally find on the cache page, including logs and encrypted clues for the caches that meet your specified criteria. The idea is to carry your Palm device into the field and save yourself from printing off cache pages to take with you.

Date Ranges

One of the most effective ways of making sure you collect all the caches for a particular state is to set Pocket queries to work using "date windows".

These date windows work effectively because once you know there are about 500 records in a given date range, it won't change. Nobody can go back to 2004 and put more information in!

Australian Capital Territory

  • 1/1/2000 - 31/12/2006

New South Wales

  • 1/1/2000 to 30/6/2004
  • 1/7/2004 to 30/6/2005
  • 1/7/2005 to 31/12/2005
  • 1/1/2006 to 30/6/2006
  • 1/7/2006 to 31/12/2006

Northern Territory

  • 1/1/2000 - 31/12/2006


  • 1/1/2000 to 31/10/2005
  • 1/11/2005 to 31/10/2008

South Australia

  • 1/1/2000 - 30/6/2004
  • 1/7/2004 - 31/12/2005
  • 1/1/2006 - 31/12/2006


  • 1/1/2000 - 30/6/2006
  • 1/7/2006 - 31/12/2006


  • 1/1/2000 - 31/3/2004
  • 1/4/2004 - 31/1/2005
  • 1/2/2005 - 31/10/2005
  • 1/11/2005 - 31/12/2008

Western Australia

  • 1/1/2000 - 30/4/2005
  • 1/5/2005 - 31/12/2006

Pocket queries do not transmit data for archived caches. Because some caches will inevitably get archived, your pocket queries will get smaller over time if you base them on date windows. For this reason it's a good practice to re-jig the date window of your PQ's every so often. This will keep the number of PQ's you recieve down to a manageable level and possibly under Groundspeaks' level of 5 PQ's per day.

Caches Along A Route

A new addition to GC.com is the ability to generate Pocket Queries along a predefined Route. Visit Caches Along A Route