Jump to content

Search the Community

Showing results for '길음역청소년출입금지제주출장샵[katalk:ZA32]200%보장 전지역 모두 출장가능'.

  • Search By Author

Content Type


Forums

  • Geocaching HQ Communications
    • Announcements
    • Release Notes
    • User Insights
  • General Geocaching Discussions
    • Getting Started
    • How Do I...?
    • Geocaching Topics
    • Geocache Types and Additional GPS Based Gameplay
  • Community
    • Geocaching Discussions by Country
  • Trackables
    • Travel Bugs
    • Geocoins
  • Bug Reports and Feature Discussions
    • Website
    • Geocaching® iPhone App
    • Geocaching® Android App
  • Geocaching and...
    • GPS/API/Technology
    • Education
    • Hiking/Backpacking
    • Photography
    • Design

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Location

Found 28815 results

  1. Some COs lack the intelligence and imagination to see that a cache of that size (say nano)/placed in that location/etc would need lots of maintenance. It's not just inexperience; there should be some common sense (intelligence) by those COs. Agreed. Also, need to have a minimum of finds before being able to place a cache. This could be flexible, depending on the location. Ha, ha, I had 'conversations' both with logs and private messages with one CO with a cache that had off-coordinates. Others were doing similar. I think 150 to 200 metres off in this location. I carefully and patiently explained how to fix the coordinates a number of times. They called me a troll, and said they would report me. I can't remember what I replied, but I might have said, 'go ahead', knowing the reviewer would not side with them. Turns out there was another cache near where they placed their cache and so they couldn't have that spot, but they thought it was their right to have that spot. Meanwhile several cachers were messaging each other about this CO. One messaged me to say, "They're mad". The reviewer came in and disabled the cache. The CO immediately re-enable it without moving their cache. The reviewer came back and said they were not playing games and disabled it again. It was archived.
  2. I have owned 4 Earthcaches (3 still active), the first being created in 2011. A couple times each year I need to delete Found logs because the cacher never sent answers. I have always followed up with a reminder message too, usually about 48 hours after the log without answers. I wait a week without answers before deleting the log. In my experience, 9 times out of 10 that I need to send a reminder message it means the cacher will never send any answers. A couple times I've gotten a response that they will send answers, but they never do. I am fortunate to have only had one stubborn faux-finder and he gave up after his log was deleted for the 2nd or 3rd time (logged a find, I sent a reminder message, never got answers, deleted, he relogged, I deleted again and sent a second message that he was welcome to log a find if he sent answers otherwise any future logs would be deleted without further warning). I'm not super-stringent with the answers; I think everyone who has ever sent wrong answers was still pretty close. But it becomes annoying to have someone log a find then have to wait around wondering if the answers will ever come. I send a courtesy confirmation reply to answers via the Message Center, and I will also send one via email if I get answers but no find has been logged yet. Given what it's like owning 3-4 Earthcaches, I can imagine how annoying it can become to own 50 or 100 or 200 Earthcaches, especially in locations that get lots of visitors (my oldest and busiest Earthcache only averages about 2 Finds per month). I might have a dozen log notifications from a dozen different cachers on a dozen different Earthcaches in my Inbox at any one time waiting to see if they will ever send answers. Not to mention more belligerent faux-finders. Combined with the increasing stringent requirements about what kinds of Earthcaches, it's becoming increasing discouraging to be an Earthcache CO, especially over a long period of time. FWIW when I'm traveling, I use a notebook or notepad to record all my Finds in order plus calculating multi stages, solving field puzzles, and especially recording answers to Virtuals an Earthcaches. After I'm back home from my trip I will start sending answers to COs then logging Finds.
  3. Henne1312

    etrex 20 und gpx

    Grundsätzlich wird nach dem Einschalten sowohl auf den internen Speicher als auch auf die Speicherkarte zugegriffen, d.h. es spielt keine Rolle, in welchem Garmin/GPX Ordner die Caches sind. Wo hast du sie denn abgelegt? Wenn sie auf der Speicherkarte sind, kann es sein, dass die defekt ist und nicht bei jedem Start gelesen wird. Andere Möglichkeiten, warum ein Cache nicht angezeigt wird, sind Filter oder eine zu große Entfernung zwischen Standort und Cache. Caches, die mehr als ca. 150 bis 200 km entfernt sind, werden nicht in der Liste, aber auf der Karte angezeigt. Andere Möglichkeiten hat Atlas Cached beschrieben.
  4. @Keystone, I sent you a PM, basically explaining to you that I wasn't looking for a Lackey but more like a database administrator that could take 5 minutes and save me hours. You didn't write me back and actually the message has somehow been deleted. I'm giving you the benefit of the doubt that you don't know how software works, which is fine of course, however just to be clear if your intent was to just give me a hard time then you should really use your personal account. The last thing I wanted to tell you is that while you take issue to 200 trackables, know that there is no limit and if anything I just enjoyed buying trackables and by that I was also supporting geocaching so you really shouldn't hold it against me.
  5. Once a log is logged are the corresponding TB logs connected with it? Maybe they are behind the scenes, but looking at the logs on the user side they don't seem to be. It seems like if you log 1 Find with 200 Visits you have created 201 independent logs with no direct connection to each other. Someone correct me if that's wrong. It just looks that way on the front end. If they are linked, it would be a nice option to offer ("Delete associated trackable logs?"). But I'm sure an argument could made for situations where someone would want to keep the TB logs. Examples: 1. Someone logs a Find, but forgets to log trackables. Not realizing they could do this by editing the Find log, instead log a Note with and mark trackable visits. Then delete the Note so it does waste space in the logs. 2. Log a Find in the field via the app because you're dropping a trackable. Cacher gets home a week later and wants to write a proper log about their visit so they delete the original Find and write a new Find log so that the CO and Watchers will see it. 3. For whatever reason the log is deleted, but the trackable really was dropped in that cache and has already been retrieved by another finder.
  6. If you are visiting "nearly 200" trackables with every cache you find, and you make a mistake, I think that's on you to fix. Asking a Lackey to fix your mistake for you is not a reasonable customer support expectation for the amount of money you were (previously) paying.
  7. I know how to manually fix the problem with the trackables but the problem was that I had nearly 200 of them and in the end I did manually delete each log from each trackable, which took me a long time. That whole point is that one time I asked for help and I didn't get any help and that's why I canceled my membership. What I said about souvenirs is an exaggeration, it means for what they are getting paid they can do a lot more. My case is just another example, when you delete a trip to a geocache, the trackable logs that went along with that should also be deleted, that's common sense; however it would actually require someone to get off their butt and put in some real work for a week to do it. No matter how many years go by, they don't care enough to put in the effort. You guys can say whatever you want, I'm glad I canceled my membership and I'm sticking to my opinion!
  8. You don't say which GPSr you have, but even some old-timers can still be loaded online, it just takes a bit more to do. I've loaded caches manually since starting, so at a little over 200 finds in thirteen years, that doesn't seem that big a deal to me. I feel "value" only means what's important to you. For me, value is simply having an "accurate", unfailing GPSr. A 60csx does that... Unless you plan on going full-steam-ahead on finding hides now, I feel the etrex 30 that CAVinoGal mentioned is a good bet. If you're including value as cost, I'd stay clear of the top-o-the-line models, unless you do plan on caching a lot more than you have been. Good luck.
  9. Since some days I can't use the website! The site is very slow or I can see often only a white page or the background. Location/provider: Germany/Telekom (16MBit/s) Routenverfolgung zu www.geocaching.com [63.251.163.200] über maximal 30 Abschnitte: 1 <1 ms <1 ms <1 ms 192.168.xyz.x 2 1 ms 1 ms 1 ms 192.168.xyz.x 3 9 ms 8 ms 8 ms 217.0.xyz.xyz 4 11 ms 9 ms 9 ms 217.0.66.18 5 29 ms 23 ms 23 ms 217.239.47.198 6 18 ms 18 ms 17 ms 62.159.61.206 7 22 ms 33 ms 28 ms ae-8.r23.londen03.uk.bb.gin.ntt.net [129.250.6.206] 8 22 ms 23 ms 28 ms ae-0.r22.londen03.uk.bb.gin.ntt.net [129.250.4.85] 9 122 ms 124 ms * ae-4.r22.nycmny01.us.bb.gin.ntt.net [129.250.3.126] 10 182 ms 190 ms * ae-1.r21.sttlwa01.us.bb.gin.ntt.net [129.250.4.13] 11 204 ms 199 ms 200 ms ae-2.r04.sttlwa01.us.bb.gin.ntt.net [129.250.5.45] 12 169 ms 172 ms 169 ms ae-0.internap.sttlwa01.us.bb.gin.ntt.net [129.250.201.18] 13 196 ms 206 ms 205 ms border9.po1-40g-bbnet1.sef.pnap.net [63.251.160.19] 14 171 ms 169 ms 171 ms 63.251.163.200 C:\Windows\system32>ping geocaching.com -t Ping wird ausgeführt für geocaching.com [63.251.163.200] mit 32 Bytes Daten: Antwort von 63.251.163.200: Bytes=32 Zeit=167ms TTL=246 Antwort von 63.251.163.200: Bytes=32 Zeit=168ms TTL=246 Antwort von 63.251.163.200: Bytes=32 Zeit=170ms TTL=246 Antwort von 63.251.163.200: Bytes=32 Zeit=169ms TTL=246 Antwort von 63.251.163.200: Bytes=32 Zeit=169ms TTL=246 Antwort von 63.251.163.200: Bytes=32 Zeit=168ms TTL=246 Antwort von 63.251.163.200: Bytes=32 Zeit=175ms TTL=246 Antwort von 63.251.163.200: Bytes=32 Zeit=168ms TTL=246 Antwort von 63.251.163.200: Bytes=32 Zeit=168ms TTL=246 Antwort von 63.251.163.200: Bytes=32 Zeit=173ms TTL=246 Antwort von 63.251.163.200: Bytes=32 Zeit=170ms TTL=246 Antwort von 63.251.163.200: Bytes=32 Zeit=170ms TTL=246 Antwort von 63.251.163.200: Bytes=32 Zeit=179ms TTL=246 Antwort von 63.251.163.200: Bytes=32 Zeit=167ms TTL=246 Antwort von 63.251.163.200: Bytes=32 Zeit=168ms TTL=246 Antwort von 63.251.163.200: Bytes=32 Zeit=174ms TTL=246 Antwort von 63.251.163.200: Bytes=32 Zeit=168ms TTL=246 Antwort von 63.251.163.200: Bytes=32 Zeit=169ms TTL=246 Ping-Statistik für 63.251.163.200: Pakete: Gesendet = 18, Empfangen = 18, Verloren = 0 (0% Verlust), Ca. Zeitangaben in Millisek.: Minimum = 167ms, Maximum = 179ms, Mittelwert = 170ms ---------- Location/provider: Germany/Unitymedia (150MBit/s) Routenverfolgung zu www.geocaching.com [63.251.163.200] über maximal 30 Abschnitte: 1 3 ms <1 ms <1 ms 172.30.xyz.x 2 1 ms 1 ms 1 ms 192.168.xyz.x 3 2 ms 1 ms 1 ms xxxxxxxxxxxxxxxx [xx.xx.xx.xx] 4 11 ms 15 ms 9 ms 10.144.0.1 5 17 ms 15 ms 14 ms de-fra04a-ra1-ae10-1210.fra.unity-media.net [81.210.128.65] 6 168 ms 165 ms 167 ms de-fra04a-rc1-ae8.fra.unity-media.net [81.210.129.225] 7 166 ms 169 ms 170 ms uk-lon01b-rd1-xe-1-2-2.aorta.net [84.116.132.17] 8 91 ms 99 ms 92 ms 84.116.140.30 9 164 ms 167 ms 163 ms 84.116.135.121 10 176 ms 167 ms 165 ms xe-0.equinix.snjsca04.us.bb.gin.ntt.net [206.223.116.12] 11 166 ms 171 ms 164 ms ae-6.r23.snjsca04.us.bb.gin.ntt.net [129.250.4.41] 12 185 ms 184 ms 194 ms ae-3.r20.sttlwa01.us.bb.gin.ntt.net [129.250.3.125] 13 183 ms 193 ms 183 ms ae-1.r04.sttlwa01.us.bb.gin.ntt.net [129.250.5.43] 14 184 ms 182 ms 182 ms ae-0.internap.sttlwa01.us.bb.gin.ntt.net [129.250.201.18] 15 241 ms 209 ms 258 ms border9.po2-40g-bbnet2.sef.pnap.net [63.251.160.83] 16 186 ms 186 ms 191 ms 63.251.163.200 C:\Windows\system32>ping geocaching.com -t Ping wird ausgeführt für geocaching.com [63.251.163.200] mit 32 Bytes Daten: Antwort von 63.251.163.200: Bytes=32 Zeit=185ms TTL=237 Antwort von 63.251.163.200: Bytes=32 Zeit=185ms TTL=237 Antwort von 63.251.163.200: Bytes=32 Zeit=186ms TTL=237 Antwort von 63.251.163.200: Bytes=32 Zeit=184ms TTL=237 Antwort von 63.251.163.200: Bytes=32 Zeit=184ms TTL=237 Antwort von 63.251.163.200: Bytes=32 Zeit=187ms TTL=237 Antwort von 63.251.163.200: Bytes=32 Zeit=187ms TTL=237 Antwort von 63.251.163.200: Bytes=32 Zeit=184ms TTL=237 Antwort von 63.251.163.200: Bytes=32 Zeit=189ms TTL=237 Antwort von 63.251.163.200: Bytes=32 Zeit=187ms TTL=237 Zeitüberschreitung der Anforderung. Antwort von 63.251.163.200: Bytes=32 Zeit=186ms TTL=237 Antwort von 63.251.163.200: Bytes=32 Zeit=185ms TTL=237 Antwort von 63.251.163.200: Bytes=32 Zeit=189ms TTL=237 Antwort von 63.251.163.200: Bytes=32 Zeit=185ms TTL=237 Antwort von 63.251.163.200: Bytes=32 Zeit=192ms TTL=237 Antwort von 63.251.163.200: Bytes=32 Zeit=188ms TTL=237 Antwort von 63.251.163.200: Bytes=32 Zeit=188ms TTL=237 Antwort von 63.251.163.200: Bytes=32 Zeit=188ms TTL=237 Antwort von 63.251.163.200: Bytes=32 Zeit=185ms TTL=237 Ping-Statistik für 63.251.163.200: Pakete: Gesendet = 20, Empfangen = 19, Verloren = 1 (5% Verlust), Ca. Zeitangaben in Millisek.: Minimum = 184ms, Maximum = 192ms, Mittelwert = 186ms Edit: I needed over a minute to save this post!!!
  10. Someone logged a 'discovered' one of my TBs yesterday - It went out on a 5 year world tour and returned back to my possession 9 years ago - it has been in my possession ever since then. I have never posted a photo with the code, I have never offered it or the code out for 'discovering' I asked the 'logger' how he came by my TB code (among the 18,200+ other TBs/coins he has logged) - no real explanation other than he has lots of friends with huge collections and he also goes to the gallery. Ok Believe that if you choose, I have my own idea as to how he came to log mine and many of the others I have checked ;-) However my query is about the gallery - I wasn't aware of this feature - so looked Only 999 images available and only back to 5/12/19 - pesumably this is a rolling list - 999 showing changing every day, is this right ? Only a handful of those actually show the logging code, so this is unlikely to be a rich source for logging TBs / coins - how is it this is used as an explanation for logging so many TBs ? How do pictures get into this gallery ?
  11. What is the defintion of "a ton of people"? 10 geocachers weighing 200 lbs each? Or?
  12. Nennt sich "Powertrailing" . Wird leider von zu vielen Leuten mit Geocaching verwechselt. Da hast du völlig recht. Nicht, dass ich wüsste, im Gegenteil. In meiner Gegend wird eine neue "Runde" mit 20+ Dosen immer freudig begrüßt, und bei einer Serie mit 200 Caches würde der Owner vermutlich mit Lob und FP überhäuft. Der Mehrheit der "Cacher" geht es heutzutage um "Punkte, Punkte, Punkte!!!" und "Je mehr, desto besser!". Das zweitwichtigste Kriterium sind Statistiken aller Art (D/T-Matrix etc.). Die Location der Dose steht arg weit hinten in der Liste. SIe könnten es, wollen es aber nicht. Als ich angefangen habe zu cachen (Anfang 2008), gab es eine Art Anti-Powertrail-Guideline. Wenn du eine Tradi-Serie mit mehr als einer handvoll Caches eingereicht hast, die mehr oder weniger auf einem Rundweg lag, dann wurde das nicht gepublisht. Stattdessen solltest du einen Multi draus machen. Diese Guideline wurde 2009 oder 2010 (weiß nicht mehr genau) abgeschafft. Groundspeak hat keinerlei Interesse daran, dieses Rad wieder zurück zu drehen, im Gegenteil. Je mehr Caches es auf der Welt gibt, desto besser. Und wenn diese zum Großteil aus an der Landstraße aufgereihten Micros im 160m-Abstand bestehen - so what?
  13. Das Problem wird sein, dass Deine Konstellation doch recht selten ist - man muss dafür wohl schon ein Windows-Tablet haben oder eben ein Notebook mit Touchscreen (Convertible). Als Entwickler für Web-Anwendungen kann ich Dir nur sagen, dass solche die im Browser stattfindenden Aktionen meist mit JavaScript auswerten, und da ist "um 200 Pixel nach rechts verschoben" jetzt eine Nachricht, die die Anwendung vom Browser und dieser wiederum direkt vom Betriebssytem bekommt. Da den Schuldigen zu finden warum jetzt ein Verschiebn per Touchscreen anders signalisiert wird als mit der Maus ist sicher nicht ganz trivial. Wie ist es denn bei der "neuen" Karte, also https://www.geocaching.com/play/map/ ? Die ist ja größtenteils auch ganz nützlich, hat ein paar mehr Filterfunktionen aber weniger brauchbare Kartenebenen und ist insgesamt etwas umständlicher für "nur mal Caches suchen". Allerdings kann man sie schneller ans Ziel verschieben und dort dann per Button die Caches suchen. Interessant wäre trotzdem, ob ein echter Chromium/Chrome sich doch anders verhält als der auf Chromium basierende Edge-Browser. Dann könnte man u.a. sehen ob die Chromium-Engine ein Problem verursacht oder doch der Edge drumherum.
  14. Yes and no. Sure, the fundamental structure of the Garmin units remains the same since the switch from the non-paperless to paperless caching units. (or I guess I should say from the units that fully support mass storage mode and those that don't). Once can easily pick up an Oregon 200 or Colorado and still load it up with a PQ file and go geocaching. On the other hand, the hardware itself has a limited shelf life, and the plastic and rubber on those old units is going to break down much faster from a current date of purchase than something newer. And the newer body style of the Oregons seem to be made of more durable materials than that of the Oregon 200-450 series. It's not always easy to find those older units in new or decent condition, whereas the 600 can still be found unopened at the $200 or less price point. Of course, the OP decided on a 700, which will will last them quite a long time.
  15. Ich kann es Dir nicht sagen was dann passiert... ich kann nur schätzen: Es passiert nix ? Ich bin noch in einem anderen Forum und da freuen sich gerade mehrere Leute über die derzeit freien Autobahnen. Zitat: Statt zu Normalzeiten mit Durchschnitt 68 KMH zur Arbeit schaffe ich aktuell das doppelte weil ich problemlos 200 KMH fahren kann. Ein Wort gegen das Grundrecht auf der Autobahn 200 KMH zu fahren und es ging echt heftig los... das Risiko sei ja absolut kalkulierbar und überschaubar und so schnell fahren ist legal usw. usw. Ich fahre seit Jahren nicht schneller als 150 - und das nur wenns pressiert. 130 bis 140 sind eine sehr gute Reisegeschwindigkeit auf Autobahnen. Viele Dienstwägen haben die Vorgabe maximal 130 KMH - so z.B. auch beim Fuhrparkservice der Bundeswehr und in den ersten 2 Märzwochen bin ich damit ca. 1800 KM sehr bequem zweimal durch Deutschland gefahren. Aber das wird nun sehr OT.
  16. Welche Gründe führen denn unsere Reviewer aktuell noch an um nach wie vor Events zu verweigern? Bei unseren Nachbarn dürfen seit Wochen wieder Events stattfinden, Restauraunts und Biergärten sind geöffnet und voll, an touristisch interessanten Orten drängeln sich die Besucher und selbst indoor Veranstaltungen wie z.B. Konzerte mit bis zu 200 Personen (outdoor 400) dürfen inzwischen wieder stattfinden. Warum wird behauptet ein Picknick Event in München das seit langem published ist sei verboten und droht mit Archivierung? Warum wird die Bewertung nicht auf aktuelle Verhältnisse angeglichen, auf was will man warten?
  17. I'm trying to debate between two water filters I saw at REI. One is a Katadyn Hiker filter with 0.3 micron pores, it has activated carbon, and it can filter up to 200 gallons before you have to buy another filter. The other is a Sawyer with hollow fiber with 0.1 micron pores the water travels through, comes with something to backwash the filter, and because of that "a use it a million times guarantee". As far as price, these two are only $5 from each other. Which one is better? I was thinking having a 0.1 micron filter will filter more germs than a 0.3 micron filter. However, the activated carbon will remove chemicals, odors, or if you have no choice but to take from a stagnant pond and for all you know many animals pee in it, I think it could help out. On the REI water filter comparison chart, it says both the Katadyn Hiker and Sawyer filters are rated for taking care of bacteria. However, the thing which concerns me is on another place on their chart it says bacteria can be anywhere from 0.1-10 microns, which tells me they could be slightly smaller than the Katadyn Hiker 0.3 micron filter. So that's why I'm confused on what to get.
  18. Does anyone know of a quick and easy way to adopt out large numbers of caches without individually entering the GC code for each one and submitting? I'm looking at over 200 to do and am hoping there is an easier way.
  19. Nie czepiajmy się szczegółów:) To jest tylko zabawa. Oczywiście można nauczyć się na pamięć regulaminu i nawet go recytować na konkursach:) Do dobrej zabawy wystarczy rozsądek i szacunek a reszta to zaledwie kosmetyka. Warto dać serwis potrzebny bo w tą stronę to spoko. A co mają powiedzieć ludzie szukający dużego kesza gdy w terenie jest mikrus? To tylko zabawa ale nikt praktycznie nie loguje DNF, serwisu itp a potem wszyscy mają pretensję, że jakość keszy jest słaba. Ja mając 200 skrzynek nie jestem w stanie ich sprawdzać 2x w roku i liczę na ludzi, że mi napiszą że MS005 zalany, MS065 uszkodzony pojemnik itd bo tylko dzięki temu mogę te skrzynki szybko naprawić Gorzej jak trafią się tacy co nadużywają opcji NM/NA jak im się coś w skrytce nie spodoba.
  20. Nie czepiajmy się szczegółów:) To jest tylko zabawa. Oczywiście można nauczyć się na pamięć regulaminu i nawet go recytować na konkursach:) Do dobrej zabawy wystarczy rozsądek i szacunek a reszta to zaledwie kosmetyka. Warto dać serwis potrzebny bo w tą stronę to spoko. A co mają powiedzieć ludzie szukający dużego kesza gdy w terenie jest mikrus? To tylko zabawa ale nikt praktycznie nie loguje DNF, serwisu itp a potem wszyscy mają pretensję, że jakość keszy jest słaba. Ja mając 200 skrzynek nie jestem w stanie ich sprawdzać 2x w roku i liczę na ludzi, że mi napiszą że MS005 zalany, MS065 uszkodzony pojemnik itd bo tylko dzięki temu mogę te skrzynki szybko naprawić Tak, ale nie dotyczy FTF First To Find. W takim przypadku powinno się logować z terenu ale... Nie zawsze jest możliwość zalogowania kesza w terenie np. brak zasięgu telefonii komórkowej. Gdzie jest tak napisane bo nie pamiętam? Nic bardziej wkurzającego nie ma niż log FTF reszta później dla ownera. Ja loguję zawsze w domu gdy napiszę coś sensownego, często parę dni tygodni później gdy inne kesze zejdą z kolejki.
  21. You measure the distance along the Ground Track by multiplying the elapsed time by the speed. If you search the internet to see how fast the ISS is traveling, you get anything from 17,200 mph to 14,710 mph (4.777 mps to 4.08 mps) 1509.68 miles divide by 5 min 53 sec = 4.2767 miles/sec. That is in the lower half of the speed range. 1679.574 miles divide by 5 min 53 sec = 4.758 miles/ sec. That is in the upper half of the speed range. If we use 293 miles/minute that is listed in the ISS Category instructions - 5.883 min x 293 = 1723.82 miles. That's 4.88 mps which is a bit above the speed range. Having quoted two people above, I will quote a third, my friend, Burger King, "Have it your Way!" Use what works for you. Personally I feel that 293 miles per minutes is too high. When you are using a coordinate checker you are measuring the distance between two points that are not on the flight path. Is the checker measuring a flat earth distance, or is it using a more complex formula for a curved Earth? In the below photo you can see: Red is the ISS Flight Path Black is the portion that two people are watching Blue is the distance between Coordinates of the two observers. You can see how the blue line is longer than the observed black line since it the hypotenuses of a right triangle verses the base. This is why we use the elapsed time multiplied by the speed along the ground path.
  22. I don't see why a difficult-to-qualify challenge should necessarily be a hard-to find cache. I have two challenges (https://coord.info/GC3WXTT, https://coord.info/GC4FED2) - both pre-moratorium, and neither allowed under the current guidelines! The D-ratings are both high, to reflect the difficulty of the challenges, but as Trads, they'd probably be D1.5 (or less). Their T-ratings are low - neither are more than 200 m from a reasonable parking spot. I'd say that the hides, whilst unexciting, are consistent with the sorts of caches that people are likely to use for qualification. Sorry, I was just thinking out loud trying to get my head around why there's a problem in places that needs challenge caches to be optionally converted into traditionals. I guess there are classes of challenges like streaks and calendar ones where there's no correlation between the difficulty of the challenge and the difficulty of accessing/finding the cache.
  23. I don't see why a difficult-to-qualify challenge should necessarily be a hard-to find cache. I have two challenges (https://coord.info/GC3WXTT, https://coord.info/GC4FED2) - both pre-moratorium, and neither allowed under the current guidelines! The D-ratings are both high, to reflect the difficulty of the challenges, but as Trads, they'd probably be D1.5 (or less). Their T-ratings are low - neither are more than 200 m from a reasonable parking spot. I'd say that the hides, whilst unexciting, are consistent with the sorts of caches that people are likely to use for qualification.
  24. Not so much an irk but it could be if it happened more: Easy traditional with a first DNF on May 2nd and another one on May 7th. The CO checks the cache a day later and TD's it as the container is gone stating container will be replaces ASAP. July 7th (after 2 months) a reviewer posts a standard note asking the CO to solve the problem or at least post an update. The same day the CO posts a note "Sorry that this is the way you communicate, cache will be removed since you're so impatient (I suspect they mean the listing as the container has been gone for 2 months). Cache is archived by the CO at the same time. CO is not a newbie (started in 2015) but only found about 200 traditionals and also placed one. Makes me wonder, what did they expect? No reviewer action after 2 months? Why not post a note they are "working on it" that would buy them another month.
  25. You don't want much, do you? 8^) Non of Garmin's current GPSr offerings will be supported for 'at least 10 years' - This just isn't how the portable electronics game is played today. Technology moves too fast. Most units have support lifespans of maybe half that time. Doesn't meant hey will stop working after that, just means Garmin will likely have a newer and better unit out by then, and old unit supports will be dropped in favor of the latest and greatest stuff! Less than $200? Your GPSMAP 60 series was never that inexpensive (adjusting for inflation) - why do you not want something comparable today? If you are already familiar with the GPSMAP series and like how they function, I would highly recommend the GPSMAP 66 - They can be had on sale for ~$300 (gpscity just had a great sale on them), and this unit will still be going strong for many more years. Otherwise, I echo Mineral2 sentiments (mostly) but instead suggest the Oregon 7x0 for its advanced wireless features and capabilities. These can also be had for under $300. If you must stay under $200, gpscity has some great deals on GPSMAP 78 series units right now.
×
×
  • Create New...