Equis

Sounds like a perfectly good idea to me. My wife and I headed to Canada for the afternoon last weekend and, even though it's only across the river from our hometown of Detroit, we are much less familiar with the area. Printing a map with the caches on it was tough. +1 from me!

I like the new map and how I can turn stuff on and off. That's neat. When looking at the map, I would like to be able to hide inactive caches. If I'm not going to look for them, I really don't want to see them. They'll pop back on the map when they're active again and I'll look for them then. Thanks!

Geez, next thing you know people will be requesting that the United States of America should be listed as a country as well. (It *would* be nice, btw.)

I also have the XV6700 and use CacheMate with a Bluetooth GPSr. It's been a great setup and you don't really need the data plan. You can load all the GPX waypoints using the sync and downloading one or two here and there doesn't eat up much bandwidth (aside from surfing the enormous pages on Geocaching.com). The good thing about the XV6700 is that it has WiFi, too, so a quick stop in the parking lot of your local Panera means free surfing with no data plan required. I don't have any experience with any of the other phones, but I'm pretty happy with what we have. We've only been at this a couple months and we've never printed a listing.

Yes* * I have seen another site (Ze Frank's The ORG) use a way of locating others on a Google Map, but it fuzzed the location by 1/4 mile or so (I guess to prevent weirdos from stalking you). I like the idea, but the implementation could use a little discussion.** ** Yes, I know we're not supposed to discuss here.

None of the handheld device applications listed on the current Waypoint Downloads page use any kind of connection to a GPSr. Why isn't CacheMate listed there? It is by far the best thing I've found for paperless caching. It manages multiple databases of caches, waypoints, and benchmarks, allows viewing of the cache details and logs, and uses the moving compass to point you right to your destination! Please add it. Keep up the good work!

For all those looking to download GPX files directly to their Pocket PC, here's the workaround: Option 1: When you click on the button to download the GPX eXchange File, the website incorrectly sends a file called "cache_details.aspx" instead of a file with a GPX extension. Download and save that file, because that is actually the GPX file you wanted to download! You'll have to rename it before you can import it into your favorite GPS manager (CacheMate, GPSTuner, etc). This isn't how it's supposed to work, but it will suffice when we're in the field! Option 2: Use Minimo or Opera. Minimo is the mobile version of the popular Firefox browser (hooray!), but it's slower than I can tolerate on my mobile device (boo!).

I have tried the online mobilizers (Google, Skweezer, MobileLeap) and none seem to send the actual GPX file. I have changed my user agent from Pocket IE to Firefox to IE 6 and IE 7, but the website behaves the same way with all of them. Any other suggestions?

My Pocket IE browser is now successfully reporting as IE6, but still not working. Shouldn't the website grab the user agent string and handle it accordingly?

I use Pocket IE to visit Geocaching.com on my Pocket PC. When I find a cache that I'd like to add to CacheMate, I click on the Download GPX eXchange File button, but it asks me to save the .aspx page instead. I'm assuming this is some sort of script page that automatically compiles the GPX for the desktop browsers. Steps to reproduce: 1. Open Pocket IE on an Internet-enabled Pocket PC 2. Visit http://geocaching.com 3. Navigate to a cache record & details page 4. Click the "Download GPX eXchange File" button Expected result: Pocket IE asks where to save .gpx file Actual result: Pocket IE asks where to save .aspx file (Alternate solution: Create an option to download the GPX/LOC from the wap interface, though I still think it would be easier to create a mobile stylesheet to the main site.) TFT...website! :-)

I know there has been some talk about finding caches in a polygon, along a route, etc, but this is another way to look at it... What about finding caches in a *list* of zip codes rather than just one? A zip code is really a polygonal geographic area anyway, right? You could even use the distance variable to fuzz the edges of the area a little or a lot. For me, I'd like to find all caches near my home, near my wife's family, near my family, etc. Yes, I know I can set up multiple Pocket Queries for this, but so can the polygon and route people, right? My thought was that additional zip code searches take minimal web form and database query modifications while polygon or linear searches take much more development to implement. Thanks for all your hard work. :-)

Perhaps virtuals would be better if they were rated for quality by other cachers to filter out the virtual equivalent of a park and grab. I know rating caches is a whole 'nother can of worms, but why not?

I'm new to this and have started out entirely paperless on my Pocket PC with a Bluetooth GPSr. (In fact, it didn't even occur to me to print the listings.) I can mark a cache as found and write a fairly detailed log in the field using CacheMate and export it back to a GPX file, but I can't get it back to GC.com without at least cutting and pasting. Express Logger and GSAK will both parse the found caches and their logs right from the GPX file. Both will allow you to copy/paste the logs from one field to the next. What's the difference if we use these to cut and paste our "TNLN" logs or upload my longer field notes and logs to GC.com in bulk? I've only been doing this a short time. The most we've done in a day was 12 at a large park and many were *not* park and grabs. I was shocked to find that I can download the GPX, manage the data any which way I care to, correctly tag the caches in the field as Found AND add a log, but I can't easily get this data back to GC.com. I would like to see a bulk upload. Though, I see no need for a comma-delimited file when we can use a properly formed GPX file that the site--and other apps--already know how to handle.

Instead of spending more time on the wap interface, why not create a mobile-friendly stylesheet for the regular Geocaching.com site? Unfortunately, the regular homepage is pretty hefty at over 200k, but perhaps that can be pared down using simple styles? May be a very quick way to give the mobiles every bit of function the desktop browsers have. Am I missing something?