VegBank is the public repository for vegetation plot data, maintained by the Ecological Society of America's Vegetation Classification Panel. These data support the development of the U.S. National Vegetation Classification and general ecological research across North America.
These data are also available for access with R via the vegbankr R package, and in other languages via the VegBank REST API. To upload data, request contributor permissions from the ESA Vegetation Classification Panel. Once your contributor role is granted, you will be able to upload new plot data with the vegbankr R package.
Browse the FAQ page and other info in the About dropdown for additional documentation. Please report any bugs here with details about what you were doing when the problem occurred.
When you open the app you’ll land on the Home page. Here’s an overview of what you can do on different pages:
Sibbaldiopsis tridentata, CEGL001833, Eleocharis palustris Marsh, BADL.126, ob.ob.3736, or California)Here are some of the basic functions available in the app:
"Quercus alba" ).oak prairie ).-alliance).Frequently Asked Questions about the VegBank database and website.
Please select from the following questions, or browse through this file:
What is VegBank?
Who runs VegBank?
What is a plot?
What is a community?
What is a plant concept? What is a community concept?
Where does VegBank get its plots and other data?
What is your standard list of species/communities?
How do I find plots in VegBank?
How do I download VegBank data to my computer?
What features does VegBank offer for analysis of plot data?
What is metadata?
How do I cite VegBank?
What is a VegBank Code?
How is VegBank financed? How can I help VegBank operate financially? How can I get help with VegBank? Is there a tutorial?
What if I find something not working in VegBank?
VegBank is the vegetation plot database of the Ecological Society of America’s Panel on Vegetation Classification. VegBank stores data about vegetation plots and necessary supplemental data, such as a plant taxon database and community type database. VegBank’s purpose is to allow plant ecologists to submit and share data to allow permanent documentation of plot data, which will provide a permanent record of plots which define communities.
VegBank is operated by the National Center for Ecological Analysis and Synthesis in cooperation with the Ecological Society of America’s Vegetation Panel.
The purpose of plots is to record the vegetation and its environmental context. A plot may be contained by a single bounded area, such as a 50m x 20m rectangle. It could also consist of smaller subplots which sample vegetation over a large range. While we encourage plots to have boundaries and definite size, VegBank also accepts relevés that have no bounds as valid plots. An observation is a one-time record of vegetation present in a plot. So multiple observations of a plot could be made at different times, producing different values for both vegetation (i.e., which taxa are present, and their abundance if recorded) and environmental variables (e.g., soil characteristics).
In overly simple terms, a community is a set of plant taxa that live adjacent to one another within a set of physical conditions. This community of co-occurring plants may be seen to repeat itself in a predictable pattern. One may classify (or interpret) a plot as belonging to a certain community type.
The USNVC Guide to the Classification provides more full definitions for the 8 levels of the Natural Vegetation Heirarchy from Biome down to Association.
Communities are Concept-Based in VegBank, meaning they are defined by a combination of a name and a reference. See the What is a Concept? FAQ Topic for more information on Concepts.
Generally, people use only a plant name to refer to a particular plant taxon. However, names may mean different things to different people or at different times. When users view a plant in VegBank, they need to know what is meant by a plant name, hence only a name is not enough. A reference, or context, must be provided which gives the name meaning and defines what the taxon encompasses. When we mention a “plant concept” in VegBank, we mean this unique combination of name and reference. For example, one might mention “Carya ovata” according to (reference) “Radford, 1968.” Each plant concept and community concept in VegBank has a VegBank Code which provides unique identification for the plant concept.
Community Concepts function in exactly the same way, except that Community Concepts describe a community type, not a plant taxon.
Plots in VegBank come from the users who decide to contribute their plots. VegBank does not fund plot collection, but is a means for those who do collect plots to share their data. There are two major implications of this:
- We do not guarantee the accurateness of the data in VegBank. Users are allowed to annotate (make notes and reinterpret plants and plots) to share with other users their opinions about the data already in VegBank. [Some of the annotation features are still in development.]
- We need users to share their data. There are many different reasons users share their data. Some are required to share their data by their grants, but don’t want to deal with the hassle of setting up computer servers and software to manage this. Some use VegBank as a means of collaborating with others in data analysis. Others have finished analysis and are eager to find a use for their hard work other than being filed away to collect dust. Still others see the foresight in adding their data to the greater body of knowledge on a public site like VegBank.
Other data, like plants and communities, come from VegBank’s users, but rely heavily on VegBank users like the organizations USDA Plants and NatureServe to provide this data.
VegBank does not have a standard list of taxa or communities. In VegBank, plants and communities have a Party Perspective which defines whether a plant or community is standard or not and what names may be used to describe it. VegBank has no Party Perspective of its own. However, USDA PLANTS 2002 data and NatureServe communities were initially loaded into the database and users are strongly encouraged to map any new plants or communities onto USDA’s or NatureServe’s standards. This allows other users, who may know nothing of your own views, to view information according to the USDA or NatureServe standards.
You can search for plots on the plot tab:
In the top right of the plot table is a very simple search box, where you can specify one or more of the following: plant found on the plot, community to which the plot is interpreted, state/province in which the plot is located, the code assigned by the author to the plot.
A more complex query is in the works…
Data can be downloaded from the vegbankr R package, which underpins this website and serves as an interface to the VegBank API.
VegBank does not have analysis tools. Other groups have done a good job making tools for analysis, and we encourage users to find data in VegBank, then export into a format of your choice, then work on analysis with a program like PC-Ord.
Metadata is plot data that defines not what was measured, but how it was measured. Cover Method and Stratum Method are examples of metadata. Plot size and stem sampling method might also be considered metadata. These data are often considered secondary in importance, but are essential when many different techniques are used to collect plots, as is the case with VegBank data.
You may cite VegBank, as a whole or one or more elements, with the instructions on the Cite page in the About menu. That page also shows how to cite a description of VegBank.
A VegBank Code is a unique combination of letters, numbers, and a period which uniquely identify something in VegBank. VegBank Codes are used to identify plots and observations, as well as methods, plant taxa, and community types. This allows communication about these elements to take place so that each party knows that they are mentioning the same thing. VegBank Codes are important when vegbankr and VegBank communicate, because this helps the two align the different types of data, rather than repeating redundant information.
For those who want to know how a VegBank Code works (this is not necessary!), it is broken into two parts, each divided by a period (.). An example VB Code is that of Quercus alba, with reference of USDA 2002 : pc.48413. The first part is the table identifier (i.e. pc for plant concepts), then the record number (i.e., 48413).
We are currently funded by the California Department of Fish and Wildlife (CDFW). We gratefully acknowledge the financial support of CDFW.
Eventually, we’d like to have a feature that allows you to donate to our efforts. Until then, if you have a funding source for VegBank, please contact us at help@vegbank.org. We’d be more than happy to hear about it.
Not yet. We’re working on an instructions page to help with this.
You should tell us about what wasn’t working. Just send an email to help@vegbank.org and explain what it is that isn’t working. Please be as specific as possible, i.e. what the URL was when the error occurred, what the search criteria were if you were searching for something, the time and date the error occurred, etc. Users who report errors help us improve the VegBank experience for everyone. Thank you!
One of VegBank’s strengths is that its data is permanently archived. This means that you can cite a plot in VegBank and others will be able to follow your citation hyperlink to see the same data you saw at the time of citation.
To cite a description of VegBank, please use the following citation:
Peet, R.K., M.T. Lee, M.D. Jennings, & D. Faber-Langendoen. 2012. VegBank - a permanent, open-access archive for vegetation-plot data. Biodiversity and Ecology 4: 233-241.
To cite the VegBank database as a whole or a single entity in the database, use the following citation:
Peet, R.K., M.T. Lee, M.D. Jennings, D. Faber-Langendoen (eds). 2013. VegBank: The vegetation plot archive of the Ecological Society of America. https://vegbank.org; searched on [Day, Month, Year].
The URL (web address) may be modified to cite a specific plot, community concept, or public dataset in VegBank. To do this, find its VegBank Code (the unique identifier for VegBank data) which can be found on the table and detail views of different entities.
Once you know the VegBank Code, use the following pattern to create a URL:
https://vegbank.org/cite/[VegBankCode]
Where [VegBankCode] is the VegBank Code of the plot or other data to cite.
| Entity | Citation URL |
|---|---|
| Plot | https://vegbank.org/cite/ob.3736 |
| Community | https://vegbank.org/cite/cc.5728 |
| Public Dataset | https://vegbank.org/cite//ds.200278 |