The Cityscapes Dataset focuses on semantic understanding of urban street scenes. In the following, we give an overview on the design choices that were made to target the dataset’s focus.
Polygonal annotations
Complexity
Diversity
Volume
Metadata
Extensions by other researchers
Benchmark suite and evaluation server
Labeled foreground objects must never have holes, i.e. if there is some background visible ‘through’ some foreground object, it is considered to be part of the foreground. This also applies to regions that are highly mixed with two or more classes: they are labeled with the foreground class. Examples: tree leaves in front of house or sky (everything tree), transparent car windows (everything car).
Please click on the individual classes for details on their definitions.
Group | Classes |
---|---|
flat | road · sidewalk · parking+ · rail track+ |
human | person* · rider* |
vehicle | car* · truck* · bus* · on rails* · motorcycle* · bicycle*· caravan*+ · trailer*+ |
construction | building · wall · fence · guard rail+ · bridge+ · tunnel+ |
object | pole · pole group+ · traffic sign · traffic light |
nature | vegetation · terrain |
sky | sky |
void | ground+ · dynamic+ · static+ |
* Single instance annotations are available. However, if the boundary between such instances cannot be clearly seen, the whole crowd/group is labeled together and annotated as group, e.g. car group.
+ This label is not included in any evaluation and treated as void (or in the case of license plate as the vehicle mounted on).
Please use the following citation when referencing the dataset:
@inproceedings{cordts2016cityscapes,
title={The cityscapes dataset for semantic urban scene understanding},
author={Cordts, Marius and Omran, Mohamed and Ramos, Sebastian and Rehfeld, Timo and Enzweiler,
Markus and Benenson, Rodrigo and Franke, Uwe and Roth, Stefan and Schiele, Bernt},
booktitle={Proceedings of the IEEE conference on computer vision and pattern recognition},
pages={3213--3223},
year={2016}
}