Cretti

Let me start by acknowledging how old this thread is... It still makes a good read. I think it's relevant to add to the end of the thread an additional question; so far the discussion has focussed around only two potential types of caches: virtuals; which we know are grandfathered, and traditionals; which we know are not recommended due to the physical nature of the container and the alarm caused by people searching / hiding it etc.. - Fine... But, what about event caches? - There's nothing physical there, there's nothing left anywhere. In some ways they are very much like virtual caches; there is nothing physical at all to draw any concern or attention. Indeed, the participants already have permission to be within the terminal, presuming that they are there, jointly for two purposes; the first to attend the event-cache, but legitimately with business in the airport taking a flight.. I'm considering the scenario of an event cache listing aimed at trying to meet other cachers while in transit, and I'm keen to explore, specifically the idea of transit, inside of the airport itself, on the flight side of immigration controls and security checks - Assuming too that this is in an airport where they do not allow public access into the areas past immigration. I've read through the event listing guidelines... I can't find anything specific to events which should prevent this. There are general comments about airports, but these comments appear to relate to the security concerns which is addressed above; with traditionals or people's activities which would potentially cause some interest / concern for security / safety. Holding a geocaching event deliberately at a part of an airport where people are expected to congregate, say, a meeting point, or a bar; would not in itself cause any alarm or concern. On what basis then, would such an event listing be denied by Ground Speak or the community reviewers? It seems reasonable to me that this type of listing would encourage the social interaction of geocachers, which is exactly what the event-cache listing type is intended to do... So... I'm travelling soon and am considering listing an event in transit. Can anyone see any clear issue with this?