birdhybrids.blogspot.com has some fairly extensive discussion of waterfowl
hybrids, with contributions from a number of Colorado birders.  See, for
example,
http://birdhybrids.blogspot.com/2014/02/rosss-goose-x-cackling-goose.html
or http://birdhybrids.blogspot.com/2014/02/snow-goose-x-cackling-goose.html
.  The identifications in these examples are based on observed
morphological details, not DNA.

Along these lines, in our area a dark-bodied goose with a whitish head/neck
is much more likely to be a hybrid than a dark morph Snow or Ross's.  I
have appreciated the kind guidance of eBird reviewers and other experts in
reminding me about this!

Peter Ruprecht
Superior

On Mon, Dec 7, 2020 at 11:17 AM Derek Hill <[email protected]> wrote:

>
> There is, as to be expected, an influx of goose reports for our state. Via
> ebird, there are incoming reports of the gamut: cacklingXross's,
> cacklingXsnow, canadaXsnow, canadaXross's, snowXross's.
>
> How are these hybrids being specifically identified? Can anyone share some
> data or research of hybrids of known parental provenance that would aid or
> even remotely make possible these identifications?
>
> Good birding,
> Derek Hill
> Loveland, CO
>
> --
> You received this message because you are subscribed to the Google Groups
> "Colorado Birds" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/cobirds/b554de9f-4ee2-405a-8468-1128892fe3a9n%40googlegroups.com
> <https://groups.google.com/d/msgid/cobirds/b554de9f-4ee2-405a-8468-1128892fe3a9n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Colorado Birds" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/cobirds/CAHPXVBYdYsqF%2Bhu6dDYP9rufz%2B5b9HJVEp%2BMjRRLY2wOBETEBQ%40mail.gmail.com.

Reply via email to