Archive for the ‘wap’ Tag

Comparing Geocaching WAP site and BCaching

Here’s a comparison between’s WAP site functions and, hereafter referred to as GCWAP and BC.

View Cache Search

  • GCWAP requires entry of GC waypoint with or without the GC prefix.
  • BC does this too but will also search the cache name (although name search is only done near your current origin).

View Cache Detail

  • GCWAP includes name, gc#, owner, coords, short and long descriptions in plain text.
  • BC does this but also shows when it was hidden, when the last find was, size, difficulty, terrain, and also shows the full html version of the description with images and links (note: if the description exceeds a certain size only the plaintext version is shown and truncated at that, but then there is a link to view the complete original description.)
  • GCWAP and BC both show hints and travel bugs in the cache.
  • BC will also show additional waypoints
  • GCWAP will show the 5 most recent logs. These will always be the most recent and up to date.
  • BC will show as many logs as are available on BCaching. After the first pocket query, there may only be the most recent 5, but over time with regular updates, the number of logs will increase. However, it will only be as up to date as the most recent pocket query.
  • BC also shows the icons for the 8 most recent finds up top of the detail page so you know right away if there are a bunch of finds, DNFs, notes, etc.
  • BC provides links at the bottom of the details page to various GC pages: full detail, print view with logs (same as full detail but takes less bandwidth, Cache Owner profile page, Log, and Nearest caches).
  • GCWAP has a link to a google map image.
  • BC links to Google Mobile Maps or Blackberry Maps (both of these currently only work on Blackberries though).
  • GCWAP has super small pages and uses very little bandwidth.
  • BC has larger page sizes than GCWAP, but provides more information and sends the pages compressed with gzip if possible (supported by most modern mobile phone browsers).

Logs and Field Notes

  • GCWAP lets you write LIVE cache logs and drop off trackables from your inventory.
  • BC uses Garmin Colorado-style field notes that have to be later downloaded from BC and uploaded to Trackable Inventory is managed independently of so they have to be logged in later when writing logs from the field notes.
  • BC also keeps track of your finds and can include the find# in your log.
  • BC can also include the find-time in your log and keep track of a recurring header to be included at the beginning of your logs.

Find Caches Near a Location

  • GCWAP lets you search by coordinates or zipcode and lists cache summary information with distance.
  • BC supports coordinates, zipcodes, and also city names. You can also find nearest caches from another cache.
  • BC displays summary information with distance and ALSO direction.
  • BC uses keeps track of where you are based on the field notes you write. As you travel from cache to cache and write a field note for each cache, BC automatically updates your origin based on the cache coordinates of the last field note.
  • GCWAP does not exclude caches you’ve already found from it’s list of nearby caches.
  • BC by default DOES exclude caches you’ve already found, but also lets you setup a custom filter similar to a pocket query: including cache types, container types, difficulty and terrain ranges, caches you’ve found, haven’t found or even own.

Travel Bugs

  • GCWAP lets you lookup trackables, view its detail, history, and write LIVE logs for pickup, discovers, and notes.
  • BC lets you lookup trackables, view LIMITED detail (with a link to the full page), NO history, and manage your FIELD inventory. All pickups and discovers must also be recorded later on

New Features and Enhancements

  • GCWAP hasn’t changed much in years.
  • BC is under active PART-TIME development and I’m always looking for ideas to improve the site (The Travel Bug inventory management and Field Note headers functions were user requests).

BC Only (not applicable to GCWAP)

  • Since it can be a pain to have to keep a mobile/pda application up to date with the latest pocket queries, BC provides a personalized email address for each user to which GC pocket queries can be be sent to directly on a regular basis; eliminating the need to manually run and upload pocket queries.

Paperless Caching with your Mobile Browser

Is anyone interested in yet another Paperless Caching tool?

There are a lot out there, but I thought I’d try my hand at a web-based paperless geocaching application that did the things I wanted it to do and worked how I wanted. We’ve been using it almost exclusively on a Blackberry 8130 since May 2008 and it is evolving as we continue to use it and think of new features we would like it to have.

I’d like to see a few others start using it soon and get some feedback on how it works and see how the application performs with multiple users. I’m also curious about other cacher’s opinions for more features to make it better.

