The LostAndFound Dataset addresses the problem of detecting unexpected small obstacles on the road often caused by lost cargo.
The dataset comprises 112 stereo video sequences with 2104 annotated frames (picking roughly every tenth frame from the recorded data).
If you are using this dataset in a publication please cite the following paper:
Peter Pinggera, Sebastian Ramos, Stefan Gehrig, Uwe Franke, Carsten Rother, Rudolf Mester, "Lost and Found: Detecting Small Road Hazards for Self-Driving Vehicles", Proceedings of IROS 2016, Daejeon, Korea. Link to the paper
(This material is presented to ensure timely dissemination of scholarly and technical work. Copyright and all rights therein are retained by authors or by other copyright holders. All persons copying this information are expected to adhere to the terms and constraints invoked by each author's copyright. In most cases, these works may not be reposted without the explicit permission of the copyright holder.)
For the data format and the interpretation of the data sources we refer to the description of the Cityscapes dataset format which we closely follow: http://www.cityscapes-dataset.com
Below you can find a link to the data description and some development kit (tailored for Cityscapes but applicable to LostAndFound as well):
In order to replace the cityscapes mapping with lostAndFound labels replace labels.py in the development kit with this file: labels.py
A description of the labels of the LostAndFound dataset can be found here: laf_table.pdf
In the near future we will publish results on the dataset for several metrics. Stay tuned for more. If you want to appear on the list write an e-mail to Sebastian Ramos (firstname.lastname@example.org).
Below, you can find all currently available downloads. A README and various scripts for inspection, preparation, and evaluation can be found in above git repository.
The following packages are available for download:
The LostAndFound dataset may be used according to the following license agreement: license.txt
For questions, suggestions, and comments contact Sebastian Ramos (email@example.com) or Stefan Gehrig.