Block boundary problems – part 1

Earlier this week, I spent quite a bit of time at Hammonasset State Park.  Because I had some time to kill, I went to Hammonasset Point – the area just south of Rock Pond, at the start of the Moraine Trail, which sits in a separate atlas block from the rest of park.  My goal was to see what I could find that was nesting right in the tiny piece of land that is in block 120B. Continue reading

Download the Summer Bird Count circle map

Last week, I wrote about the ways in which people conducting Summer Bird Counts this month can also contribute data to the atlas project.  To provide additional help to determine how blocks relate to count circles, we have produced a downloadable Google Earth (.kml) file, which shows the SBC circles.  If you have Google Earth on your phone and have already downloaded the data layer showing the block boundaries, you can add this layer to see how they overlap. Continue reading

Summer Bird Counts and the atlas project

Connecticut birding has a long history of citizen science, of which the Connecticut Bird Atlas is only the most recent incarnation. Summer Bird Counts (SBCs) – the mid-year equivalent of Christmas Bird Counts – have been run in the state for nearly three decades and aim to count birds within several 15-mile diameter circles scattered across the state to help track population changes. Continue reading

Cuckoos carrying food

As we’ve noted before, the CF (carrying food for young) breeding code is problematic for species that regularly carry food for their own consumption. This code is designed specifically for cases where birds are presumed to be carrying food to their dependent young and it can be hard to determine whether that is the case sometimes. Many species can be seen with food in their beaks temporarily. But if they are going to eat it, they usually do so right away. Careful observation for a minute or two will usually ensure that the code is not misused. Continue reading

2,174 and counting …

As of this afternoon, 2,174 eBird checklists have been shared with the ctbirdatlas account.  Within those checklists, we have received almost 10,000 individual records with breeding codes attached, representing 152 potential breeding species.  Given that the breeding season is still getting going for many species, this level of effort bodes well for the project’s success and we are very grateful to everyone who has shared their checklists. Continue reading

Slow birding in the swamp

Last week was widely noted to be one of the best for spring warbler migration in Connecticut for many years, and lots of birders took advantage of it to boost their year lists and to do big days. I, on the other hand, injured myself on the first morning and ended up laying on my back for most of the week (I did see 18 species of warblers and heard both cuckoos that first day … so some consolation). Yesterday, I was finally able to get back out in the field, but fearing a relapse I decided I shouldn’t push my luck. Continue reading

Confirming vultures

One of the goals of the Connecticut Bird Atlas is to document changes in distributions since the first atlas was done in the 1980s. At that time, turkey vultures were widespread, but breeding was concentrated in the western half of the state, away from the coast, and winter concentrations were still noteworthy. Black vultures were considered very rare, with no evidence of breeding recorded during the atlas, although they were starting to be seen more frequently. Both species have increased. Just how much, is something we hope the new atlas will tell us. Continue reading

Why only 20 hours? Can I do more?

For the breeding portion of the atlas we are asking block adopters to commit to 20 hours of time spent looking for breeding birds in their block over the course of the three-year study.  To some, this does not seem like very much time and many have asked whether 20 hours is enough time to adequately survey a block, and whether then can spend more time.

The short answer is that you can spend as much time as you like in your block – we will take (and use) as much data as you send us. Continue reading