Author
Listed:
- Anthony G. Vorster
(Natural Resource Ecology Laboratory, Colorado State University, Fort Collins, CO 80525, USA
Graduate Degree Program in Ecology, Colorado State University, Fort Collins, CO 80525, USA)
- Brian D. Woodward
(Natural Resource Ecology Laboratory, Colorado State University, Fort Collins, CO 80525, USA
Graduate Degree Program in Ecology, Colorado State University, Fort Collins, CO 80525, USA)
- Amanda M. West
(Natural Resource Ecology Laboratory, Colorado State University, Fort Collins, CO 80525, USA)
- Nicholas E. Young
(Natural Resource Ecology Laboratory, Colorado State University, Fort Collins, CO 80525, USA)
- Robert G. Sturtevant
(Natural Resource Ecology Laboratory, Colorado State University, Fort Collins, CO 80525, USA)
- Timothy J. Mayer
(Natural Resource Ecology Laboratory, Colorado State University, Fort Collins, CO 80525, USA)
- Rebecca K. Girma
(Natural Resource Ecology Laboratory, Colorado State University, Fort Collins, CO 80525, USA)
- Paul H. Evangelista
(Natural Resource Ecology Laboratory, Colorado State University, Fort Collins, CO 80525, USA
Graduate Degree Program in Ecology, Colorado State University, Fort Collins, CO 80525, USA)
Abstract
Non-native and invasive tamarisk ( Tamarix spp.) and Russian olive ( Elaeagnus angustifolia ) are common in riparian areas of the Colorado River Basin and are regarded as problematic by many land and water managers. Widespread location data showing current distribution of these species, especially data suitable for remote sensing analyses, are lacking. This dataset contains 3476 species occurrence and absence point records for tamarisk and Russian olive along rivers within the Colorado River Basin in Arizona, California, Colorado, Nevada, New Mexico, and Utah. Data were collected in the field in the summer of 2017 with high-resolution imagery loaded on computer tablets. This dataset includes status (live, dead, defoliated, etc.) of observed tamarisk to capture variability in tamarisk health across the basin, in part attributable to the tamarisk beetle ( Diorhabda spp.). For absence points, vegetation or land cover were recorded. These data have a range of applications including serving as a baseline for the current distribution of these species, species distribution modeling, species detection with remote sensing, and invasive species management.
Suggested Citation
Anthony G. Vorster & Brian D. Woodward & Amanda M. West & Nicholas E. Young & Robert G. Sturtevant & Timothy J. Mayer & Rebecca K. Girma & Paul H. Evangelista, 2018.
"Tamarisk and Russian Olive Occurrence and Absence Dataset Collected in Select Tributaries of the Colorado River for 2017,"
Data, MDPI, vol. 3(4), pages 1-6, October.
Handle:
RePEc:gam:jdataj:v:3:y:2018:i:4:p:42-:d:176312
Download full text from publisher
Corrections
All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:gam:jdataj:v:3:y:2018:i:4:p:42-:d:176312. See general information about how to correct material in RePEc.
If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.
We have no bibliographic references for this item. You can help adding them by using this form .
If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.
For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: MDPI Indexing Manager (email available below). General contact details of provider: https://www.mdpi.com .
Please note that corrections may take a couple of weeks to filter through
the various RePEc services.