Jump to content

Chirp


Recommended Posts

Permission issues don't "change" just because its a chirp vs a container or something else.

 

Some places have a very open caching policy, where explicit permission isn't needed, some go as far as paperwork with exact details, others, just a quick OK email is sufficient. Found out existing caching policy for the location and go from there.

Link to comment

To add to what Potato Finder said;

A Chirp is not a geocache. Rather, it is a stage of a geocache. At some point you'd need to have a container as a final.

Because a Chirp is a physical object, placed by you, the 528' rule applies, just like a stage of a multi.

True, but the volunteer cache reviewers have been asked to be very liberal in allowing leeway for conflicts between a chirp beacon and another physical geocache. Since it's the signal that matters, not the object, a chirp is in between a virtual waypoint and a physical waypoint. It counts more than a firetack but less than a metal tag.

Link to comment

To add to what Potato Finder said;

A Chirp is not a geocache. Rather, it is a stage of a geocache. At some point you'd need to have a container as a final.

Because a Chirp is a physical object, placed by you, the 528' rule applies, just like a stage of a multi.

True, but the volunteer cache reviewers have been asked to be very liberal in allowing leeway for conflicts between a chirp beacon and another physical geocache. Since it's the signal that matters, not the object, a chirp is in between a virtual waypoint and a physical waypoint. It counts more than a firetack but less than a metal tag.

Kewl! I did not know that.

Thanx for the inside scoop!

Link to comment

To add to what Potato Finder said;

A Chirp is not a geocache. Rather, it is a stage of a geocache. At some point you'd need to have a container as a final.

Because a Chirp is a physical object, placed by you, the 528' rule applies, just like a stage of a multi.

True, but the volunteer cache reviewers have been asked to be very liberal in allowing leeway for conflicts between a chirp beacon and another physical geocache. Since it's the signal that matters, not the object, a chirp is in between a virtual waypoint and a physical waypoint. It counts more than a firetack but less than a metal tag.

Kewl! I did not know that.

Thanx for the inside scoop!

A Chirp is not designed to be found as with a typical cache stage. So with its range of 50 feet, your waypoint may be in the middle of a trail, with the Chirp device off trail hidden among thorn bushes. So it would be great to have some leeway.

Edited by kunarion
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...