Re: What can Geocaching Australia do for you in 2016?
Posted: 07 January 16 10:54 pm
Geosportz please. Its an Olympic year. The last two were so much fun.
Free and Open Geocaching
https://forum.geocaching.com.au/
http://forum.geocaching.com.au/viewtopi ... =1&t=18883The Morris wrote:I love the idea of the history caches - I can see it used for a range of other special interest locations as well. I would also like to proceed with the earlier idea we had mooted about getting information from 2 related virtuals that give you the final for a physical cache. I'm assuming the programming is not going to be very different.
That could be done.No_Tomorrow wrote:Is there a way of locking people out of logging a history cache so they can only log it with a code hidden on site? I know that means you can't DNF or NA or the like, but can they just email for these? It would at least save the CO having to confirm it.
Although having said that, the owner still needs to be involved - things change, information signs disappear or are redesigned and in the case of a certain building in my home town may disappear completely.the Monkey King wrote:Keeping the cache owner from needing to confirm a historical cache has been found is a good one, especially when the cache owner no longer caches or can't answer emails for what ever reason.
If you really wanted to go down that path why not go for a QR code - these are already used on this site. Personally I'd prefer to keep the cache information and the facility to log it together. Remembering the Earthcache model which inspired this - I go to the history cache site, (hopefully) I have read the cache description, I have my list of questions to answer, I can choose to either answer them on site using my phone data or take some notes and log them at home on wifi. As a finder of this kind of cache I would prefer to log at home.This way someone has to visit the site to get the answers to the questions, and then tap their phone to the NFC chip to get a link to a web site were they can answer the questions.
I'd be happy to help with this. Might be good to take this to a thread of its own and any others who wish to be part of this conversation can be included.It also means that anyone who just wants to submit a general 'wish' for 2016 can do so without getting swamped by History Cache discussion.As GCA doesn't have reviewers we need to rely on hiders doing the right thing in regards to picking a site for a History cache, so a clear set of guide lines would be needed - I am happy to knock up a draft idea for others to pull apart or add to if it would help.
So there will still be an option to be able to log a DNF/NM/NA without having to submit a successful codeword?CraigRat wrote:That could be done.No_Tomorrow wrote:Is there a way of locking people out of logging a history cache so they can only log it with a code hidden on site? I know that means you can't DNF or NA or the like, but can they just email for these? It would at least save the CO having to confirm it.
The mechanism for using a codeword is there, we would just need to activate it for that type.
Yes, you'd only need the codeword to actually claim a find.petan wrote:So there will still be an option to be able to log a DNF/NM/NA without having to submit a successful codeword?CraigRat wrote:That could be done.No_Tomorrow wrote:Is there a way of locking people out of logging a history cache so they can only log it with a code hidden on site? I know that means you can't DNF or NA or the like, but can they just email for these? It would at least save the CO having to confirm it.
The mechanism for using a codeword is there, we would just need to activate it for that type.
No, its a good idea to be able to isolate State specific locationless. Perhaps the use of Public Tags might also work.LouiseAnn wrote:no one must have liked my idea/comment/thought/suggestion......
Except people share the codeword So it's not perfect by any means. Neither is Q&A. Nothing is. Even NFC's can be hacked. Just ask Munzee whether you can also spoof your GPS location and log Munzees in far away countries. We're going to go with the best we can and if anyone tries to cheat too much I'm sure the community will admonish them.CraigRat wrote:That could be done.No_Tomorrow wrote:Is there a way of locking people out of logging a history cache so they can only log it with a code hidden on site? I know that means you can't DNF or NA or the like, but can they just email for these? It would at least save the CO having to confirm it.
The mechanism for using a codeword is there, we would just need to activate it for that type.
Locationless means they can be found anywhere except where the lat/lon indicate. Restricting a locationless to a state is not something I'd be looking to implement on a locationless cache. The locationless concept removes the locale, state and country attributes and hacking them back in on only some circumstances is too much long term technical debt. Not saying that locationless caches can't be enhanced to have other information, but as a cache that has no location, using the locale or state or country removes the locationlessness from them. There need to be other ways to work out what locationless caches are about, so a text search needs to be allowed, or tagging to categorise them. I'd be looking for a whole of solution approach to locationless cache rather than piecemeal.LouiseAnn wrote:I have recently started researching locationless caches and I frustration I found quite early on is that there are a fair number that aren't technically locationless. I'd love it if these type of locationless could have the state you need to be in to complete them added to the attributes. This way I would stop looking at the Queensland bus one, for example.