Download Plots Database XML

Vegetation Plot Management:
A National Plots Database Demo
John Harris - NCEAS
Robert K. Peet - University of North Carolina
Funding: National Science Foundation (DBI-9906838)
Agenda:
Over-Arching Concepts
Project Overview
· Impact
· Database Design
· System Architecture
· Challenges
Use-Case Example: Wisconsin Data
Data Management Recommendations
Future Directions
The US National Plots Database
Project organized and conducted by:
Robert K. Peet, University of North Carolina
Marilyn Walker, USDA Forest Service & U. Alaska
Dennis Grossman, The Nature Conservancy / ABI
Michael Jennings, USGS-BRD & UCSB
John Harris, NCEAS
Project supported by:
National Center for Ecological Analysis & Synthesis
U.S. National Science Foundation
USGS-BRD Gap Analysis Program
ABI / The Nature Conservancy
For Plot-Related Publications:
- Reference to Accession Number in Plots
Database.
- Potential to Annotate Plots Stored in the
Plots Database.
Publication
Project Impact
Typical Vegetation Project
Analysis
Extraction
Vegetation Data Export To Analytical Tools
Including:
- ArcView
- Canoco
Web-accessible Query Mechanism.
Vegetation Database Workbench Software
to Query Either the Central Vegetation
Database or the Local Embedded Database.
Complex Nested Queries Leveraging
Logical and Boolean Statements.
Plots Database Based on a Comprehensive
Data Model which Includes Hundreds of
Commonly Collected Plot Attributes.
Archival
Databases Designed with Scalabilty in Mind.
Vegetation Community and Plant Taxonomy
Databases Based on Emerging Concept-Based
Taxonomic Data Models.
Integration
Collection
Integration of Legacy Plots Data From:
- Government Agencies
- Academic Institutions
'Concept-Based Taxonomic Normalization'
Dynamic Linking Between Plots and
Vegetation Community Assignment.
Uses Extensible Markup Language (XML)
to Automate the Import of Data From
Legacy Data Sources to the Vegetation
Databases.
Development Cycle
Preliminary
design
Build
prototype #n
interface
Design
modification
are made
Supported by 3 other NCEAS Developers
Database Design: Aug. 2000 – Jan. 2001
Interface Design: Nov. 2000 – Feb. 2001
Build
prototype #1
interface
User
evaluates
interface
Evaluation
studied by
designer
Backend Development: Jan. 2001 Interface Development: Mar. 2001 –
Backend Version: Prototype 3
Interface Version: Prototype 1
Expected Beta Release: Late Sept. – Mid Oct.
Plots Database Design
communityType
projectContributor
project
PROJECTCONTRIBUTOR_ID
PROJECT_ID(FK)
PARTY_ID(FK)
roleCode
PROJECT_ID
projectName
description
startDate
stopDate
Red Text --> Required Fields
Black Text --> Optional Fields
Green Header --> Auxiliary table
stratum
communityUsage
COMMUNITYTYPE_ID
communityName
communityDescription
CEGLCode
classificationCode
stratumCompostion
COMMUNITYUSAGE_ID
PARTY_ID(FK)
OBS_ID(FK)
COMMUNITYTYPE_ID(FK)
type[yes/no]
startDate
stopDate
classQuality
STRATUM_ID
OBS_ID(FK)
STRATUMTYPEID(FK)
stratumCover
stratumHeight
STRATUMCOMPOSITION_ID
TAXONOBSERVATION_ID
STRATUM_ID(FK)
percentCoverage
(FK)
inferenceClassIndex
plotPlace
PLOTPLACE_ID
PLOT_ ID (FK)
NAMEDPLACE_ID(FK)
stratumType
SAMPLEMETHOD_ID
sampleMethodName
sampleMethodDescription
CITATION_ID (FK)
plot
PLOT_ID
PROJECT_ID (FK)
authorCode
PARENT (FK)
origLat
origLong
azimuth
horizPosAccuracy
shape
area
dsgpolyo
subPlotInferenceArea
subPlotDispersion
areaAccuracy
elevationValue
elevationAccuracy
slopeAspect
slopeGradient
topoPosition
hydrologicRegime
soilDrainage
surfGeo
USGSquad
state
county
country
ownerConfidentiality
layoutNarrative
placementMethod
sourceCitation(FK)
sensitivity
landFormIndex
terrainShapeIndex
soilSeries
soilGreatGroup
PREVIOUSPLOTVERS (FK)
plotVersion
locationNarrative
namedPlace
NAMEDPLACE_ID
PLOT_ID(FK)
placeName
placeDesc
GAZATEERREF(FK)
graphic
GRAPHIC_ID
PLOT_ID(FK)
graphicName
graphicDescription
graphicType
graphicData
coverIndex
COVERINDEX_ID
COVERMETHOD_ID(FK)
indexCode
upperLimit
lowerLimit
indexDescription
coverMethod
COVERMETHOD_ID
CITATION_ID(FK)
coverType
CITATIONCONTRIBUTOR_ID
CITATION_ID(FK)
PARTY_ID(FK)
roleCode
PLOTCONTRIBUTOR_ID
OBS _ID (FK)
PARTY_ID(FK)
roleCode
institution
plotObservation
OBS_ID
PLOT_ID (FK)
PREVIOUSOBS (FK)
SAMPLEMETHOD_ID(FK)
COVERMETHOD_ID(FK)
authorObsCode
obsStartDate
obsEndDate
dateAccuracy
effortLevel
plotQuality
hardCopyLocation
treeStemArea
soilType
soilDepth
soilDepthRange
percentRockGravel
percentSoil
percentLitter
percentWood
percentWater
percentSand
percentSilt
percentClay
percentOrganic
percentBaseSaturation
soilPH
vegetationOrigin
landUseFormer
landUseCurrent
timeSinceFire
PREVIOUSOBSERVATIONVERS (FK)
observationVersion
STRATUMTYPE_ID
stratumName
stratumDescription
treeStem
STEM_ID
TAXONOBSERVATION_ID(FK)
stemCode
stemDiameter
stemDiameterAccuracy
stemPosition
stemHeight
stemHeightAccuracy
stemCount
notationIntersection
NOTATIONINTERSECTION_ID
OBS_ID (FK)
tableName
attributeName
tableRecord
NOTATION_ID(FK)
notation
NOTATION_ID
notationText
notationDate
PARTY_ID(FK)
notationType
taxonObservation
TAXONOBSERVATION_ID
OBS_ID(FK)
authNameId -originaltaxonname
originalAuthority
originalAuthorityRef(FK)
cumStrataCoverage
userDefined
definedValue
USERDEFINED_ID
userDefinedName
userDefinedCategory
userDefinedType
userDefinedMetadata
tableName
DEFINEDVALUE_ID
USERDEFINED_ID(FK)
value
tableRecord
citationContributor
plotContributor
citation
CITATION_ID
OBS_ID (FK)
SAMPLEMETHOD_ID
title
alternateTitle
pubDate
edition
editionDate
seriesName
issueIdentification
otherCitationDetails
page
ISBN
ISSN
vegPlotParty
PARTY_ID
salutation
givenName
surName
organizationName
positionName
hoursOfService
contactInstructions
address
ADDRESS_ID
PARTY_ID(FK)
deliveryPoint
city
administrativeArea
postalCode
country
currentFlag
CLASSINDEX_ID
TAXONOBSERVATION_ID(FK)
OBS _ID(FK)
STRATUMCOMPOSITION_ID(FK)
indexType(height,diameter,both)
className
indexCode
lowerLimit
upperLimit
meanValue
indexDescription
inferenceArea
sampleMethod
telephone
email
TELEPHONE_ID
PARTY_ID(FK)
phoneNumber
phoneType
EMAIL_ID
PARTY_ID(FK)
emailAddress
revisions
taxonInterpretation
INTERPRETATION_ID
TAXONOBSERVATION_ID(FK)
PARTY_ID(FK)
role
taxonRef_id(FK)
taxonCircumName_id(FK)
taxonName_id(FK)
interpretationDate
type
notes
REVISION_ID
tableName
tableAttribute
tableRecord
revisionDate
previousValueText
previousValueType
revisedValueTexT
previousREVISION_ID(FK)
Plots Database Design Goals
 Support the National Vegetation Classification.
 Provide a comprehensive facility to store the most
