Login | Datasets | Logout
Jump to... Home PLOT search PLANT search COMMUNITY search Simple search Manage datasets Tutorial About FAQ ------- Site map VegBranch Data dictionary ERD

detaildba_tabledescriptiongraphicwhere_tablenamegraphic

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 for VegBank Table >>

Search VegBank Fields Here

Show field labels | Show database names

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.
Field DB Field Name Req'd? Data Type Misc Flag List? Definition ID GRAPHIC_ID no serial PK no Database generated identifier assigned to each unique graphic idem. Observation OBSERVATION_ID required Integer FK no Link from a graphic file to a specific plot observation. Graphic Name graphicName no varchar (30) n/a no Name of the graphic file. Graphic Location graphicLocation no text n/a no Where the graphic is located, if not in the database Graphic Description graphicDescription no text n/a no Description of the graphical file and associated metadata such as contributor, author, sensor, etc. Graphic Type graphicType no varchar (20) n/a no The type of the graphical file format (e.g. gif, tif, ,jpeg). Graphic Date graphicDate no Date n/a no Date that the graphic was produced. Graphic Data graphicData no oid n/a no The graphical file data. - Max = 5 M total per plot 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).