Skip to content

Commit 80d30e6

Browse files
authored
docs: clarify expected species list format for Perch (#921)
1 parent 62def02 commit 80d30e6

1 file changed

Lines changed: 11 additions & 3 deletions

File tree

docs/best-practices/species-lists.rst

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,17 @@ When editing your own `species_list.txt` file, make sure to copy species names f
55

66
You can find label files in the checkpoints folder, e.g., `checkpoints/V2.4/BirdNET_GLOBAL_6K_V2.4_Labels.txt`.
77

8-
Species names need to consist of `scientific name_common name` to be valid.
9-
If you want to use the Perch model, you have to use their naming convention, which is just `scientific name`.
10-
For examples check the respective label files.
8+
Species names need to consist of `scientific name_common name` to be valid, for example::
9+
10+
Turdus merula_Common Blackbird
11+
Parus major_Great Tit
12+
13+
If you want to use the Perch model, you have to use only the scientific name with no underscore or common name, for example::
14+
15+
Turdus merula
16+
Parus major
17+
18+
Note that `birdnet_analyzer.species` only generates BirdNET-format names and cannot be used to build a Perch species list.
1119

1220
You can generate a species list for a given location using :ref:`birdnet_analyzer.species <cli-species>`.
1321

0 commit comments

Comments
 (0)