This elephant dataset was provided by researchers from the Elephant Listening Project (ELP) at the Cornell University Ithaca, who are conducting research on forest elephants visiting the Dzanga bai clearing in the Dzanga-Ndoki National Park in the Central African Republic. It was devised for re-identification of elephants that have been documented before. The images have been taken over a range of about 15 years.
To get a download link for the dataset, please write an E-mail to matthias(dot)koerschens(at)uni-jena(dot)de stating your name, institution and acknowledgement of the license terms.
Statistics of the datasets
The dataset comprises 2078 images with 276 elephant individuals, i.e. classes. The distribution of the images over the classes is very unequal, as can be seen in the diagram below. We can see that there are many classes with only 3-5 images. The minimum number of images per class is one and the maximum 22. Thus, the dataset is very imbalanced. As the defining features for elephants are very subtle, this dataset can be viewed as a fine-grained classification dataset.It should also be noted that there is a small number of duplicate images in the dataset (~30). This dataset has no overlap with any other computer vision image datasets.
Use of dataset
The dataset is divided into a training and a validation part. For this we did a 75%/25% stratified split, resulting in 1573 training and 505 validation images. Classes with >1 image have at least 1 image in the validation set, classes with only 1 image are only contained in the training set.
The image names consist of an elephant ID separated by an underscore by the rest of the name, e.g. ’15_4th Tuskless VI_Apr2003.jpg’. Usually the ID is an integer, but as we corrected some wrong labels by adding 00 to the ID to designate a different ID for a different elephant, where the actual ID is unknown, parsing these IDs as integers will result in errors. For this, please use either the provided class mapping in the file ‘class_mapping.txt’ from the original IDs to an integer value starting at 0, or create your own mapping.
train.txt and val.txt
These files share the same structure: two columns, separated by a tabulator character (‘\ŧ’), the first of which designates the original ID of the elephant, and the second the name of the image belonging to the class label.
This file consists of two columns, which are separated by a tabulator character (‘\t’), whereas the first column designates the original ID of the elephant and the second column contains the new mapped 0-indexed integer value, which can be used for encoding the classes.
We would like to thank the members of the Elephant Listening Project, especially Peter Wrege, for providing us with this dataset and allowing us to make it available to the scientific community. Additionally, we would like to thank Andrea Turkalo and Daniela Hedwig for acquiring the images in this dataset during their work in the Kongo.
This dataset is only to be used for non-commercial research purposes. Please find the full license text below.
Usage of the dataset implies the agreement to the following license terms:
1. This dataset is only to be used for research purposes.
2. Redistribution in any form as well as commercial use is strictly forbidden without explicit agreement of the copyright holders. In case of redistribution, appropriate credit to the copyright holders must be given and this License Agreement must be provided.
Additionally anyone using this dataset agrees to the following conditions:
THIS DATASET IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
HOLDER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.