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. Another page, left open all day. In the last minute, it went from 38 to 100 to 200 MB (!) simply by me scrolling a bit, up-and-down with the scroll-wheel click for smooth scrolling, entirely within the (moderately long-winded) cache description, and pointedly above the logs area which are loaded dynamically. (They were already fully loaded a while ago.) Stand back, she's gonna blow! 275. Yesterday I tried to diagnose this with the inspector, but trying to display a report (can't remember which) triggered a runaway page-file top-up, which I aborted just before the file filled (7GB of 8), and I aborted quickly, well as quickly as possible given the duress. Not sure how Linux handles a full page file; no app has ever taken me that high... PgDn, PgUp. 356. Anything I should look for in the inspector? This is incredibly repeatable. (Or are you sick of hearing from me?) 363. PgDn, PgUp. 450 MB. Aborting.
  2. I recently started Geocaching and love that I can combine it with my love for hiking. I always stay on the trails, but with GC I've now discovered great places off the trail both hiking and mtn biking that I can be comfortable exploring seeing as how people before me have blazed the way. Time to get a GPS! Its all about the kids this time of the year so my budget is $200 (Merry Christmas to me). I am comfortable with technology and would like something that won't be obsolete in a year or two. What I've found so far is: Garmin eTrex 20 and Magellan eXplorist 310. Which do you recommend and why? Is there another in this price range you would suggest? Thank you in advance for your advice!
  3. 200 finds in 10 minutes. Maybe a time-stopping machine as well
  4. Hello, It looks like you have done some machine translation on the Finnish language version of geocaching.com website. The most blatant errors are on the page Profile - (My) statistics,. but the errors seem to repeat all over the place. The new translations are incorrect, unprofessional, way below your previous high standard, and confusing. Can you please revert back to the old Finnish translations as soon as possible? The problems are: Incorrect translations for the word 'cache' (examples below) Multiple incorrect and misleading translations (e.g. for find stats and for the different cache types) (examples below) Incorrectly conjugated words (examples below) Mismatched conjugations, adjective-noun agreements and English langauge prepositions mixed in. 1. Incorrectly translated 'cache" The word Cache translates in Finnish as 'kätkö' (a hide) or geokätkö, instead of 'kontti' (a Docker container, or an ocean container, meaning the standardized transportation container) or a 'välimuisti' (the temporary cache file on your computer). Currently the profile page has interesting translations such as "Olet löytänyt 3500 välimuistia ensimmäisestä välimuistihakuistasi 08.04.20XX" . (=You have discovered 3500 temporary files since your first temporary file search 08.04.20XX.) or Löytämäni konttityypit = The types of ocean containers I have found. 2. Multiple incorrect translations The profile part describing the streaks, slumps, best days, etc. is now unreadable. Etsi hinta --> translates as "Find price" and is misleading. What price am I supposed to find? 1.1089 välimuistia / päivä --> translates as (xx temporary cache files / day) Pisin juova --> Now translates as "Longest stripe" and is meaningless 32 peräkkäistä päivää löytöillä 13.07.2017 - 13.08.2017 --> The word löytö is now incorrectly conjugated. Pisin romahdus --> Now translates as "Longest collapse" and is meaningless 361 peräkkäistä päivää ilman löytöä 17.04.2012 - 13.04.2013 Nykyinen juova --> Now translates as "Current stripe" and is meaningless 2 peräkkäistä päivää löytöillä 28.11.2020 lähtien Nykyinen romahdus --> Now translates as "Current collapse" and is meaningless. 0 peräkkäistä päivää ilman löytöä The profile part describing the finds nearest/farthest from home has multiple incorrect translations. E.g. "Löydä Kaukin itä (pääministeriltä)" now translates as "Find *remoteist (from the prime minister)" 3. Incorrect conjugations, mismatched conjugations, etc. The following serve as examples: 200 kätköt marraskuu of 2016 --> "Kätköt" is ungrammatical, should be "kätköä", and what's the English preposition "of" doing here? 2 peräkkäistä päivää löytöillä 28.11.2020 lähtien --> "Löytöillä" for the noun "löytö" is not grammatical. Cumulative finds per month --"Kumulatiiviset löydöt kuukaudessa" has mismatched adjective-noun agreement There are multiple other examples on this page, but currently the same problems seem to repeat on other Finnish language pages as well. As said, this is way below your (up until now) fluent everyday Finnish language. Please revert to the old translations, or have someone re-translate the pages properly using the old translations as reference. Thanks already in advance!
  5. Hi, I know this question gets asked a lot but I'm looking for recommendations on a GPS to use for geocaching. I'm still mostly new to this and used to use my phone but recently had to switch to a cheap $50 Samsung and it gets cranky and freezes a lot so geocaching wouldn't be the best for it. I don't ha routerloginve much money and I'm looking for something hopefully less than $200. Thanks in advance for any help y'all can provide. 192.168.0.1
  6. Wondering if anyone in the St. Louis area would mind hunting down a TB from a recently archived cache? It may not even be there, as it may have been muggled right before the cache was archived. Not sure. Cache is (was) the TB Chateau at GCRDJD. TB is TB7797W. She's travelled more than 20,000 miles from Missouri all the way to Hawaii and back, up through the east coast, only to make it within 200 miles of her goal to get back home to us before this happened. We'd love to see her again. She's a seahorse travelling with a froggy friend on the same chain. We know it's a long shot, but if there's even a slim chance that she might be able to make it home, we have to try!! Thanks!!
  7. 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.
  8. 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.
  9. 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.
  10. 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
  11. 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.
  12. Set up a 200 stage multi - I think the answer to your question will be similar to the number of finders of that multi..... :) I don't think there'd be any relation. People won't tackle a 200 stage multi because it will be difficult and time consuming to finish. I doubt the fact they they only get one find at the end will be a significant factor. And, on the other hand, people crazy enough to do a 200 cache power trail are sometimes the same people that are crazy enough to tackle a 200 stage multi.
  13. 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.
  14. 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.
  15. Has anyone ever seen a BMW roundel Geocoin. I own a Bimmer and would like to turn it into a discoverable coin by posting the registration number onto my window or bumper (just like a TB sticker) but not at the cost of designing a coin and selling off the hundreds of extras. I tried to search online but got nowhere. Just as searching within the forums. Because BMW is a short word the forums just kick back an error, not a result. If you know where I might be able to get one that has not been activated, I would be very happy. Many thanks in advance. BigBadger
  16. 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
  17. 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....
  18. Ich kann es Dir nicht sagen was dann passiert... ich kann nur schätzen: Es passiert nix ? Ich bin noch in einem anderen Forum und da freuen sich gerade mehrere Leute über die derzeit freien Autobahnen. Zitat: Statt zu Normalzeiten mit Durchschnitt 68 KMH zur Arbeit schaffe ich aktuell das doppelte weil ich problemlos 200 KMH fahren kann. Ein Wort gegen das Grundrecht auf der Autobahn 200 KMH zu fahren und es ging echt heftig los... das Risiko sei ja absolut kalkulierbar und überschaubar und so schnell fahren ist legal usw. usw. Ich fahre seit Jahren nicht schneller als 150 - und das nur wenns pressiert. 130 bis 140 sind eine sehr gute Reisegeschwindigkeit auf Autobahnen. Viele Dienstwägen haben die Vorgabe maximal 130 KMH - so z.B. auch beim Fuhrparkservice der Bundeswehr und in den ersten 2 Märzwochen bin ich damit ca. 1800 KM sehr bequem zweimal durch Deutschland gefahren. Aber das wird nun sehr OT.
  19. 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.
  20. @Mineral2 I thank you very much for the suggestion above. I now have a GPSMAP 66i, and tested with the settings you provided. Prior to the test, I modified the Trip Computer page: (1) I retained “Elevation” in the upper most left column slot, (2) I replaced the next slot down with “GPS Elevatiom, (3) I replaced the upper most right column slot with “Barometer”, and (4) I replaced the next slot down with “Ambient Press.”. I then changed the Auto Calibration to “Off” and the Barometer Mode to “Fixed Elevation”. Additionally, I manually selected the Calibrate Altimeter Method of Current Elevation to Calibrate to 200 ft. Walking along the level Green Belt (about 100 yards off the shore) in Sunset Beach, CA, I recorded about a ½ mile track. As I walked the Elevation slot displayed a constant value of 200 ft. while the GPS Elevation slot displayed between 9 ft. and 15 ft., which was reasonable. After concluding the walk, I synced to the Explore app on my phone and viewed the elevation profile as a constant 200 ft. Conclusion, these Altitude settings resulted in the barometric elevations being recorded and not the GPS derived elevations. My next test was to set the Auto Calibration to “Continuous” and the Barometer Mode to “Variable Elevation”.Additionally, I manually selected the Calibrate Altimeter Method of GPS Altitude and selected “Calibrate”. I then drove up and down a hill, while not recording a track, of about 50 feet and noticed that the Elevation and GPS values were identical. Now, selecting “Start” to record the track, I noticed that the values for Elevation and GPS Elevation varied by a few feet, with the Elevation being a few feet higher than the GPS Elevation values/ Actually, they both decreased going down the hill and increased going up. On basically a level street, they both went up and down slightly, with the Elevation values always slightly higher than the GPS Elevation values. Conclusion: Referring back to the top, with the two top fields, on the left, being Elevation above GPS Elevation, it is the top most, Elevation values that always are recorded. When Altitude calibrated to GPS and Continous selected, the top most value is GPS. However, when not recording, both fields are identical while there are slight differences when recording.
  21. 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.
  22. 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.
  23. 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.
  24. 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.
  25. 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.
×
×
  • Create New...