Teuto-Yachter

Hi, hab' ich auch manchmal mit aktuellem Firefox unter Win 7 - leider keine Erklärung, aber kräftiges reinzoomen hilft machmal, Tab schließen und Karte neu aufrufen eigentlich immer. Nicht schön, aber auch kein Drama. CU - Jens

Rattenscharf! "T5, wieso T5? Als ich den Baum erstmal plattgefahren hatte, kam ich wunderbar an die Dose..."

Ich habe eine Kiste im Auto, in der sich alles mögliche angesammelt hat, u.a. so viele verschiedene "Multitools" (Leatherman, Schweizermesser, Zangenhammer,...), dass ich die ganzen Werkzeuge eigentlich auch einzeln mitnehmen könnte... ;-) Wenig davon ist wichtig: - Handy: ein gebrochener Fuß nach Einbruch der Dämmerung und 5 km vom nächsten Haus ist auch in Mitteleuropa ein Problem, wenn man alleine unterwegs ist; - Taschenlampe und Gummistiefel für Feierabendcaches (dafür ggf. auch eine Jeans und einen alten Pullover; man _muss_ sich ja nicht die Büroklamotten versauen), - und als Joker: einen Drahtkleiderbügel aus der Reinigung, auseinandergebogen und aufgerollt (zu Hause mit der Zange) und ggf. eine Kombizange dazu. Der Draht ist weich genug um ihn mit Hand & Zange zurechtbiegen zu können, aber steif genug, um was damit zu machen (etwas aus dem Baum angeln zum Beispiel), außerdem leicht und rostfrei. Daraus bastele ich mir vor Ort das Werkzeug, das ich brauche. Brauche ich zwar auch nur selten, aber öfter als den Zangenhammer... ;-) Viele Grüße Jens

Fullack! This is not the first time this feature has been suggested, either. It seems to be overdue.

I agree, there's still some points to be improved. I suggested some improvements a while ago (http://forums.Groundspeak.com/GC/index.php?showtopic=286848&st=0&p=4921514&fromsearch=1entry4921514) and to be fair, the labels are much better now. But the map itself is still too small. Maybe the best idea would be to move the whole trackable map over to the regular geocaching map (http://www.geocaching.com/map/). Kind regards Jens

I'd very much like the feature to be extended to _all_ cache types: For Unknown and Multi Caches, the feature is there. For Taditionals there's always the issue of correcting coordinates which are off, but I can think of other uses as well. Sometimes the hiding place is quite obvious, but getting there is not: you may want to mark your own trailhead, or a handy parking area. This also applies to Events, Mega Events, and CITOs. There are Wherigo Caches wich are puzzles as well, e.g. http://coord.info/GC3P49N. You may also want to mark the place where to re-enter an unfinished Wherigo you have saved, just as you would do with an unfinished Multi. This also applies for some Virtuals. For a Webcam Cache: mark a parking area or a better place to stand while being photographed. Earthcaches: mark a trailhead (since you'll probably find the relevant mountain even without using your GPS, e.g. http://coord.info/GC1EPYZ) I admit that you could do all this by using our own waypoints, but those won't be included in a PQ. And of course you could use some extra software like GSAK, but since the feature of correcting coordinates is there already, it seems easier just to expand it on the other cache types. Kind regards Jens

You're right, it's correct now, and so is the sum of finds displayed under "Distance to Finds". When I looked at it yesterday, the "Find Farthest East" was still a cache named "Fyren los" farther west, and the sum under "Distance to Finds" was still off. There just appears to be some sort of time lag for this section when the statistics page is generated. Anyway, thanks for looking into it! [] Kind regards - Jens

Hi, a minor matter: After logging some Finds today, I went to the statistics tab on my public profile. The statistics had been generated yesterday, so I clicked the button "Update manually" to get the new numbers. This worked allright except in the section "My Home Location Statistics", which remained unchanged. Since this section had been OK up to now, I suppose it will rectify with the next automatic generation, but at laest in the manual process it seems to be left out. "Heeeyyy, this is aaallll wrrrrong....!!!" Regards Jens (Teuto-Yachter)