commonly collected vegetation plot data attributes.
Provide the user with a large number of user-defined
attributes to store not-so-commonly collected data.
Integrate plots with the dynamic plant taxonomy
and vegetation community data.
Design meeting September 2000, NCEAS
Project
Plot
Project: Top-level vegetation-related project
information. May include: Project contributor
information, Over-arching project description,
Date range for the project...
Plot: Environmental and conditional data that
do not change between sampling events. May
include: Location Information, Static
environmental attributes (geology, slope, etc.)...
Plant Taxonomic Observation(s):
Plant abundance/coverage
data may be stored for any or all of
the strata comprising a plot. Uniquely,
we have designed the ability for
interpretations of taxonomic elements
to be made and stored in the database
subsequent to the upload of a plot.
Notice the taxonomic element
interpretation is linked directly to the
'concept-based' plant taxonomy
database.
StratumCompostion
PlotObservation
VegCommunity
Plot Observation(s): Environmental and
conditional data that have the potential
to change between sampling events. May
include: Soil composition, Observation
details (dates, contributors, etc.)...
Vegetation Community: Vegetation
community assignment. Notice the link
into the 'concept-based' vegetation
community database. Queries issued
based on a vegetation community
attribute may be used to select all the
plots interpreted as that community type.
TaxonObservation
Interpretation
6.1 Plot attributes
project
project: Stores information
about a vegetation sampling
project - for which there may
be multiple plots.
plot: Contains plot specific
identification, location, and
environmental data that are
expected to remain constant
during the observational life
of the plot.
plotPlace: Links a
plot with a named place.
graphic
plot
plotPlace
namedPlace: Stores
a series of place names,
their descriptions and a
link to a reference in an
external database.
namedPlace
plotObservation: Environmental
and conditional data that have
the potential to change between
sampling events are stored in this
table.
plotObservation
graphic: Stores graphical
files related to a plot.
stratumComposition: The percent
coverage of a specific taxon
within a specific stratum is stored
here.
stratum: General data
regarding the dimensions
of the various strata are
included in this table.
6.2 Plot observations
stratum
stratumCompostion
plot
stratumType: Contains
the names of various strata
recognized in the plot.
inferenceClassIndex:
Contains information about
classification schemes used
to infer plot properties.
stratumType
inferenceClassIndex
plotObservation: Environmental
and conditional data that have
the potential to change between
sampling events are stored in this
table.
plotObservation
taxonObservation
coverMethod
sampleMethod: Stores information
about the sampling methodology used
for sampling plots.
sampleMethod
stemData: Contains
information about physical
properties of plant stems
observed within a plot.
taxonObservation: Contains
data related to the species of
vegetation sampled within the
plot.
coverMethod: Links a plot
to a cover classification
type that was used while
sampling a plot.
coverIndices: Stores the
various classes used in the
different cover indices and
the quantatative/qualitative
meaning for each of the indices.
coverIndices
stemData
taxonInference:
Stores data about the
inference area for a
specific plant species
within a specific stratum.
interpretation
interpretation: Contains
interpretations made about
the taxa recognized in
various plot observations.
projectContributor
6.3 Plot contributors
plotContributor:
a party to a plot
projectContributor:
a party to a project
Links
vegPlotParty: Stores general
information about a party (an
individual or organization) who
had a role in the business of
plot collection
Links
plotContributor
citationContributor:
a party to a citation
Links
vegPlotParty
citationContributor
address
plotContributor:
of the party
Address
telephone
email
telephone: Phone
number(s) of the party
email: Email
address of the party
6.4 Plot classification
communityType: Stores names
of communities and links to other
community oriented databases
such as HDMS
communityUsage: Links a community
name to a plot observation as applied
by a particular party.
communityType
communityUsage
plotObservation
6.5 Supporting functions
notationIntersection: Links a
specific database element to a
note.
notationIntersection
notation
userDefined: Links
user defined fields with
a database element.
definedValue: Stores
user defined values
userDefined
definedValue
revisions
notation: Store a note
that is linked to a database
element.
revisions: Stores
changes made in
the database
Taxonomy Module
•Smithsonian meeting:
Peet-Taswell model vs Berendsohn model
•FGDC Biological Nomenclature Working Group
•Update on ABI & HDMS
•Prospects for implementation
•The difficult choice
Taxonomy Database Design Goals
Logical separation of a "taxonomic name" with the
"taxonomic concept", so that taxonomic data
can be stored at the most 'atomic' level without ambiguity
 The ability to incorporate multiple organizations' 'views'
