1 / 9

BFO Raptor Database

The BFO Raptor Database has been updated to improve tracking of species associated with nests by year. Each active nest is recorded with a unique entry, allowing comprehensive monitoring of nest status, species assignment, and observer data. With recent enhancements, the Bureau of Land Management (BLM) can track observations across different areas, identify nest conditions, and standardize reporting codes to reduce data inconsistencies. This improvement facilitates better analysis of nesting trends and species interactions over time.

jensen
Télécharger la présentation

BFO Raptor Database

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. BFO Raptor Database

  2. Updates • Species is specific to a year, not to a nest • Species only gets assigned to a year if the nest was active This is because more than one species can use a nest over time. The database is now set up to easily track this information.

  3. Updates • At least one record per observer each year. • Each report for a nest gets entered as a unique record into the database. Observer is included as a field. This allows BLM to track and maintain all the information reported by consultants and analyze similarities & differences and identify issues. • 50 nests with more than one species in a year • 241 nests with more than one status in a year

  4. # Nests Counted by More than One Observer in a Year

  5. Updates • The database now allows BLM to track which POD(s) each observation was reported for. Allows BLM to easily monitor COAs

  6. Clarification:Gone vs. Did not Locate • DNLO refers to nest status. • GONE refers to nest condition. • If status = DNLO, then condition will always = Unknown. • If condition = GONE, then status will usually = INAC.

  7. Clarification:Is the nest gone? • A nest that is GONE because of prolonged inactivity is different than a situation where the substrate is no longer available for use. • Current proposal - If the nest substrate is no longer available for use as a nest location, then code as Status = “Substrate Gone” and Condition = “n/a”.

  8. Clarification:Nest Status/Condition Codes Some of the nest status codes refer to condition of the nest. This creates inconsistencies in data reporting and makes analysis difficult. • Example: • INDI, and INDE all refer to an inactive nest in various conditions. • PRED refers to an active nest that has been predated upon.

  9. Issues:Nest Status Codes Solution – Use INAC to describe an inactive nest and then use the appropriate status code. Avoid use of INDE, INDE, PRED.

More Related