Note: To be current with eBird, install the current Taxonomy Update for AviSys.
Do you need to upload CSV files? If so, you will need use eBird to AviSys checklist import (Version 1). Click here
eBird to AviSys checklist import will convert one or more eBird checklists into an AviSys stream file with which you can import the data into AviSys (Version 6).
Let's say you have a checklist https://ebird.org/view/checklist/S46116491.
You can copy-and-paste just the "S46116491",
or you can copy-and-paste the whole "https://ebird.org/view/checklist/S46116491".
If you enter multiple checklists, enter them on separate lines, or else just separate them with spaces or commas.
For example you could enter
S46116491, S21594122, S48759196
S46116491 S21594122 S48759196
Read the tutorial on using AviSys stream files to import data if you are not familiar with the process.
You might have some species recorded in eBird that you don't want recorded in AviSys. These might include domestic forms like Muscovy Duck (Domestic type), non-countable exotics like Red-masked Parakeet, or others. Maybe you don't record these species yourself, but they show up on lists someone shares with you. You can exclude these species from the import from eBird by listing them, one per line, in the "Excludes" input.
If AviSys does not recognize a species name while importing a stream file, it will skip that sighting record. (It will tell you!) You will need to be sure that you have AviSys up-to-date with current taxonomy.
One prominent difference between eBird names and AviSys names is that eBird accepts certain names with parenthetic qualifiers, e.g., “Northern Flicker (Yellow-shafted)”. You don't need to worry about these cases! eBird to AviSys checklist import will remove the parenthetic part of the name and insert it at the beginning of the AviSys comment.
Another difference is that eBird allows “sp” or “slash” entries (e.g. Downy/Hairy Woodpecker). AviSys ignores these.
A checklist that is flagged for some reason with a comment similar to “This checklist and its observations do not appear in public eBird outputs” cannot be imported with this version. You will need to use Version 1
Yes, but not with this version of eBird to AviSys checklist import. You will need to use Version 1 which supports csv files.
Before you generate the AviSys stream file, eBird to AviSys checklist import gives you a summary of what is in the checklists that you specified. In the summary, you can correct the AviSys place name, and you have the option to enter a global comment that will be added to all observations for that location.
By default, the summary is by location. In other words, no matter how many checklists you select for a location, the summary will only have a single entry for the location. This is "Summarize by location".
Sometimes you might prefer to be able to enter a custom comment for each checklist rather than for each location. In that case, select "Summarize by checklist", and the summary will contain an entry for each checklist. Each entry will display the time and effort data for the checklist, so that you can recognize it.
Whichever type of summary you choose, the generated stream file will be the same, except for anything that you enter in the Global comment field.
In many cases, your eBird location names may not match up exactly with your AviSys place names, and you will need to manually enter your corresponding AviSys place name for each eBird location. As a convenience, eBird to AviSys checklist import remembers AviSys places from one session to the next. Once you "train" it by entering the AviSys place name for an eBird location, the name pairing will be saved for future use. The Places data is stored locally in your browser. This has a couple of consequences.
AviSys can only record dates between Jan 1, 1930 and Dec 31, 2029. Any dates older than 1930 will be recorded with a year of 1930. Dates after 2030 will be recorded with a year 100 years earlier.