CCH1:
Featuring California vascular plant data from the Consortium of California Herbaria and other sources
Supplementary information for CCH search and detail pages

About the records displayed

Records are from botanical specimens. Collection dates may range from the mid-19th Century to the present. Applicable taxonomy and geographic distributions may have changed since collection. Curation of specimens varies by institution and accuracy of data varies by collector.

Specimen number

Most of the herbaria have a number fixed to each specimen. This number, sometimes called the accession number, serves as a unique identifier in the database when associated with a herbarium abbreviation. Some herbaria have such a number only for the database, and it does not appear on the sheet.

Determination; scientific name

The name under which the specimen is currently filed. Note that participating herbaria may use different names for what is the same taxon. The author of the name is not given, but may be retrieved, along with other taxonomic information, by clicking on "More information: Jepson Online Interchange".

Botanical "scientific" names ("taxon" names) of plants are governed by an internationally agreed upon Code. Forms of botanical names differ according to the classificatory rank of the taxon being named. For example, names of families and genera are single words (uninomials), such as Pinaceae, Fabaceae, Juniperus, Astragalus, and so on.

Names of taxa at species rank comprise two words (they are binomials): Pinus alba, Rosa woodsii, and so on.

Names of taxa at ranks below species comprise four elements: genus name, species epithet, indicator of rank (forma, subspecies, or variety), and infraspecific epithet: Rosa woodsii subsp. gratissima, Rosa woodsii var. gratissima, Rosa woodsii var. glabrata and so on. Note that statements such as Rosa woodsii subsp. gratissima var. glabrata, consisting of more than four elements, are not supported in CCH1. They may be thought of a botanical name as well as a statement of classification.

Collector, number, date

The collector is the person or people recorded on the label as having collected the specimen. Only the last name of the first collector is used for searching and sorting. That is, Hall and Michener will sort with H. M. Hall and a search for Michener will not turn up specimens collected by Hall and Michener. The collector name is linked to the Harvard Index of Botanists, or for a few collectors, to other sources of biographical information. The collector number is the number used by the collector to index the specimen. Collector numbers have a variety of formats. For the purposes of searching and sorting, the collector number is assumed to contain an alphanumeric prefix followed by a numeric stem followed by an alphanumeric suffix, of which only the stem is pertinent. The date is the date or date range on which the specimen was collected. It is stored in the database both as it occurs on the label, and as early and late Julian dates. The Julian dates, which are used for searches, accommodate date ranges. Searches for specific dates (e.g., June 6 1946), will also retrieve specimen data with a date range that includes the specific date (e.g., Jun 1946 or 1946). The date on the detail display is formatted as in the database. The date in the primary result set is formatted consistently: month, day, year. Jepson's collection numbers are linked to images of his field books, as are Brewer's and Bolander's Geological Survey collection numbers, and some of the numbers of C.A. Purpus and Annie Alexander.

County

The standardized California county from the label. Typos and misspellings are corrected in CCH1. Note that during the history of botanical collection in California, county boundaries have been altered several times. If the county does not appear on the label it has either been entered as "unknown" or secondarily determined by a data enterer or user.

Locality

The name of the place the specimen was collected, or a description of how to reach that place. Locality information may have a wide variety of spellings or usages for the same place may be encountered. Users should not expect to retrieve the data for all specimens collected from Yosemite National Park by searching for "Yosemite". Results will be returned only if all the words are found. Very common words are disregarded. If the search box is filled with a quoted 2 or 3 word phrase, only records containing that exact phrase will be returned.

Elevation

If you want to search within an elevation range, fill out both the Upper and the Lower field. On the detail page the elevation in feet or meters (units indicated) of the collection site. Elevation may be determined by instrument, map, or estimation. Accuracy should not be relied upon. For the primary result set, all elevations are displayed as meters.

orange color-coded flags

Orange flags indicate that the elevation of this record is higher than the highest elevation point for the county listed on the label. The discrepancy may have multiple causes. Not all specimens with this flag have an correct label county. Sometimes the county boundaries have changed or the collector made an error on the label regarding the county or the elevation data. The corrected elevation and metadata fields are stored in a separate table and overwrite those present in the data from CCH2.

