ohgood

Consider the situation from the viewpoint of the person/organization that erected the fencing. You presumably erected it to keep people out of that particular area, right? Now, wouldn't you find it irritating to learn that someone online was telling people it's fine to cross your fence and enter that area to play their game? Might you be tempted to ban that particular game from being played in that area if that's the way they're going to act? Is it really worth it for cachers to "poke the bear" and potentially irritate land owners/managers rather than simply disable the cache while the area is fenced off? Believe it or not, geocaching has been banned from areas for less. Again, it depends on the circumstances. Common sense instead of blanket generalities. Actual common sense should dictate that you put away the sense of entitlement and don't cross a construction fence to play a game. The only posts I've seen mentioning crossing a fence, are the posts that want the cache disabled. There are a lot of assumptions in this thread.

Consider the situation from the viewpoint of the person/organization that erected the fencing. You presumably erected it to keep people out of that particular area, right? Now, wouldn't you find it irritating to learn that someone online was telling people it's fine to cross your fence and enter that area to play their game? Might you be tempted to ban that particular game from being played in that area if that's the way they're going to act? Is it really worth it for cachers to "poke the bear" and potentially irritate land owners/managers rather than simply disable the cache while the area is fenced off? Believe it or not, geocaching has been banned from areas for less. Again, it depends on the circumstances. Common sense instead of blanket generalities.

+1. The third party applications on the android market are awesome, and fully baked.

It's simple, the person uses their senses to decide if they want to go for it. It's not a DMZ with watch towers and machine guns. Its kind of funny that an orange fence is getting this mutch attention and hand wringing. It's simple, You don't cross the orange fence. Find another geocache to do and come back to this one when whatever's going on is done. You can speculate all you want as to why the fence is there but what ever the reason the land owner or land manager doesn't want anyone on the other side of it. I didn't say that. :-)

Except that the guidelines are currently being interpreted as requiring a log that is somehow separate from the container. A scrap of paper behind a magnet has both a container (the magnet) and a log (the scrap of paper contained between the magnet and the surface). A magnet that you sign the back of has only one (take your pick: the magnet is either the container or the log, but not both). Oh , well there's a rule that makes a world of difference, lol. I'm not knocking YOU at all, is just very funny how insignificant some things are.

Educate people to use less packaging, and waste fewer things everyday. Just transporting garbage from non land fill areas to landfills is ignoring the real issue.

... or other type of log for geocachers to record their visit ... OK then, that covers writing on the magnet.

It's simple, the person uses their senses to decide if they want to go for it. It's not a DMZ with watch towers and machine guns. Its kind of funny that an orange fence is getting this mutch attention and hand wringing.

Sounds like the cool caches ! Seeing a log with signatures on it would have made me lol and improved the day for sure!

Looks like the co answered your question. Wazzabigdeal ?

