markandsandy

The advantage of option 1 above would be that you'd now have two caches ready and waiting to be placed in a new location! The disadvantage is if the reviewers see a habit of this, they might point out the Cache Permanence section of the guidelines and you could have difficulty placing new caches.

Just happened to have my old blue legend in my coat pocket On the Navigation screen, go to the options: There is a toggle between "bearing pointer" and "course pointer". It only shows the one that you can change it to, so if it says 'course', you are set to 'bearing' like you want.

Having designed user interface software for devices with much more complexity than a pocket query, I agree with Markwell on this. Combinations that are mutually exclusive should not be allowed to be selected. But since they have not changed the interface , just remember this: If nothing is selected - all caches are returned. Anything you select, restricts the caches that are returned to only those that meet that criteria. If a cache does not meet all of the criteria selected, it won't be returned.

They are mutually exclusive. As far as I know it's impossible to be both. That would make sense though I'm not sure why you can't do both. I guess if they're both mutually exclusive I'll have to run two queries or, depending on how many member's only caches there are in my area, just manually load them onto the GPS. Thanks for the reply. If you want all caches, don't select either.

No. A cache cannot be both "available to all users" and "for members only". For a cache to be included in the query, it has to meet all the selected criteria.

Of course, now they have posted a flood watch The current forecast for the Snoqualmie river out by us is 6 feet over flood stage by Thursday morning (that's 1 foot below the record). No direct problem for us, but we might not be getting out of town for a day or two. I hope that isn't a surprise for anyone. With the amount of water that fell from the sky as snow, only to have it melt because of warm temps and even more water from the sky as rain...it was inevitable. Not that I'm not sorry for those affected by it, but it was only a matter of time. Not a surprise, we've lived in Carnation for 25 years, so we know what to expect. It's interesting that it still fits the title of this thread.

I'm curious about this statement. I've seen it a lot and not sure if it's a forum thing like "prolly" or "pwned" or are people saying that it sounds like them, or are they saying "resemble" when they mean something else like resent? Thanks. In this case, hydnsek was the person I was referring to when I made the statement that she replied to. Usually it means that it either sounds like them, or it was them.

So it's OK to do something illegal if you probably won't get caught?

This same topic was raised just a few days ago in this thread: Music Cache This would be a clear violation of copyright, as is the "Operation Disc Drop" also mentioned above. In the US, damages could be between $750 and $150,000, depending on how good your lawyer is, and how good their lawyer is. This would be for each copyright violation.

That means we will see people ask all the same old worn-out questions again, because they "couldn't find if this was asked before". Oh, wait. They already do.

Of course, now they have posted a flood watch The current forecast for the Snoqualmie river out by us is 6 feet over flood stage by Thursday morning (that's 1 foot below the record). No direct problem for us, but we might not be getting out of town for a day or two.

Not quite right. From the link in the original post:

<raises hand> OOOH! OOOH! OOOH! I know the answer to that one! When the seeker either (1) chooses to read the disclaimer, or (2) chooses NOT to read the disclaimer. That was easy. Gimme another one! The disclaimer only frees Groundspeak from legal responsibility. It doesn't free the hider or the seeker.First line of the disclaimer assigns the responsibility to the seeker: Cache seekers assume all risks involved in seeking a cache. I don't think that phrase frees the hider. It is a fact that hiders have been fined for poor cache placements (bomb scares). You're not even talking about the same thing. Caches that have been causes of bomb scares, where the hider was fined for wasting the bomb squad's time, didn't cause any harm to a cacher. Cache seekers assume all risks involved in seeking a cache. The original question quoted above had to do with responsibility for the cache seeker's actions . Bomb scares have nothing to do with seeking a cache, so I would not expect those risks to be the responsibility of the seeker. Clearly they are the responsibility of the hider.

<raises hand> OOOH! OOOH! OOOH! I know the answer to that one! When the seeker either (1) chooses to read the disclaimer, or (2) chooses NOT to read the disclaimer. That was easy. Gimme another one! The disclaimer only frees Groundspeak from legal responsibility. It doesn't free the hider or the seeker. First line of the disclaimer assigns the responsibility to the seeker: Cache seekers assume all risks involved in seeking a cache.

In that case, you aren't sharing, you are transferring ownership. No violation. Now if you are keeping a copy for yourself, that copy would be a violation.

Damages could be between $750 and $150,000, depending on how good your lawyer is, and how good their lawyer is. This would be for each copyright violation. Now, if you have an extra $150 grand lying around, you can save yourself a lot of hassle and just send it to me

Thanks! I suppose that accuracy of GPS coordinates is not all that important, eh? Some folks put the co-ordinates as for their front garden/yard or a nearby road intersection. One point to consider: Although the intention is to keep such a cache unpublished, it is a good idea to make it clear in the cache description that it is only a 'hidden home cache' and you have no intentions of submitting it as a real cache. This is because if another cacher places a real cache near to your unpublished cache then your local reviewer may see your cache when he does the proximity check for all nearby caches. It will help him (and the other cacher) if he can see clearly from your description that there is no physical cache associated with your 'hidden cache' co-ordinates. MrsB You can actually archive your unpublished cache. Then your reviewer won't see your coordinates and won't have to deal with it if a real cache is placed nearby.

The Gardiner Bird Store and Gardens A 1/1 cache that is now at 152 finds and 2 DNFs. We were the first DNF, haven't had a chance to go back and look again. The second DNF was by a very experienced local cacher.

I think he means "Western Australia". Heh, I was trying to figure out where in the heck Perth was in Washington. It's 9245 miles West-Southwest of Seattle

I may have received bad information, but I was told it is legal here in WA. However, anything mounted on the dash or windshield may not obstruct your view of the road. I have a suction cup type mount and use it in all three of my vehicles. (Honda CRV, 91 Ford F150 pick up, and a class C motor home.) In each case it is easy to mount it in such a way that the only view blocked is a part of the hood. Your information was good for Washington: RCW 46.37.410 Windshields required, exception — Must be unobstructed and equipped with wipers. (2) No person shall drive any motor vehicle with any sign, poster, or other nontransparent material upon the front windshield, side wings, or side or rear windows of such vehicle which obstructs the driver's clear view of the highway or any intersecting highway.

The most common standard was 39 feet, which could be carried on a standard 40 foot flatcar. Some railroads varied, especially early ones.

OK, let's try this again. When moving TBs, I will look at their page and note not only if they have a mission, but who has moved them, and which caches they have visited. I will also follow up on them after placing them, to see that they eventually have moved on from the cache that I have placed them in. In doing this, and in reading this forum, I've made some observations: Occasionally, a cacher will post a thread such as "I've got a TB that needs to travel to <insert destination>. Is anyone heading that direction?" It's as if they have appointed themselves as TRAVEL AGENTS for someone elses Bug. When TBs travel through some (non-prison) TB Hotels, a few cachers frequently visit the cache and pick up a large number of TBs, which are later dropped off at another TB Hotel. The TBs then get dispersed from that cache into a new geographical area. These cachers are kind of like BUS DRIVERS traveling regular routes. On the other hand, TBs that travel in a more random cacher/random cache mode tend to stay longer in one geographic area, and often seem to have trouble breaking out of that area. These TBs are HITCHHIKERS. They may have a specific destination, but never know who is going to pick them up, or where they will actually end up. I'm just curious how do you, as a travel bug owner, prefer to see your bug move? Please keep the discussion light (I deliberately left out PRISON GUARDS and BUGNAPPERS).

Oh no! It ate my post. I'll recompose and be back later.

Go to the cache page. Upper right corner - click "log your visit" Select "write a note" as log type Add any text you want to the note. Below the text entry box is a box that lists all trackables in your possesion. Highlight the one you dropped off. Submit your note.