This table contains the author's determination of a taxon and the overall cover of that taxon.
Description
This table stores information about the original identification by the author of the plot and the taxonomic authority used by that author (i.e. a name - citation pair constituting a taxonomic concept). The table also contains a record of cumulative cover (cover across all strata) of the taxon when not divided into strata.
The authority for the taxon that was used by the plot author. If the authority is unknown the author of the plot is the authority. For other than legacy data, this field plus plantName_ID will be sufficient to determine taxonInterpretation.plantConcept_ID.
This is the area in m2 used to infer the presence of a given taxon. Generally this should be equal to observation.taxonInferenceArea, but at times this area may be larger or smaller for a specific taxon. RESERVED VALUE: -1 is used to indicate that no known plot boundaries were used when recording this species on the plot. That is, this species may occur outside the plot area as indicated in the plot and observation tables.
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
taxonAlt
Table
Taxon Alt
Notes
This table shows alternate taxa that are to be grouped for a taxonInterpretation.
Description
When this table is used, the taxonInterpretation that is referenced here is interpreting the taxonObservation as the combination of all plantConcepts referenced in this table with the same taxonInterpretation_ID. TaxonInterpretation.groupType shows what type of group this is (one of, union, unknown).
Links to the taxonInterpretation for which several plantConcepts are grouped to form an irregular taxon. The plantConcept referenced here is one member of the group.
Indicates the degree of fit with the plant concept being assigned. Values derive from Gopal, S., and Woodcock, C. (1994), Theory and methods for accuracy assessment of thematic maps using fuzzy sets. Photogrammetric Engineering and Remote Sensing 60(2):181-188.
Indicates the degree of confidence of the interpreter(s) in the interpretation made. This can reflect the level of familiarity with the classification or the sufficiency of information about the plot (e.g., High, Moderate, Low).
This is the type of telephone: home, work, fax, cell, secretary, other.
DB Table Name
userDefined
Table
User Defined
Notes
This table contains the definitions of user-defined variables. The table structure stems from desire to keep the user-defined variables separate from the main body of the database.
Description
This table contains the definitions of user-defined variables. The table structure stems from desire to keep the user-defined variables separate from the main body of the database.
Name of table with which this user-defined variable is associated. For example soilBHorizonColor may be defined by the data contributor as associated with the observation table.
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).
This table stores observation on soil horizons made during the plot observation event.
Description
soilObs is child of observation in recognition of the fact that the horizons observed vary among plot observation events as a results of real change plus changes in investigators, methods and circumstances.
Parent soil taxon in the soil taxon hierarchy for this particular framwork. For example, in USDA soils list, the parent of a soil SubGroup would be the GreatGroup.
System in which this soil taxon is part. This field may be used to separate multiple soil taxonomic systems. Each unique soil taxonomic system should have all its soilTaxon records with the same soilFramework value. Correlation of different framework taxa is not currently possible.
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
stemCount
Table
Stem Count
Notes
This table is intended to store information about the abundance of tree stems of a specific size.
The diameter of the stem in centimeters. When diameter classes are used, the stemDiameter is the midpoint between the low end and high end for the diameter class; the offset between this and the endpoints is stored in the stemDiameterAccuracy attribute.
The measured height of the stem in meters. When height classes are used, the stemHeight is the midpoint between the low end and high end for the height class; the offset between this and the endpoint is stored in the stemHeightAccuracy field.
This is the area in m2 used to infer the presence of the stem(s) referenced in this record. Overrides similar area field in taxonObservation, taxonImportance, and/or observation. RESERVED VALUE: -1 is used to indicate no known boundaries were used while collecting this stem size.
DB Table Name
stemLocation
Table
Stem Location
Notes
This table is intended to store location information about individual tree stems.
The X-coordinate of the stem position in m. The user will enter the relative position of stems with respect to the plot origin (in meters) with the x-axis defined by the plot azimuth.