This table associates a cover scale recognized by the plot data collectors with a set of coverclasses specified in the coverIndex table. This table, together with the coverIndex table, defines a coverclass method.
Code that uniquely references this record, allowing reference to this record for this version of this database. Better than a primary key, which is automatically generated by a database and not globally unique. VegBank Accession codes are only generated by VegBank, and therefore data integrity can be guaranteed, unlike with a primary key (number).
DB Table Name
definedValue
Table
Defined Value
Notes
This table stores the values of user-defined variables.
Description
This table stores values associated with specific user-defined variables identified in the userDefined table.
Text description of details of the disturbance and its impact on the vegetation.
DB Table Name
graphic
Table
Graphic
Notes
This table stores information about graphical files related to vegetation plot observations
Description
Graphical files can include, among other formats: gif, jpeg, and tif file formats. Because many graphical files, especially remote sensing digital photographs, may be too large to be stored within the database, a graphicLocation may be given as an alternative. Current Business rules cap graphic size at 5M per plot. Graphics of modest size should be included rather than referenced by external address.
Code that uniquely references this record, allowing reference to this record for this version of this database. Better than a primary key, which is automatically generated by a database and not globally unique. VegBank Accession codes are only generated by VegBank, and therefore data integrity can be guaranteed, unlike with a primary key (number).
DB Table Name
namedPlace
Table
Named Place
Notes
This tables stores information about the various 'named places' that a plot may have been located within. Such places could include geographic regions, study sites, ownership units, managed units, any placename in the USGS glossary (http://www-nmd.usgs.gov/www/gnis/), or equivalent glossary.
Name of the system of names. These can be treated as points as with place names, or as a coverage or set of polygons (e.g., geographic area names, HUC codes, Ecoregions, Quadrangles).
The name of a place in or at which a plot is located. The system "Geographic Name" is an open list defined within this table. The other systems are generally closed lists constrained by aux_tables. These include at least USGSQuad, Continent, Country, State, County, HUC, and Ecoregion.
Although somewhat redundant with the owner information contained in observationContributor with roleCode of owner, this allows the program to provide ownership information automatically. The ownership field supercedes this field in priority.
Code that uniquely references this record, allowing reference to this record for this version of this database. Better than a primary key, which is automatically generated by a database and not globally unique. VegBank Accession codes are only generated by VegBank, and therefore data integrity can be guaranteed, unlike with a primary key (number).
DB Table Name
namedPlaceCorrelation
Table
Named Place Correlation
Notes
Stores information about how different named places related to one another.
The commParent is a recursive key to the concept of the parent level in the classification hierarchy. For example, if this concept were at the association level, the parentClass would be a concept that is the parent alliance type.
The commLevel attribute specifies a level in the taxonomic hierarchy to which a class belongs. Field commLevel is an open list with the possible values defined by the classification system employed. If the party responsible for the record in the commStatus table is using the U.S. National Vegetation Classification, the acceptable levels are defined in the Vegetation Classification Standard of the Federal Geographic Data Committee as adopted June 1997. The standard is available at http://biology.usgs.gov/fgdc.veg/standards/vegstd.htm and the allowable entries for each of the physiognomic levels are listed in the appendix (see http://www.fgdc.gov/standards/documents/standards/vegetation/tables19-41.pdf). If the Braun-Blanquet classification system is employed, the acceptable values are defined in the International Code of Phytosociological Nomenclature (Weber, H.E., Moravec, J. Theurillat, J.-P. 2000. Journal of Vegetation Science. 11: 739-769).
Code that uniquely references this record, allowing reference to this record for this version of this database. Better than a primary key, which is automatically generated by a database and not globally unique. VegBank Accession codes are only generated by VegBank, and therefore data integrity can be guaranteed, unlike with a primary key (number).
Code that uniquely references this record, allowing reference to this record for this version of this database. Better than a primary key, which is automatically generated by a database and not globally unique. VegBank Accession codes are only generated by VegBank, and therefore data integrity can be guaranteed, unlike with a primary key (number).
DB Table Name
plantCorrelation
Table
Plant Correlation
Notes
This table correlates multiple plant concepts as they change through time.
This is the descriptive attribute that is used to relate the congruence between two concepts. The concept that is represented in the party perspective, via the Status_ID field is [this field, i.e. <,>,=] the concept represented in Concept_ID field. As normally used, (no Longer Valid Concept) [convergence] (Valid Concept). For example, if a concept is split, the convergence would be 'greater than' (The old concept is 'greater than' the new concept).
unhighlight
highlight