dfx

Just what I thought. Nope, you don't need a program to do that. Any somewhat recent operating system (including all Windows version since 98) come with a tool to unpack ZIP files. Just right-click on it and extract (or double click to open). Out will come two GPX files (or occasionally there will be only one). Copy those onto your device's storage (either internal or SD card) into the \Garmin\GPX\ directory. Done.

The information provided is wrong. You don't need Internet access for receiving text messages. You need to be on a cell provider that offers an email-to-SMS gateway. Internet access on y our phone has nothing to do with that.

I don't have an answer, but I have a question myself: What GPS are you using, and do you have any good reason to use EasyGPS other than loading the PQs to your GPS? I'm asking because it might be possible that you can skip the EasyGPS step entirely.

Heh. I'm so used to being someones beta tester I don't even flinch anymore. In my experience: Garmin purchaser = Beta tester Not knocking Garmin in any way - I own three, but just the way it seems to be. Which honestly I don't mind, as long as they're responsive to any issues that pop up. Which most of the time they are. Maybe not as quick as I'd like them to be, but during their designated beta phases they're pretty good with pushing out updates. In any case, I'd take it over having broken firmware without anybody bothering to ever fix it any day.

Sure is a lot of conclusion-jumping going on around here. Good catch. Archive.org has a snapshot of the relevant article from April 27th 2010, citing: Which implies that it wasn't verboten back then.

I guess the eTrexers are just the guinea pigs for now...

Sure sounds like it. Where's the beta for the other models? Huh? Huh?

They are special because thy Frog blesseth them.

My guess is that you haven't actually set up any notifications yet.

Some people just like a competition.

The GPS can give a magnetic bearing that can be read off the numbers on a magnetic compass. Yup. But I have found that most of the time I couldn't be bothered taking the compass out. In fact, I only did it once, and that was simply for the sake of trying it out. Sure, it works, but by the time I've got it all done I could just as well have walked a few steps and then backtracked in case I got the direction wrong. A GPS with an integrated compass saves you from that trouble. Point and go. Fire and forget.

Really!?! I'd have thunk that the responses here were more towards 'cache cop' than reinforcing your opinion. Oh, well. Different strokes for different folks. Read what you want to, to reinforce your preconceived notions. That's gotta be because of his "type A personality"

Still trespassing, I'd say. In Canada railways lands were granted to the Railway Companies in most cases and are covered by the Railway Act which is a whole body of law unto itself. ... RR rights of way are bit narrower up here though in many cases, I think it's about 50 feet from the ballast edge or something like that... at least on the ONR lines I was most familiar with. I'm sure it varies a bit... plus the guage has changed a bit as well, so it would have been based on whatever was originally used. That's what I was getting at. I don't buy the "too close" thing. Either it's on their property or it isn't. Simply being too close (or more precisely, somebody feeling/thinking that it's too close) to some tracks is not an argument. Only if you know that it's a trespassing issue.

Does anyone know who runs it? I could provide hosting.

I never understood what the problem with railroad tracks is. Apparently in the US there's a trespassing issue, ok fair enough. But this isn't the US. Unless the cache is actually on some active railroad tracks, what's the big deal? Yup, I'd be thinking the same.

That is interesting indeed. I have quite a lot of stuff on my SD card and it works just fine. Can't speak for tracks though.

Not from a (Groundspeak) developer's perspective. Not that I care, but if it was my API, I wouldn't do it. An API is meant to be used by applications. If some functionality is desired that could either be implemented in the API backend or in the application, then it makes more sense for it to go into the application. The only API that should be responsible for posting things to Twitter is Twitter's API. A website on the other hand is meant to be used by humans - it constitutes an application in itself and so it makes sense for it to provide as much functionality as possible (either server-side or client-side), which includes talking to (various) APIs. I don't see the API's method to post logs as being equivalent to posting logs on the website, nor to the field notes functionality of the website. It's simply a way to get logs into the database. Just saying how I (being a systems developer) see it.

Wouldn't it make more sense to have the application post the log to twitter/facebook/whatever instead? It's already using the Groundspeak API, so why not also use another API to relay those logs? Having the Groundspeak API backend cascade a request to another API seems illogical to me.

It does weaken the satellite signals, which in turn can lessen accuracy. Older GPS receivers are affected by this more than newer ones. The new so-called "high sensitivity" receivers are quite resilient and are able to keep a GPS lock with at least decent accuracy when older receivers may even lose lock completely. Question: What kind of GPS were you using? And how did you know that the coordinates were bad?

It's just one of those features that everybody wants, but doesn't exist. All you can do is create a regular PQ, download it, load it up in an application on your PC and then search for the name in there. Or search on your GPS if you have one that can do that. A Google search can also be used to search within your state only at least: http://www.google.com/#q=site:geocaching.com+intitle%3Afrog+intitle%3A%22in+oregon%22+intitle%3Atraditional

Birdseye comes in two flavors: One is the Birdseye satellite/aerial imagery, similar to what you see on Google Earth. Those are not topo maps and there's no comparable freebies. The other thing is the "Birdseye Select" maps, which also includes the North American Birdseye Topo map. Those are scanned raster topo maps and provide similar info as what you can get on gpsfiledepot and also similar to Garmin's own non-Birdseye topo maps. The main difference is that Birdseye gives you raster maps, while everything else is vector maps. Vector maps generally give you the same amount of detail, but with the additional benefit of taking up much less space, having unlimited zoom capabilities and providing POIs and sometimes even street navigation. So unless you have a very good reason to prefer scanned raster maps over vector maps, you're better off with the freebies.

Is it going to be a user selectable new GPX schema (like there's 1.0 and 1.0.1 now)?

Geocaching, Facebook, what's the difference...

At first glace, I would have thought that you GIMP'd the roof off! I can't imagine anyone from Edmonton driving "top-less"

Medium is the new regular