Jump to content

Hynz

+Premium Members
  • Posts

    539
  • Joined

  • Last visited

Everything posted by Hynz

  1. OK.... seems not to be a pressing issue Is it because I'm the only one experiencing this behaviour or that everybody (including HQ) already lost any interest in that pages since they are in so many cases basically unreadable anway? So I'm talking about eg this page: https://www.geocaching.com/track/map_gm.aspx?ID=1023357 I can only see "placed" and "took it to" logs. No "retrieved", "grabbed", "discovered" logs which are present on the paginated main page of the TB/Geocoin. Clearly a bug in my opinion. But I would not complain if only "took it to" and "discovered" logs would be filtered out.....
  2. Start from here: https://www.geocaching.com/seek/nearest.aspx
  3. This TB (a heavy frying pan) has currently 514 "took it" logs and the map view suggests that this TB was all over Europe. At how many of that 514 caches this TB was actually present you think? Can you try to explain why the owner of this TB should be happy to have this partly forged history but no hint what way the frying pan actually went and since "placed" logs went out of fashion it is even impossible to reconstruct in which caches this TB actually was placed. So trying to be on topic: I consider thoughtless "took it" logs as bad but would not call out the geocacher as bad. But "took it" logs when the TB is not even close to the cache are made by bad cachers.
  4. What a fitting statement to that discussion! I can't say that fake logs often affected my experience. Simply because (at least on those caches I like to hunt) those are extremely rare. But for me the only explanation to have such a rigorous stance that fake logs never ever can affect my experience as a searcher must come from a complete negligence/inobservance of all logs. That's hard for me to comprehend since logs are an important part for me to get a complete picture of a cache and if I will enjoy looking for it.
  5. To me as somebody starting caching in 2004 where TBs didn't had "visit" and "took it" logs was (and up to this date for me still is) the fun aspect that I can follow the path of the "item" moved by different cacher and not to follow the path of a handfull of "cacher" holding the TB for an extended period of time. In combination with the fact that cacher like to visit (and "took it" TBs to) high number of caches makes most of the TB listings and the map view practically unreadable and uninteresting. But apparently (and unfortunately for me) that's part of the shift you are an example of. But I would not say you are a bad cacher.
  6. It seems only "placed" and "took" logs are shown on that page (reachable by clicking on "View map" on every TB and Geocoin listing) And since I'm here and while I don't have high hopes that the IMHO broken trackable system will ever recover from the misguided use of "took it" and "discover" logs, it would be so helpfull if I could filter out those logs from that view.
  7. Hynz

    I wish....

    Unfortunately this is apparently neither the answer the old OP nor the new poster is looking for. I don't think there is an easy way to get a list of "Caches I DNFd in the past and haven't found afterwards so I might be able to log a find on them" Without third-party tools like GSAK I think the "Bookmark/List Method" is the best way to go (for Premium Members)
  8. Year, I'm missing this website too. Given the history I think it's unlikely that the problem will be resolved. So far I'm happy with https://extract.bbbike.org where you also can request specific areas and additionally different layouts are selectable.
  9. Auch wenn es nur eine rhetorische Frage ist Kannst du dich bitte mit deinen Massregelungen zurueckhalten wenn jemand einen eindeutig auf dem Abstellgleis von GS befindlichen und meines Wissens auch nur mehr mittels Deep-Link aufrufbaren "Workaround" nicht kennt bzw. sich eventuell trotz Kenntniss die von Groundspeak derzeit vorgesehenen und propagierten Moeglichkeiten aufzeigt und diese kritisiert?
  10. I confirm this behaviour as it seems to happen only immediately after writing the log. When this happened yesterday I opened the listing and could then edit my log by following the edit link. I used the old logging experience.
  11. Die wird dem BM nicht genommen und allein auf diesem Level kann und muss man dir natuerlich recht geben. BMs haben im Verlauf der Jahre auch viele Annehmlichkeiten bekommen die GS theoretisch auch nur fuer PMs zugaenglich machen haetten koennen. Wie sehr diese Entscheidungen von reinen Marketingueberlegungen geleitet war oder (so wuerde ich es zumindest gerne sehen) doch auch im Sinne eines Fair-Play kann ich nicht beurteilen. Die kuerzlich eingefuehrte Einschraenkung, dass BMs keinen Einblick mehr in die Fund Historie von anderen Mitspielern haben sollen (ja, derzeit geht es mit der alten Suche noch) finde ich aber sehr grenzwertig weil das keine spaeter eingefuehrte Bequemlichkeit ist sondern von Anfang an als aus meiner Sicht wichtige Informationsquelle vorhanden war.
  12. Thank you. I agree but more and more I think App user often don't know or consider that there is a webpage offering a bit more possibilities. I just found out that when logging on the GC-App you are completely restricted: *) you can not change the text *) you can not change the date *) you can not delete the log *) when logging, the date is automaticaly set to the current date. No way of adjusting/correcting it. *) you can not easily find you own log down the log history *) not even the date of your own find is shown This rigit frame of possibilities is unfortunately educating smartphone users to log quickly in the field, and write only short logs. While I get it that you don't want to overload a GUI on a small screen with features rarely used it still should be possible to performe above tasks.
  13. I'm sure it was as I'm quite certain that often I was the first one starting to watch a cache which had 0 watchers. I never tried to watch my own caches so I can't comment about this.
  14. I'm tempted to go more that way, a plain text sticker (or bit of metal) with some text. The only issue is data density - for those of us with less-than-perfect eyesight, small text under something in an awkward spot could be quite difficult for some, less difficult for others. Why do you want to present text? Can you not put it in the cache description? Just put up an easy to read number and make up a formula (in the description) to calculate the final coordinates. I guess there are clever and creative ways to use QR-Codes in stages but I don't understand why holding up a smartphone to get "A=3523" or the next coordinate is so much more fun than finding an (even smaller and less obtrusive) plaque with "A=3523".
  15. I buy old Geocoins and then re-sell them. People dont like the history attached to the coin One for the irks-thread. Thanks for providing a "in a nutshell"-explanation why the traveller system is broken beyond repair
  16. Wahrscheinlich befindet sich dort jetzt eine physische Stage eines Multis. Wenn die Koordinaten dieser Stage schon im Listing angegeben sind (sich also nicht erst durch eine Berechnung aus einer vorherigen Stage ergeben) dann werden diese Stellen auch schon auf der Karte als belegte Zonen markiert. Welcher Multi das ist (es koennete aber auch ein Mysterie sein) musst du selber herausfinden. Wenn es nicht gerade ein mehrtaegiger Wandermulti ist sollten seine Headerkoordinaten nicht allzu weit weg liegen.
  17. Exactly! While a lot of current TB logs (thinking of took it and discoveries....) are IMHO disposable I would be quite pissed if my log on a traveler acompanied with a nice picture of the surounding was deleted and removed from my history just because a new owner of the TB (or even the same owner) want's to start new.
  18. IMNSHO proofing the visit by a photo without signing the logbook is *an exception*. At least a little bit of an apology should be part of such a log. It irks me a lot stumbling over such logs written in a way as if a photolog is completely normal and the way to go and might be even the prefered way.
  19. Actually no I'm learning here (beeing currently a Basic Member and can not enjoy this new list) that on this new list not only *my* eventually found date is missing but it is also missing the date when the cacher *I'm looking at* has found the cache. Seriously?
  20. Kann es sein dass fast alle die "kreative Caches" schaetzen damit ausschliesslich die Ausgestaltung der Dose meinen? Wenn man einen Multi "genauso kreativ" als Tradirunde auslegen kann dann ist das - mit Verlaub - kein besonderst kreativer Multi. Wenn ich im Vorfeld schon exakt weiss welche Wegstrecke ich zu gehen habe (kann man natuerlich als Multi mit oeffentlichen Wegpunkten so konzipieren) dann mach ich ihn zwar auch noch lieber als die entsprechende Tradirunde aber kreative Multis schauen fuer mich anderst aus und die koennen gern auch mit einem Petling enden
  21. That's what Basic Member see on your profile: When the old seek page https://www.geocaching.com/seek/nearest.aspx will be removed BM will have no way of checking the found history of other cacher. I don't think that information could be provided by third parties and to me this is quite a fundamental restriction. Again I'm asking HQ to reconsider this decision since I have no doubt that the old seek page will be removed sooner than later.
  22. On the bottom on that page you can click on the "advanced search options" https://www.geocaching.com/seek/nearest.aspx There all of the above search criterias can be performed and the result is the good, old paginated list view (unfortunately on some of the results the pagination does not work as intended, eg searching for Multis only work for the first page) I shudder thinking of the time when *this* page will finally go the way of the dodo......
  23. Wow! Thanx. That feature completely slipped my mind. I never tried it in the past and since (as you already mentioned) there is no Garmin app compatible with the Oregon 600 line to transfer to a smartphone I again forgot about it. But it seems my device only allows to transfer the current track and not the archived tracks which would make this solution useless for me. Is this restriction what to expect?
  24. Over the years the USB connection on my Garmin Oregon 600 became more and more flaky and currently I don't have any data connection anymore. I tried with various cables and PCs and certainly tried to clean the connector. I even opened the device but to de- and resolder the surface mounted socket is a bit over my abilities. I know it's a long shot but does anybody eventualy has an idea for a workaround or hack to access the internal memory to get the recorded tracks and waypoints out of the device? I really need to archive my tracks but hate to replace the otherwise fine working unit. Using the SD card I can update maps and gpx files albeit I'm not sure how long the continuing removing and insertig of the SD card will work flawless.
×
×
  • Create New...