I absolutely support this feature (as I did in the old feedback system), and I would like mixed bookmark lists of caches, trackables (and maybe challenges, too) even better. I can see a lot of uses: - Bundle caches, trackables and challenges (let's call them 'objects') which are connected in some way: it may be objects about art or certain landscape features, or objects belonging to certain persons, or trackables needed to solve mystery caches or finish challenges. - Bundle trackables, especially TBs, which you found remarkable in some way, e.g. very large ones, very beautiful ones etc. (without putting them on the watchlist and receiving each and every log about them). - You could even use bookmarks to list certain trackables which you want to be sure to log when they come your way, or which you want to pick up during your holidays to take to your home zone. In short: good idea! Kind regards - Jens

This is a very good idea. Attitudes towards cemetaries tend to vary very much, as I just recently read in the German speaking forum (see http://forums.Groundspeak.com/GC/index.php?showtopic=192193) about a cemetary night cache... Reactions went from "no big deal" to "SBA" (btw., according to the reviewer the cemetary is allowed to be entered at night), and the discussion got quite emotional. An attribute could certainly help here.

Hi, Of course, a power trail or something like that will always cause a splash on the map, but I'd rather have that happen later than sooner. The current lables seem unnecessary large to me, without even making the TB's trail more readable. It's a matter of the relative sizes of the lables and the map. That's why I also suggested to make the map itself larger. Until some months ago, I used a script called "GC Tidy" which allowed me to resize just that map, and that worked fine. But GC Tidy has stopped working with one of this year's site updates, and appearently it isn't maintained any more. Alas, I lack the skill to script this myself. Kind regards Jens

Hi melissalep, our profiles on GC.com are very aptly called "Your Public Profile", so I agree that you shouldn't put private data there. If I were you I'd put the private profile somewhere safe - e.g. your local computer - and just put a link on the profile. This link would be of no use for anyone else but you, but you'd have you private data handy. Kind regards Jens

Hi! The TB Map on a trackables page shows all the caches the trackable has been to, using numered labels connected by lines. (cf. e.g. http://www.geocaching.com/track/map_gm.aspx?ID=3818218) For trackables which are personal coins or have a lot of visits, the map very quickly gets crowded. Labels obscure both each other and the map itself, which soon gets more or less useless (cf. http://www.geocaching.com/track/map_gm.aspx?ID=2605610, and this is only a mild case). One of this year's site updates made this even worse by "decorating" said labels with shadows, larger fonts and larger margins. I suggest: - Make the labels smaller and neater, and take the shadows away. - Make the map itself larger, especially higher, so it fills a screen. Ideally, the viewer would be able to resize the map. Kind regards Jens

Indeed it would; good idea!

I like the idea. The "View past Trackables" list as it is now is not very useful, but it can be sorted. So, why not add two additional colunms "type of log" and "date of log" to the list and make the list sortable by those fields? Sorting the list accordingly would place the "Visited" logs conveniently out of the way at he end of the list. Kind regards Jens

...wenn das Schule macht, rege ich "6 - Extra Large" als Größenklasse an, und ein neues Attribut "zur Übernachtung geeignet"! Mein größter Open-Air-Large bisher war ein Plastikfass mit Hebelverschluss; das war dicht, aber wohl in erster Linie wegen des überhängenden Deckelrandes. Das Logbuch lag vorsichtshalber noch in einer wasserdichten Dose - sowas geht im Zweifel natürlich auch.

Hi Dr.MORO and everybody, here I am getting home, starting the computer, logging the latest find, taking a casual look at my personal coin and what do I see? IT'S FIXED! TB order on the map page is correct, and so is the Path. Bliss!! Thanks a lot to the crew Jens (Teuto-Yachter)

Hi, first of all, thanks for the great job you did, I really like the new PQ features. Still, the issue concerning the sorting of log listings is yet unresolved. Since this is obviously more complex than it seems, I'll try to give a decription of the problem as I see it: First, as a minor point, the log listing on "Your Profile"/"Quick View". This is a mixed list of logs concerning both caches and trackables, sorted correctly by log date, newest on top. On the second level, that is, within one log date, it's sorted by object - sometimes caches first and TBs second, sometimes the other way round; all within the same list. The order doesn't just alternate, I cannot find a pattern. On the third level, the logs of cache finds are sorted correctly (as I understand it): in the order I logged them, newest log on top. The sorting of trackable logs is the other way round: in the order I logged them, _oldest_ log on top. As I wrote, this is a minor matter, but I think it may be connected to the second point: Second, the log listing on a trackable page (e.g. TB3884W, my personal coin). The log listing itself is correct: 1st by log date, newest on top, then in the order the logs where entered, newest on top again. Now I click "View Map" and get a second listing from which the track on the map is derived. Here, the sorting on the first level is reversed (oldest on top), this makes the track run "the wrong way round", starting with my newest log numbered "1" (and ending with my first log). This reversal is only there since the recent update. On the second level, within one day, the order is reversed again; the _newest_ log is on top of the day. Since the two levels of the list are sorted in different orders, the track on the map gets "loops" where a straight line should be. Instead of going like this: 2nd day, 4th log - 3rd log - 2nd log - 1st log - 1st day, 4th log - 3rd log - 2nd log - 1st log it goes like this (now): 1st day, 4th log - 3rd log - 2nd log - 1st log (loop back) 2nd day, 4th log - 3rd log - 2nd log - 1st log. Before the recent update, I think it "jumped" the other way round: 2nd day, 1st log - 2nd log - 3rd log - 4th log (loop back) 1st day, 1st log - 2nd log - 3rd log - 4th log. So, the issue seems to be the sorting order of trackables within one log date being inconsistent with the sorting order of the log dates themselves. What was changed in the recent update was the sorting order _of_ the log dates. (I hope I got that right - please consider that I'm writing this in Germany in a foreign language...) Kind regards from Bielefeld/ Germany Jens aka Teuto-Yachter