Jump to content

Search the Community

Showing results for 'bmw������ ������������������������katalk:PC53���200%������ ��������� ������ ������������'.

  • Search By Author

Content Type


Forums

  • Geocaching HQ communications
    • Announcements
    • Release Notes
  • General geocaching discussions
    • Getting started
    • How do I...?
    • Geocaching topics
    • Geocache types and additional GPS-based gameplay
  • Adventure Lab® Discussions
    • Play Adventure Lab®
    • Create an Adventure Lab®
  • 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

  1. This post is a continuation of the one of 26-Oct-21. In it I presented graphs of the last log locations (last-logs) of my trackables in the United States (US) versus locations outside the US, which are mostly Canada and the countries of Europe. The present text is a discussion of the tabulated data from which those graphs were derived. The methods for acquiring the information used here are described in the previous post, but let me state again that about 75% of the trackables under discussion have had no logs for at least three years (my criterion for missing) while about 25% are considered still active. The layout of both tables below is exactly the same, so one description will suffice. The Location column is either countries or US states, depending on the table. The Release (Rel) column is total trackables released in the respective locations. The columns under Drop Intervals are counts of trackables having last logs that fall into the specified count category. The values in the 5 column are the pool for drops five through nine, and for the 10 column, it is for drop ten through fourteen, and so on. Both tables have 51 locations with at least one last-log. In the case of the US, it is all 50 states plus the District of Columbia (Washington DC). Even Little Rhody has five. The states with the greatest numbers are California (101), Colorado (57), Florida (62) and Texas (146). These all have caches in leisure destinations, many of which, in my opinion, are frequently black holes for trackables, particularly if they are urban and not Premium Member Only. That said, some Premium Members are well short of sainthood. Thus, trackable longevity is more about luck and probability, rather than some cacher designation. I would have expected Texas to have many more last-logs, given that more than 4,200 trackables have been released there. Moreover, my definition of an old trackable is one having more than 25 drops (about five years old, on average). Texas has none, ranking it below the 20 states do have old trackables. Granted, I want my trackables to move, and even leave the state, but something about this disparity is not quite logical. All trackables will eventually go missing, no matter where they are. Nonetheless, I have believed for years that trackables in Europe move more frequently and last longer than here in the US. This, and future posts should begin to convince others. In my previous report, I suggested the longevity two trackables at Drop 55 was aided by drops (not visits only) in Europe. I thought later to look at all entries at 25 drops and beyond. There are 37 total, with none past 60 drops. The seven orange cells are those with earlier drops in Europe. The four blue cells are those with drops in Canada. As is shown in the second table below, the Canadian profile fits best with those of European countries. Thus, I believe drops outside the US benefitted the longevity of 30 percent the old trackables in the US. The 37 old trackables are 0.85 percent of the 4354 trackables in the US and 0.81 percent of all 4593 trackables. It is said that if a trackable was to survive long enough, it would eventually land in Germany. The second table below supports that statement. Without any releases in that country, it is the location of more last-logs (142) than any place outside the US, and more than any US state except Texas, where most of the trackables are released. The distant second place is a tie between Canada and the UK at 112. Both countries should have some advantage over Germany…a long, shared US/Canada border and my semi-annual trackable trades with an Englishman that resulted in 158 releases, mostly in the UK. Some of the lesser counts are in locations that spur this vicarious traveler to continue making and releasing trackables. Included are the British Virgin Islands, the Isle of Man, Liechtenstein, the Seychelles, Turks & Caicos and the Ukraine. A recent visit to Antarctica by one of my trackables just missed being formally included in this report. When this particular project started, there had been 239 trackable released in Canada (2) and Europe (237), yet 712 last logs were counted in the non-US collection, leaving 473 trackables taken there from the US. Most of this movement must have been done before the C19 travel restrictions of the last two years, suggesting there could have been a larger total migration, under different circumstances. In the non-US sample, there are 167 old trackables of 25 drops or more. This is 23 percent of the 712 trackables outside the US and 4 percent of all 4593 trackables. These percentages are embarrassingly high when compared to the US-only percentages of 0.83 and 0.81, respectively. These data are why I regularly send trackables to a friend abroad, a few of my own and most of those discovered in my caches.
  2. Ich als grosser TB/coin usw. liebhaber würde alle mitnehmen weil das ziel dieser dinger ist es ja zu reisen und nicht zu schimmeln. ich bin niemandem böse wenn er auch aus einem viel besuchten cache alle TBs mitnimmt denn sie wollen ja meistens schnell reisen. ich habe insgesamt 18 TBs was ziemlich viel ist für einen der erst fast 200 caches gefunden hat. ich finde es super wenn meine TBs schnell reisen!
  3. Not exactly true . I have an iPad (granted, it’s not a phone) that uses WiFi signals for location and that’s about it, no cell tower, no GPS. And it’s not clear what any iThing is using for location info at any given moment, the device won’t say. But It’s not improving anything when it’s WiFi only, for example when a phone is not getting a decent GPS signal. Mine wasn’t, it didn’t have the circuitry. AND my iPhone 8 seems to get confused by signals other than GPS when calculating its location. I have one of the phones that is 200 feet off in one direction, then 200 feet off in the other direction when using The App (and possibly in other cases). There’s an unaddressed thread about it. Not to wade too far into the deep grass on that issue, it seems like removing the SIM card helps — therefore removing ground based triangulation? Or something. Anyway, yes and no.
  4. The thing that's cool about Garmin handhelds is they can be customized for specific activities. Sometimes down to moving the most used menu icons onto the first screen. I don't know about the Montana, but the Oregon line from about the 650 on, have entire modes to choose, and they vastly affect the way the menus work. I set mine up so I'm maybe a couple of taps away from any function I often use. The iPhone Apps, and worse, the Android Apps, are an unchangeable maze. And I sometimes try Cachly instead, and it's set up completely differently. But for cache research, messaging, logging, and satellite photos, of course the phone is great for that. If you can find the functions. Your Montana would be ideal for driving directions, with the right maps. It has a great car dock. I found a decent car charging dock (wireless charging) for my iphone, to keep it nice and charged. It does go dead on a hike. I usually just plan to get it back into the charger. And I've typically had the Garmin running and tracking the entire hike. I can't seem to get "maps" to exist properly for offline Geocaching on my iPhone 8 (my Garmin has a map chip for the entire US, plus Topo). But the iphone also has that bug where it's 200 feet off and wandering and compass flipping to 90 and 180 degrees out, so I don't bother with the buggy parts. I used the phone these past couple of weeks for "getting a quick cache", and got a suitable reminder why I don't use "a phone" for the actual search.
  5. I maintain records on all my trackables. I have linked a number of my spreadsheets so that as trackable activity is recorded, summaries and graphs are automatically updated. One such graph is shown below. It is the survivorship curve of all my trackables, based on the number of drops achieved. The graph shows the activity of 4,593 trackables, released at a rate of about 200-450 trackables per year, between January of 2010, as of 22 Sep 21. The time lag between the latter date and the present is the time required to visit the home page of every one of my trackables to extract information needed for another post to follow, but using data from the same survivorship curve. While the curve is continuously updated, the shape has not materially changed for many years, owing to the number of trackables included, and that at least 75% of the trackables have not had logs for three years (my criterion for missing). As such, the tabulated values shaping the curve might be treated as kind of simple actuarial table, whereby one might predict the chances of a trackable reaching a specific number of drops. For example, the table below predicts that after releasing a trackable, that trackable has an 89.1% chance that someone will retrieve it and make the first drop. Or, there is a 10.9% chance the trackable will go missing before a first drop is made. The chance of making as many as 40 drops is just over one percent, or slightly better than 1 in a hundred. One of my trackables has had 78 drops, producing a probability of 0.0221%. Viewing the table yet another way, 50% of trackables go missing before five drops, which on average is about a year. For now, the reader will have to trust me on that time estimate, but it is close. There are some caveats. These data are based solely on my collection of trackables, nearly 90% of which were released in Texas, mostly on the Southern High Plains in the rural northwest part of the state, south of the Panhandle. The remainder were released in Europe or during travels around the US and Canada. Furthermore, my trackables are widely variable in size, shape and materials. Some are ready-made, some are hand-made. I have no way of knowing if these various circumstances cause significant differences in activity, as compared to trackables released by other cachers. All that said, I doubt any other US-based trackable collection will yield survivorship values that are orders-of-magnitude better or worse than demonstrated here. Trackable activity and longevity outside the US are very different matters, and will be the focus of my next post.
  6. I relogged and my Earthcache souvenir appeared. I need 200 souvenirs for a challenge cache I have found and signed the log for, so I can log that cache. That's the only reason at present I care about souvenirs. 182 and counting, and then I can again ignore them.
  7. Meist ziehe ich allein los oder schleppe den Nachwuchs oder Freunde mit. Da meine Freunde und Bekannten eigentlich nur Cachen gehen, um sich dabei zu bewegen und mit mir zu quatschen, und ich doch manchmal denke, wär doch bestimmt mal schön, mit jemandem loszuziehen, der/die/insertpreferredpronoun auch gern auf Schatzsuche geht, würde ich mich freuen, wenn sich da mal eine Gelegenheit zu ergibt. Bisher bin ich nie mit der Bahn, selten zu Fuß oder mit dem Auto allein, oft mit dem Auto irgendwohin und dann mit dem Fahrrad weiter oder direkt mit diesem startend unterwegs. Kletterausrüstung oder Angel habe ich keine, bisherige Schwierigkeits-und Geländestatistik im Anhang. Generell freue ich mich über einen Tradi am Wegesrand, wie auch über tricky, kreative, gut getarnte und versteckte Caches. Auch mal ne halbe Stunde an einem Ort gemütlich zu Suchen ist für mich absolut ok, in seltenen Fällen auch mal mehr, aber auch ein DNF, wenns keinen Spaß mehr macht, ist durchaus drin. Kleine Challenges machen mir Spaß, allzu wichtig nehme ich sie aber nicht. Mein vorsichtiges Jahresziel von 200 Caches werde ich vermutlich vor Jahresende knacken. Tageszeit und Wetter finde ich zweitrangig, dazu sind Zeitfenster im Alltag zu spärlich und ich mag sie nicht verschwenden. Mal ergibt sich eins für nur-mal-schnell, mal ist ein halber Tag frei, und ne Tagestour ist auch machmal drin. Die Homezone ist rechtsrheinisch, Leverkusen, Bergisch Gladbach und auch die linke Rheinseite werden im Alltag und zum Cachen von mir oft frequentiert. Wenn da also was für jemanden gut passt und ein paar nette unverbindliche Kontakte zum gemeinsamen Cachen bei Gelegenheit gut findet - yay! Schreibe mir gern.
  8. geodarts

    Glyphs

    We camped at Needles in the Canyonlands. I knew I was not going to find the 200 Hands cave even if I could do the hike. But the Polestar Rock Cache was the trailhead to Rock Art and other panels were nearby.
  9. Mine was around 200 miles. Noticed the area in "newest" in the profile/"dashboard", a favorite fishing creek nearby, and clicked on it. The CO used the wrong North, which put it on the other side of the state. First and last to find, as it was on NPS property to boot.
  10. No souvenirs are showing on my profile now.....!! Had well over 200....!
  11. Thanks. Did the same. That worked. The only interest I have in these souvenirs, is that I have found and logged a challenge cache, that I don't qualify for, until I have 200 souvenirs. I hid this souvenir, along with all the others, except country/state and the like. They are my only interest in souvenirs, besides that challenge cache. I have no wish to display souvenirs such as this one.
  12. Thank you for patience as I try to solve this. No the geocaches are not close to my location they are about 200 miles away or more. This is where I put them: F:\Garmin\GPX
  13. Moin, Unterordner sollten kein Problem sein. Wenn ich meine Pocket-Query ziehe, dann habe ich eine Datei "PQ-Name.zip", die ich immer in den gpx-Ordner direkt runterlade. Danach entpacke ich sie direkt in den Ordner ("hier entpacken") oder auch in den Unterordner "PQ-Name", den mir mein zip-Programm vorschlägt, wenn ich "entpacken nach" wähle. Egal, ob die beiden gpx-Dateien anschließend im Hauptordner "gpx" oder im Unterordner liegen, die PQ ist drauf. Kannst du beides mal ausprobieren, BlueStone, wichtig ist auf jeden Fall, dass du eine PQ immer entpackst, weil die als zip heruntergeladen wird, auf dem Gerät aber die beiden (!) gpx-Dateien (Caches plus Wegpunkte) entpackt liegen müssen. Ich gehe übrigens davon aus, dass die Anzahl der Geocaches/Wegpunkte, die das Gerät handeln kann, wie bei allen Etrex eingeschränkt ist, zumindest wenn man Listing und Logs und so haben möchte, das, was in der PQ mitgeliefert wird. Das sind meistens so um die 2000 (plusminus!?) Caches, die locker für normales Cachen reichen (keine Sorge). Diese vielen Caches sind immer ein anderes Format (loc? oder sowas?!), was nicht das ist, was du willst. Aber 200.000 vorinstallierte halte ich sowieso für völligen Blödsinn - was will man mit 200.000 Caches in den USA, wenn man in Buxtehude cachen möchte, zumal die Caches sicher nicht aktuell sind?! Sollten diese vorinstallierten Caches der wichtigste Kaufgrund gewesen sein, schick das Gerät zurück wegen fälschlicher Beschreibung. Wenn du aber ein solides Gerät haben willst und kein Problem damit hast, selbst Caches per PQ aufzuspielen (das ist kinderleicht, wenn man es ein paar Mal gemacht hat), dann fährst du mit einem Etrex sicher ziemlich gut! Herzliche Grüße Jochen
  14. Hello! This might not be the correct forum but maybe another GC user had the same problem: I drive a new BMW 3er. This car has the built-in feature for Screen Mirroring. Sometimes I want to display the GC Android App on the car's screen and this works fine. But as soon as I start driving, the screen switches off with the note: "No motion pictues allowed while driving" (or something like that). From a safety perspective is this (in my mind) not different than a ordinary navigation system, so that I don't see a risk for that. Had anybody of you also the idea to display the Geocaching App in his car and has a solution for that? Regards, Michael
  15. As a side question: I see that there are almost 200 waymarks missing their region in the Mountain Summits category. I assume, that some of them are also the border between two regions. What is usually done then? No region, maybe? Or does a mountain summit always "belong" to one or the other region?
  16. Same problem for me too, three times a day, the app consummed 200,02mb, i exhausted my 4gb package in 5 days !! The solution was to disable thé background data for géocaching app on my phone.
  17. Um das mal genauer zu beschreiben: wenn du eine .gpx Datei mit den Cache hast dann kannst du die entweder in den internen Ordner \garmin\gpx kopieren, oder auf die externe SD Karte im GPSr ebenfalls in den Ordner \garmin\gpx. Wenn du dein GPSr mit einem USB Kabel an den PC anschließt dann kannst du die Dateistruktur des GPSr direkt sehen und kontrollieren, ob die .gpx Dateien auch wirklich im oben erwähnten Ordner sind. Ich würde nicht mixen, internen Speicher und SD Karte, sondern nur die SD Karte als Speichermedium nutzen. Wenn alles passt solltest du die ganzen Cache ansehen können indem du beim GPSr einfach die Option "Geocache" anklickst und dann die Option "Geocache suchen". Alternativ kannst du auch die Karte öffnen und dort die Cache suchen. Bei manchen GPSr (z.B. beim O600 und anderen) werden keine Cache angezeigt die weiter als ca. 200 Km von deinem Standort entfernt sind, keine Ahnung ob das bei dir auch so ist. Gruß, MB Da fällt mir noch was ein: Immer wenn du eine neue .gpx lädst wird die vorherige mit gleichem Namen ohne Nachfrage überschrieben. ALso, den .gpx die du auf das GPSr laden willst, immer einen griffigen Namen geben.
  18. I did not like the inclusion of Kneipp pools into the Spas category, because they are completely different to all the other accepted venues (Just this e.g., they are not a venue). But it has happened and I have to live with it. Barefoot walks and Self-Guided Trails are in a very similar relation, although a tiny bit closer. The first do not need any guidance, self or not, because they are short and almost all I know have start and end in a visible range. And they are too short for "trails". I know about half a dozen of them within maybe 10 kilometers from home. They all are permanent and well maintained. Their lengths vary between about 30 and maybe 200 meters, but more often on the short end. 30 meters are not a trail (Although I know an official 50-meters trail in the Alps: it a straight line towards an spectacular panorama. It is called the Zen Trail and officially supposed to take about an hour. But this is a very singular occurrence and kind of tongue in cheek - or Zen - whatever you prefer).
  19. Having performed a search for location "United Kingdom" which returns ~200,000 caches, if I then click to show the map then the filter automatically applies the "within 16km" limit, and so only maps the caches within 16km of the centre of the country:
  20. Same Problem I also reported to GSAK's Forum as I hate having to baby sit the refresh cache data. I get the same message as above but I'll post the verbose log here. When the retry box comes up it only displays fail. Generating GPX file HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1315120 ResponseContentLength: 1315120 PercentDone: 97 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1562156 ResponseContentLength: 1562156 PercentDone: 98 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ... no response after 40 seconds Previous request ended in error, now doing a retry.... 1/1 SocketConnect: api.Groundspeak.com:443 HostnameResolve: api.Groundspeak.com SslHandshake: Finished HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ... no response after 40 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1558834 ResponseContentLength: 1558834 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ... no response after 40 seconds Previous request ended in error, now doing a retry.... 1/1 SocketConnect: api.Groundspeak.com:443 HostnameResolve: api.Groundspeak.com SslHandshake: Finished HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1520065 ResponseContentLength: 1520065 PercentDone: 96 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3791 PercentDone: 100 HttpInfo: Begin reading response ... no response after 40 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1458884 ResponseContentLength: 1458884 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ... no response after 40 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1520388 ResponseContentLength: 1520388 PercentDone: 96 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ... no response after 40 seconds Previous request ended in error, now doing a retry.... 1/1 SocketConnect: api.Groundspeak.com:443 HostnameResolve: api.Groundspeak.com SocketConnected: api.Groundspeak.com:443 SslHandshake: Starting SslHandshake: Finished HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1531170 ResponseContentLength: 1531170 PercentDone: 99 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ... no response after 40 seconds Previous request ended in error, now doing a retry.... 1/1 SocketConnect: api.Groundspeak.com:443 HostnameResolve: api.Groundspeak.com SocketConnected: api.Groundspeak.com:443 SslHandshake: Starting SslHandshake: Finished HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1594075 ResponseContentLength: 1594075 PercentDone: 96 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1608946 ResponseContentLength: 1608946 PercentDone: 98 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ... no response after 40 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1598748 ResponseContentLength: 1598748 PercentDone: 95 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ... no response after 40 seconds Previous request ended in error, now doing a retry.... 1/1 SocketConnect: api.Groundspeak.com:443 HostnameResolve: api.Groundspeak.com SslHandshake: Finished HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1582142 ResponseContentLength: 1582142 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1593705 ResponseContentLength: 1593705 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1575006 ResponseContentLength: 1575006 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3791 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1732328 ResponseContentLength: 1732328 PercentDone: 98 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1568665 ResponseContentLength: 1568665 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1598342 ResponseContentLength: 1598342 PercentDone: 97 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1515672 ResponseContentLength: 1515672 PercentDone: 96 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1519951 ResponseContentLength: 1519951 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ... no response after 40 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1636958 ResponseContentLength: 1636958 PercentDone: 96 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1594417 ResponseContentLength: 1594417 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1652692 ResponseContentLength: 1652692 PercentDone: 96 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1598360 ResponseContentLength: 1598360 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1522540 ResponseContentLength: 1522540 PercentDone: 98 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1604733 ResponseContentLength: 1604733 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1514843 ResponseContentLength: 1514843 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1452286 ResponseContentLength: 1452286 PercentDone: 99 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1400037 ResponseContentLength: 1400037 PercentDone: 97 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1389432 ResponseContentLength: 1389432 PercentDone: 98 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3790 PercentDone: 100 HttpInfo: Begin reading response ... no response after 40 seconds Previous request ended in error, now doing a retry.... 1/1 SocketConnect: api.Groundspeak.com:443 HostnameResolve: api.Groundspeak.com SslHandshake: Finished HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3790 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1606997 ResponseContentLength: 1606997 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3791 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1516387 ResponseContentLength: 1516387 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1549087 ResponseContentLength: 1549087 PercentDone: 97 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3791 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1556103 ResponseContentLength: 1556103 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1505221 ResponseContentLength: 1505221 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ... no response after 40 seconds Previous request ended in error, now doing a retry.... 1/1 SocketConnect: api.Groundspeak.com:443 HostnameResolve: api.Groundspeak.com SslHandshake: Finished HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1573695 ResponseContentLength: 1573695 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3790 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ... no response after 40 seconds Previous request ended in error, now doing a retry.... 1/1 SocketConnect: api.Groundspeak.com:443 HostnameResolve: api.Groundspeak.com SslHandshake: Finished HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3790 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 719 ResponseContentLength: 719 PercentDone: 100 HttpInfo: Finished reading response Retry requested by user SocketConnect: api.Groundspeak.com:443 HostnameResolve: api.Groundspeak.com SslHandshake: Finished HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3790 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ... no response after 40 seconds Retry requested by user SocketConnect: api.Groundspeak.com:443 HostnameResolve: api.Groundspeak.com SslHandshake: Finished HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3790 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1569470 ResponseContentLength: 1569470 PercentDone: 96 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3790 PercentDone: 100 HttpInfo: Begin reading response ... no response after 40 seconds Previous request ended in error, now doing a retry.... 1/1 SocketConnect: api.Groundspeak.com:443 HostnameResolve: api.Groundspeak.com SslHandshake: Finished HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3790 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ... no response after 40 seconds Retry requested by user SocketConnect: api.Groundspeak.com:443 HostnameResolve: api.Groundspeak.com SslHandshake: Finished HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3790 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1565747 ResponseContentLength: 1565747 PercentDone: 97 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3791 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1526568 ResponseContentLength: 1526568 PercentDone: 95 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3791 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1510008 ResponseContentLength: 1510008 PercentDone: 95 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1502623 ResponseContentLength: 1502623 PercentDone: 97 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1539459 ResponseContentLength: 1539459 PercentDone: 97 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3790 PercentDone: 100 HttpInfo: Begin reading response ... no response after 40 seconds Previous request ended in error, now doing a retry.... 1/1 SocketConnect: api.Groundspeak.com:443 HostnameResolve: api.Groundspeak.com SslHandshake: Finished HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3790 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1651791 ResponseContentLength: 1651791 PercentDone: 99 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1615182 ResponseContentLength: 1615182 PercentDone: 98 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1578108 ResponseContentLength: 1578108 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3790 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1624945 ResponseContentLength: 1624945 PercentDone: 98 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3790 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1560598 ResponseContentLength: 1560598 PercentDone: 96 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3791 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1550252 ResponseContentLength: 1550252 PercentDone: 97 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1601545 ResponseContentLength: 1601545 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3791 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1514466 ResponseContentLength: 1514466 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3789 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1618248 ResponseContentLength: 1618248 PercentDone: 98 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3791 PercentDone: 100 HttpInfo: Begin reading response ... no response after 40 seconds Previous request ended in error, now doing a retry.... 1/1 SocketConnect: api.Groundspeak.com:443 HostnameResolve: api.Groundspeak.com SslHandshake: Finished HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3791 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1497792 ResponseContentLength: 1497792 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1435307 ResponseContentLength: 1435307 PercentDone: 97 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1534777 ResponseContentLength: 1534777 PercentDone: 96 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3791 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1415077 ResponseContentLength: 1415077 PercentDone: 95 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1495783 ResponseContentLength: 1495783 PercentDone: 98 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3791 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1431797 ResponseContentLength: 1431797 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3791 PercentDone: 100 HttpInfo: Begin reading response ... no response after 40 seconds Previous request ended in error, now doing a retry.... 1/1 SocketConnect: api.Groundspeak.com:443 HostnameResolve: api.Groundspeak.com SslHandshake: Finished HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3791 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1542920 ResponseContentLength: 1542920 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3791 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1654787 ResponseContentLength: 1654787 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1594828 ResponseContentLength: 1594828 PercentDone: 99 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1412145 ResponseContentLength: 1412145 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3790 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1501462 ResponseContentLength: 1501462 PercentDone: 96 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1512429 ResponseContentLength: 1512429 PercentDone: 96 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1552743 ResponseContentLength: 1552743 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1556073 ResponseContentLength: 1556073 PercentDone: 70 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1531850 ResponseContentLength: 1531850 PercentDone: 96 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1589441 ResponseContentLength: 1589441 PercentDone: 98 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ... no response after 40 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1550856 ResponseContentLength: 1550856 PercentDone: 98 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ... no response after 40 seconds Previous request ended in error, now doing a retry.... 1/1 SocketConnect: api.Groundspeak.com:443 HostnameResolve: api.Groundspeak.com SslHandshake: Finished HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1488617 ResponseContentLength: 1488617 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1504728 ResponseContentLength: 1504728 PercentDone: 97 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1389881 ResponseContentLength: 1389881 PercentDone: 98 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3790 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1383110 ResponseContentLength: 1383110 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3791 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1419921 ResponseContentLength: 1419921 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3787 PercentDone: 100 HttpInfo: Begin reading response ... no response after 40 seconds Previous request ended in error, now doing a retry.... 1/1 SocketConnect: api.Groundspeak.com:443 HostnameResolve: api.Groundspeak.com SslHandshake: Finished HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3787 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1525443 ResponseContentLength: 1525443 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3791 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1478544 ResponseContentLength: 1478544 PercentDone: 95 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ... no response after 40 seconds Previous request ended in error, now doing a retry.... 1/1 SocketConnect: api.Groundspeak.com:443 HostnameResolve: api.Groundspeak.com SslHandshake: Finished HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1313690 ResponseContentLength: 1313690 PercentDone: 96 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1420872 ResponseContentLength: 1420872 PercentDone: 98 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3789 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1458983 ResponseContentLength: 1458983 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1506756 ResponseContentLength: 1506756 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ... no response after 40 seconds Previous request ended in error, now doing a retry.... 1/1 SocketConnect: api.Groundspeak.com:443 HostnameResolve: api.Groundspeak.com SslHandshake: Finished HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1424883 ResponseContentLength: 1424883 PercentDone: 98 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1508722 ResponseContentLength: 1508722 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1521102 ResponseContentLength: 1521102 PercentDone: 96 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1482986 ResponseContentLength: 1482986 PercentDone: 97 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1561505 ResponseContentLength: 1561505 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1547087 ResponseContentLength: 1547087 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1488359 ResponseContentLength: 1488359 PercentDone: 97 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1455750 ResponseContentLength: 1455750 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3791 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1435319 ResponseContentLength: 1435319 PercentDone: 97 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3791 PercentDone: 100 HttpInfo: Begin reading response ... no response after 40 seconds Previous request ended in error, now doing a retry.... 1/1 SocketConnect: api.Groundspeak.com:443 HostnameResolve: api.Groundspeak.com SslHandshake: Finished HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3791 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1447466 ResponseContentLength: 1447466 PercentDone: 99 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3791 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1401151 ResponseContentLength: 1401151 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1436416 ResponseContentLength: 1436416 PercentDone: 98 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1498197 ResponseContentLength: 1498197 PercentDone: 98 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1398498 ResponseContentLength: 1398498 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1423236 ResponseContentLength: 1423236 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1351777 ResponseContentLength: 1351777 PercentDone: 99 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1455461 ResponseContentLength: 1455461 PercentDone: 99 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1466495 ResponseContentLength: 1466495 PercentDone: 98 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1438485 ResponseContentLength: 1438485 PercentDone: 94 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1544745 ResponseContentLength: 1544745 PercentDone: 98 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1572019 ResponseContentLength: 1572019 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3785 PercentDone: 100 HttpInfo: Begin reading response ... no response after 40 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1613930 ResponseContentLength: 1613930 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3784 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ... no response after 40 seconds Previous request ended in error, now doing a retry.... 1/1 SocketConnect: api.Groundspeak.com:443 HostnameResolve: api.Groundspeak.com SslHandshake: Finished HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3784 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 719 ResponseContentLength: 719 PercentDone: 100 HttpInfo: Finished reading response Retry requested by user SocketConnect: api.Groundspeak.com:443 HostnameResolve: api.Groundspeak.com SslHandshake: Finished HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3784 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1519730 ResponseContentLength: 1519730 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3787 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1566553 ResponseContentLength: 1566553 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3791 PercentDone: 100 HttpInfo: Begin reading response ... no response after 40 seconds Previous request ended in error, now doing a retry.... 1/1 SocketConnect: api.Groundspeak.com:443 HostnameResolve: api.Groundspeak.com SslHandshake: Finished HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3791 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 719 ResponseContentLength: 719 PercentDone: 100 HttpInfo: Finished reading response Retry requested by user SocketConnect: api.Groundspeak.com:443 HostnameResolve: api.Groundspeak.com SslHandshake: Finished HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3791 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1635520 ResponseContentLength: 1635520 PercentDone: 98 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3790 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1592193 ResponseContentLength: 1592193 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1574209 ResponseContentLength: 1574209 PercentDone: 96 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ... no response after 40 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1574350 ResponseContentLength: 1574350 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1540250 ResponseContentLength: 1540250 PercentDone: 99 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ... no response after 20 seconds ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1614597 ResponseContentLength: 1614597 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3792 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1583136 ResponseContentLength: 1583136 PercentDone: 97 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3790 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1575804 ResponseContentLength: 1575804 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1705987 ResponseContentLength: 1705987 PercentDone: 99 HttpInfo: Finished reading response PercentDone: 100 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3793 PercentDone: 100 HttpInfo: Begin reading response ResponseHeader: HTTP/1.1 200 OK HttpStatusCode: 200 ResponseContentLength: 1618298 ResponseContentLength: 1618298 PercentDone: 98 HttpRequestBegin: POST,api.Groundspeak.com:443/LiveV6/Geocaching.svc/SearchForGeocaches RequestHeader: POST /LiveV6/Geocaching.svc/SearchForGeocaches HTTP/1.1 StartSendingRequest: 3794 PercentDone: 100 HttpInfo: Begin reading response
  21. I also spend quite a long time on developing, testing and building the caches. For most of the more difficult ideas I also try to get someone testing it. The most extreme cache to date is GC8YEYQ, an online mystery with a dedicated website. It has 22 questions and puzzles to be solved embedded in a story of a young woman losing her memory. The outdoor part is "just" a 2 stage multi with a really big box and some surprises. The time spend on this is really hard to estimate, but even before the publish it was far more than 200 hours for me alone developing the software, selecting and processing the images, sounds and music. Additionally we need to take into account the efforts of developing the story done by my geocaching partner. We had two teams for beta-testing the online part and the outdoor part. Unfortunately, we had to move the final at one point and therefore we re-did the beta as well. But that's not all...such a complex website needs maintenance. We experiences some glitches that had to be fixed and add another 100 to 200 hours for that and for also for our monitoring tools. Sounds like work? Not at all. It is such a rewarding and fun thing that I love spending the time! All the requests for help, that we love to answer for the perspectve of this poor woman, it's fun! And most cachers write really lovely and long logs. Unfortunately: only available in German :-(
  22. This is not a "Getting Started" question, so I moved your thread to a more appropriate forum section. From a Reviewer's perspective, your proposal would give me nightmares. We already see people doing all sorts of creative things to get around the 528 foot proximity rule. Enabling them to simply choose "Large" as the cache size in order to skirt the rule just means that they can switch the size post-publication to achieve their "objective." How do I enforce the special rule for "Large" size caches only? These are fairly rare, by the way. Do I require a photo and verification that the container size meets the minimum standards? That will add time to the review process. What happens if I say that a 50 cal ammo box is a "Regular," not a "Large?" How do you know that this would "not be a hard change for the IT folks?" Do you have insight into the Reviewer toolbox, and specifically the Litmus Test module? It works great now, but it would be quite a change to the UI to call out "Large" size caches only, in addition to the underlying code for the exemption. What is the shorter separation distance you're advocating for? 400 feet? 200? In my experience, "Large" caches are either hidden way out in the woods, where muggles are less likely to come across them, or as gadget type caches at someone's residence where there is less likelihood of a cache saturation issue. Micros out in the woods, where a Large might be hidden, tend to be frowned upon. If micros in the woods are prevalent in your area, perhaps the better path might be to hide more non-micro caches in the woods and encourage others to do the same.
  23. Finally after many years, King Pellinore breaks the 200 caches found barrier. He found his first cache in 08/25/2001 and quickly became one of NJ's top cachers. Petering out at the end of 2006, his long hiatus (until 2019) was broken by a single find in 2013 of https://www.geocaching.com/geocache/GC3A1QK_block-head He has been getting around a bit, adding states to his geocaching collection. Who knows, he might even place another cache!
  24. Hallo Accu, der Unterschied zwischen aktiviert/unaktiviert ist ein bisschen wir genutzt/ungenutzt. Da man Coins eigentlich immer aktivieren kann (wenn man den Aktivierungscode hat ;-)), sind sie unaktiviert als "Neumodell" tendenziell etwas wertvoller als Sammelobjekt, aber natürlich unaktiviert auch zu nichts anderem zu gebrauchen. Es kann schon sein, dass so eine Serie einen gewissen Sammlerwert hat, wenn sie heute nicht mehr hergestellt werden. Es gibt ja manche Cacher(innen), die Coins sammeln und die zahlen da vielleicht schon ein paar Euro dafür. Reich wirst du aber nicht werden. :-( Eine gute Richtlinie, was die Coins wert sind, wäre für mich, was du selbst bezahlt hast. Ich nehme an, dass du die Coins vor Kurzem geholt hast und nicht schon 10 Jahre rumliegen hast - Wertsteigerung passiert hier höchstens über die Zeit, wie gesagt, zum Beispiel, wenn die Coins nicht mehr hergestellt werden. Wenn du die vier Coins vor Kurzem für sagen wir mal 50 Euronen gekauft hast, dann würde ich jetzt nicht damit rechnen, dass du sie für 200 wieder verkaufen kannst. Was hast du denn - Größenordnung! - bezahlt? Normalerweise würde ich vorschlagen, bei deinem Plan zu bleiben, aktiviere sie, nimm sie zu Events mit, zeige sie Freunden - dann haben die Coins einen gewissen Sinn. Ich nutze Tracking-Codes schöner Coins auch gerne als Gimmicks zum Entdecken in meinen Caches. Ansonsten würde ich mal schauen, ob du Geocoin-Sammler-Foren oder Facebookgruppen oder so etwas zu dem Thema findest. Ein echter "Coiner" kann dir sicher mehr sagen und auch ein Angebot machen. ;-) Herzliche Grüße und viel Spaß beim Cachen - Trackables haben da meiner Meinung nach eigentlich recht wenig mit zu tun - Jochen PS: Ich fand deine Anfrage übrigens völlig klar formuliert und verstehe Alferics Beitrag nicht.
  25. https://www.geocaching.com/blog/2021/03/new-souvenir-challenge-the-science-of-discovery/ It’s 21 years into the 21st century and geocachers continue to be experts in the science of discovery. Recently, geocaching innovators have experimented in the Adventure Lab® to create new experiences. From interactive food tours to local trivia, cachers are formulating Adventures in new ways. Let’s combine geocaching with Adventure Lab to create the perfect solution for discovery. April 12 through July 11, find Adventure Lab Caches and other geocache types to earn up to four scien-terrific souvenirs. Join this challenge to learn more about Adventures and the undeniable chemistry between geocaching and science. How to play From April 12 at noon UTC through July 11, 2021, collect points on your leaderboard by logging Adventure Lab Caches and other geocache types. Earn up to four new souvenirs by collecting 300 points during the promotion period. How do I find Adventure Lab Caches? Download the Adventure Lab® app for Android or iOS and start playing! Open the app, go to your profile, and log in with your Geocaching account. Select a nearby Adventure from the map or the directory list. Read the description to learn more. Tap Start and navigate to the nearest available Location. Follow the instructions in the description. Find and enter the Location answer. After submitting the correct answer, you earn an Adventure Lab Cache find for your geocaching statistics and 10 points on your leaderboard. Visit all Locations. Enter the solution for each Location to complete the Adventure. Be sure to rate it and share your experience! What are the four souvenirs I can earn? Rocket science: 50 points Geology: 100 points Environmental science: 200 points Futurology: 300 points
×
×
  • Create New...