skramble

In the source code I found this Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 R28gZmluZCA6IA== Few days ago I got a slightly longer email. (As you see, I do not read the HTML formatted email for security reasons.) I hope that this is just a temporary feature. May be there could be some more fields in the plain text formatted part but even the link would be fine. It seems to have returned to its previous spartan content.

Until recently, text mode emails for new cache notifications were sparse, but looked like this: Go find GCXXXXX: http://coord.info/GCXXXXX ...and the URL was a link. I have just received several email notifications that look like this: Go find : Is this a bug, or an intended change? (the subject line still includes the GC# and name, and the HTML body is the same as before) Thanks.

Thanks very much, I understand now. But I've installed Javawa on my Mac and I don't see how to get the .img files onto it so I can change their internal headers. There doesn't seem to be an option within Javawa to load .img files, only to create backups, which is not what I want to do. I'm not a Mac user, but there looks to be a good guide on using JaVaWa with a Mac at http://springerphotographics.com/2014/03/21/using-javawa-gmtk-to-fix-open-street-map-garmin-files/ When you select the maps at garmin.openstreetmap.nl you are emailed a link to several versions of your chosen tile set. One of those versions is Mac installable. After you have installed it, it should appear as an editable choice in JaVaWa. When you have edited and saved it, you would use MapManager, BaseCamp, or MapInstall to transfer it to the GPS. As indicated in the referenced guide, be sure those utilities are closed while editing the map with JaVaWa. Here's a more "geeky" way to accomplish the same thing directly with a hex editor: http://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin#What_if_I_have_an_existing_gmapsupp.img_file.3F Hope this helps.

I don't think that was it, since I renamed each map on the PC prior to copying them to the etrex. So each map on the etrex already had a unique name. But thanks for the suggestion. When you change the OS filename, you don't change the internal map name and ID. For e.g., if you have two gmapsupp.img files and rename them to file1.img and file2.img so they can both reside in your GARMIN folder, when you enable them in the GPS they are either both enabled or disabled as a unit. You'll see (for e.g. with the open cycle map) one openfietsmap map with two subentries for the separate files. It could be that this internal map name conflict is what's getting in your way, hence the suggestion to try changing the internal header with JaVaWa, so the Garmin doesn't confuse them.

I don't agree. This may be the case in your crowd, but please don't generalize. Smartphone navigators account for a minority of experienced cachers I encounter. .... And I've been called a lot worse things than Old School. No offense intended. I was writing in a threat about the new smartphone app and about its features. You are reading this App Update Announcement thread and replying and even saying you use your smartphone some, so my comment applies to you too. I would also bet if you ask all those other experienced cachers you encounter, they too would tell you they use the smartphone app some as well. I too have a dedicated gps device (older, that I bought used to get started) but frankly my iPhone and Android devices are far better for me, but that is not the point of this thread. So rather than getting off topic, do you have something about the new app to add that is relevant to this thread? I don't participate here much (only posted because of the importance of this change), but I bet if you are interested there are dozens of threads here on which device is better and are you a real cacher if you use a smartphone app in the field. My point is/was that this change in the app is extremely significant and affects the vast majority of members and premium members who use this app AT LEAST SOME OF THE TIME which includes you and the majority of members. I think we should focus (at least in this thread) on how to help Groundspeak update it in a way that best serves the community. No offense taken, and none consciously projected. My shopping list for the fully developed app would include: - OSM trail maps - complete offline functionality. I'm usually out of cell range. - track logging and export. When exploring new trails I like to be able to upload to OSM. - custom GPX import/export. I like to be able to include data the stock GPXs don't. - user waypoints. For trailheads, POIs, new placements etc. - list mode should include those custom waypoints and distances. Especially for when we're dropping new caches. - direct phone-phone data sharing. For offline situations where one person has loaded the cache and another hasn't. It would be amazing if they could also hack Garmin's ANT and make phone-GPSr possible. - waypoint averaging - "enter next stage" Oh, and an orange in the toe of my stocking.

