VegBank A vegetation field plot archive Produced at: The National Center for Ecological Analysis and Synthesis Principal Investigators: Robert K. Peet, University of North Carolina Michael D. Jennings, U.S. Geological Survey Dennis Grossman, NatureServe Marilyn D. Walker, USDA Forest Service Primary collaborators: Don Faber-Langendoen, NatureServe Michael Lee, University of North Carolina Mark Anderson, NCEAS Gabriel Farrell, NCEAS John Harris, NCEAS
VegBank A vegetation field plot archive. Produced at: The National Center for Ecological Analysis and Synthesis Principal Investigators: Robert K. Peet, University of North Carolina Michael D. Jennings, U.S. Geological Survey Dennis Grossman, NatureServe - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
VegBank A vegetation field plot archiveProduced at:
The National Center for Ecological Analysis and Synthesis
Principal Investigators:Robert K. Peet, University of North CarolinaMichael D. Jennings, U.S. Geological SurveyDennis Grossman, NatureServeMarilyn D. Walker, USDA Forest Service
Primary collaborators: Don Faber-Langendoen, NatureServeMichael Lee, University of North CarolinaMark Anderson, NCEASGabriel Farrell, NCEASJohn Harris, NCEAS
A vegetation plot archive?
Currently there is no standard plot data repository.
A repository is needed for:
• Plot storage and preservation
• Plot access and identification
• Plot documentation in literature/databases
In addition, data exchange standards are needed to support alternative data archive initiatives.
Biodiversity data structure
Taxonomic database
Plot/Inventory database
Occurrence database
Plot Observation/Collection Event
Specimen or Object
Bio-Taxon
Locality
Vegetation Type
Vegetation type database
Plot
PlotObservation
Taxon Observation
Taxon Interpretation
Plot Interpretation
Core elements
of VegBank
Taxon Assignment
Plot Assignment
Taxonomic database challenge:
Standardizing organisms and communities
The problem: Integration of data potentially
representing different times, places, investigators and taxonomic standards.
The traditional solution: A standard checklists of organisms.
Standard checklists for Taxa
Representative examples for higher plants in North America / US USDA Plants http://plants.usda.gov ITIS http://www.itis.usda.gov NatureServe http://www.natureserve.org BONAP http://www.bonap.org/ Flora North America http://hua.huh.harvard.edu/FNA/
These are intended to be checklists wherein the taxa recognized perfectly partition all plants. The lists can be dynamic.
Most taxon checklists fail to allow effective dataset integration
The reasons include:
• The user cannot reconstruct the database as viewed at an arbitrary time in the past,
• Taxonomic concepts are not defined (just lists),
• Multiple party perspectives on taxonomic concepts and names cannot be supported or reconciled.
R. plumosa
R. plumosa
R plumosav. intermedia
R. plumosav. plumosa
R. intermedia
R. plumosav. interrupta
R. pineticola
R. plumosa
R. sp. 1
R. plumosav. plumosa
R. plumosav. pineticola
Multiple concepts of Rhynchospora plumosa s.l.
Elliot 1816
Gray 1834
Kral 2003
Peet 2004?
1
2
3
Chapman1860
Name ReferenceConcept
Taxonomic theory
A taxon concept represents a unique combination of a name and a reference
“Taxon concept” roughly equivalent to “Potential taxon” & “assertion”
Name ConceptUsage
A usage represents an association of a concept with
a name.
• Usage does not appear in the IOPI model, but instead is a special case of concept
• Desirable for stability in recognized concepts when strictly nomenclatural synonyms are created.
• Usage can be used to apply multiple name systems to a concept