BIT Cache/ Unknown Cache Combo
Posted: Wed Feb 11, 2015 5:39 pm
If I scan a BIT cache...does it take me to the cache listing where I can read the actual cache description or does just ask me for the password and then logs the cache as found?
Here is why I am asking...
I want to increase awareness of OCUS in my area but I really am trying not to cross-list my caches. Plus even if I cross-list a traditional, and clearly advertise the cross-listing in/on the physical cache container, the finder will still have to write down the OC #, go to the website, and log the cache...some might feel that is redundant work for the same find. So a BIT cache takes care of that...simply scan and log. But I am looking for an added incentive. I would like to hide additional OC Unknown Caches in the same vicinity...taking advantage of the less restrictive 300' limit. My thought is that on my OC Bit Cache page, I could have at the bottom of the description "Unknown Cache OUXXXX is located at NXXXX, WXXXX about 350' away". That way, a BIT finder knows there is another find nearby...one that he can't find on any other listing service.
On the Cache page for the Unknown cache, I would simply say "actual coordinates can be found on BIT Cache Page OU####. Someone searching online for OCUS caches in the area will be essentially handed the coords for the unknowns...but I have no problem with that...that would be a good problem to have.
I am planning a series to come out in the next few months, but wanted to start doing some of the planning now.
Here is why I am asking...
I want to increase awareness of OCUS in my area but I really am trying not to cross-list my caches. Plus even if I cross-list a traditional, and clearly advertise the cross-listing in/on the physical cache container, the finder will still have to write down the OC #, go to the website, and log the cache...some might feel that is redundant work for the same find. So a BIT cache takes care of that...simply scan and log. But I am looking for an added incentive. I would like to hide additional OC Unknown Caches in the same vicinity...taking advantage of the less restrictive 300' limit. My thought is that on my OC Bit Cache page, I could have at the bottom of the description "Unknown Cache OUXXXX is located at NXXXX, WXXXX about 350' away". That way, a BIT finder knows there is another find nearby...one that he can't find on any other listing service.
On the Cache page for the Unknown cache, I would simply say "actual coordinates can be found on BIT Cache Page OU####. Someone searching online for OCUS caches in the area will be essentially handed the coords for the unknowns...but I have no problem with that...that would be a good problem to have.
I am planning a series to come out in the next few months, but wanted to start doing some of the planning now.