Login | Datasets | Logout

VegBank Data Dictionary: Tables

  Search for a VegBank Table (enter a word, field name, etc.):    <<Hide search
Match any word
Match whole words only

   Search VegBank Fields Here

Show field labels | Show database names

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.
Field DB Field Name Req'd? Data Type Misc Flag List? Definition
ID NAMEDPLACE_ID no serial PK no Database generated identifier assigned to each unique named place.
Place System placeSystem no varchar (50) n/a closed 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).
Place Name placeName required varchar (100) n/a no 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.
Place Description placeDescription no text n/a no This is the description of a named place.
Place Code placeCode no varchar (15) n/a no Optional code for location identification
Owner owner no varchar (100) n/a no 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.
Reference reference_ID no Integer FK no Link to a reference that contains further information on the named place.
Accession Code accessionCode no varchar (100) n/a no 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).