dfx

Ridiculous is right. That number is based on a totally naive calculation with not enough information available. Apparently nobody has noticed that Google doesn't give any prices for their Maps for Business license - you have to contact them for more information and the price will be based on page loads. This is not the same as the excess usage fees on the regular Maps API. We don't know how much it would cost for them to keep Google Maps, but it's safe to assume that it's not $3m per year.

I really wonder what the fanboys/girls think they are gaining or accomplishing. Nothing, it's just blind worship.

Only updated today, will test later.

So why does the link on cache pages still say "Geocaching.com Google Maps", when they aren't, anyway?

The Oregon knows which way you're holding it and records that information into the picture when you take it. Find and use an "auto-rotate" software that orients the picture the right way before you upload it anywhere.

I fixed it for you. If anything it should help you to understand and appreciate that ultimately APIs are neither "open" nor "free." Wat? So what are you saying here? That OSM is neither open nor free? Or that the Groundspeak API is open and free?

So Groundspeak finally realizes and appreciates the availability of an open and free API, eh?

561 days and counting. And there I was, thinking that "challenge cache based on one or more non-accomplishments, such as DNFs, will likely not be published."

Come to think of it, wouldn't that turn the micro into being the "regular" cache size? I see it now... Micros are regular, nanos would be small, and then you have large, extra large and supersize

Don't use any of the "geocaching" dashboards. Instead, use one of the "data fields" dashboard for example, and either use the compass screen or set one of the data fields to "pointer".

You have one "&" too many in there. To convert ą into something that works, you need to make it ą

That is exactly why. I'm not on Windows, so I could use it only by jumping through some hoops. And then eventually paying up, because the nag screen gets too... naggy. Of course it's privileged. I use my own scripts and database to handle all my GPX data (pretty much exactly what GSAK does, just without the GUI frontend). But I can't use the API because I don't have access to anything that's allowed to.

How many logs does that give you per cache? Edit: Thinking about it, I guess you could guess them all. I don't have easy access to any such privileged application, so I don't consider API to be an option.

gc.com doesn't provide a way to search logs and since there's no way to bulk download a lot of logs for a lot of caches, you can't even do that on your PC. The only way I can think of is through a google kludge, such as: http://www.google.com/#q=site:geocaching.com+intitle%3A%22log+by%22+swim

Yes, absolutely. It was one of the main reasons why I switched from a PDA to a proper handheld GPS. Anything with a modern 3-axis compass. Forget the older 2-axis ones.

You still get notifications when you do that though.

As Hungary is pretty much all flat, there's only so much topo data that you could put, even if you wanted to 850 MB is plenty of storage if you manage your maps a bit. Yeah, you can't put maps of large areas all at once, but you rarely need to do that anyway. It's a convenience to be able to do it, but not a necessity.

You could see the difference with the GPS sitting still. The map pointer was "twitchy" like my old Legend. Looks like they dialed down the deadband on detected motion... That's gonna screw with people's odometer...

dfx does not like this.

Who, compared to the rest of the geocaching world, are a minority

I just used it now (bringing my ignore list up to a whopping 21 entries) and it worked just fine.

True, but that's not what we're talking about. The article says "Your phone needs to have internet access to receive Instant Notifications by text. Most mobile service providers offer this service, but it may not work on all phones. Your mobile provider’s text messaging rates may apply." That is just not true. I know that the article is in the context of new cache alerts and FTF and all that, but there's other reasons to have instant notifications as well, and you don't need to load a cache page for those.

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. Not exactly. In order to confirm the new email address, you have to visit a web hotlink, so you do need internet. Good point. You don't actually have to visit that link from the phone though. If you can get the URL to a PC somehow (in the worst case you can just type it in), it would still work. Another option is not to use the mail2sms address directly, but use an intermediate forwarding address instead. At first the emails go to your desktop, just to confirm the address, then you redirect it to the gateway.

I've noticed people on smartphones are getting preferential treatment on notifies. thats why when you open the email on your pc, you visit the page and ftf was 45 minutes ago[its always someone with a smartphone] Emails are emails. All notification emails go out at the same time. Whether they end up on somebody's smartphone or on somebody's desktop (or sometimes both) or anywhere else makes no difference (and Groundspeak doesn't even have a way of knowing where it's gonna go). There's no other delivery mechanism.