<!DOCTYPE METADATA PUBLIC "-//FGDC//DTD METADATA 2.0//EN">
<metadata>
 <idinfo>
  <citation>
   <citeinfo>
    <origin>PRBO Conservation Science</origin>
    <pubdate>2005</pubdate>
    <title>PRBO - All Point Counts</title>
    <geoform>vector digital data</geoform>
    <pubinfo>
     <pubplace>Petaluma, CA</pubplace>
     <publish>PRBO Conservation Science</publish>
    </pubinfo>
    <onlink>http://www.prbo.org/cadc/songbird/</onlink>
   </citeinfo>
  </citation>
  <descript>
   <abstract>
    In many countries, point counts are the main method in monitoring the population changes of breeding landbirds. With the point count method it is possible to study the yearly changes of bird populations at fixed points, differences in species composition between habitats, and abundance patterns of species. The point count method is probably the most efficient and data-rich method of counting birds. It is the preferred method in forested habitats or difficult terrain. Point counts involve an observer standing in one spot and recording all the birds seen or heard at either a fixed distance, or unlimited distance. This method can be conducted one or many times at a given point. The North American Breeding Bird Survey of the U.S.D.I. Fish and Wildlife Service is such a method.* These data come from PRBO point count locations throughout the western United States for surveys conducted by trained observers between 1991 and the present. As of 2005, there were over 10,000 point count locations (sites) in 43 projects in a variety of habitats. As new surveys are added on a yearly basis, this database is constantly being updated. All counts were 5 minutes duration and data were collected which denote, at least, whether individuals were within 50 m of the observer. All species were recorded. For more information on field protocols please see http://www.prbo.org/cadc/songbird/pc.php. 
    *Excerpted from Ralph, C J; Geupel, G R; Pyle, P; Martin, T E; DeSante, D F. 1993. Handbook of field methods for monitoring landbirds. Gen. Tech. Rep. PSW-GTR-144. Albany, CA: Pacific Southwest Research Station, Forest Service, U.S. Department of Agriculture; 41 p. (http://www.fs.fed.us/psw/publications/documents/gtr-144/06-censusing.html)
   </abstract>
   <purpose>Point count surveys measure bird abundance and diversity and can be used to measure habitat sustainability, population trends, and habitat associations in bird populations. Aside from providing the bird species and numbers detected at each point count location, this dataset is also a record of the location of point count locations so that surveys can be repeated in subsequent years.</purpose>
   <supplinf>For more information on point counts (eg, background information, methodologies, data forms, and field protocols) see http://www.prbo.org/cadc/songbird/pc.php.</supplinf>
  </descript>
  <timeperd>
   <timeinfo>
    <rngdates>
     <begdate>1991</begdate>
     <enddate>current</enddate>
    </rngdates>
   </timeinfo>
   <current>ground condition</current>
  </timeperd>
  <status>
   <progress>In work</progress>
   <update>Continually</update>
  </status>
  <spdom>
   <descgeog>PRBO point count locations throughout the western United States.</descgeog>
   <bounding>
    <westbc>-123.069489</westbc>
    <eastbc>-109.342559</eastbc>
    <northbc>48.990540</northbc>
    <southbc>32.849533</southbc>
    <boundalt>
     <altmin>0</altmin>
     <altmax>3000</altmax>
     <altunits>meters</altunits>
    </boundalt>
   </bounding>
  </spdom>
  <keywords>
   <theme>
    <themekt>CSA-NBII Biocomplexity Thesaurus (http://thesaurus.nbii.gov/SearchNBIIThesaurus/)</themekt>
    <themekey>BIRDS</themekey>
    <themekey>SONGBIRDS</themekey>
    <themekey>POPULATION DYNAMICS</themekey>
    <themekey>BIODIVERSITY</themekey>
    <themekey>BIOMONITORING</themekey>
    <themekey>BIOLOGICAL ANALYSIS</themekey>
    <themekey>GEOGRAPHICAL DISTRIBUTION</themekey>
    <themekey>COUNTING METHODS</themekey>
    <themekey>ABUNDANCE (ORGANISMS)</themekey>
   </theme>
   <place>
    <placekt>CIESIN Indexing Vocabulary (http://www.ciesin.org/metadata/documentation/vocab/introv.html)</placekt>
    <placekey>NORTH AMERICA</placekey>
    <placekey>UNITED STATES</placekey>
    <placekey>WESTERN UNITED STATES</placekey>
    <placekey>OREGON</placekey>
    <placekey>NEVADA</placekey>
    <placekey>ARIZONA</placekey>
    <placekey>WASHINGTON</placekey>
    <placekey>IDAHO</placekey>
    <placekey>CALIFORNIA</placekey>
    <placekey>WYOMING</placekey>
   </place>
  </keywords>
  <taxonomy>
   <keywtax>
    <taxonkt>None</taxonkt>
    <taxonkey>multiple species</taxonkey>
    <taxonkey>birds</taxonkey>
   </keywtax>
   <taxonsys>
    <classsys>
     <classcit>
      <citeinfo>
       <origin>American Ornithologists&apos; Union</origin>
       <pubdate>1998</pubdate>
       <title>Check-list of North American Birds</title>
       <edition>Seventh</edition>
       <geoform>book</geoform>
       <onlink>http://www.aou.org/checklist/index.php3</onlink>
      </citeinfo>
     </classcit>
     <classmod>The check-list is revised and updated on an annual basis by the American Ornithologists&apos; Union. Revisions are published in The Auk.</classmod>
    </classsys>
    <taxonpro>Observers have pre-existing knowledge of bird identification or they use published field guides.</taxonpro>
   </taxonsys>
   <taxongen>Birds.</taxongen>
   <taxoncl>
    <taxonrn>Kingdom</taxonrn>
    <taxonrv>Animalia</taxonrv>
    <common>animals</common>
    <taxoncl>
     <taxonrn>Phylum</taxonrn>
     <taxonrv>Chordata</taxonrv>
     <common>chordates</common>
     <taxoncl>
      <taxonrn>Subphylum</taxonrn>
      <taxonrv>Vertebrata</taxonrv>
      <common>vertebrates</common>
      <taxoncl>
       <taxonrn>Class</taxonrn>
       <taxonrv>Aves</taxonrv>
       <common>birds</common>
      </taxoncl>
     </taxoncl>
    </taxoncl>
   </taxoncl>
  </taxonomy>
  <accconst>Point count locations (lat and long) are PRBO property.</accconst>
  <useconst>User must receive written permission from PRBO before using or sharing this information.</useconst>
  <ptcontac>
   <cntinfo>
    <cntorgp>
     <cntorg>PRBO Conservation Science</cntorg>
     <cntper>Chris Rintoul</cntper>
    </cntorgp>
    <cntpos>Informatics Specialist</cntpos>
    <cntaddr>
     <addrtype>mailing and physical</addrtype>
     <address>3820 Cypress Drive, #11</address>
     <city>Petaluma</city>
     <state>CA</state>
     <postal>94954</postal>
     <country>US</country>
    </cntaddr>
    <cntvoice>707-781-2555</cntvoice>
    <cntemail>crintoul@prbo.org</cntemail>
   </cntinfo>
  </ptcontac>
  <datacred>PRBO Conservation Science.</datacred>
  <native>Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.2.2.1350 Shapefile.</native>
 </idinfo>
 <dataqual>
  <logic>not applicable</logic>
  <posacc>
   <horizpa>
    <horizpar>All points collected before the year 2000 are accurate to within 30 meters, while points collected since 2000 are accurate to within 5 meters of the actual point count location. Most points were collected using a Garmin II or later version GPS unit.</horizpar>
   </horizpa>
   <vertacc>
    <vertaccr>Elevation is accurate to within 30 m or 90 m.  Elevation information was derived using GIS and any available 30 m or 90 m DEM layers for each location.</vertaccr>
   </vertacc>
  </posacc>
  <lineage>
   <srcinfo>
    <srccite>
     <citeinfo>
      <origin>Unknown</origin>
      <pubdate>Unknown</pubdate>
     </citeinfo>
    </srccite>
    <typesrc>online</typesrc>
    <srctime>
     <timeinfo>
      <rngdates>
       <begdate>1991</begdate>
       <enddate>current</enddate>
      </rngdates>
     </timeinfo>
     <srccurr>ground condition</srccurr>
    </srctime>
   </srcinfo>
   <procstep>
    <procdesc>Metadata imported.</procdesc>
    <srcused>C:\DOCUME~1\vtoniolo\LOCALS~1\Temp\xml59FE.tmp</srcused>
    <procdate>Unknown</procdate>
   </procstep>
   <procstep>
    <procdesc>Dataset moved.</procdesc>
    <srcused>V:\gis_projects\all_sites\all_pc\allpc_albers</srcused>
    <procdate>Unknown</procdate>
   </procstep>
   <procstep>
    <procdesc>Metadata imported.</procdesc>
    <srcused>V:\gis_projects\all_sites\Old\allpc_albers.shp.xml</srcused>
    <procdate>Unknown</procdate>
   </procstep>
   <procstep>
    <procdesc>Metadata imported.</procdesc>
    <srcused>C:\DOCUME~1\vtoniolo\LOCALS~1\Temp\xml1B58.tmp</srcused>
    <procdate>20050620</procdate>
    <proctime>184116</proctime>
   </procstep>
   <procstep>
    <procdesc>Metadata imported.</procdesc>
    <srcused>V:\project\prbo\all_sites\all_pc\metadata\allpc_metadata_oct05.xml</srcused>
    <procdate>20060601</procdate>
    <proctime>155647</proctime>
   </procstep>
   <procstep>
    <procdesc>Dataset moved.</procdesc>
    <srcused>V:\PROJECT\prbo\all_sites\all_pc\allpc_geo</srcused>
    <procdate>20070320</procdate>
    <proctime>160105</proctime>
   </procstep>
   <procstep>
    <procdesc>Metadata imported.</procdesc>
    <srcused>V:\PROJECT\prbo\all_sites\all_pc\shp\allpc_geo.shp.xml</srcused>
    <procdate>20070427</procdate>
    <proctime>111153</proctime>
   </procstep>
  </lineage>
 </dataqual>
 <spdoinfo>
  <direct>Vector</direct>
  <ptvctinf>
   <sdtsterm>
    <sdtstype>Entity point</sdtstype>
    <ptvctcnt>11666</ptvctcnt>
   </sdtsterm>
  </ptvctinf>
 </spdoinfo>
 <spref>
  <horizsys>
   <geograph>
    <latres>0</latres>
    <longres>0</longres>
    <geogunit>Decimal degrees</geogunit>
   </geograph>
   <geodetic>
    <horizdn>North American Datum of 1983</horizdn>
    <ellips>Geodetic Reference System 80</ellips>
    <semiaxis>6378137</semiaxis>
    <denflat>298.257222</denflat>
   </geodetic>
  </horizsys>
 </spref>
 <eainfo>
  <detailed>
   <enttyp>
    <enttypl>allpc_BASE</enttypl>
    <enttypd>Feature Class</enttypd>
    <enttypds>11666</enttypds>
   </enttyp>
   <attr>
    <attrlabl>FID</attrlabl>
    <attrdef>Internal feature number.</attrdef>
    <attrdefs>ESRI</attrdefs>
    <attrdomv>
     <udom>Sequential unique whole numbers that are automatically generated.</udom>
    </attrdomv>
   </attr>
   <attr>
    <attrlabl>Shape</attrlabl>
    <attrdef>Feature geometry.</attrdef>
    <attrdefs>ESRI</attrdefs>
    <attrdomv>
     <udom>Coordinates defining the features.</udom>
    </attrdomv>
   </attr>
   <attr>
    <attrlabl>UNIQUEID</attrlabl>
    <attrdef>Unique ID for each survey point (project code + id_code).</attrdef>
    <attrdefs>PRBO</attrdefs>
    <attrdomv>
     <udom>String, 254 characters.</udom>
    </attrdomv>
   </attr>
   <attr>
    <attrlabl>PRBOSITE</attrlabl>
    <attrdef>PRBO site (Y) or partner organization (N).</attrdef>
    <attrdefs>PRBO</attrdefs>
    <attrdomv>
     <udom>String, 254 characters.</udom>
    </attrdomv>
   </attr>
   <attr>
    <attrlabl>PROJECT</attrlabl>
    <attrdef>PRBO project name.</attrdef>
    <attrdefs>PRBO</attrdefs>
    <attrdomv>
     <udom>String, 254 characters.</udom>
    </attrdomv>
   </attr>
   <attr>
    <attrlabl>STATIONNAM</attrlabl>
    <attrdef>Station/transect full name.</attrdef>
    <attrdefs>PRBO</attrdefs>
    <attrdomv>
     <udom>String, 254 characters.</udom>
    </attrdomv>
   </attr>
   <attr>
    <attrlabl>ID_CODE</attrlabl>
    <attrdef>STATIONID + SITEID.</attrdef>
    <attrdefs>PRBO</attrdefs>
    <attrdomv>
     <udom>String, 254 characters.</udom>
    </attrdomv>
   </attr>
   <attr>
    <attrlabl>X</attrlabl>
    <attrdef>Longitude (decimal degrees)</attrdef>
    <attrdefs>none</attrdefs>
    <attrdomv>
     <udom>String, 254 characters.</udom>
    </attrdomv>
   </attr>
   <attr>
    <attrlabl>Y</attrlabl>
    <attrdef>Latitude (decimal degrees)</attrdef>
    <attrdefs>none</attrdefs>
    <attrdomv>
     <udom>String, 50 characters.</udom>
    </attrdomv>
   </attr>
   <attr>
    <attrlabl>PROJECTID</attrlabl>
    <attrdef>PRBO unique project code</attrdef>
    <attrdefs>PRBO</attrdefs>
    <attrdomv>
     <udom>String, 254 characters.</udom>
    </attrdomv>
   </attr>
   <attr>
    <attrlabl>STATIONID</attrlabl>
    <attrdef>Station / transect code (4-6 letter)</attrdef>
    <attrdefs>PRBO</attrdefs>
    <attrdomv>
     <udom>Float, 19 characters.</udom>
    </attrdomv>
   </attr>
   <attr>
    <attrlabl>SITEID</attrlabl>
    <attrdef>Point number within transect.</attrdef>
    <attrdefs>PRBO</attrdefs>
    <attrdomv>
     <udom>Float, 19 characters.</udom>
    </attrdomv>
   </attr>
   <attr>
    <attrlabl>ORIGIN</attrlabl>
    <attrdef>Origin of the coordinates of the data record (e.g. GPS unit, hand-digitized, etc.)</attrdef>
    <attrdefs>PRBO</attrdefs>
    <attrdomv>
     <udom>String, 50 characters.</udom>
    </attrdomv>
   </attr>
   <attr>
    <attrlabl>NON_PUBLIC</attrlabl>
    <attrdef>Designates if the data record can be shared with the public.</attrdef>
    <attrdefs>PRBO</attrdefs>
    <attrdomv>
     <udom>String, 4 characters.</udom>
    </attrdomv>
   </attr>
  </detailed>
  <overview>
   <eaover>PRBO Point Count Data Structure Ballard and Geupel, 1994 Last revision: 9/2002 Each individual bird encountered during a point count has its own record (corresponding to rows in the table) in the file. Each record is comprised of nine fields (corresponding to columns in the table). The nine fields are: 1. SPEC: The four letter AOU abbreviation for species name. SOSP = Song Sparrow. Enter &quot;9999&quot; for no detections. 2. DATA: A five character code for type, distance, and timing of detection. The first character corresponds to the behavior of the bird that caused it to be detected, &quot;S&quot; for singing, &quot;C&quot; for calling, &quot;V&quot; for visual. The second through fourth characters correspond to distance of detection from point count location. In general, &quot;L50&quot; for within 50 meters, &quot;G50&quot; for greater than 50 meters, &quot;FLO&quot; for flying over. Use &quot;B00&quot; for &gt; 100m. The final character represents the timing of the detection, and could be used to identify the duration of each count. &quot;3&quot; for three minutes, &quot;5&quot; for five minutes, etc. Example: &quot;CL505&quot; would correspond to an individual detected calling within 50 meters during a five-minute point count. Enter &quot;99999&quot; for no detections. For variable circular plot (VCP) data, &quot;L&quot; still signifies &lt; 50, G &gt;50. However, the upper end of the distance band is used rather than &quot;50&quot;. For detections &gt; 100 m, use &quot;B&quot;. See examples at end. 3. State: Two letter abbreviation for the State in which the census occurred. 4. Region: Generally the county in which the census occurred, though could be used for more descriptive location information, if applicable. Nine characters. 5. Station: Six character study area identifier. 6. Date: Date of count. 7. Initials: Three characters for initials of observer. 8. Site: Two digits for individual point count site number. 9. Time: Four numbers for beginning time (in 24 hour format with no colon)of census for each site. Each record contains all of this information. Though it may seem redundant, it is important for keeping track of data and for ease of analysis using each individual as a separate statistical observation.</eaover>
   <eadetcit>See &quot;Entity and Attribute Overview&quot; for a list of fields contained in the raw bird data. Data will be shared with non-PRBO entities at the discretion of the party responsible for its collection and maintenance (PRBO project leader and/or data manager) and in accordance with PRBO&apos;s data-sharing policy.</eadetcit>
  </overview>
 </eainfo>
 <distinfo>
  <distrib>
   <cntinfo>
    <cntorgp>
     <cntorg>PRBO Conservation Science</cntorg>
     <cntper>Grant Ballard</cntper>
    </cntorgp>
    <cntpos>Terrestrial Ecology Division data manager</cntpos>
    <cntaddr>
     <addrtype>mailing</addrtype>
     <address>4990 Shoreline Hwy</address>
     <city>Stinson Beach</city>
     <state>CA</state>
     <postal>94970</postal>
     <country>USA</country>
    </cntaddr>
    <cntvoice>(415) 868-0655 x 302</cntvoice>
    <cntemail>gballard@prbo.org</cntemail>
   </cntinfo>
  </distrib>
  <resdesc>Downloadable Data</resdesc>
  <distliab>PRBO Conservation Science does not assume any responsibility regarding the accuracy, utility or completeness of the data for general or scientific purposes, nor shall the act of distribution constitute any such warranty. We strongly recommend that the data be acquired directly from PRBO Conservation Science and not from an independent third party, which may have modified the data after obtaining it. PRBO shall not be held liable for improper or incorrect use of the data described and/or contained herein. ~~~ PRBO Data Sharing Policy November 2003 It is PRBO policy that data should be shared whenever possible while considering the tradeoffs between widespread distribution of data sets, the need to assure data quality and validity, and the privacy rights of land owners, as applicable. The general rule is that data should be released as soon as possible, along with documentation that can be used to judge data quality and potential usefulness. PRBO believes that the intellectual investment and time committed to the collection of a data set entitles the investigator to the fundamental benefits of the work. Therefore, publication of descriptive or interpretive results derived immediately and directly from the data is the privilege and responsibility of the investigators who collect the data. This is one of the primary motivations for scientific data collection, and the scientific method is supported by this principle. PRBO encourages its scientists to anticipate that most data collected will eventually become part of the public domain, and recommends that procedures be employed to facilitate this sharing, such as concurrent metadata generation, data verification, data entry, and data backup. Data for which there are no associated metadata, or which have not been verified, should not be shared. Data that have not been used for peer-reviewed publication should be shared with caution. Data used in publications should be ready for public distribution at the same time as the actual publication. Data relevant to public policy should be shared as quickly and widely as possible. All PRBO data that have been shared should be maintained in a fashion that facilitates its continued public accessibility. This includes the need for data versioning, informing users when there have been important changes to public datasets. Data collected on private lands may be subject to more extensive sharing restrictions, depending on agreements between PRBO and landowners. PRBO maintains numerous datasets, including several with hundreds of thousands of records covering 20 or more years and involving multiple investigators. PRBO recognizes that these datasets can be used for many purposes, either on their own or through combination with other data. Any researcher making substantial use of a dataset should communicate with the investigators who acquired the data, or those to whom responsibility for the data has been entrusted, prior to publication. In most cases these researchers should anticipate that the data collectors or current managers would be co-authors of published results. PRBO will encourage and facilitate the ethical and courteous use of data within its archives. PRBO will maintain a list of all data access and will notify those who access the data that they may be the intellectual property of the collecting scientists. PRBO requests that it be acknowledged in any publication, report, or presentation using data that have been collected by PRBO scientists. The requesting party(s) and the appropriate PRBO Division Director should sign a data sharing agreement, and a copy should be filed with the Division Director. Data may be posted on the web with approval in advance from the collecting scientists and the Division Director. Such public posting of data must be permissible under relevant contracts. Any costs that PRBO incurs in the process of providing or maintaining public access to its datasets should be reimbursed. These costs should be considered at the project proposal stage for new data, and at the data request stage for legacy data. Costs include hourly wages for persons responsible for data maintenance and retrieval, as well as indirect costs for maintenance of computer equipment and backup systems. -------------------------------------------------------------------- Developed by Grant Ballard, revised per feedback at PRBO&apos;s 2003 Science Retreat and with additional revisions and approval by the PRBO Management Team, November 2003. PRBO reserves the right to modify, revise or supplement this policy, as it deems appropriate.</distliab>
  <stdorder>
   <digform>
    <digtinfo>
     <formname>website</formname>
     <transize>0.257</transize>
    </digtinfo>
   </digform>
   <fees>none</fees>
  </stdorder>
  <custom>To obtain the most recent version of the point count shapefile, contact PRBO&apos;s Informatics Specialist: Chris Rintoul PRBO Conservation Science 3820 Cypress Drive, #11 crintoul@prbo.org To obtain a copy of the bird data (summarized by year for each point) associated with each point count location please contact PRBO&apos;s Terrestrial Ecology Division data manager: Grant Ballard PRBO Conservation Science 4990 Shoreline Hwy Stinson Beach, CA 94970 (415) 868-0655 x 302 gballard@prbo.org Bird data will be shared with non-PRBO entities at the discretion of the party responsible for its collection and maintenance (PRBO project leader and/or data manager) and according to PRBO&apos;s data-sharing policy.</custom>
 </distinfo>
 <distinfo>
  <distrib>
   <cntinfo>
    <cntorgp>
     <cntorg>Avian Knowledge Network</cntorg>
    </cntorgp>
    <cntaddr>
     <addrtype>mailing</addrtype>
     <address>Cornell Lab of Ornithology,</address>
     <address>159 Sapsucker Woods Rd.</address>
     <city>Ithaca</city>
     <state>NY</state>
     <postal>14850</postal>
     <country>USA</country>
    </cntaddr>
   </cntinfo>
  </distrib>
  <resdesc>Point Counts: Point Reyes Bird Observatory</resdesc>
  <distliab>These data are made available through the Avian Knowledge Network, a National Science Foundation funded project of the Cornell Lab of Ornithology and Department of Computer Science at Cornell University. No warranty, expressed or implied, is made regarding the accuracy or utility of these data.</distliab>
  <stdorder>
   <digform>
    <digtinfo>
     <formname>website</formname>
    </digtinfo>
    <digtopt>
     <onlinopt>
      <computer>
       <networka>
        <networkr>http://www.avianknowledge.net/</networkr>
       </networka>
      </computer>
     </onlinopt>
    </digtopt>
   </digform>
   <fees>none</fees>
  </stdorder>
 </distinfo>
 <metainfo>
  <metd>20070427</metd>
  <metc>
   <cntinfo>
    <cntorgp>
     <cntorg>PRBO Conservation Science</cntorg>
     <cntper>Viola Toniolo</cntper>
    </cntorgp>
    <cntpos>GIS Biologist</cntpos>
    <cntaddr>
     <addrtype>physical</addrtype>
     <address>4990 Shoreline Hwy</address>
     <city>Stinson Beach</city>
     <state>CA</state>
     <postal>94970</postal>
     <country>US</country>
    </cntaddr>
    <cntvoice>&gt;(415) 868-0655 x 302</cntvoice>
    <cntfax>(415) 868-9363</cntfax>
    <cntemail>vtoniolo@prbo.org</cntemail>
   </cntinfo>
  </metc>
  <metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
  <metstdv>FGDC-STD-001-1998</metstdv>
 </metainfo>
</metadata>

