NilsK

To put it simple: This rocks. I was just putting together the PQs needed for a car trip through germany, when HHL pointed me to this feature. So, just used my already prepared route from Google-Earth (quite a complex one, with > 200 turns) and uploaded it. Worked like a charme. Thanks, this saved me about 10 PQs and filtering everything not needed out with GSAK afterwards. Nils

You mean there are other languages out there? Yes. There is american, scottish, welsh, canadian etc. Nils

Many caches here (in germany) only have german descriptions for a very simple reason: Many cache owners do not speak english well enough (at least thats what they feel) to make an english description. Though in western germany nowadays everyone has english classes in school, many people do not feel they are good enough in that language to use it. It is even harder for many Cachers, that went to school in eastern germany before 1990: They also learned a foreign language, but it was russian, not the language of the big enemy in the west. ;-) And some are just lazy, because 99% or more of the people looking for caches here are able to read german. So why bother? Nils

I see that quite often with TBs now. Being in germany, where we use a lot of Umlauts (äöü): I want to offer a wild guess: Could there be a problem with diacritics? Nils

In case there is an unexpected christmas: This is also on my wishlist. The prefixing makes the additional waypoints relatively useless, the not standarzised prefixes make the additional waypoints completely useless. I think the two-letter-code should be fixed by waypoint type (when multiples are required that is a problem, I know). The path choosen now means, we can never have anything new, which requires a new two-letter-code, because by saying "anything not used yet is allowed" means now all codes are blocked. Additionally this means, that the waypoint name gives no hint about what this waypoint is, which I think is a disadvantage (if I prefix my parking coordinates with "th" and my trailhead coordinates with "pa" that only increases the confusion). I think the additional waypoints are a really nice idea, but not implemented all too well. But with some changes this can become a powerful feature. Nils

I have 58 DNF and 762 found. Now te way of calculating the ratio comes into play, but this most likely will end up somewhere between 7 and 7.7%. Is there a worst cacher of the year award also? Nils, replacing luck and ability with stubborness.

Hey, Ralph! Gratulations for your upcoming 21hundred. I hope that cache will meet all expectations. Viele Grüße auch an Oma, Nils

Reading the Description sure shows it. But it gets quite annoying, when you are driving and see you have some time left, see a cache on your map, drive there and when you stop find out there is not cache. Also I had the case, where I was in an area, that somehow seems to be series-final-wonderland. When I was hitting "show nearest caches" I had to read through five or so descriptions to find a cache that really existed. When there are so simple ways to mark these caches, why not do it? If anyone has a good reason why these can not be mystery caches or put into the system with coordinates 0N,0E that is okay. I just currently see no reason. Nils

Nothing bad about a nice series of caches for collecting hints ... finding the final cache is always a pleasure. But is it possible to have a flag for all those "these are not the real cache coordinates", so I can avoid getting them in my pocket query? I just hate it when I see a cache on my map, go close to it and after finding a parking spot read the description to find out there is no cache here at all. I often go caching alone and driving and reading cache descriptions at the same time seems a bad idea. I have four ideas for that problem: (a) have a database flag for those caches, so they can easily be filtered out ( have specific coordinates for these caches (0N, 0E for example ... I doubt there will ever be a real cache). © define a new cache type "final of a series" for them, which again makes them easy to filter out. (d) Make these caches "mystery caches" and do not approve them, when they have another type - this again allows easy filtering All ways allow them to still be there but make them go away from the waypoints in the GPS, where they do not make sense anyway. Just my $.02 Nils

True, making it a mystery cache would help. I find most people mark it as a multi cache, though, which I think is plain wrong. Is that not exactly the reason, why caches have to be approved? This kind of formal stuff should be checked, I think. Nils

Nothing bad about a nice series of caches for collecting hints ... finding the final cache is always a pleasure. But is it possible to have a flag for all those "these are not the real cache coordinates", so I can avoid getting them in my pocket query? I just hate it when I see a cache on my map, go close to it and after finding a parking spot read the description to find out there is no cache here at all. I often go caching alone and driving and reading cache descriptions at the same time seems a bad idea. I have three ideas for that problem: (a) have a database flag for those caches, so they can easily be filtered out ( have specific coordinates for these caches (0N, 0E for example ... I doubt there will ever be a real cache). © define a new cache type "final of a series" for them, which again makes them easy to filter out. Both ways allow them to still be there but make them go away from the waypoints in the GPS, where they do not make sense anyway. Just my $.02 Nils