Summary: | This data package is formatted according to the "ecocomDP", a data package design pattern for ecological community surveys, and data from studies of composition and biodiversity. For more information on the ecocomDP project see https://github.com/EDIorg/ecocomDP/tree/master, or contact EDI https://environmentaldatainitiative.org. This Level 1 data package was derived from the Level 0 data package found here: https://portal.edirepository.org/nis/mapbrowse?scope=knb-lter-bes&identifier=543&revision=170 The abstract below was extracted from the Level 0 data package and is included for context: This dataset is associated with BES Bird Monitoring Bird Monitoring Project: ================= The BES Bird Monitoring Project is a breeding bird survey designed to find out what birds are found in the breeding season in Baltimore and where. Our monitoring efforts will show associations among block group socioeconomic variables, land cover, land use, and habitat features with breeding bird abundance, to provide information for land managers on possible consequences of land use changes on bird communities. A distinguishing feature of the bird monitoring at BES LTER, relative to other urban bird work, is the capacity for long-term monitoring of features at multiple scales through links to other parts of the project. Different processes influence habitat for birds at different scales, e.g. ongoing household level human decision-making at lot scale vs. block or neighborhood scale abandonment/re-development. Our project seeks to understand how these processes impact bird occurrence, abundance, and composition differ at the lot, block and neighborhood scale. The database consists of four tables. Sites, Surveys, Taxalist, and Birds. Sites records thje sites and their characteristics. Surveys describe the actual outings or sampling sessions. They describe the weather, the temperature, the sites visited. Taxalist provides the integration of speciaies abbreviations and common names, and Birds describes the actual sightings, linking to the other three tables. Attribute information: The tables form a set. Here are the fields and relationship information: Surveys: site_id FK->Sites[site_id] survey_id survey_date time_start time_end observer wind_speed wind_dir air_temp temp_units cloud_cover notes Sites: site_id park_code park_district park_name point_code point_location park_acreage Taxalist: species_id common_name Birds: survey_id FK->surveys[survey_id] site_id FK->surveys[site_id] species_id FK->taxalist[species_id] distance bird_count notes seen heard direction time_class
|