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. What I don't get is the need to put symbols there in the first place we all know the format by know I reckon without degrees and minutes symbols i.e. N51 23.200 W 1 42.000. Keep it simple and problems like this just will not happen.
  2. Oregon 700 is fine if you dont want the camera, and is available for closer to $200 USD. A new Oregon is, as far as I can determine, at least a year or two away.
  3. I like the idea. We just need someone who writes the virtual category and we have to think about the options we offer. I like option 2 (very unique ones and maybe super large ones about 200 items), I see no problem to combine these two criterias as long as the description state it clear.
  4. Ich will jetzt da nicht der Naturschädigung das Wort reden -. aber was Du da schilderst, ist harmlos. Vielleicht sogar nützlich. Da gibts andere Dinge, die man meiden sollte. Zum Beispiel Astlöcher. Oder andere Löcher, die oft Unterschlupfe sind. Oder bergseitige Böschungen. Oder oder oder. Aber am wichtigsten ist, sich Gedanken zu machen. Auch über den Effekt, ob man nicht massenweise Leute herlockt (im Normalfall ist das ausserhalb von Schnellgreifrunden und 3 km weg vom Parkplatz eher nicht der Fall). Und dass es sinnvoll ist, Caches so zu verstecken, dass Cacher die einfach finden - was (von Versteckideen mit Mehrwert abgesehen) sowieso die Regel sein sollte. Aber die Challange, Caches naturverträglich zu verstecken bzw. die damit verbundenen Effekte zu minimieren, ist eine interne - wenn auch höchst lobenswerte - Challenge. Da sind wir bei bei den schlimmsten beim Grad 3 auf der Skala - der Forst und andere Naturnutzungen bei gefühlten 200 - jeden Tag. Das muss man auch einordnen. Höchsten Anspruch nach innen - realistische Betrachtungsweisen nach aussen. Gruss Zappo
  5. It's because the Wherigo Foundation site is an alternate listing service. It was supposed to demonstrate to Groundspeak what we were intending to do with Wherigo so we could run Wherigo for Groundspeak, free of charge for everyone involved. The other Wherigo player apps and builders are on Groundspeak's ban list because of the same reason: they're an alternate to something else--their PocketPC app and their builder, respectively. Though I worked to get community work officially recognized, those at the top of Groundspeak never communicated any of their verbal support to those enforcing Groundspeak's guidelines. Throughout Wherigo's lifetime, regardless of individual intentions at the company, Groundspeak's apparent attitude has always felt one of apathy and passive hostility towards anyone attempting to make their product more accessible to the community. I coined the term "the Wherigo Foundation is Fight Club". They've always told their reviewers not to allow any mention of the Wherigo Foundation or other non-Groundspeak Wherigo applications in cache listings. It's just that the reviewers aren't consistent with each other that caches in some areas were published and others not. Part of the partnership agreement I was reviewing did state that, if the Wherigo Foundation site were to be discontinued, all cartridge files would be provided to Groundspeak for dispersal to community members. I was planning to do that, anyway, so that was fine. There was one other clause I haven't before talked openly about. Suffice it to say, the way I interpreted it, if I ever walked away from Wherigo and did not transition its running to others, the entire game would come to an end. I did not like that Wherigo would then seem to rely on one person's continued health, existence, and interest. The partnership agreement never panned out because Groundspeak took too long in replying, which further showed their apathy (I'd say nine months, several times, classifies as too long, regardless of how patient you are--while waiting for one such reply, I had a house built and moved into it). An odd quirk to all this is this Wherigo forum. Why can we openly talk about these applications? The answer is a combination of me and Groundspeak's apathy. Back when matejcik and charlenni first presented their applications, the forum rule was that moderators needed to clear through Groundspeak talk of new applications. So, as the moderator, I hid the threads and sought approval. Groundspeak did not reply for a month, so I unhid the thread. When that second application was announced, I hid the thread again and asked Groundspeak. I again didn't hear a reply and unhid the thread. Later, I did get a reply, saying it was fine and that there wasn't anyone at Groundspeak who could speak for authorizing these, so that's why it took so long. I asked, then, for something no other moderator has: the authority to make these decisions on my own. It was granted. Ever since then, so long as something wasn't commercial, I allowed it. Now, mind you, Groundspeak's employees have definitely changed since then, so no one there remembers that this responsibility was delegated, so would likely take it away. Another odd footnote is Wherigo\\kit. I am able to use Groundspeak's API for authentication, which does require approval and a review. More recently, when I had to submit an updated overview of this application, I was asked by someone at Groundspeak if I wanted Kit to appear in the list of official Groundspeak partners. I guffawed, pointing out that Groundspeak's reviewers do not allow caches to be published if they mention Kit, the Wherigo Foundation, or any other application, so listing Kit as an official Groundspeak partner would thoroughly confuse the situation, so Groundspeak should really consider its stance on the matter. This was about two years ago. Finally, something that irritates me. Groundspeak allows cachers to mention GSAK and Project GC in their cache listings. Both are commercial applications--GSAK was up until recently and Project GC pushes a subscription model. Groundspeak also allows mention of other commercial applications in cache listings. But, yet, when it comes to everything the community has done to help Groundspeak with Wherigo--and everything we have has always been free, with the individual developer shouldering 100% of the continued cost--Groundspeak has this as their official position. And, believe me, there are ongoing costs. I average about $200/month for hosting, storage, SSL/TLS license, and domain registrations between Kit, the Wherigo Foundation site, DevOps/TFS, and the staging areas I use when publishing. I could decrease the cost by doing a shared hosting plan, I suppose. I suppose I could have still continued to create things. But there comes a time when one needs a solid support group to provide feedback and motivation. I don't have that. And you'd figure people in my own area would be really supportive of my endeavors, be it Wherigo or having found almost 95K caches. They're not. There's a distinct anti-Wherigo feeling in my area. There have been some that would like it if I quit geocaching altogether. So, no support there. One can continue only so long against the flow and apathy before exhausting oneself. So, later, my job became the beneficiary of some of my free time. I worked uncompensated overtime 300 hours last year and 400 hours this year (and no time off). You'd think they'd be grateful, but instead I get managers telling me they're not asking me to work extra hours and they're apathetic about all the things I'm doing to fix their aging application single-handedly. No encouragement, no support, no appreciation from there. Sigh. So, anyway, that's my view on the matter. There are always other sides to it, though I've tried to be neutral.
  6. The same user apparently visited two of my waymarks 200 km apart. Both without pictures. The first one stated that he/die walked by it, the second one simply "and another". I deleted the second visit.
  7. One of my favorite caches had lat/long coordinates that would take you to a strip mall parking lot. There were quite a DNF logs which said that they search in the obvious spot (a light pole skirt...I know that you don't have them in the U.K.). Although the listing didn't include elevation, there were clues in the listing which suggested that it was not in the parking log, but under the parking lot. About 200' from the published coordinates was an entrance to a tunnel under the parking lot and a mostly dry creek bed. The surface of the earth was actually under the parking lot. There was also a heavily favorited cache in German that required one to get into an elevator (which also had room for a car) which took you down to a tunnel that went under a river. If one looked at an satellite map with the lat/long coordinates it would appear that the cache was in the middle of the river, instead of in the tunnel about half way through. Since elevation is not included in geocache metadata, the terrain rating can be used to give seekers a clue to where the container is hidden. For that cache in Germany, the fact that it didn't have a T5 rating indicated that it was not *in* the river and would require special equipment.
  8. 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
  9. After running a mini non-event with local cachers at my Wherigo last night, a few of them wanted a rundown on the known working hardware platforms. I searched through the messages on the board and came up with this list. Feel free to reply with anything else that works. Asus MyPal A639 AT&T 8525 with Windows Mobile 6 and a Bluetooth GPSr (i.Trek M7) Dell Axim X3(Windows 03) connected to an Etrex Summit Dell Axim X51v Pocket PC and Pharos Pocket GPS-360 Dopod 818 pro with either Garmin 10x or GlobalSat BT-338 Eten x500+ Fujitsu Siemens Pocket Loox T830 a smartphone running WM5 Garmin Colorado Garmin iQue M4 Garmin iQue M5 Garmin Oregon HP iPAQ 110/111 Classic (624 MHz PXA310) with a DeLorme BT-20 GPS HP iPAQ 2210 +GPS HI-303CF HP iPAQ 2795b and a Blue Next 905GR HP iPAQ 3870 with a Pretec Compact GPS Low Power CF Card HP iPAQ 3955 with the compact flash GlobalSat BC-337 HP iPAQ 4150 (Windows Mobile 2003) using the Garmin Mobile 10 Bluetooth GPS HP iPAQ 4700 with GlobalSat BT GPSr HP iPAQ 6815 with BT-GPS HP iPAQ rx5915 HP iPAQ rx5935 HTC Touch Cruise HTC TyTN with Navicore BT Mouse I-Mate JasJam with a Holux external Bluetooth GPS I-Mate PDA-N Medion pocket pc, running windows 5.1 Mio A201 Mio P350 PDA Mitac Mio 168 Mobile Crossing Waypoint 200 with a BT-GPS Palm Treo 700WX phone (Windows Mobile 5) with the same Garmin Mobile 10 Pharos GPS 525+ which is a Windows Mobile 5.1 Pocket PC platform and built-in GPSr Pharos Traveler GPS 525+ has a built in GPS Verizon XV6700 using a Delorme BT-20 GPS Choosing the right hardware at an affordable price seems to be a major barrier to entry for new folks. I lucked out and got a Garmin iQue M5 for $100 on craigslist. Dave
  10. Fair enough. But there are limits to this when it just gets annoying too - I tend to have a common sentence or two/three for sections of a day or the day, depending on what we're doing. Then a unique sentence or ten for each find (depending on the find). Sometimes you see logs where someone on a trip writes out a full essay about the whole week or two, and that becomes the log for the 200 finds during that time, that's a definite irk....
  11. I still don't understand it. How do you loop your AVERAGE? Do you loop it if the average is at least 200 words? I also aksed one guy why he does that nonsense. He even said that he might think about changig his way of logging. Sadly, but not surprisingly, he still logs the same way with impolite and inappropriate logs.
  12. I sent out two high-end TBs, now long gone, working miniature fishing reel, and a solid miniature of a v-twin motor. The other 2/3rds sent out around a dozen coins, all long gone too. - It didn't take us long to figure that's a losing side-hobby, especially when you're talking coins. Two promotion Trackables went missing shortly after they were placed. Another two promotion Trackables are supposedly still sitting in the caches I first placed them in, one a year ago, the other two... The other 2/3rds now has TBs, and 280 coins activated in her collection, and around another 200 unactivated. I now have "our" sig coins, so have over 300 unactivated ... a lotta sets (the AT n stuff...), and around 200 sig coins. I've been placing sig coins in caches, as an incentive to get folks to walk, or hand a newb one at an event. - I'd rather give them away, than find some maggot stole them...
  13. For statistical analysis - I started this thread 6 days ago. On that day I reached out to 15 finders of 8 of my ECs about not logging caches. Of those, 5 have gotten back to me. Of those 5, four were veteran players who either 1) forgot to send the email or 2) their email went to my spam folder on accident. The last was a newbie who responded to my email with "hi no." So of 15 players reached out to, 4/15 have supplied answers of 9/15 have not and 0/9 newbies* have responded to the messages with answers. *a self defined term based on number of caches and specifically earthcaches found, typically less than 200/5 split.
  14. That's semantics, but it's hard to argue that averaging is not beneficial to improving accuracy. Let's run a simulation as an example. Take a random number. Say 57 value = 57 We have a hypothetical GPS device that isn't very accurate. In fact, that device can only tell you the coordinates to value within 50 places. It will return a value randomly anywhere between 7 and 107. Not very accurate at all. Now, let's take 200 random readings of "value" where the results can wildly range from 7 to 107 and average them together. If we run this simulation multiple times (just for fun!)... 57.020301980532984 56.60828961934022 58.36645537356805 Now, let's take a "precision" device. that gives us coordinates to within 15 feet and grab a single value that we think looks accurate. 70 66 52 My personal experience shows GPS averaging gives more accurate coordinates than trying to pick out a single reading. Is it possible that a single reading can be more accurate than the average? Yes, it can, but most of the time, it probably won't be as good as an average of many samples taken.
  15. Add me to the wishful thinking queue. I thought I'd read that the new hosting laws would not be backdated? But they have, in a seemingly random manner. Like others on here, I've been hosting images and other files on my own website since 2010. I had fears about the Jan2020 release, but on checking quite a few of my puzzles, whatever I'd done to the images had stayed intact. The recent removal of the image proxies, without notice. (I get global emails telling me what souvenirs I can collect, so why not tell everyone the image hosting rules are changing, again.) I now have 200+ puzzles to redo. On my caches, the line seems to stop on 22May2014. I had 2 caches published that day, one of them still has the image proxy, and on the other it has been removed. No sense to it at all.
  16. I'm trying to edit my notification distance to pick up newly published caches in my neighboring communities. My original distance was 80 kilometers, I'm trying to update it to 200 or 250 kilometers. I enter the new distance and then select edit notification, I get an instant message on screen that it has been updated but it remains at 80 kilometers. I even tried deleting the notification and then creating a new one and it still stays at 80 kilometers, its like it has a memory of 80 and won't save anything else. Tried this a least a dozen times over the past couple of months thinking maybe it was just a bug and may have been fixed. Nope.
  17. Unless it's accurate for any cache, I don't recommend it. There are some places where the satellite imagery is intentionally skewed but hundreds of feet. I found a few caches in that area, one of which appeared on the map to be in the middle of a lake (it was a good 100' from the shore). Although not the problem that it used to, there used to be a lot of places in the world (this isn't just a game played in urban/suburban America) where the resolution was so poor it was difficult to even identify features on the map as a building. There also was an issue of cloud cover completely obscuring what one would see on the ground. This is an old image be it shows an area in Costa Rica (in a rain forest) where a cache was placed. The coordinates were actually pretty accurate but were about 30 feet from a 200' steep drop into a river bed.
  18. Wenn der andere Owner geschrieben hat, wird er doch auch eine Entfernung angegeben haben, oder? Ich würde vermutlich erstmal antworten mit der ermittelten Entfernung, und ihn fragen warum er meint dass es da Probleme wie Verwechslungsgefahr o.ä. geben könnte. Ich habe schon mal einen Cache um ein paar Meter verschoben damit ein anderer Owner seinen neuen Cache an der Wunschposition ausbringen konnte - aber auch da gabe es keine Verwechslungsgefahr. Im schlimmsten Fall muss man eben in beiden Listings schreiben warum jetzt nicht hier, sondern da zu suchen ist. Aber selbst dann sollten mehr als 200 m Abstand noch genug sein. Ergänzung: Die sind ja auch beide noch an unterschiedlichen Seiten der B2. Also keine Verwechslungsgefahr.
  19. That's exactly what I'm saying. So out of 3,000 caches found, not a single one meets your standards? Get off your high horse. It doesn't have to literally be your favorite, they votes to tell other cachers which ones are the best of the 3,000. If you haven't found one favorite in the last 3,000 (ratio) then you sure as hell aren't gonna suddenly find 300 in a row that you deem worthy, so what's the point of saving them? But hey, I'm just a peasant with 200 finds. It would sure be nice to have some more votes on the thousands of caches around me so I can visit the the better crappy caches over the worse crappy caches on my way to 300 finds.
  20. Bei mir in der Nähe gibt es eine Holzbrücke mit einer Länge von ca 200 m. Die Planken sind mit ca 250- 300 Hutmuttern befestigt, nun kam mir der Gedanke in eine der Hutmuttern ein Nano einzubauen. Was denkt ihr wäre das du schwer zum finden und was wäre das für eine Schwierigkeit? Die Hutmutter soll sich mit den Fingern lösen und wieder festschrauben lassen.
  21. Hallo, Die gesperrte Fläche ist erstmal der Bereich um einen Geocache, in dem du keinen anderen Cache legen kannst also die 161Meter. D.h. Wenn jetzt auf der Karte 2 Tradis in einem 200 Meter Abstand gelegt wurden und um beide wird diese rote Sperrfläche von 161 Meter gezogen, dann überschneiden sich zwar die roten Kreise, die Caches sind aber trotzdem weit genug auseinander. So zumindest verstehe ich das (falls nicht kann mich ja jemand verbessern ). Grüße Qmm
  22. I just looks 15 is the most in one day for me. While on vacation all traditional puzzle caches. I need the passwords from 10 in 2 counties to complete the challenge. We did 7 the next day covering 250 miles to finish a series. Also stopped for lunch went shopping and visited a second hand store. In my 20 mile drive to work there's a cache every mile a few park and grabs some puzzles and a couple multis. I get two or three a week during my drive. Usually when my daughter or wife are with. I've had to call the CO on acouple I couldn't figure them out. Most are 200 to 500 feet from the road in a tree row. I'm not chasing any numbers so I do at my pace.
  23. Hier liest man ja aber genauso - bzw. sogar deutlich öfters -, dass der schnöde PETling des Powertrails (der da nur liegt, weil die letzte Dose schon wieder 180 Meter her ist) auch die tollen Locations blockiert. Und der wird ganz oft gefunden, also mit welchem Argument werden wir den los? Für mich ist "Cache wird oft/selten gefunden" weder ein Qualitätsmerkmal noch wird daraus eine Daseinsberechtigung abgeleitet. individueller einfacher Tradi an einer tollen Location mit großer Dose Powertrail-Caches Hardcore-Cache mit T5-Einlagen Stadt-Multi D5-Knobel-Mystery Leitplanken-Micro ...... Das ist für mich alles Geocachen und die Abwechselung finde ich toll. Und da ich einzelne davon nicht mag, mache ich sie halt einfach nicht. Liegenlassen muss man halt lernen und genug Hardcore-Caches bewundere ich auch nur aus der Ferne.... Irgendwie toll ist das sicher trotzdem und dann bin ich traurig, dass ich das nicht kann. Aber deswegen darf der doch trotzdem andere Cacher erfreuen. Und - ganz ehrlich - ich glaube, der Hardcore-Cache erfreut mehr Cacher als die Filmdose mit nassem Logbuch an der Leitplanke; auch wenn der zweite Cache öfters gefunden wird. Der eine Cache hat halt 200 Finder, von denen 199 den Cache halt machen, weil er da ist, und sich über den ungepflegten Zustand auslassen. Der andere Cache hat 3 Finder, die auch Jahre später noch davon schwärmen. Meine Entscheidung ist klar - Quantität ist nicht alles.
  24. I've mentioned this one a few times in the past but there was a cache which had coordinates for a spot near a lamp post in a parking lot but that's not where the cache was hidden. There was a culvert (about 30 feet wide and 8 feet high) under the parking lot that held a small creek. The entrance to the culvert was about 200 feet from GZ and it was a fairly easy walk 200' into the culvert where the cache was hidden. The cache had quite a few "searched in the obvious spot, it isn't there" logs.
  25. Memory Lane Souvenirs I took me a couple reads to understand the promotion. At first glance, I thought I'd get a souvenir for attending my first Mega. But no, I get a First Mega souvenir even though I've never attended a Mega event before. So far I'm not a big fan, but I do enjoy new promotions! At Geocaching HQ, we’re honored to be part of the worldwide community of adventure-seekers known as geocachers. As we continue through the 20th year of geocaching, we invite you to take a trip down Memory Lane to celebrate the community and the milestones that have made geocaching what it is today! We realize not everyone is able to go out caching right now so we are doing things a little different this year. Memory Lane will start on June 1st and be available all year long through January 3, 2021. Move through the Memory Lane game board by finding different geocache types to collect points and earn up to five new souvenirs! Memory Lane FAQs: What are the five souvenirs I can earn? First geocache hidden: 10 points First geocoin: 50 points First Mega-Event: 100 points First million geocaches hidden: 150 points 20 years of geocaching: 200 points How can I earn points? The maximum number of points you can earn for any cache log is 10 points. How do I participate? From June 1, 2020 through January 3, 2021, collect points by logging geocaches. Earn up to five new souvenirs by collecting 200 points during the promotion period. What about COVID-19? As the Coronavirus 2019 (COVID-19) situation is evolving rapidly around the world, we encourage geocachers to follow the most current guidance from public health authorities when choosing how to participate in activities such as geocaching. Your health and safety are the top priority. Our goal is to have a promotion that is both fun and safe. As such, we will continue to make any adjustments as needed so that the promotion is as inclusive as possible. Why does Memory Lane last the rest of the year? This extension of Memory Lane is to accommodate areas of the world that are facing stay-in-place mandates due to COVID-19, while also being accessible to those who can safely go geocaching. We hope this extension of Memory Lane will allow geocachers around the world the ability to participate in the promotion at a later date, without feeling pressure to go geocaching when it is not safe to do so. Can I join Memory Lane at any time? Of course! If you are not starting right away, you still have the chance to earn all five souvenirs as long as you collect enough points through January 3, 2021. Make sure to log your finds by January 6, 2021 noon UTC to earn souvenirs. Where can I see my souvenirs? As soon as you collect a certain number of points, the associated souvenir will automatically be awarded to your profile. The souvenirs appear on your profile on Geocaching.com and in the Geocaching® app under the souvenir tab. Is Memory Lane in the Geocaching® app? Memory Lane will temporarily be in the Geocaching® app starting with the beginning of Memory Lane on June 1, and will be accessible until January 11, 2021. Go to your profile and click on Memory Lane to see your progress in the Geocaching® app. Do Adventure Lab Caches count towards earning points? Yes! You will earn five points for each Adventure Lab Cache you find. Do points stack for an individual geocache find? Points do not stack. For each geocache find, you will earn the higher amount of points available. So for example, if you find a Mystery Cache (worth 7 points in Memory Lane) with over 10 Favorite points (worth 10 points in Memory Lane), you will receive 10 points total. My points aren’t correct, help! If you change a Write Note, DNF, or other log type to a Found it log, it will not be recognized in Memory Lane. You logged on Monday, June 1 before noon UTC (convert to your local time here). We suggest that you wait to log until AFTER Monday noon UTC – which in some places like New Zealand is Tuesday at midnight. Otherwise the points will not count for the first week. You saved a Draft on a Monday, June 1 before noon UTC. If you have already posted your logs, select “View / Edit Log / Images”, then click the pen icon and “Submit Log Entry” on the website. Your logs should now be counted towards your total. What does UTC stand for? Coordinated Universal Time (UTC) is the basis for civil time today. It is the time standard (not a time zone) commonly used across the world. You can convert UTC to your local time here.
×
×
  • Create New...