Jump to content

Search the Community

Showing results for '������������ 1���2���,�����������������������������Talk:za32��������� ��������� ������ ���������'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Geocaching HQ communications
    • Geocaching HQ communications
  • General geocaching discussions
    • How do I...?
    • General geocaching topics
    • Trackables
    • Geocache types and additional GPS-based gameplay
  • Adventure Lab® Discussions
    • Play Adventure Lab®
    • Create an Adventure Lab®
  • Community
    • Geocaching Discussions by Country
  • Bug reports and feature discussions
    • Website
    • Official Geocaching® apps
    • Authorized Developer applications (API)
  • Geocaching and...
    • GPS technology and devices

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Location

  1. Let's talk, you pick the subject. You will get our two cents worth... and take it with a grain of salt... oops, should have said: Open topic about Waymarking.
  2. Sorry for the vague title, I didn't know how else to address this. So, I know there's a lot of talk about Geocaching and YouTube, and there's been a sort of agreement as far as I can tell that as long as you don't really post spoilers about a cache and it's specific location, for the most part all is well. Well, there's a pair of YouTubers whom I occasionally watch called MoreJStu that make all kinds of vlog type videos, several of which have recently included geocaching. At first I had no problem with what they were posting. I figured if it got some more people interested in our hobby, that's great! But then they posted this video today: https://www.youtube.com/watch?v=FEub1s5AXUI There is so much misinformation in it about geocaching that I was nearly yelling at my screen. I think it's okay that they're wanting to share a geocache with the fans, there's nothing wrong with that. Except they show where they pack snacks into the cache and encourage others to come out and trade snacks too. Not only that, but they practically bury the cache. It's one thing to hide it with some foliage, but they literally made a hole to put it in. I'm not here to get them in trouble or anything, but I just hate the fact that they're demonstrating behavior against the rules of Geocaching to their 2.7 million subscribers... They also make it kind of known that in more than one video they usually don't trade swag, only take it. If you look on the comments on their vids, you constantly see things like "Ya'll inspired me to start geocaching!" and "Because of ya'll I'm building a geocache fort!". Which is great, except the majority of their followers are young kids who I know aren't going to read any of the rules before going out and geocaching, which will just create more problems... What are ya'll's thoughts?
  3. Good day fellow Geocachers, ill get right to the point, i always had a iPhone but these have become very expensive devices. I subsequently bought a Huawei P40 5G lite, but was not told that it does not work with any google apps. so all the maps on the Geo apps don't work thus i cant geocache anymore! it has an Android version 10, EMUI Version 10.1.1 operating system. has anyone been able to fix this or have a work around? i have a "fake" google maps that works on the phone but obviously the Geo Apps don't talk to it?
  4. Greetings from the WISA Woodsat HQ! After the announcement of WISA Woodsat satellite trackable (TB9GB8G) mid August, we have over 6200 people on the watch list! That also means that I have received a fair amount of messages regarding the satellite itself, the procedure of logging it, launch schedule and many others. Unfortunately I am not able to answer them one by one, so, let's talk satellites in this discussion thread. The most common question is, how you can log the satellite trackable. I have added the instructions to the trackable page https://coord.info/TB9GB8G. The thing to note is that you can only do that AFTER the satellite has been launched. The trackable code is only visibile in the photos taken by the satellite itself with its selfie-camera. You can follow WISA Woodsat project progress on https://wisawoodsat.space. We have blogs and videos showing how the satellite materials are made, how they are machined, and tested. You can also find WISA Woodsat on Instagram and Twitter with the handles @wisawoodsat and #wisawoodsat. Anything else you would like to know about the satellite?
  5. Yes, in civil engineering professionals are using RTK (Real-time kinematic positioning) and DGPS for land surveying. Technically speaking, this application is not a pure GPSr as it requires a reference station. Anyway, it is better to talk about consumer GPS as you suggested.
  6. We don't talk about the wastelands - by which I mean the east coast...
  7. Here is a misunderstanding. A compass is a device that shows the cardinal directions used for navigation and geographic orientation. It commonly consists of a magnetized needle or other element, such as a compass card or compass rose, which can pivot to align itself with magnetic north. Other methods may be used, including gyroscopes, magnetometers, and GPS receivers. I think that the correct term should be relative bearing when we talk about the arrow pointing to the waypoint.
  8. It can also cause frustration when the different devices on different days are off in different directions. So your gps could be 15 feet off to the left, the cache owner's gps could have been 15 feet off to the right when they placed the cache. So even if you are 100% certain you are at exactly the right coords, you could actually be 30 feet away from where the cache physically is. It's why some people talk about "geo-senses", which really just means past experience. Which can also be why it can be very frustrating when you come across a new way of hiding a cache that you haven't experienced before but others have. Lots of "so easy" and "obvious" logs, but you've spent the last two hours checking every nook and cranny in a larger and larger area...
  9. No, it's the same issue that I described previously. Comcast is now throttling Weekly Mailer messages we attempt to send by deferment, so our server keeps retrying until the message is accepted or expired. In this case, it took ~4 days. Here are the logs: Sep 30 13:40:36 signal2 postfix/error[18592]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=0.1, delays=0.1/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta34.westchester.pa.mail.comcast.net comcast Try again later) Sep 30 14:21:55 signal2 postfix/error[27076]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=2478, delays=2478/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta24.emeryville.ca.mail.comcast.net comcast Try again later) Sep 30 15:15:28 signal2 postfix/error[26069]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=5692, delays=5692/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta10.westchester.pa.mail.comcast.net comcast Try again later) Sep 30 17:31:19 signal2 postfix/error[21426]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=13842, delays=13842/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta19.westchester.pa.mail.comcast.net comcast Try again later) Sep 30 21:50:24 signal2 postfix/error[21488]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=29388, delays=29388/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta25.westchester.pa.mail.comcast.net comcast Try again later) Oct 1 02:20:11 signal2 postfix/error[17888]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=45575, delays=45575/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta25.emeryville.ca.mail.comcast.net comcast Try again later) Oct 1 06:50:08 signal2 postfix/error[14401]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=61771, delays=61767/4.3/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta28.emeryville.ca.mail.comcast.net comcast Try again later) Oct 1 11:20:24 signal2 postfix/error[10233]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=77988, delays=77967/21/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta09.westchester.pa.mail.comcast.net comcast Try again later) Oct 1 15:50:18 signal2 postfix/error[5719]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=94181, delays=94167/15/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta30.westchester.pa.mail.comcast.net comcast Try again later) Oct 1 20:20:06 signal2 postfix/error[1014]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=110369, delays=110367/2.6/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta29.westchester.pa.mail.comcast.net comcast Try again later) Oct 2 00:50:09 signal2 postfix/error[29149]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=126572, delays=126572/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta12.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 05:20:20 signal2 postfix/error[24714]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=142783, delays=142764/19/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta32.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 09:50:20 signal2 postfix/error[20450]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=158983, delays=158965/19/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta27.westchester.pa.mail.comcast.net comcast Try again later) Oct 2 14:20:05 signal2 postfix/error[15686]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=175169, delays=175165/3.9/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta02.westchester.pa.mail.comcast.net comcast Try again later) Oct 2 18:50:05 signal2 postfix/error[11213]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=191369, delays=191365/4/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta21.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 23:20:32 signal2 postfix/error[5842]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=207596, delays=207564/32/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta26.westchester.pa.mail.comcast.net comcast Try again later) Oct 3 03:50:18 signal2 postfix/error[1119]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=223782, delays=223765/17/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta12.westchester.pa.mail.comcast.net comcast Try again later) Oct 3 08:20:09 signal2 postfix/error[28593]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=239973, delays=239966/7/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta38.emeryville.ca.mail.comcast.net comcast Try again later) Oct 3 12:50:08 signal2 postfix/error[23322]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=256172, delays=256167/4.6/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta17.emeryville.ca.mail.comcast.net comcast Try again later) Oct 3 17:20:18 signal2 postfix/error[18820]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=272382, delays=272367/15/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta08.emeryville.ca.mail.comcast.net comcast Try again later) Oct 3 21:50:19 signal2 postfix/smtp[13687]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=mx1.comcast.net[68.87.26.147]:25, delay=288583, delays=288567/15/0.3/0, dsn=4.0.0, status=deferred (host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta18.westchester.pa.mail.comcast.net comcast Try again later) Oct 4 02:20:12 signal2 postfix/smtp[8287]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=mx1.comcast.net[68.87.26.147]:25, delay=304776, delays=304768/6.3/0.3/0.7, dsn=2.0.0, status=sent (250 2.0.0 YxL81m02s3RP4Bm0QxL95o mail accepted for delivery) And I still don't get one. Yours is still in queue for delivery: Sep 30 14:23:56 signal2 postfix/error[17402]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=0.1, delays=0.1/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta24.emeryville.ca.mail.comcast.net comcast Try again later) Sep 30 17:01:53 signal2 postfix/error[20668]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=9478, delays=9478/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta14.westchester.pa.mail.comcast.net comcast Try again later) Sep 30 19:48:30 signal2 postfix/error[10666]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=19475, delays=19475/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta06.emeryville.ca.mail.comcast.net comcast Try again later) Sep 30 23:50:09 signal2 postfix/error[26238]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=33974, delays=33974/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta21.westchester.pa.mail.comcast.net comcast Try again later) Oct 1 04:20:05 signal2 postfix/error[22530]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=50169, delays=50169/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta24.emeryville.ca.mail.comcast.net comcast Try again later) Oct 1 08:50:11 signal2 postfix/error[18967]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=66376, delays=66367/8.7/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta35.emeryville.ca.mail.comcast.net comcast Try again later) Oct 1 13:20:23 signal2 postfix/error[14592]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=82587, delays=82569/18/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta17.westchester.pa.mail.comcast.net comcast Try again later) Oct 1 17:50:19 signal2 postfix/error[10261]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=98784, delays=98769/15/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta18.emeryville.ca.mail.comcast.net comcast Try again later) Oct 1 22:20:17 signal2 postfix/error[5594]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=114981, delays=114969/13/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta06.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 02:50:19 signal2 postfix/error[1345]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=131184, delays=131171/12/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta30.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 07:20:30 signal2 postfix/error[29898]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=147394, delays=147371/23/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta37.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 11:50:23 signal2 postfix/error[25103]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=163587, delays=163571/17/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta13.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 16:20:22 signal2 postfix/error[20394]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=179787, delays=179771/16/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.COMCAST.NET[68.87.26.147] refused to talk to me: 421 imta38.westchester.pa.mail.comcast.net comcast Try again later) Oct 2 20:50:21 signal2 postfix/error[15742]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=195986, delays=195971/14/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta15.emeryville.ca.mail.comcast.net comcast Try again later) Oct 3 01:20:22 signal2 postfix/error[10582]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=212186, delays=212171/15/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta20.emeryville.ca.mail.comcast.net comcast Try again later) Oct 3 05:50:22 signal2 postfix/error[5603]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=228386, delays=228370/16/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta24.emeryville.ca.mail.comcast.net comcast Try again later) Oct 3 10:20:31 signal2 postfix/error[832]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=244595, delays=244572/23/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta15.westchester.pa.mail.comcast.net comcast Try again later) Oct 3 14:50:28 signal2 postfix/error[28274]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=260792, delays=260773/19/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta23.westchester.pa.mail.comcast.net comcast Try again later) Oct 3 19:20:24 signal2 postfix/error[23125]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=276989, delays=276974/14/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta24.westchester.pa.mail.comcast.net comcast Try again later) Oct 3 23:50:26 signal2 postfix/error[18230]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=293191, delays=293174/16/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta03.emeryville.ca.mail.comcast.net comcast Try again later) Oct 4 04:20:30 signal2 postfix/error[12972]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=309394, delays=309376/18/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta01.westchester.pa.mail.comcast.net comcast Try again later) Oct 4 08:50:36 signal2 postfix/error[8163]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=325600, delays=325579/22/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta16.westchester.pa.mail.comcast.net comcast Try again later) Oct 4 13:20:35 signal2 postfix/error[2929]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=341800, delays=341778/22/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta24.westchester.pa.mail.comcast.net comcast Try again later)
  10. When I travel, it would be great if I could get the GPS to talk to my android tablet. I got an adapter cord so I could hook the two together, but if I try to send way points to the GPS I get "your browser is not compatible" and I've tried all three browsers on my tablet. Should I give up this dream, or is there a way to do it?
  11. Nun, bis auf die Möglichkeit, mit dem Händi auch mal OHNE Vorbereitung loszuziehen und ein paar Tradis am Wege abzugreifen - gerne auch mal anlässlich eines Muggelausflugs, wo man sich erst im Auto klar wird, wo es überhaupt hingeht (Elsass, Schwarzwald, Kraichgau, Pfalz...) - mach ich das heute noch so. Auch mit demselben Gerät. Und ehrlich gesagt - ich finde die Behauptung, anders wäre einfacher, Ergebnis einer Art Hirnwäsche. Jede "Abkürzung" oder jedes "bequemer gehen" bedeutet erstmal mehr Aufwand in Form von Equipement, Proggies, Einarbeiten. In zum Teil völlig abstruse Gedankenwelten, die an Umständlichkeit oder der Problematik, dass genau DAS am umständlichsten ist, was am greifbarsten als Grundfunktion benötigt wird, nicht geizen. Dem, dem das quasi körperliche Schmerzen bereitet, der wird das so weit es geht meiden wollen Das alles mag ab "stufe 7" einen Sinn geben - aber die Stufe 7 ist die Ebene, in der man anfängt, alles zu nutzen, was als Ergebnis von ganz viel vorheriger Umständlichkeit erzeugt wurde. Die Ernte eines vorherigen Aufwands. Neolithische Revolution, sozusagen. Dem User, der als Ergebnis auf Stufe 3 stehenbleibt, ist das alles ein grosser, unnötiger Rucksack. Und die Diskussionen um deren Genzen für BMs - ich bin von der GC-Vergrämungstaktik nicht begeistert, aber eine Beschränkung für ne App ist doch keine Beschränkung, solange die andere komfortablere Möglichkeit noch funktioniert. Mittlerweile hat man den Eindruck, es existiert nichts, wo es keine App dafür gibt. Aber selbst die ist auch unterhalb einer gewissen Nutzungshäufigkeit resp. - frequenz - völlig unnötig. Unnötig, aufwendig, umständlich, umweltfeindlich Was ist einfacher, als auf der Karte gucken, was da iiegt, wo man hinwill und dann per "send to GPS" bzw. leider nur noch per "gpx downloaden" die Koords aufs Gerät zu schieben, ne kleine Übersichtskatre auszudrucken, ein paar Hints drauf zu notieren und dann loszuziehen? 1 Cachetag, 6 Stunden unterwegs, Rüstzeit 15 Minuten - und zwar zuhause, aufm grossen Bildschirm, mit Talk Talk im Ohr und nem Glas Primitivo. Geht schlechter. Gruss in den wilden Süden Zappo
  12. Yep. The pace is your own, and the last thing I want when relaxing outside is idle chat, talk politics, or hear rumors.
  13. I'm guessing that's because the caches in your area aren't that interesting, so the COs aren't expecting anyone to say anything interesting about them. I'd be really puzzled by a CO that placed a cache to encourage people to take a nice hike up a mountain to a beautiful view and then didn't read the reactions. That's the kind of cache we're talking about here. But to react to your comment, if a CO placed mundane caches and didn't even scan the DNFs for longer than usual logs that might indicate a problem, I'd say they weren't planning on maintaining their caches. I'd talk to them about that; I wouldn't accept it as a given that COs don't even glance at logs. But beyond that -- to go back to the original point about DNFs that don't reflect the cache's health -- I'd be kinda tickled if they got a CHS alarm and then ran out to fix a cache that wasn't broken because they didn't even bother to read the DNF logs that caused the CHS. Serves them right.
  14. If you don't need the vicar in the zone after the player talks to him, you could move the vicar to the next zone as the first command when you talk to him. If you still need him around in the current zone, you should be able to disable the command, at which point the player app is supposed to be smart enough to recognize there isn't an object in that zone anymore that has that command. If that's not the case--it really depends on how the player app handles things--disabling the command and then toggling the zone's enabled state should do the trick. So: - On Talk() - - Disable Talk command - - Set zone.Enabled = false - - Set zone.Enabled = true - - Do things for Talk
  15. Last year we did Cape York from CQ, 6491.4 km without leaving the state. But all this talk of remote travelling, and looking at photos and caches found, has my brain ticking over, so I have just posted this to our 4wd clubs Facebook page. I reckon it would be well over 10000km over the 4-5 week trip. Must be time to put forward a proposal for another big trip. Hopefully all this Covid rubbish is gone by then. Autumn/Winter 2023. Central Australia. Approx 4-5 weeks. Simpson Desert crossing west to east. It can easily include Plenty Highway, or better still Sandover Highway, Birdsville Track, Oodnadatta Track, Strezlekie Track. So, a potential itinerary, up to Mt Isa, Sandover Highway, Alice Springs, Mt Dare, Simpson Desert, Birdsville, Birdsville Track, Oodnadatta Track to William Ck, Lake Eyre, Coober Pedy, Port Augusta, Strezlekie Track, home via Cameron Corner and/or Haddon Corner, Windorah, Blackall, Tambo, Springsure, Biloela. No idea of what distance that involves. Just looking back at some of the photos from our last Simpson Desert crossing about 7 years ago, and thinking, we should do that again. Thoughts?
  16. I've never seen anything that bad, but I have no trouble imagining it. I suggest you talk to the new CO and mention how his inaccurate ratings have ruined your statistics. Point out to him that, like most geocachers, you aren't interested in meeting challenges using fake data.
  17. Please can you advise how to shut off the talk to command for each zone. I am doing a Church Wherigo and I want the vicar to pop up at each question point. As such he is in zone 1, has a talk to command, asks a question, gives commands to move on or retry if answer wrong or right. I am stuck at the next bit, as in how do I turn off the talk to, or attribute it to one zone only so I can do a further talk to at zone 2...
  18. Some people talk about High D/T ratings. Some people talk about solving a difficult puzzle. Some people talk about the cool places they go. But I'll be honest, I'm still chasing that high from the first time I submitted an EC to the Geoaware and said "looking for feedback on what needs to change" and he said "I can publish it right now." Whoosh. Blew. My. Mind.
  19. If we are allowed to talk about our own "children", I would vote for Victoria Amazonica and Jaguar.
  20. Okay, yeah, I misread your comment to infer that YOU updated something, which really, really threw me for a loop. There have been some changes in years past in the Datasheet program on how it interprets log entries for stations, which likely helped these stations get an accurate monumented date. (I only know this because one such update that was made back about a year ago) caused a whole bunch of logs that had no status, no agency, and no date appear tacked onto the history list on the datasheet. Had to talk to them and point out some stations that were causing this.
  21. I don't think so, not for me. I usually talk to the people I know and not to all 100 who have signed-up. Just recently have attended an Event with more than 800 People https://www.geocaching.com/geocache/GC8GVCH_event-am-see-2021-event-at-the-lake-2021?guid=1768bcdd-034c-4155-950a-718a51a3accc and I have been in contact with about 10. The other 790 were not even close to me.
  22. i have a problem and not sure how to fix it . i have a old lap top on vista and runs an old version of chrome and my gps does communicate ok with it. but my windows7 based pc used to comunicate to the gps then chrome and firefox and others change things to make the it safer to use the web .i belive since then i plug the gps in and the computer does not even know its there, i have down loaded the plugin from garmin still no go its getting to a point i belive its the windows7 based pc and chrome that have caused the connection problem , but how do i sort it please help in easy to understand computer garble. cheers steve
  23. Thanks Keystone, this is the same advice I offered the cache owner when the caches were first submitted. Dan, In regards to the distance, the distance is variable but what we take into account is the audience and if the cache is part of a series. Let me talk in a local example for you. If for example caches were placed around the Canberra region but to the cardinal points then these caches may be further than 100km from each other but are set to appeal for the same audience. This is even more the case where the cache have the same names as a Platinum step within a series. In regards to appealing a reviewers decision this is always an option. Reviewers don't take offence and it helps us to ensure we are following the intent of the guidelines. Often for borderline case we will take a cache to appeals for you. Hope that helps.
  24. Who do I contact and talk to if I have a problem with a reviewer? I am trying to hide and publish my first geocache but the volunteer reviewing my geocache asserts that it is in Indian Reservation Land despite the fact I have a vast amount of evidence to prove it is not. Please help.
  25. Here we have a classic example of WHY we have peer review for new categories. Talk about a category that is completely subjective - one person's "urban legend" may not be another's... Then, you have the creator of the category bugging out of Waymarking the same year he created this "interesting" piece of Waymarking. My question is - if you expand to just "Legends", and these are people, how would this be different than "Epic Beings" if Epic Beings allow a statue of Lewis and Clark to be included in their category????
×
×
  • Create New...