I don't agree. This may be the case in your crowd, but please don't generalize. Smartphone navigators account for a minority of experienced cachers I encounter. Phones are IMO (perhaps) acceptable in an urban environment, but they soon become a hindrance off road, or in inclement weather. Every now and again I'll try using my phone and usually put it away with a frustrated head shake after a short time for the same long list of annoyances and deficiencies. And I've been called a lot worse things than Old School. Ironically, you just did what you're asking jpadc not to do I was agreeing with your points right up until one part - the urban/offroad/weather misnomers once again. Years ago, they would have been bigger issues. Smartphone GPS today is much much better, with recent phone brands rivaling even the best dedicated gps devices. Dedicated GPSrs should ideally always be better devices since they are, well, dedicated to gps technology. But it's quite common that someone who's only experience with a phone is an older or less capable phone, and having used a very capable dedicated GPSr, will presume that all phones are as bad or worse than the one they have experience with. That's not the case. Ultimately, there's just a much wider swath of quality amongst the smorgasboard of smartphone brands than there is amongst GPS devices, so yes it's easier to point at a lower average capability, but these days anyone picking up a relatively new smartphone will have more than sufficient power and technology to make use of the phone for geocaching even in the most questionable of environments. I started with a 3GS in 2009 which was iffy, but still quite sufficient for geocaching - finding and placing - and used it in deep forest, in desert with no reception, over water, snow, ice, lengthy day hikes and high urban cores. Today I have a 6S Plus and can't form a viable reason I would switch to a less technologically capable device even though it would be dedicated to GPS. Basically: dedicated GPSr - good chance you'll have a trustworthy device with excellent GPS technology almost guaranteed to be excellent for geocaching. Smartphone - wider range of quality and technology also affected by user knowledge of the device, with more recent hardware much more likely to be on par with a dedicated GPSr. The only legitimate issue I've found with a smartphone (by my experience) that can't be directly dealt with in a practical manner (imo) is cold weather, which plays havoc with battery life/reporting. All other smartphone concerns are non-issues. That said, I do agree that dedicated GPSrs are still quite prolific in the community, at least around here. I think that anyone taking up this hobby at some point with a smartphone decides whether they want to stay with a smartphone or at least try a dedicated GPS. I'd bet it's then a relatively small segment of those people who decide to stay with the smartphone exclusively; but that's probably highly dependent on demographic, age, culture, region, environment, etc. The best geocaching tech setup is to have both a smartphone and a good dedicated handheld GPS. Make use of both their strengths; why not? I think you may have jumped to a conclusion. I don't believe I generalized, I stated my personal opinion. I also didn't say anything about the relative accuracies (precision of language please). But let me count (some of) the ways I prefer GPSr... - My main concern when it's pouring rain is the relative water resistance of the devices (yes, I've tried the Otterbox and didn't care for it). My Oregon has survived some river dunkings, I panic if my Samsung gets more than a splattering. - My concern in uncertain footing is the loss of or damage to a phone many times the replacement cost of a GPSr. - I find the phone to be too hard to hold onto and use single handedly when in the bush (other hand has firm grasp on hiking stick), I have to hold it just so to avoid pushing buttons or touching the screen where I don't want to, without it slipping away. - I suppose there's a lanyard that can be attached to the phone to stop it from hitting the ground when dropped, like the GPS, but I don't like that expensive screen swinging against rocks,(see replacement cost), so it needs to be carefully fished from a pocket when needed. The GPSr is built to take (and has taken) some knocks so it hangs conveniently around my neck or on my pack when not in active use. - The lack of trail maps is a major deterrent to me, although I know somebody with an iPhone (mine's Android) who has maps, so I suppose they must be available, and the GS app should hopefully incorporate OSM in time, but if they don't work offline they'd be of limited use. Where I usually trek there's no cell signal for miles. - It often turns out that somebody in the group du jour is missing a cache or several on their machine for one reason or another. We all use Garmins, and are able to beam to each other. Haven't yet figured a way to do that using phones, and reciting coordinates, descriptions, hints and possibly logs is tedious. - there may be a way to download daily finds from a phone to GSAK, but I don't know how. With the GPS it's simple. The same goes for uploading GSAK formatted GPX files to the GPS. I like to include several useful stats in them other than what GS provide in theirs. - I suppose there are apps for the phone to record tracks so I can upload new trails to OSM, but the GPS already does it with just a click. I do find the phone to be indispensable, though, when we stop for a break and find we have a fleeting bar of reception and can check for any email notifications of new caches in the vicinity.