Habitat

Physiographic or biological details about the collection site.

Georeferencing and Coordinates

From 2006 through 2018, georeferencing was completed using tools on the CCH website at UC/JEPS. Around 1.7 million georeferences were creating during this period through several georeferencing grants.

There is a paper on georeferencing protocol by Arthur D. Chapman and John Wieczorek (the latter the developer of Biogeomancer) at https://www.gbif.org/document/80536/biogeomancer-guide-to-best-practices-in-georeferencing.

The procedures and protocols for georeferencing are archived at the California Botanical Garden (RSA) georeferenecing website .

Here is a brief account of how longitude and latitude coordinates for California localities have been georeferenced in CCH1:

  1. Coordinates from the collection label

    Less than 10% of specimens in CCH1 have latitude and longitude coordinates included on the specimen label. For the majority of these specimens, the geodetic datum, georeference source and coordinate uncertainty is not known. The georeference is assumed to be by the collector, but that is rarely ever entered into the georeferencedBy field. Some of these label coordinates require revision by specialists because errors on the label are frequent. These errors and derive from a variety of sources inlcuding misreading maps, mistyping figures, missetting GPS units, and computer operation errors. Additionally, labels are often not typed by the collector, but are transcribed from a fieldbook or other medium by someone who may or may not be familiar with the collection region. The label transcriber sometimes adds coordinates.

  2. Coordinates from field notebooks.

    If coordinates on the specimen label are absent, sometimes the localities are evaluated using archival material at the herbaria, including the collector's field notebooks, itineraries, historical maps, etc.

  3. Township Range and Section Coordinates (TRS)

    Often, if a coordinate is included on a specimen label, it is in the TRS format. Prior to 2012, TRS coordinates were converted in CCH1 from the label data using the program TRS2LL. If no section is given, a section in the middle is assigned. Coordinates assigned this way can be off by several miles (or much more if the original TRS numbers are not accurately entered). Over the years, TRS coordinates were found to be troublesome due two severa factors:

    • it is easy to transcribe an inaccurate TRS from a map, since it is easy to confuse E from W or N from S when assigning a township or range.
    • It is also easy to reverse numbers when transcribing from a map to a label.
    • It is east to convert to the wrong coordinate if the baseline meridian is not specified on the label.

    Since In California, there are three baseline meridians: Humboldt, Mount Diablo, and San Bernardino. An accurate conversion of TRS coordinates requires knowledge of the baseline for the region of the label locality. Since this is missing on most labels, the wrong meridian is too-often assigned by the georeference volunteer when converting to latitude longitude coordinates.

  4. Assigned by staff or volunteers using Biogeomancer.

    The Biogeomancer program was used to calculate coordinates prior to 2012. It is now deprecated and no longer functional. Biogeomancer-supplied coordinates do not generally contain uncertainty estimates because the program was not in-development long enough to enable that capability. Most of the time, this application was used to supply coordinates for localities that are represented as one place -- Coalinga, Peanut, Yreka.

  5. Assigned by staff or volunteers using GEOLocate

    This is a Tulane University application with aerial imagery, place name search feature, measure tool, error radius calculation, and copy/paste-able lat/longs. Like Biogeomancer, GEOLocate can automatically parse an English locality description and assign latitude and longitude. Projects using GEOLocate often use it to calculate corrdinated for specimens with distance-based localities. The locality, 4 miles W of Coalinga, is georeferenced as 4 air miles due west of Coalinga, whereas the location is probably 4 road miles along a road trending northwest or southwest rather than due west. The location of a linear features like streams are georeferenced as as the mouth of the stream, which causes additional mapping-related problems.

  6. Assigned by staff or volunteers using Terrain Navigator

    The Terrain Navigator mapping program was used to georeference specimens for the NSF grants between 2012 and 2016. This system was developed by the Museum of Vertebrate Zoology at Berkeley. Staff and volunteers extracted the databased locality data into an Access file by county. Another georeferencer works on one county at a time, georeferencing using Terrain Navigator, which allows quick lookup of a databased locality. The error assigned in this process takes into account uncertainty of the reference point and other uncertainty variables.

  7. Assigned by staff or volunteers using BerkeleyMapper.

    BerkeleyMapper provides an interface for working with GoogleMaps's geocoding services, in addition to tools for finding the latitude/longitude of a point, and measuring areas and lines

  8. Cultivated specimen georeferences

    Specimens from cultivation have two localities of interest: the place where the plant was cultivated and the place in the wild from which seeds, bulbs, rhizomes, cuttings, etc. were found. Both localities are useful and interesting in different ways, but only one set of coordinates can be mapped. Past efforts attempted to display coordinates for source material over that of the in-cultivation locality. However that proved to be very difficult, since herbaria databased and georeferenced cultivated specimens inconsistently. Currently, cultivated specimens are flagged based on fields in CCH2. An additional list of known cultivated specimens is tabulated for CCH1. Most of these are not flaged as cultivated in CCH2. Both are added to the CCH1 database and used to flag cultivated records with purple map icons, whether or not the specimen is mapped to the cultivated or wild locality. No further checking is currently done to determine if a cultivated specimen is mapped as the wild or cultivated locality. CCH1 currently does not add coordinates to cultivated specimens without a georeference.