We're aware of the compass zeroes issue and have put in a fix that should go out with the next release. As for the GPS refresh rate: The app request updates from the system at a rate of every 5 seconds, or 15 meters of displacement. Looking at your video, it seems to be behaving as intended. However, if it's refreshing so slowly that you can walk several hundred feet between updates, that would indicate a problem, and we'd love to hear more. Clearly 5 seconds is tooooooo long. This is a huge issue and usability problem. Every other GPS enabled app seems to be able to do a continuous update and not this INTENTIONAL????????? 5 second delay. That is way way way to long .... or 15 meters of displacement???? Really????? On an app where we are looking for things within FEET????? 15 Meters and 5 seconds is absolutely HUGE!!!!! Please fix this. Five seconds is fine for navigation to the area, but once in the area (300 feet or so) it (that application) could switch to two seconds for reporting position. Most of the devices can report every second, so two should be acceptable, unless there is a reason for not using those as a frequency? I understand the offset accuracy but 5 seconds traveling in a car when you are at 300 feet and then next update you are at 300 feet past the cache is not good. This app didn't used to have this issue. This is a recent development. 15 meters displacement again is just bad. We are trying to locate items within much smaller areas then 15 meters which by the way is 49.2 Feet -- if you are in the woods, it takes a while to move 49.2 feet. Not good. I happen to like this app and use it as my primary -- however, these are the things that other cachers are constantly complaining about and why they don't want to switch from the Classic app -- which doesn't appear to have this issue, nor does c:geo, nor does Cachly. Again - 5 seconds and 15 meters are arbitrary numbers which are detrimental to the usability of the app on the whole. Add to this the recent bug of starting off at 1.2 Miles really makes it bad. I've gotten out of the car with 3 other cachers (running the other apps) -- and I have to stand around for 30-60 seconds before I can even figure out where to go - meanwhile the others have located the cache. sorry, i wasn't making excuses for the long refresh times or big distances.... i was hoping to point out that the app could be smart enough to CHANGE from 5 seconds (or whatever amount) to a shorter frequency once you're x feet from the cache area. i reallllly like using proximity alerts for this kind of thing. i'll turn on proximity alerts for a folder of waypoints (or caches, or whatever we're calling them) so that I'll get a beep/buzz when i get within 1000 feet of one. then, after making sure it's not A) near a guardrail or a micro i'll turn on guidance alerts that increase with frequency as the distances decreases..... and i can usually walk right up to the cache. now, i know, if you're in a car, it's going to be more difficult to do this unless you're familiar with the area. i'm usually on a motorcycle, so dropping off the road and into a safe place to check the gps isn't a big deal. changing directions/etc to get on top of the cache is pretty easy. usually. i wonder if anyone is interested in a smarter smartphone app that can change the gps update rate ? i bet that would make people really happy.

you could just keep on typing about this if you like. pictures, notions, potions, and whatever else that went along with the fun. spill the beans man, it sounds like a hoot !

We're aware of the compass zeroes issue and have put in a fix that should go out with the next release. As for the GPS refresh rate: The app request updates from the system at a rate of every 5 seconds, or 15 meters of displacement. Looking at your video, it seems to be behaving as intended. However, if it's refreshing so slowly that you can walk several hundred feet between updates, that would indicate a problem, and we'd love to hear more. Clearly 5 seconds is tooooooo long. This is a huge issue and usability problem. Every other GPS enabled app seems to be able to do a continuous update and not this INTENTIONAL????????? 5 second delay. That is way way way to long .... or 15 meters of displacement???? Really????? On an app where we are looking for things within FEET????? 15 Meters and 5 seconds is absolutely HUGE!!!!! Please fix this. Five seconds is fine for navigation to the area, but once in the area (300 feet or so) it (that application) could switch to two seconds for reporting position. Most of the devices can report every second, so two should be acceptable, unless there is a reason for not using those as a frequency?

Link to the website you downloaded from? And the proven you used (online or offline) to create the map? I usually carry several map types with me when going outside my known areas, and two different routing (route creating) backups.

Look on Amazon, there are cases/sleeves for just about every device made. Or you can diy with some silicon and corn starch.... http://www.youtube.com/shared?ci=dj7UfvDPlo0 I bet some pretty cool "I'm just geocaching bro!" Cases could be made by some of the folks here. Maybe incorporate a NFC tag, trackable, number, and ice all in the same case back?

have you tried clearing the cache for that application? if there are other applications requesting GPS info it can make one (or all) of them lag in reporting position. The only app that has issues with GPS displaying is the new Geocaching app. well that stinks. have you posted a bug about it ? maybe that would help ?

have you tried clearing the cache for that application? if there are other applications requesting GPS info it can make one (or all) of them lag in reporting position.

Curious, didn't you ever read the guidelines? One of the basic requirements is a log and container. If someone ever reported it, it'd be temp-disabled by a Reviewer (for not having a log or container), giving the CO time to "fix" it. Doubtful the Reviewer knew of this when it was published. Some odd reason, caches like this (that break guidelines) seem to be the ones getting favorites too... exactly. think i'll start using 'favorited' as a filter to find cool caches. it's so much more fun to be surprised by a rule-bender, instead of just another pill bottle with a log.

last weekend we used locus in a casio c811 to record the track from a morning of frisbee golf. personally i'd give it a 1/5 for terrain since riding a bike wouldn't be difficult, and 3/5 for tree cover but given what i've seen from geocaching it would probably be considered a '3/5 hiking trail' with '4/5 tree cover'. the phone was either in a pants pocket, or the bottom of a backpack, unless i was recording a waypoint. according to the automagical track coloring, the worst reported accuracy was 43feet (red) and the best 10feet (blue) and the average around 30ft (green). waypoints were not averaged, or given any longer than it takes to type "launch 3" for each waypoints name. again, the gps wasn't given any help by standing still for ten minutes, averaging, or holding it up on a 20 ft pole to help it see more satellites. i did notice that what would normally be a 10ft reported accuracy when attached to my handlebars was instead a 30-40ft accuracy while in a pants pocket, or the bottom of my backpack. i'm not planning on carrying a surveyors pole on any of my next hikes/bikes, so this is unlikely to change in the future. anyway, a picture is here i hoped to find another gpx on gpsies/everytrail but failed to find one to compare. if anyone would like to provide their gpx track from the location, that would be pretty cool to have on hand.

i could show you how to do all that (offline, no data needed) via my favorite application, if you aren't only considering stand alone devices.

Yes! There are a bunch of logs on my caches "I forgot my pen" ...so I'm counting it as a Find because I frankly cannot stand the cache nor its location and want to forget the whole ordeal, I couldn't be bothered to do even the most basic "find the cache and sign the log" and I can never return, and let's never mention it again, it's all so very very traumatizing... I would much prefer a Note "Will be back when I've saved up enough to buy a pen" or whatever the issue is, with the actual Found It after signing. With non-pen logs on my caches, the "Finder" often doesn't even open the container. Is the log missing? Is the container lid stuck? They don't even know, and the non-pen "Found It" provides me with no information about cache condition. But I'm pretty sure those guys weren't Canadian. maybe that one is an inside joke ?

The tech is far superior, however there is still physics. The electronics to correlate the satellite signals has gotten a lot better. But phones don't have much room for a proper GPS antenna, so their ability to detect the signals in marginal conditions tends to be worse. And new GPS units use the same tech as new phones. So comparing a new Garmin 64 to a iPhone, the Garmin will still win. BINGO The only drawback of a phone I have ever seen is GPS sensitivity. Under heavy tree cover, a phone will crap out before a good handheld GPSr. However, have you looked at my "downtown accuracy" event results. The phones dramatically outperformed handhelds. this part is odd to me. you've stated that trees are problematic, but then started that phones are better in cities. do you have an explanation for this? Trees block the signal. Large buildings cause multipath reflections. Different problem. Both situations suffer from both problems to a degree although as stated the dominate problem is different for each. In tree cover there is reduction of signal availability as well as some multi-path issues resulting in loss of signal, loss of track, and loss of accuracy. In urban canyons multi-path errors can be far greater. Cell phones can oft times be seen to outperform in urban areas as they get assisted positional data over the cell network to augment GPS positions. The technological downside of phone based GPS is often antenna design and capability. oh, so you're saying that agps isn't just for start-up, and that it constantly helps the phones ?

The tech is far superior, however there is still physics. The electronics to correlate the satellite signals has gotten a lot better. But phones don't have much room for a proper GPS antenna, so their ability to detect the signals in marginal conditions tends to be worse. And new GPS units use the same tech as new phones. So comparing a new Garmin 64 to a iPhone, the Garmin will still win. BINGO The only drawback of a phone I have ever seen is GPS sensitivity. Under heavy tree cover, a phone will crap out before a good handheld GPSr. However, have you looked at my "downtown accuracy" event results. The phones dramatically outperformed handhelds. this part is odd to me. you've stated that trees are problematic, but then started that phones are better in cities. do you have an explanation for this?

i don't know how the app store works on ios devices, but i'm assuming it's possible to sideload, or install applications without using the official apple market ? maybe you could copy the app from one iphone to another ? i do this frequently for android devices, when someone asks about "hey what mapping app is that?" and push them the freebie over bluetooth.

you mean you're not sure if you want to go through all the work again, only to have very few people appreciate it ? i can understand not seeing the point if no one notices. if you're worried about the official rules and regs, i'd say you have nothing to worry about.