I don't agree. This may be the case in your crowd, but please don't generalize. Smartphone navigators account for a minority of experienced cachers I encounter. Phones are IMO (perhaps) acceptable in an urban environment, but they soon become a hindrance off road, or in inclement weather. Every now and again I'll try using my phone and usually put it away with a frustrated head shake after a short time for the same long list of annoyances and deficiencies. And I've been called a lot worse things than Old School.

Beside the log in question is a "view log" link. From there you can "edit image" and should be able to delete it.

Here's a good place to start: http://cryptograms.org/tutorial.php Have fun.

...it would also be nice to at least be allowed the <font color> tag. IMO the logs are too dull looking.

I'll add my voice to those preferring the old alternately shaded format. I'd also like to see the unnecessary white space preceding the horizontal rule eliminated. I do rather like the Markdown preview underneath the new message composition frame though. And the ability to resize it vertically.

If Burger King closes the deal, you may well get Timbits "your way" yet...

No longer any need. Configure your notification preference to forward all MC messages to your email, et voila! And as long as you reply to any such forwarded messages from the same email address as is set as your default, you get email and the other end gets MC. Best of both worlds.

It's probably this one: http://www.geocaching.com/geocache/GCZ2BK_wellis-wanderings It didn't show on your map because it's a Mystery, but Mr. Google found it.

I tried it. If you reply by email, you get another email (containing your reply) from the message center! Please don't send the replies! I didn't get the reply sent to me when I tested it. They either fixed it already, or perhaps you were using the same ID for testing?

Excellent improvement, thank you! My little niggle is that the notification preference setting defaults to only sending emails after a 30 minute conversation inactivity, so subsequent test messages didn't come through until I thought to check it, but notwithstanding that little wrinkle, this is a very welcome MC/email integration move.

Seems like a perfectly reasonable way to keep both sides happy and communications options open. The only downside would be for whoever initiated the MC contact and was expecting a reply through that interface (not checking email?). Perhaps the reverse could also apply... if the receiver of a MC notification replied through email, the MC could be CCed?

So you don't like the change and decide to punish the finders of your cache? I don't share your definition of punishment, and you apparently don't share mine.

I've already deleted the few that I've received, and conveyed my reasons to the senders for not participating in this new system, but if/when they continue I suspect I won't be the only one trying to automate an advice to message center users that I only respond to emails. Can't we just have an opt in/out though (similar to blocking friend requests)? Failing that, couldn't you include the message content in the notification, and an email reply link?

+1 +2 +3

Please send the contents of the message in the email notification, as we'll then have the choice of which way to use the system. As it is, it's clunky and an annoying extra step for those of us not constantly on the site. TPTB seem to be keen on a Facebook or Twitter style social network, but there are plenty of us who aren't interested in that aspect. And for Pete's sake dump the cutesy fluttering envelope white space and make the text box more of a useful size.

After reporting this in "Website" forum, bug is now fixed.

Just got a reply in "Website" forum... bug has been fixed now.

Looks good, thanks!

TB stats images are being replaced by a generic image. At http://support.Groundspeak.com/index.php?pg=kb.printer.friendly&id=10 section 2.2 list item 3. displays what you should see at http://img.geocaching.com/stats/tb.aspx?guid=96d16114-bebf-4d5d-a75f-6fbea5c0fab4 as being: what is actually displayed is This occurs using any TB's GUID.