TRS

Township, Range, Section are frequently indicated on labels. Since is easy to mistranscribe TRS from a map and easy to miscopy the combination of numbers and letters, TRS coordinates are not always correct on labels or in databases.

Georeference source

Herbaria participating in the Consortium use a variety of protocols for evaluating locality descriptions and obtaining coordinates. If the source is blank or listed as "Not recorded", it could have come from a label or it could have been derived secondarily. If the coordinates are obtained by georeferencing using the Terrain Navigator, Biogeomancer, GEOLocate, BerkeleyMapper, or TRS2LL programs, then this is indicated.

Georeference coordinate uncertainty

Herbaria participating in the Consortium use a variety of protocols for estimating the uncertainty of georeferenced coordinates.

  • Coordinates from the collection label or field notebooks

    Less than 10% of specimens in CCH1 have latitude and longitude coordinates included on the specimen label. For the majority of these specimens, coordinate uncertainty is not specified on the label and therefore null in the database. Coordinates on labels obtained from GPS units may be assumed to be accurate to within 25 to 100 meters. That value if often added to the uncertainty field by CCH1 georeference staff working to verify the accuracy of coordinates

  • Township Range and Section Coordinates (TRS)

    Most coordinated derived by the program TRS2LL have no uncertainty estimates. Coordinates derived from Township Ranges with sections can reasonably assumed to have an uncertainty radius between 0.5 and 1 miles

  • Assigned by staff or volunteers using GEOLocate or Biogeomancer

    These two programs provide an estimate of an uncertainty based on a mathematical algorithm.

  • Assigned by staff or volunteers using BerkeleyMapper.

    Users create an estimate of an uncertainty based the size of the error polygon drawn around the georeference. This is a user-derived estimate and not computer-generated.

  • Assigned by staff or volunteers Terrain Navigator or other USGS Digital map software

    Users create an estimate of an uncertainty based on the georeference. This is a user-derived estimate and not computer-generated.

Datum

...Read Wikipedia article

