Submitting Data to the CNDDB
Data may be submitted to the CNDDB in a number of formats:
- Field survey forms and maps
- Digital data
- Tabular lists of coordinate data
- Other, such as herbarium collection data and reports
How data is submitted to the CNDDB will probably depend on the amount of data collected and the type of project being carried out. For example, if you have relatively few sightings or incidental observations, individual field survey forms may be the best method for submission. If systematic surveys are conducted over an entire field season resulting in large data sets stored in a database or GIS, the CNDDB would prefer electronic submission of the data in a database, spreadsheet, and/or GIS layer with the appropriate locational and biological information.
Field Survey Forms and Maps
[PDF] CNDDB Field Survey Form (153 KB)
[PDF] General Instructions for Completing CNDDB Field Survey Form (1.8 Mb)
[PDF] Instructions for Reporting Coordinates to the CNDDB (100 Kb)
Not all fields are required on the forms; however, we do need a map, preferably at the 1:24,000 scale, and/or complete coordinate information to map the data. "Complete" here means GPS data must include both the datum (NAD83, WGS84, or NAD27) and accuracy information. For a thorough discussion of datum and projection at the CNDDB see: Projection and Datum Guidelines
In addition, the more information you provide on site condition, population viability, threats, etc., the better we can assign an accurate occurrence rank to the site which helps prioritize sites for protection.
If mailing field survey forms, mail to:
1807 13th Street, Suite 202
Sacramento, CA 95811
If emailing forms, email to:
Electronic Field Form Submission
Our goal is to provide an online field survey form and mapping capability; this is under development. Currently, the PDF form we provide can be saved and emailed if you have Adobe Acrobat Reader software (a free download) installed on your computer. If you have this and wish to email the form and a map, a map (for point locations only) can be created on the BIOS site.
Digital datasets are welcomed, however, there are requirements.
- Spatial information for each observation or location can be provided either as a shapefile, or as tabular geospatial coordinates in an Excel or standard DBF file. Data may be in either geographic (latitude/longitude) or projected format. Universal Transverse Mercator UTM with Zone; State Plane with Zone, or Albers are some examples of projected data. Also include the units in which the data were collected (meters, feet). With this information, we will convert the data to the State standard projection and datum: Teale Albers, NAD83. You may submit the data in any format; however, you must note the projection and datum with your submission.
- Attributes must accompany the spatial information. The minimum attributes consist of:
- species name
- unique, key field that links the spatial feature (point, polygon) to the corresponding attribute record
- observer name and date of observation. We prefer, however, to receive more complete attribute data such as the fields seen on the field survey form (e.g. habitat, land use, threats, occurrence condition and rank, etc.).
Tabular Lists of Coordinate data
We will map these but prefer to also receive attribute data on each site beyond just the location. Tabular data must at a minimum include name of species observed, observer name, date of fieldwork and Datum used. In order to minimize transcription errors it is best to send us lists of coordinates in digital format such as Excel or dBase IV in addition to the paper copy. Otherwise we have to type or scan them in, both of which can result in typos and lengthen the time to process the data.
Herbarium or Museum Data
We welcome lists of collection data from museums and herbaria. Museum data frequently make up the bulk of new rare species' datasets; later, these data are refined by fieldworkers. These data may be submitted in almost any way convenient to the institution. Often it is available on the Internet and we access it ourselves; other times it is sent as output from a local database.
Reports are gleaned for occurrence information on special status taxa. However, this work is time-consuming and occasionally less rewarding than we would like. To help us process reports efficiently, we request report preparers use CNDDB Occurrence Numbers as seen in all RareFind output. In general, referencing CNDDB Occurrence Numbers is a helpful practice for field survey forms and any other format where the reporter is submitting data on known sites.
For Revisits; using annotated printouts
For simple text-only updates (i.e. the mapped location at the CNDDB does not need updating), you can annotate a copy of a RareFind full report and submit that, or simply send the information in an email, complete with species name and occurrence number, to the CNDDB. This can save the time to complete an entire new field survey form. You can also annotate copies of your own previously completed field survey forms and send those in if you prefer.