of how a taxonomic name is applied to a taxonomic concept
 The ability to link a taxonomic name used in the Plots
database with a 'name - concept' pair in the taxonomic
database.
*Although one can store vegetation community data in the same database table-structure as the plant
taxonomy database, we have implemented two separate table structures and have created two separate data sets.
Taxon Usage
Taxon Usage:
The usage of a taxon is an
application of a 'Taxon Name'
with a 'Taxon Concept'. This
usage may vary depending on the
organization populating the database
Taxon Lineage:
The lineage entity
stores information
related to how
concepts 'lump'
or 'split'.
Taxon Lineage
Taxon Concept:
The concept is the over-arching 'definition'
of what the taxon element is. In the
database, a key associated with each
unique concept is stored in this entity.
Taxon Concept
Taxon Correlation:
The correlation entity
stores information
related to how
concepts 'overlap'.
Taxon Correlation
Taxon Name
Taxon Citation
Taxon Name:
The name used to
describe a taxonomic
element.
Taxon Citation:
A reference to literature describing
a specific taxonomic element.
Central Vegetation Database System
Web server
HTTP
XML +
stylesheets
web
client
J
a
v
a
Data Access Module
Community
Access
S
e
r
v
le
t
HTTP
PlotsAccess
Central Vegetation Database
J
D
B
C
Plots
Plant
Taxonomy
PlantAccess
XML/HTML
Embedded Vegetation Database System
Data Access Module
Community Access
XML
desk
top
client
PlotsAccess
PlantAccess
Central Vegetation Database(s)
J
D
B
C
National
Plots DB
plant
taxonomy
veg
community
Vegetation
Community
Development Choices
Representative tools reflect the desire
to have the following features:
High performance
Robust
Open architecture
Platform neutral
Scaleable
Features - JAVA
Java -- Write once, Cross platform – Linux,
Windows, MacOS*
Java Servlet -- Dynamic, database-driven,
web content
JDBC -- Connect to any database - Oracle,
PostgreSql, SQL Server backend
Swing -- Classy interface tools
Beans -- Reusable components
* Not tested yet :-)
Features - XML
XML: is the format for structured data on the Web.
Simple and flexible data conversions, using XSLT
Straightforward to write generic tools which export parts of a
relational database as XML encoded data, or even to write
generic code that serializes Java (or other) objects as XML
data structures.
Examples later…
An Example Workflow Using Wisconsin Plots Data
What data integration means to us
Taxonomic / Semantic Integration
Data formatting for database ingestion
General Comments about Current Format
Data Parsing
Transformation to XML standard
Legacy Data Loader
Plots Data Integration & DB Ingestion
Reformat by Hand
Research
MS Access
MS Excel
Perl
Shell scripts
?
Plots
DB
Integration
What is meant by data integration? …
Taxonomic Integration
Carya carolinae-sept.
(Ashe) Engler & Graebner
Carya ovata
(Miller)K. Koch
Carya ovata
sec. Gleason 1952
(Miller)K. Koch
sec. Radford et al. 1968
Splitting one species into two illustrates the ambiguity often
associated with scientific names. If you encounter the name
“Carya ovata (Miller) K. Koch” in a database, you cannot
be sure which of two meanings applies.
Integration
Semantic Integration of Plot Attributes
‘Basic yet Important’
Cover Scales
Strata Dimensions
Environmental Attributes
Integration
Parse Data from Forms into Table Structure to be Transformed into
XML Consistent with the Database Structure
Text
Forms
Columnar
Tables
Integration
XML
Parsed Data
Text
Forms
Columnar
Tables
plotCode
Hemlock1
Oak1
Oak2
communityName
state placeName
Hemlock Draw [Hemlock-Yellow birch]
WI
Hemlock Draw Nature Preserve
Southern Dry Mesic Red Oak-White Oak-Sugar Maple WI
ForestHemlock Draw Nature Preserve
Southern Dry Mesic Red Oak-White Oak-Sugar Maple WI
ForestHemlock Draw Nature Preserve
plotCode
Hemlock1
Oak1
Oak2
Integration
quadCode
Black Haw k
Black Haw k
Black Haw k
communityName
state placeName
Hemlock Draw [Hemlock-Yellow
WI
Hemlock
birch]
Draw Nature Preserve
Southern Dry Mesic Red
WI Oak-White
HemlockOak-Sugar
Draw Nature
Maple
Preserve
Forest
Southern Dry Mesic Red
WI Oak-White
HemlockOak-Sugar
Draw Nature
Maple
Preserve
Forest
Xcoord
?
?
?
quadCode
Black Haw k
Black Haw k
Black Haw k
Xcoord
?
?
?
Ycoord CoordType obsDate
?
UTM
9-Jul-01
?
UTM
9-Jul-01
?
UTM
9-Jul-01
Ycoord CoordType obsDate
?
UTM
9-Jul-01
?
UTM
9-Jul-01
?
UTM
9-Jul-01
contributorscontributorsInst
plotShape plotSize (m^2)PlotRepresentativeness
Shannon Menard,
ABI Eric Epstein,
squareElizabeth Spencer
100 Disjunct, small patch forest
Shannon Menard,
ABI Eric Epstein,
squareElizabeth Spencer,
100 Paul
Matrix
West,
forest
Jimtype
Welsh,
in the
Emmet
Bar
Shannon Menard,
ABI Eric Epstein,
squareElizabeth Spencer,
100 Paul
Matrix
West,
forest
Jimtype
Welsh,
in the
Emmet
Bar
contributorscontributorsInst
plotShape plotSize (m^2)PlotRepresentativeness
Shannon Menard,
ABI Eric Epstein,
squareElizabeth Spencer
100 Disjunct, small patch forest type along draw s w ithin the Bara
Shannon Menard,
ABI Eric Epstein,
squareElizabeth Spencer,
100 Paul
Matrix
West,
forest
Jimtype
Welsh,
in the
Emmet
Baraboo
Judziew
Hillsicz,
region
John
ofWagner
WI
Shannon Menard,
ABI Eric Epstein,
squareElizabeth Spencer,
100 Paul
Matrix
West,
forest
Jimtype
Welsh,
in the
Emmet
Baraboo
Judziew
Hillsicz,
region
John
ofWagner
WI
Transform Parsed Data to XML Consistent with the Plots Database
Columnar
Tables
Legacy
Data
Loader
Data Definition (XML)
Integration
Plots DB
XML
Data Definition (XML) – Single file
<plotDataPackage>
<plotDataFile>
<fileName>siteData.csv</fileName>
<attributeDelimeter>’,’</attributeDelimeter>
<fileTheme> site data </fileTheme>
<attribute>
plotCode
Hemlock1
Oak1
Oak2
communityName
Hemlock Draw [Hemlock-Yellow birch]
Southern Dry Mesic Red Oak-White Oak-Sugar Maple Forest
Southern Dry Mesic Red Oak-White Oak-Sugar Maple Forest
state
WI
WI
WI
<attributeName>plotCode</attributeName>
<plotDBAttribute>authorPlotCode</plotDBAttribute>
<attributePosition>1</attributePosition>
</attribute>
<attribute>
<attributeName>communityName</attributeName>
<plotDBAttribute>communityName</plotDBAttribute>
<attributePosition>2</attributePosition>
</attribute>
… <state>
</plotDataFile>
Integration
</plotDataPackage>
Data Definition (XML) – Multiple files
<plotDataFile>
<fileName>vegData.csv</fileName>
<constraint>
<fileName>siteData.csv</fileName>
<themeName> site data </themeName>
plotCode
Hemlock1
Oak1
Oak2
communityName
Hemlock Draw [Hemlock-Yellow birch]
Southern Dry Mesic Red Oak-White Oak-Sugar Maple Forest
Southern Dry Mesic Red Oak-White Oak-Sugar Maple Forest
state
WI
WI
WI
<attributeName>authorPlotCode</attributeName>
<cardnality>'+'</cardnality>
</constraint>
<attributeDelimeter>‘,’</attributeDelimeter>
<fileTheme>species</fileTheme>
plotCode taxonName
strataName
Oak1
Quercus rubra
T2
Oak1
Anenome quinquefolia H
strataCover
5
1
<attribute>
<attributeName>plotName</attributeName>
<plotDBAttribute>authorPlotCode</plotDBAttribute>
<attributePosition>1</attributePosition>
</attribute>
<attribute>
<attributeName>scientificName</attributeName>
<plotDBAttribute>taxonName</plotDBAttribute>
<attributePosition>2</attributePosition>
</attribute>
Integration
Plots Database XML
<plot>
<authorPlotCode> </authorPlotCode>
<plotType> </plotType>
<samplingMethod> </samplingMethod>
<plotOriginLat> </plotOriginLat>
<plotOriginLong> </plotOriginLong>
<plotShape> </plotShape>
<plotSize> </plotSize>
<plotSizeAcc> </plotSizeAcc>
<altValue> </altValue>
<altPosAcc> </altPosAcc>
<slopeAspect> </slopeAspect>
<slopeGradient> </slopeGradient>
<slopePosition> </slopePosition>
<hydrologicRegime> </hydrologicRegime>
<soilDrainage> </soilDrainage>
<surfGeo> </surfGeo>
<plotObservation>
<previousPlot> </previousPlot>
<plotStartDate> </plotStartDate>
<plotStopDate> </plotStopDate>
<dateAccuracy> </dateAccuracy>
<effortLevel> </effortLevel>
Integration
<strata>
<stratumCover> </stratumCover>
<stratumHeight> </stratumHeight>
</strata>
<taxonObservations>
<authNameId> </authNameId>
<originalAuthority> </originalAuthority>
<strataComposition>
<strataType> </strataType>
<percentCover> </percentCover>
</strataComposition>
</taxonObservations>
<communityType>
<classAssociation> </classAssociation>
<classQuality> </classQuality>
<startDate> </startDate>
<stopDate> </stopDate>
</communityType>
</plotObservation>
<plotContributor>
<role> </role>
<party> </party>
</plotContributor>
</plot>
Existing Prototype Functionality
Vegetation Database Client
Vegetation Desktop Database Client
Extra slides to follow:
PARTY
PARTY_ID
ORG_NAME
STATUS
CORRELATION
STATUS_CIRCUM_ID
CIRCUM_ID (FK)
PARTY_ID (FK)
STATUS
STARTDATE
STOPDATE
CORRELATION_ID DOUBLE
STATUS_CIRCUM1 (FK)
STATUS_CIRCUM2 (FK)
CONVERGENCE
CORR_START
CORR_STOP
NAME
NAME_ID
symbol
NAME
REF_ID (FK)
family
commonName
Name_author
DATE_ENTERED
REFERENCE
REF_ID
AUTHOR
DATE_ENTERED
CITATION
PAGE
speciesName
ReferenceType
NAME_USAGE
NAME_USAGE_ID.
CIRCUM_ID (FK)
NAME_ID (FK)
PARTY_ID (FK)
USAGE_START
USAGE_STOP
Acceptence
CIRCUMSCRIPTION
CIRCUM_ID
REF_ID (FK)
Notes
General Data Management Practices
general formats
weird formats
unusable formats
modeled the software after the way that people
collect plots data -- at least that is what I thought
At times tortuous path to the database in terms of
reformating
class indicies (these are rectified at the
plots loading software step)
Management Case: Example from Wisconsin
 Baraboo Hills -- Collected Yesterday
 PEL -- Legacy Data