Color-coded specimen status flags

  • Dark blue color-coded flags

    This is the default color code for dots on the map. A dark blue colored dot means that the specimen falls within the geographic range of the taxon as specifed in the Jepson eFlora.

  • Light green color-coded flags

    Light green flags indicate that the geographic coordinate fields of this record are identical to those in CCH2.

  • Light blue color-coded flags

    Light blue flags indicate that the geographic coordinates of this record have been changed from those in CCH2. These records in CCH1 have coordinates that have been corrected by various CCH1 volunteers (during georeferencing grants) or staff at UC/JEPS, including Dick Moe and Jason Alexander. The coordinate and metadata fields are stored in a separate table and overwrite those present in the data from CCH2.

  • Yellow color-coded flags

    There is a discrepancy between the geographic coordinates of this record and the geographic range of the taxon as specifed in the Jepson eFlora. The discrepancy may have multiple causes. Read more ...
    The yellow flags are stored in a separate table. This feature is unique to CCH1.

  • Black color-coded flags

    The locality of this record is too vague to be mapped and has an uncertinty polygon with a radius greater than 10,000 meters. Most records with just the county or a large geographic region as locality (San Bernardino County, Sierra Nevada, Mojave Desert, Salton Sea, Imperial Valley, etc) are have too great an uncertainty black-tinted or black flagged. The reason for black-flagging a specimens is variable. Some of the black flags were created during previous CCH georeferencing grants. For those the name of the georefereencer and the reason for black-flagging is displayed in the detailed specimen record page. Records with black flags have coordinate and metadata fields nulled and left intentionally blank in CCH1, even if there is data in CCH2. This feature is unique to CCH1.

  • Red color-coded flags

    Records that have this flag on the detailed specimen label page have a problem with the quality or value of the data.

    • County red flag

      The spelling of the county has been changed from that displayed in CCH2. This can happen in four ways.

      • A typographical or formatting error in CCH2 was corrected. County names were corrected by the CCH1 loading scripts.
      • Extraneous text such as the word 'County' or 'Co.' were removed. County names were corrected by the CCH1 loading scripts.
      • An empty field or 'unknown' phrase was replaced with a suggested county. County names were corrected from user comments in the original CCH1.
      • There is a discrepancy between the georeferenced county and the herbarium label county. Specifically, the georeferenced locality is not within the same county as listed on the herbarium label. County names were corrected by GIS software.

        This discrepancy may have multiple causes. Not all specimens with this flag have an incorrect label county. For some historic specimens, the county was correct at the time of collection. However, California county boundaries have been altered several times in the past hundred and fifty years and these boundary changes may be the source of these discrepancies.

    • Date red flag

      The year value for the date is either before 1800 or greater than the current year. The discrepancy may have multiple causes, but the most common is that there is a typo in the year (i.e. 1097 instead of 1997)

    • Scientific Name red flag

      The scientific name in the determination field has been significantly changed from the determination in CCH2. When there The name can be just a error correction completed by the CCH1 loading scripts, a determination update from a comment database (usually with an author, date and comment added) or a the verbatim determination is questioned (a comment indicates that the ID likely to be incorrect, but a new determination was not specified).

  • Purple color-coded flags

    This record has been found to be cultivated specimen. Cultivated flag data has been collected over the years by staff at UC/JEPS. Some of these records are marked as cultivated in CCH2 itself, and others are only so marked in CCH1. The cultivated flags are stored in a separate table and overwrite data present in the data from CCH2 when appropriate.

  • orange color-coded flags

    Orange flags indicate that the elevation of this record is higher than the highest elevation point for the county listed on the label. The discrepancy may have multiple causes. Not all specimens with this flag have an correct label county. Sometimes the county boundaries have changed or the collector made an error on the label regarding the county or the elevation data. The corrected elevation and metadata fields are stored in a separate table and overwrite those present in the data from CCH2.

  • No Color change in headings or checkboxes

    This record has not been georeferenced in CCH1 or CCH2 and it has an unknown status with regards to its yellow flag, black flag, or purple flag status.

Voucher information

Information about a variety of other sources on the label.

Annotations and/or curatorial actions

Some of the participant databases store annotations that have been posted on the specimen sheet: reidentifications, assignments to an infraspecific rank, etc. Sometimes, in accordance with a recent taxonomic treatment, a curator transfers all specimens assigned to a species from one genus to another, without evaluating the specimens. This is what is meant by "curatorial action". Usually, but not always, the specimen is filed in accordance with the most recent annotation.

Comments

We welcome comments and corrections of the specimen data that we display here. Action on the comments will be taken by the curators of the participating herbaria. You should provide helpful explanatory information if you can. Often a discrepancy can be caused by more than one error, and investigation of an error sometimes reveals related problems.


  Copyright © 2023 Regents of the University of California — Updated September 30, 2021