Cache attributes: Difference between revisions

From Opencaching.eu
Jump to navigation Jump to search
mNo edit summary
Line 13: Line 13:


* all OC attributes that have equivalent meaning to a GC attribute to use the same numeric ID; ''(while the meaning is equivalent, the exact wording of it's name need not be the same. examples are "bring your children / suitable for children / kids friendly / etc");''
* all OC attributes that have equivalent meaning to a GC attribute to use the same numeric ID; ''(while the meaning is equivalent, the exact wording of it's name need not be the same. examples are "bring your children / suitable for children / kids friendly / etc");''
* all OC attributes that have equivalent meaning to a negated GC attribute to use the same numeric ID added to 9000. ''(for example: "available 24/7" is ID 13. "NOT available 24/7" to be ID 9013.);''
* all OC attributes that have equivalent meaning to a negated GC attribute to use the same numeric ID added to 9000. ''(for example: "available 24/7" is ID 13. "NOT available 24/7" to be ID 9013.);''  
* OC attributes that have equivalent meaning on both PL and DE branches and existing DE only attributes to have numeric IDs in the range 100 - 199;  
**DE branch negated attributes use a separate flag and retain the ID without adding 9000.
* all OC future and existing attributes that are PL branch specific to have numeric IDs in the range 200 - 299;
*OC attributes that have equivalent meaning on both PL and DE branches
*existing DE branch only attributes to retain their IDs in the range 100 - 199;
*all OC future and existing attributes that are PL branch specific to have numeric IDs in the range 200 - 299;
* all OC future attributes that are DE branch specific to have numeric IDs in the range 300 - 399;
* all OC future attributes that are DE branch specific to have numeric IDs in the range 300 - 399;
* all OC special purpose attributes to have numeric IDs in the range 900 - 999;
* all OC special purpose attributes to have numeric IDs in the range 900 - 999;

Revision as of 10:00, 15 May 2019


DRAFT, WORK IN PROGRESS

A geocache may have attached a number of attributes, giving more information about the cache, the hiding, the recommendations, requirements, permissions, hazards, other helpful information related with the search.

This document describes the existing cache attributes across Opencaching sites.

Attribute numbering rules

  • all OC attributes that have equivalent meaning to a GC attribute to use the same numeric ID; (while the meaning is equivalent, the exact wording of it's name need not be the same. examples are "bring your children / suitable for children / kids friendly / etc");
  • all OC attributes that have equivalent meaning to a negated GC attribute to use the same numeric ID added to 9000. (for example: "available 24/7" is ID 13. "NOT available 24/7" to be ID 9013.);
    • DE branch negated attributes use a separate flag and retain the ID without adding 9000.
  • OC attributes that have equivalent meaning on both PL and DE branches
  • existing DE branch only attributes to retain their IDs in the range 100 - 199;
  • all OC future and existing attributes that are PL branch specific to have numeric IDs in the range 200 - 299;
  • all OC future attributes that are DE branch specific to have numeric IDs in the range 300 - 399;
  • all OC special purpose attributes to have numeric IDs in the range 900 - 999;
  • all OC attributes that have the meaning of a negated OC attribute to use the same numeric ID on the least significant 3 digits, the fourth digit be the branch designator (according to applicability) and the fifth (most significant digit) be 9; (hypothetical generic example: "available during high tide" ID 241 - PL branch (UK), "NOT available during high tide" ID 9241 - PL branch)
  • all attributes have assigned a unique ACODE (according to OKAPI).
  • all "OC only" attributes have assigned a unique OCGS number, equal to their ID. (for GPX export purposes).

Cache attributes matrix