Data Transformation of Forms
plotCode
Hemlock1
Oak1
Oak2
communityName
state placeName
Hemlock Draw [Hemlock-Yellow birch]
WI
Hemlock Draw Nature Preserve
Southern Dry Mesic Red Oak-White Oak-Sugar Maple WI
ForestHemlock Draw Nature Preserve
Southern Dry Mesic Red Oak-White Oak-Sugar Maple WI
ForestHemlock Draw Nature Preserve
plotCode
Hemlock1
Oak1
Oak2
communityName
state placeName
Hemlock Draw [Hemlock-Yellow
WI
Hemlock
birch]
Draw Nature Preserve
Southern Dry Mesic Red
WI Oak-White
HemlockOak-Sugar
Draw Nature
Maple
Preserve
Forest
Southern Dry Mesic Red
WI Oak-White
HemlockOak-Sugar
Draw Nature
Maple
Preserve
Forest
quadCode
Black Haw k
Black Haw k
Black Haw k
quadCode
Black Haw k
Black Haw k
Black Haw k
Xcoord
?
?
?
Xcoord
?
?
?
Ycoord CoordType obsDate
?
UTM
9-Jul-01
?
UTM
9-Jul-01
?
UTM
9-Jul-01
Ycoord CoordType obsDate
?
UTM
9-Jul-01
?
UTM
9-Jul-01
?
UTM
9-Jul-01
contributorscontributorsInst
plotShape plotSize (m^2)PlotRepresentativeness
Shannon Menard,
ABI Eric Epstein,
squareElizabeth Spencer
100 Disjunct, small patch forest
Shannon Menard,
ABI Eric Epstein,
squareElizabeth Spencer,
100 Paul
Matrix
West,
forest
Jimtype
Welsh,
in the
Emmet
Bar
Shannon Menard,
ABI Eric Epstein,
squareElizabeth Spencer,
100 Paul
Matrix
West,
forest
Jimtype
Welsh,
in the
Emmet
Bar
contributorscontributorsInst
plotShape plotSize (m^2)PlotRepresentativeness
Shannon Menard,
ABI Eric Epstein,
squareElizabeth Spencer
100 Disjunct, small patch forest type along draw s w ithin the Baraboo Hills region of
Shannon Menard,
ABI Eric Epstein,
squareElizabeth Spencer,
100 Paul
Matrix
West,
forest
Jimtype
Welsh,
in the
Emmet
Baraboo
Judziew
Hillsicz,
region
John
ofWagner
WI
Shannon Menard,
ABI Eric Epstein,
squareElizabeth Spencer,
100 Paul
Matrix
West,
forest
Jimtype
Welsh,
in the
Emmet
Baraboo
Judziew
Hillsicz,
region
John
ofWagner
WI
Project
Project: Top-level vegetation-related project
information. May include: Project contributor
information, Over-arching project description,
Date range for the project...
Plot
Plot: Environmental and conditional data that
do not change between sampling events. May
include: Location Information, Static
environmental attributes (geology, slope, etc.)...
Plant Taxonomic Observation(s):
Plant abundance/coverage
data may be stored for any or all of
the strata comprising a plot. Uniquely,
we have designed the ability for
interpretations of taxonomic elements
to be made and stored in the database
subsequent to the upload of a plot.
Notice the taxonomic element
interpretation is linked directly to the
'concept-based' plant taxonomy
database.
StratumCompostion
PlotObservation
VegCommunity
Plot Observation(s): Environmental and
conditional data that have the potential
to change between sampling events. May
include: Soil composition, Observation
details (dates, contributors, etc.)...
Vegetation Community: Vegetation
community assignment. Notice the link
into the 'concept-based' vegetation
community database. Queries issued
based on a vegetation community
attribute may be used to select all the
plots interpreted as that community type.
TaxonObservation
Interpretation