Jump to content

Cache Attributes


Jeremy

Recommended Posts

Parking is not an "attribute."  All caches have parking; it is a question of where. 

Not quite. As soon as parking is far enough away (which is obviously not a question of distance in time), there is no way of logically associating a parking area to a cache IMHO.

Let's assume that the parking area is some five hours' walking distance from a cache and fifteen minutes by cablecar - would you associate the parking area to the cache???

BalkanSabranje

I would think that if you have to take a cable car, then that will be specified in the text. In this example the "parking neaby" attribute would probably not be selected unless you make it a multi-stage that starts in the parking lot of the cable-car facility.

 

I suspect the descritive text for the meaning of the attributes need to be pretty specific about the fact that "parking" means being able to park any normal sedan (some folks at this site pride themselves in driving their off-road vehicles to ANY location on the plante and parking it there) and that it refers to a clearly legal parking spot (not in front of a gate to private property, 3-ft shoulder, etc). Also, as BalkanSabranje illustrates, the term "nearby" will need some definition (I would suggest 512ft).

Link to comment
Also, will "trading cache" "non-trading cache" or whatever be part of the attributes?  I must have missed any answer.

 

I know a lot of past threads where ragging on micros because they (most) don't contain trades, yet most, if not all, of the ones around here do.

 

I figure trading is more of the issue than the size of the container.

Wouldn't a micro with trade items be a small cache?

Well, what do you call a 35mm film cannister with trade items. Is that a micro or a small?

Link to comment
Wouldn't a micro with trade items be a small cache?

Yes. It seems the addition of a small size has made that attribute moot.

Don't let the fact that I was the one that suggested it cloud your judgement.

 

The ability to trade has little to do with size. There are trading and non-trading hybrids for example, and as mentioned in an above post, trading in 35mm film cans--even an APS film can. As a matter of fact, the last cache we did was a trading micro.

 

Trying to filter trading on a completely unrelated field is not good sense. You know it. Don't let pride get in the way of a good data model.

Link to comment
Also, as BalkanSabranje illustrates, the term "nearby" will need some definition (I would suggest 512ft).

 

Odd choice of distance. Binary? I would suggest 528 feet, which is the point at which my Garmin eTrex changes its distance readings from miles to feet.

Link to comment

Jeremy said:

 

Wouldn't a micro with trade items be a small cache?

 

Yes. It seems the addition of a small size has made that attribute moot.

 

Perhaps this is the wrong forum, but I think the description of "small" is confusing. It says it's big enough for a log book and a few trade items. The couple of caches I have placed that I eventually decided should be called "small" were NOT big enough for a log book. What I call a "small" is a large prescription pill bottle or a macadamia nut jar, which the standard 3x5 lined notebook will not fit into. I use a roll of cash register paper, perhaps 20 feet, rolled up in such caches for a log. Since it can't hold a "log book", it looks like it should be called a micro, but it's far bigger than a 35mm film canister. And anything that holds an actual log "book" probably usually ends up called a regular.

 

I think a micro is pretty clear: a 35mm film canister or a hide-a-key, with only a folded scrap of paper for a log and no trade items (although I often leave a foreign coin or a sticker or some such). The "small" should be described as larger than a micro and large enough for small trade items, but the comment about being large enough for a log book should be dropped.

Link to comment
I like the idea of "kid friendly" or perhaps some basic age range (e.g., ok for < 10 yo).

 

I like the idea of "kid friendly" or perhaps some basic age range (e.g., ok for < 10 yo).

 

The problem I have with this idea is that ALL geocaches are supposed to be "kid friendly". If you're placing one that ISN'T kid friendly, you need to rethink what you're doing!

Link to comment
I like the idea of "kid friendly" or perhaps some basic age range (e.g., ok for < 10 yo).

 

The problem I have with this idea is that ALL geocaches are supposed to be "kid friendly". If you're placing one that ISN'T kid friendly, you need to rethink what you're doing!

"kid friendly" in the given context might refer to the terrain difficulty rather than to "adult contents" of the cache (whatever that might be anyway).

 

BS/2

Link to comment
"kid friendly" in the given context might refer to the terrain difficulty rather than to "adult contents" of the cache (whatever that might be anyway).

Yes, or the cache is particularly interesting and/or educational for kids, or contains kid-themed items, or was placed by a kid (or class), etc. Not kid friendly may be a place that would be dangerous for kids like terrain, etc.

 

It is assumed caches are kid friendly in the way that kids could see the contents. Not kid friendly does not mean that there is porn in the cache. I suppose an "adult theme" attribute would fit the bill if we were to swing that way. We don't.

Link to comment
I suppose an "adult theme" attribute would fit the bill if we were to swing that way.

 

And I can envision a number of delightfully lascivious icons to represent such!

 

Enjoy,

 

Randy

 

PS: Upp! I now see kid-friendly's already in there (removed earlier comment), but would still endorse "near interstate" as I believe it compliments "along-a-route" rather than being redundant. (Nevermind a quicker implementation of such--allowing "route" coding to be more sophisticated rather than spending time/effort on a temporary jerry-rig, assuming that's still the plan...)

Edited by RJFerret
Link to comment

Noticed in another thread that this was to implemented early this week (Hooray :D)

Wanted to add a suggestion for a cache attribute. It might not fit with the others, but it certainly could be useful, what about a "This cache is up for adoption" attribute. That way if you moved, or left caching, the cache could somehow be marked, and could be filtered on as needing someone to adopt it.

Reviewers might even be able to set the flag in certain circumstances. Anyways, just thought I'd throw it out there.

Link to comment
Kirbert wrote:

The problem I have with this idea is that ALL geocaches are supposed to be "kid friendly". If you're placing one that ISN'T kid friendly, you need to rethink what you're doing!

I guess caches that require rock climbing or scuba equipemnt should be archived, or we should "rethink" them. :D

I don't think you have a good grasp of what geocaching is / can be, buddy.

Link to comment
Perhaps this is the wrong forum, but I think the description of "small" is confusing.  It says it's big enough for a log book and a few trade items.  The couple of caches I have placed that I eventually decided should be called "small" were NOT big enough for a log book.

By your own admission you understood what the site definition for "small" was, but you decided to go ahead and categorize your listing as a "small" cache even though it wasn't. There is a difference between being confused about a definition and disregarding it. Stick with the definition and don't supersize your cache listing if it doesn't fit the definition.

Edited by Jeremy
Link to comment
Guest
This topic is now closed to further replies.
×
×
  • Create New...