These data were converted from the originally delivered Microsoft Access PLOTs database from the Vegetation Mapping Inventory Project of John Day Fossil Beds National Monument. These comma-delimited data tables contain(s) vegetation mapping plot classification and accuracy assessment data, as well as summary information about the data itself. If a table is empty, then it was empty in the original database.

These data were converted from the originally delivered Microsoft Access PLOTs database from the Vegetation Mapping Inventory Project of Agate Fossil Beds National Monument. These comma-delimited data tables contain(s) vegetation mapping plot classification and accuracy assessment data, as well as summary information about the data itself. If a table is empty, then it was empty in the original database.

These data were converted from the originally delivered Microsoft Access PLOTs database from the Vegetation Mapping Inventory Project of Agate Fossil Beds National Monument. These comma-delimited data tables contain(s) vegetation mapping plot classification and accuracy assessment data, as well as summary information about the data itself. If a table is empty, then it was empty in the original database.

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. Mapping and interpretation of JODA involved a five step process including: (1) field reconnaissance, (2) map class development, (3) image processing and interpretation, (4) draft map validation, and (5) spatial database development. Field reconnaissance was initiated by CTI and NMI staff in 2008 to quickly familiarize the mappers with the vegetation patterns and distribution at JODA. As the classification plot data were acquired later in 2008, feedback on the dominant and characteristic plant species was solicited from ORNHIC ecologists. boundary placement and labeling. Field notes were made directly on vegetation map copies and an additional 70 observation points were sampled to support the notations. Confusing sites were visited including the Picture Gorge area where shadows on the NAIP imagery prevented viewing the distribution of vegetation types. Ground data and ground photographs were collected to insure consistent mapping of confusing sites. Upon return to the office, minor updates of the draft vegetation map were completed prior to the AA task.

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. Mapping and interpretation of JODA involved a five step process including: (1) field reconnaissance, (2) map class development, (3) image processing and interpretation, (4) draft map validation, and (5) spatial database development. Field reconnaissance was initiated by CTI and NMI staff in 2008 to quickly familiarize the mappers with the vegetation patterns and distribution at JODA. As the classification plot data were acquired later in 2008, feedback on the dominant and characteristic plant species was solicited from ORNHIC ecologists. boundary placement and labeling. Field notes were made directly on vegetation map copies and an additional 70 observation points were sampled to support the notations. Confusing sites were visited including the Picture Gorge area where shadows on the NAIP imagery prevented viewing the distribution of vegetation types. Ground data and ground photographs were collected to insure consistent mapping of confusing sites. Upon return to the office, minor updates of the draft vegetation map were completed prior to the AA task.

This reference contains the imagery data used in the completion of the baseline vegetation inventory project for the NPS park unit. Orthophotos, raw imagery, and scanned aerial photos are common files held here. Since JODA represented a small site, existing sources of imagery were evaluated and the National Aerial Imagery Program (NAIP) products were found to be adequate. Based on the currentness of the 2009 product, this true-color, 1-meter pixel was accepted as the base imagery. The 2005 true-color, 1-meter pixel product was also used as ancillary data.

This reference contains the imagery data used in the completion of the baseline vegetation inventory project for the NPS park unit. Orthophotos, raw imagery, and scanned aerial photos are common files held here. Since JODA represented a small site, existing sources of imagery were evaluated and the National Aerial Imagery Program (NAIP) products were found to be adequate. Based on the currentness of the 2009 product, this true-color, 1-meter pixel was accepted as the base imagery. The 2005 true-color, 1-meter pixel product was also used as ancillary data.

These data were converted from the originally delivered Microsoft Access PLOTs database from the Vegetation Mapping Inventory Project of Fossil Butte National Monument. These comma-delimited data tables contain(s) vegetation mapping plot classification and accuracy assessment data, as well as summary information about the data itself. If a table is empty, then it was empty in the original database.

These data were converted from the originally delivered Microsoft Access PLOTs database from the Vegetation Mapping Inventory Project of Hagerman Fossil Beds National Monument. These comma-delimited data tables contain(s) vegetation mapping plot classification and accuracy assessment data, as well as summary information about the data itself. If a table is empty, then it was empty in the original database.

These data were converted from the originally delivered Microsoft Access PLOTs database from the Vegetation Mapping Inventory Project of Hagerman Fossil Beds National Monument. These comma-delimited data tables contain(s) vegetation mapping plot classification and accuracy assessment data, as well as summary information about the data itself. If a table is empty, then it was empty in the original database.