Bill makes a very good point. I think there are really two issues here,
one is identifying the bird (specifically use of banding codes), and the
other is location. people are generally good about using a full name
somewhere in a post, even if a banding code is used in subject line. I
think the bigger problem is location, and here part of the problem is when
someone mentions a park or road or other geological feature and GoogleMaps
doesn't know of it (a too common occurrence in my experience). the
failures of GoogleMaps we just have to live with, but mentioning a nearby
town or county (as many do) is a big help, and is to be encouraged, even
when posting from a cell phone.
Chris Kessler
Seattle
On Sun, May 17, 2020 at 11:11 PM Bill Anderson <
billandersonbic at yahoo.com>
wrote:
>
I think the use of abbreviations and acronyms for birds and locations is
>
only going to increase with the increased use of cell phones and IPads to
>
send e-mails instead of laptop and desk top computers.
>
>
Bill Anderson; Edmonds, WA. USA
>
>
>
On Sunday, May 17, 2020, 9:56:04 PM PDT, Doug Santoni <
>
dougsantoni at gmail.com> wrote:
>
>
>
Dear Tweeters Moderator --
>
>
I have been here in Washington state for about six years, but I'm still
>
not familiar with all of the areas of this big wonderful state. Can you
>
please ask posters to help decipher abbreviations and acronyms for those of
>
us who aren't as familiar with the state and all of its wonderful pockets
>
for good birding?
>
>
Doug Santoni
>
Phone 305-962-4226
>
>
>
_______________________________________________
>
Tweeters mailing list
>
Tweeters at u.washington.edu
>
http://mailman11.u.washington.edu/mailman/listinfo/tweeters
>
_______________________________________________
>
Tweeters mailing list
>
Tweeters at u.washington.edu
>
http://mailman11.u.washington.edu/mailman/listinfo/tweeters
>
--
"moderation in everything, including moderation"
Rustin Thompson
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://mailman11.u.washington.edu/pipermail/tweeters/attachments/20200518/3c77d370/attachment.html>