Possible exceptions in AviSys taxonomy update for 2016

If you have sightings of a species whose name no longer exists in the updated taxonomy, AviSys will report that as an exception. For each exception, you will need to figure out what the corresponding new name is, and manually update your AviSys data accordingly before the update will run to completion. Exceptions are reported in a file named UPDEXCEP.TXT, and suggestions for how to deal with exceptions are provided in that file. Read these suggestions carefully.

Here is a summary of exceptions that AviSys could report in the UPDEXCEP.TXT file for an upgrade from the 2014 taxonomy to 2016. AviSys will report an exception only for species for which you actually have sightings, so your UPDEXCEP.TXT file will surely have fewer exceptions than are listed here. Note that hardly any of the exceptions involve ABA-area species. If you are upgrading from a taxonomy level before 2014 you will likely have additional exceptions not shown here.

I am not providing the PDF files that AviSys mentions; the relevant information is in this web page. You can find more details on many of the changes on pages on the Clements website: for 2016, for 2015, and for earlier years. My authority for this update, however, is the Clements Checklist v2016 spreadsheet which includes additional changes that are not described in the web pages.

Simple name changes

These are listed separately under simple name changes.

Lumps

In this table, "old name" is a name that was in the 2014 taxonomy but has disappeared from the 2016 taxonomy due to a lump. An entry in the "new name" column means that the lump resulted in a new species. An entry in the "lump target" column means that the species was lumped into an existing species.

Splits

There are two tables of splits. The first table lists splits where the species that was split no longer exists, and thus any sightings of it will be reported by AviSys as an exception.

This second table lists splits where one of the split species retains the original name. Thus, because the name still exists, AviSys will not flag your sightings of that species as an exception; however you will want to review your records to see if you need to transfer some sightings to one of the new species.