The idea is to allow smart phones with unlimited data plans to access geocaching data via the phone’s browser. It is relatively easy to use (I think) and gets things done with as few clicks as possible, and does not require the use of any separate programs to manage or organize data.

It does not provide navigation, it simply manages the geocaching data and notes so you still need to use a separate program or GPS for the navigation. The geocaching data comes from uploading Pocket Queries to the web site to individual accounts. I contacted Groundspeak regarding their terms of use and expect to get their blessing regarding the use of the geocaching data from pocket queries. Their primary concern is that users only be able to see the data they’ve uploaded, and the data should not be allowed to become “stale”. If the data has not updated after a month, it should no longer be available until refreshed from a new pocket query. The application has met that criteria.

Here is a breakdown of the current features:


  • Web-based, allowing the server to do all the heavy lifting. Phone does not have to be very powerful, but must have Internet data access.
    – Downside to this is that Internet data access is always required. Loss of data connectivity results in a non-functioning application from the client’s perspective.
  • Relatively small, compressed pages (if compression is supported by the phone’s browser) in order to keep bandwidth usage low. Even so, an unlimited data plan is recommended since every interaction requires data communication with the server.
    – Typical list of Nearest 20 caches requires about 7 KB of bandwidth on first request (compressed) – including images. With caching of the static images and style sheet, additional requests on the Nearest Caches page drops to about 1.5 KB (compressed) with the uncompressed page size around 5.5 KB.
    – Typical Details page varies depending on size of cache owner’s description, but are usually around 3KB (compressed).
  • Target clients are any relatively modern smart phone with an Internet mobile browser and a data plan. So far testing has only been done with a Blackberry Pearl 8130 and to a more limited extent on an OpenWave simulator.
  • Easy to use Pocket Query management for uploads, using a desktop browser.
  • All times are stored in GMT. Local time zone can be set on user profile page.

Nearest Caches

  • Default view is limited to the nearest unfound caches based on the current location (currently to a max of 15 miles away).
  • Aware of location without needing a GPS. Set current location by street address, city/state, zip code, or coordinates. Location lookups provided by Google – any location you can look up in Google Maps can also be used here.
  • As you post notes on caches (found or otherwise), the current location is updated based on that cache’s location.
  • Search for specific caches that are further away by GC# (with or without the GC prefix) or by partial cache name.
  • Filter allows for more advanced searches and selection criteria; by cache type, difficulty and terrain rating, container type, and more.

Cache Details

  • Cache Details page contains full description (in html) with all available logs based on imported GPX files – this still may not be all logs, but iterative GPX file uploads over time will increase the amount of log data available.
  • If full description is too long, it is converted to plain text and truncated on the main details page. A link is then provided to the full HTML description.
  • List most recent log icons at the top of the details page indicating finds, dnfs, owner maintenance, etc. Full logs are listed below the cache description.
  • Link for KML version of currently displayed cache. Clicking the link will automatically launch Google Maps for Mobile if installed with the cache information summary.
  • Links to cache pages for quick access to the latest and complete information on a cache page – print version in order to keep pages as small and noise-free as possible.

Field Notes

  • Field Notes can be entered, edited, or deleted on any cache including log type (Found it, Didn’t Find it, etc.) along with a short description.
  • Field notes can be easily exported and uploaded to Field Notes using a desktop browser.

Data restrictions

  • Cache data terms of use is the same as Groundspeak terms of use. Uploads and use of Groundspeak/ data is with permission from Groundspeak (pending).
  • All cache data comes from Pocket Queries. Caches you’ve uploaded are available to you for about a month since they were last updated with a pocket query. It is therefore necessary to upload pocket queries on a regular basis. This ensures that the data remains “fresh”. Archived caches will “fall off the radar” since they won’t be updated.
  • Caches that you’ve found or written field notes on will always remain available for reference.
  • In order to use the site, you must upload a new “My Finds” pocket query at least once a month.

If you have any thoughts on the topic or would be interested in field testing in the future, please let me know in the comments section.


— update 10/15/2008

I don’t intend to release the application for installation on other web servers but plan to open up the application for other cachers once I have a license agreement set up with Groundspeak.

I’ve set up forums to discuss the application at If you’re interested in field testing the application, please register there.