<?xml version='1.0' encoding='utf-8'?>
<oai_dc:dc xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
  <dc:contributor>Rachel A. Katz</dc:contributor>
  <dc:contributor>Kate E. Iaquinto</dc:contributor>
  <dc:contributor>Kevin J. Suir</dc:contributor>
  <dc:contributor>M.J. Baldwin</dc:contributor>
  <dc:contributor>A. Hecht</dc:contributor>
  <dc:creator>Erin King</dc:creator>
  <dc:date>2019</dc:date>
  <dc:description>&lt;p&gt;This regional protocol provides a framework for quantifying the number of breeding pairs and&amp;nbsp;productivity of Atlantic Coast piping plover (Charadrius melodus) populations during the&amp;nbsp;breeding season. A primary purpose of this protocol is to standardize piping plover monitoring&amp;nbsp;during the breeding season. The survey techniques described herein involve repeated visual&amp;nbsp;counts of adults, nests, eggs, and chicks within a defined survey site (i.e., beach) as well as visual&amp;nbsp;identification of potential threats to survival and productivity. Resulting data can be compiled&amp;nbsp;and analyzed across multiple geographic units (i.e., sites, states, and recovery units) to assess&amp;nbsp;progress toward recovery goals, inform local management decisions, assess management&amp;nbsp;effectiveness, and improve monitoring efforts.&amp;nbsp;This protocol framework was developed as part of the United States Fish and Wildlife Service&amp;nbsp;(USFWS) National Wildlife Refuge System (NWRS) Inventory and Monitoring (I&amp;amp;M) Initiative&amp;nbsp;in coordination with Ecological Services (ES) and state coordinators within the Southeast and&amp;nbsp;Northeast Regions (4 and 5, respectively). Although this protocol framework is to be used&amp;nbsp;primarily by NWRS to inform recovery goals, assist with local management decision-making,&amp;nbsp;and meet State reporting requirements, the approach strives to assist monitoring efforts of nonNWRS partners, such as other federal agencies (e.g. National Park Service), State wildlife&amp;nbsp;agencies, non-governmental organizations, and private landowners. This protocol framework and&amp;nbsp;associated data management system (PIPLweb) aims to interface with existing data management&amp;nbsp;and analysis tools (i.e., PIPLODES, NestStory, and PiperEx) to ensure that data collection is&lt;br&gt;efficient and comparable across scales, and supports management decisions across partners.&amp;nbsp;The content and structure of the protocol framework follows standards set forth in the USFWS’s&amp;nbsp;How to Develop Survey Protocols: A Handbook (Version 1.0; 2013). The eight elements&amp;nbsp;addressed include: introduction, sampling design, field methods, data management and analysis,&amp;nbsp;reporting, personnel requirements and training, operational requirements, and references. A&amp;nbsp;series of standard operating procedures (SOPs) provides greater detail on recommended methods&amp;nbsp;and technical aspects of this protocol. Data entry, archival, and multi-scale analysis are handled&amp;nbsp;through a secure web application (Plover Inventory and Productivity Library; PIPLweb)&amp;nbsp;developed by the United States Geological Survey (USGS). When management activities and&amp;nbsp;survey objectives are similar across management units, partners (Refuges, other federal agencies,&amp;nbsp;State, NGOs, private) are encouraged to use this protocol framework to develop stepped-down&lt;br&gt;site-specific survey protocols that include guidance for conducting on-the-ground monitoring and&amp;nbsp;management plans. &lt;/p&gt;</dc:description>
  <dc:format>application/pdf</dc:format>
  <dc:language>en</dc:language>
  <dc:publisher>U. S. Fish and Wildlife Service</dc:publisher>
  <dc:title>Regional protocol framework for the inventory and monitoring of breeding Atlantic Coast Piping Plovers</dc:title>
  <dc:type>reports</dc:type>
</oai_dc:dc>