sieann commited on
Commit
049a11b
·
verified ·
1 Parent(s): 3d176d2

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +169 -7
README.md CHANGED
@@ -35,19 +35,39 @@ size_categories:
35
  <!-- Provide a quick summary of the dataset. -->
36
  The GTSRB subset of the <em>Synset Signset Germany</em> dataset addresses the task of traffic sign recognition in Germany. It contains the same 43 traffic
37
  sign classes as the well-known [GTSRB](https://ieeexplore.ieee.org/abstract/document/6033395) dataset and thus represents its “synthetic twin”. For each class, the dataset
38
- contains 500 images, accumulating to 21,500 images in total.
39
 
40
- **Website**: [synset.de/datasets/synset-signset-ger/](https://synset.de/datasets/synset-signset-ger/) <br>
41
  **Paper:** Sielemann, A., Loercher, L., Schumacher, M. L., Wolf, S., Roschani, M., Ziehn, J. and Beyerer, J. (2024). [Synset Signset Germany: a Synthetic Dataset for German Traffic Sign Recognition](https://ieeexplore.ieee.org/abstract/document/10920175). In 2024 IEEE International Conference on Robotics and Automation (ICRA). [[arXiv](https://arxiv.org/abs/2512.05936)] <br>
42
  **Authors:** [Anne Sielemann](https://www.linkedin.com/in/anne-sielemann-23011026a/), Lena Lörcher, Max-Lion Schumacher, [Stefan Wolf](https://www.linkedin.com/in/stefan-wolf-2552211a9/),
43
  Masoud Roschani, [Jens Ziehn](https://www.linkedin.com/in/jrziehn/), and Juergen Beyerer. [Fraunhofer IOSB](https://www.iosb.fraunhofer.de/) and [Fraunhofer IPA](https://www.ipa.fraunhofer.de/), Germany. <br>
44
  **Funded by:** [Fraunhofer](https://www.fraunhofer.de/en.html) Internal Programs under Grant No. PREPARE 40-02702 within the ML4Safety project and the [German Federal Ministry for Economic Affairs and Climate Action](https://www.bundeswirtschaftsministerium.de/Navigation/EN/Home/home.html), within the program “New Vehicle and System Technologies” as part of the [AVEAS](https://aveas.org/) research project. <br>
45
  **License:** CC-BY 4.0 <br>
46
 
47
- ## Citation
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
48
 
49
  <!-- If there is a paper or blog post introducing the dataset, the APA and Bibtex information for that should go in this section. -->
50
 
 
 
51
  **BibTeX:**
52
 
53
  @inproceedings{synset_signset_ger_sielemann_2024,
@@ -59,12 +79,143 @@ Masoud Roschani, [Jens Ziehn](https://www.linkedin.com/in/jrziehn/), and Juergen
59
 
60
  **APA:**
61
 
62
- Sielemann, A., Loercher, L., Schumacher, M., Wolf, S., Roschani, M., Ziehn, J., and Beyerer, J. (2024).<br>
63
- Synset Signset Germany: A Synthetic Dataset for German Traffic Sign Recognition. <br>
64
- In 2024 IEEE 27th International Conference on Intelligent Transportation Systems (ITSC).
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
65
 
66
  ## Bias, Risks, and Limitations
67
 
 
 
 
 
 
 
 
 
 
 
 
 
 
68
  ### Recommendations
69
 
70
  <!-- This section is meant to convey recommendations with respect to the bias, risk, and technical limitations. -->
@@ -72,7 +223,18 @@ In 2024 IEEE 27th International Conference on Intelligent Transportation Systems
72
  <!-- Users should be made aware of the risks, biases and limitations of the dataset. More information needed for further recommendations. -->
73
 
74
  It is recommended to use the dataset primarily for scientific research. Application to practical real-world use cases should include
75
- human oversight and the exhaustive evaluation of the fitness for the respective purpose, including the impact of domain shifts.
 
 
 
 
 
 
 
 
 
 
 
76
 
77
  ## Dataset Card Contact
78
 
 
35
  <!-- Provide a quick summary of the dataset. -->
36
  The GTSRB subset of the <em>Synset Signset Germany</em> dataset addresses the task of traffic sign recognition in Germany. It contains the same 43 traffic
37
  sign classes as the well-known [GTSRB](https://ieeexplore.ieee.org/abstract/document/6033395) dataset and thus represents its “synthetic twin”. For each class, the dataset
38
+ contains 500 images, accumulating to 21,500 independent images in total.
39
 
40
+ **Website:** [synset.de/datasets/synset-signset-ger/](https://synset.de/datasets/synset-signset-ger/) <br>
41
  **Paper:** Sielemann, A., Loercher, L., Schumacher, M. L., Wolf, S., Roschani, M., Ziehn, J. and Beyerer, J. (2024). [Synset Signset Germany: a Synthetic Dataset for German Traffic Sign Recognition](https://ieeexplore.ieee.org/abstract/document/10920175). In 2024 IEEE International Conference on Robotics and Automation (ICRA). [[arXiv](https://arxiv.org/abs/2512.05936)] <br>
42
  **Authors:** [Anne Sielemann](https://www.linkedin.com/in/anne-sielemann-23011026a/), Lena Lörcher, Max-Lion Schumacher, [Stefan Wolf](https://www.linkedin.com/in/stefan-wolf-2552211a9/),
43
  Masoud Roschani, [Jens Ziehn](https://www.linkedin.com/in/jrziehn/), and Juergen Beyerer. [Fraunhofer IOSB](https://www.iosb.fraunhofer.de/) and [Fraunhofer IPA](https://www.ipa.fraunhofer.de/), Germany. <br>
44
  **Funded by:** [Fraunhofer](https://www.fraunhofer.de/en.html) Internal Programs under Grant No. PREPARE 40-02702 within the ML4Safety project and the [German Federal Ministry for Economic Affairs and Climate Action](https://www.bundeswirtschaftsministerium.de/Navigation/EN/Home/home.html), within the program “New Vehicle and System Technologies” as part of the [AVEAS](https://aveas.org/) research project. <br>
45
  **License:** CC-BY 4.0 <br>
46
 
47
+ ## Description
48
+
49
+ The <em>Synset Signset Germany - GTSRB Subset</em> is a subset of 43 classes of the synthetic
50
+ [Synset Signset Germany](https://huggingface.co/datasets/FraunhoferIOSB/Synset-Signset-Germany) dataset, which is designed to address the task of traffic sign recognition
51
+ for the country of Germany. It is intended to be a “synthetic twin” of the well-known <em>German Traffic Sign Recognition Benchmark</em> (GTSRB) and is thus well-suited
52
+ for comparing real-world and synthetic data. Thanks to the extensive metadata, it can also be used for applications in the context of explainable AI (XAI) or robustness
53
+ analyzes and systematic tests.
54
+
55
+ Our data generation approach is based on the Fraunhofer simulation platform [OCTAS®](https://octas.org/) following the general framework of physically-based rendering.
56
+ It combines the advantages of data-driven and analytical modeling approaches: GAN-based texture generation is employed to produce data-driven dirt and wear artifacts,
57
+ resulting in unique and realistic traffic sign surfaces. In parallel, analytical scene modulation ensures physically accurate illumination and appropriate geometric
58
+ transformations, while also enabling fine-grained parameterization of the rendered scenes.
59
+
60
+ For each of the 43 traffic sign classes, the dataset contains 500 RGB images, accumulating to 21,500 independent images in total. All images were rendered by the
61
+ rasterization-based engine [OGRE](https://ogre3d.org) as well as by the path tracing engine [Cycles](https://www.cycles-renderer.org/). In addition to a sample-wise mask
62
+ and segmentation image, the dataset also contains extensive metadata, including the stochastically selected environment and imaging effect parameters for each image.
63
+
64
+
65
+ ## Citation and Reference
66
 
67
  <!-- If there is a paper or blog post introducing the dataset, the APA and Bibtex information for that should go in this section. -->
68
 
69
+ To cite this dataset in your scientific work, please use the following bibliography entry:
70
+
71
  **BibTeX:**
72
 
73
  @inproceedings{synset_signset_ger_sielemann_2024,
 
79
 
80
  **APA:**
81
 
82
+ Sielemann, A., Loercher, L., Schumacher, M., Wolf, S., Roschani, M., Ziehn, J., and Beyerer, J. (2024).
83
+ Synset Signset Germany: A Synthetic Dataset for German Traffic Sign Recognition.
84
+ In 2024 IEEE 27th International Conference on Intelligent Transportation Systems (ITSC).
85
+
86
+ In case of copying and redistributing, or publishing an adapted version of our dataset, please provide the name of our dataset, the creator names, a copyright notice,
87
+ a link to this website, a license notice with a link to the license, and, if changes were made, a disclaimer notice, and a short description of the applied changes.
88
+ For example, as follows:
89
+
90
+ This work is based on the Synset Signset Germany Dataset
91
+ by Anne Sielemann, Lena Loercher, Max-Lion Schumacher, Stefan Wolf, Jens Ziehn, Masoud Roschani, and Juergen Beyerer,
92
+ © 2024 Fraunhofer IOSB, All rights reserved.
93
+ Link: https://synset.de/datasets/synset-signset-ger/
94
+ Licence: CC BY 4.0, https://creativecommons.org/licenses/by/4.0/
95
+ Disclaimer: The original authors are neither affiliated nor responsible for any applied changes.
96
+
97
+ ## Uses
98
+
99
+ The dataset is designed for the task of traffic sign recognition in Germany.
100
+
101
+ ### Direct Use
102
+
103
+ <!-- This section describes suitable use cases for the dataset. -->
104
+
105
+ The dataset is intended for the following use cases:
106
+ - Training ML models for the task of German traffic sign recognition
107
+ - Analyzing the difference between the synthetic dataset and real-world traffic sign recognition datasets, especially the closely related
108
+ [GTSRB](https://ieeexplore.ieee.org/abstract/document/6033395) dataset.
109
+ - Testing ML models for the task of traffic sign recognition, in particular by using the detailed meta data of each image
110
+
111
+ ### Out-of-Scope Use
112
+
113
+ <!-- This section addresses misuse, malicious use, and uses that the dataset will not work well for. -->
114
+
115
+ The dataset should not be used for critical applications, particularly high-risk applications as named by the European AI Act under Annex III (which includes "AI systems intended to be used for the ‘real-time’ and ‘post’ remote biometric
116
+ identification of natural persons" and "AI systems intended to be used as safety components in the management and operation of road traffic"), without exhaustive
117
+ research into the fitness of the dataset, to evaluate whether it is "relevant, sufficiently representative, and to the best extent possible free of errors and complete
118
+ in view of the intended purpose of the system." No such claim is not made with the publication of this dataset.
119
+
120
+ ## Dataset Structure
121
+
122
+ <!-- This section provides a description of the dataset fields, and additional information about the dataset structure such as criteria used to create the splits, relationships between data points, etc. -->
123
+
124
+ The dataset is available in two rendering variants:
125
+
126
+ - Rendering performed by the [OCTAS®](https://octas.org/) API to [OGRE](https://ogre3d.org) engine interface.
127
+ - Rendering performed by the [OCTAS®](https://octas.org/) API to [Cycles](https://www.cycles-renderer.org/) engine interface.
128
+
129
+ Both variants include the 43 GTSRB traffic sign classes with 500 images each, leading to a total of 21,500 images.
130
+
131
+ Each of the 21,500 renderings contains the raw image (i.e., the simulated camera image), a semantic segmentation image, a mask image,
132
+ and metadata about the traffic sign status (orientation, upper signs, lower signs, etc.), the environment (daytime, contrast, location, etc.), and the imaging effects
133
+ (noise level, motion blur strength, aec error, etc.).
134
+
135
+ The dataset provides an exemplary training and validation split.
136
+
137
+ ## Dataset Creation
138
+
139
+ ### Curation Rationale
140
+
141
+ <!-- Motivation for the creation of this dataset. -->
142
+
143
+ The use case of traffic sign recognition has the advantages of, on the one hand, representing a well-understood and established task that provides a wide range of
144
+ publicly available datasets and applicable models. On the other hand, it remains the subject of active research, in particular, to address challenges such as corner
145
+ cases and weather conditions, and it has practical relevance, for example, for driver assistance systems, automated driving, and mapping. Since new traffic signs are
146
+ constantly being released (2020 in Germany) and the coverage of existing signs in publicly available datasets is still limited for a distinction of less common classes,
147
+ the demand for both training and testing data still persists.
148
+
149
+ The dataset was designed to be comparable to the [GTSRB](https://ieeexplore.ieee.org/abstract/document/6033395) dataset, one of the best known available
150
+ traffic sign recognition benchmark datasets.
151
+
152
+ Furthermore, it was aimed at providing detailed metadata to enable dataset uses such as XAI analyzes and robustness checks.
153
+
154
+ ### Source Data
155
+
156
+ <!-- This section describes the source data (e.g. news text and headlines, social media posts, translated sentences, ...). -->
157
+
158
+ - The dataset was generated in the [OCTAS®](https://octas.org/) simulation framework, by using rasterization trough the [OGRE](https://ogre3d.org) engine, as well as
159
+ path tracing through the [Cycles](https://www.cycles-renderer.org/) engine developed by the [Blender Project](https://docs.blender.org/manual/en/latest/render/cycles/index.html).
160
+
161
+ - The traffic sign template images, which are used as input to the GAN-based texture synthesis, stem from the [Wikipedia overview of German traffic signs](https://de.wikipedia.org/wiki/Bildtafel_der_Verkehrszeichen_in_der_Bundesrepublik_Deutschland_seit_2017).
162
+
163
+ - Image-based lighting (IBL) uses 327 environment maps from [PolyHaven](https://polyhaven.com/).
164
+
165
+ - The 3D geometry of the tree that serves as an occlusion object originates from [PolyHaven](https://polyhaven.com/).
166
+
167
+ #### Who are the source data producers?
168
+
169
+ <!-- This section describes the people or systems who originally created the data. It should also include self-reported demographic or identity information for the source data creators if this information is available. -->
170
+
171
+ - [PolyHaven](https://polyhaven.com/), as the provider of the environment maps for image-based lighting (IBL) and the 3D tree object, is an online library for open (CC0)
172
+ 3D assets provided by different authors.
173
+
174
+ - [Wikipedia](https://de.wikipedia.org/), one of the largest free multilingual open-content encyclopedias, includes the complete list of existing German traffic signs
175
+ and their template images.
176
+
177
+ ### Annotations
178
+
179
+ <!-- If the dataset contains annotations which are not part of the initial data collection, use this section to describe them. -->
180
+
181
+ #### Annotation process
182
+
183
+ <!-- This section describes the annotation process such as annotation tools used in the process, the amount of data annotated, annotation guidelines provided to the annotators, interannotator statistics, annotation validation, etc. -->
184
+
185
+ The major part of the annotations, including masks, segmentation images, camera parameters and artifacts, and environmental conditions, is based on ground truth data created
186
+ as part of the scene generation / rendering process. Semantic segmentation images were rendered using the [Ogre](https://www.ogre3d.org/) rendering engine plugin for
187
+ [OCTAS®](https://octas.org/), which provides rasterization / shading-based image generation.
188
+
189
+ The only manual annotation performed in the creation of the particular dataset is the labeling of permissible upper and lower signs taking the
190
+ German traffic code / regulation [StVO](https://www.stvo2go.de/verkehrszeichen-wissensnetz/) (Straßenverkehrs-Ordnung) and real-world examples into account.
191
+
192
+ #### Who are the annotators?
193
+
194
+ <!-- This section describes the people or systems who created the annotations. -->
195
+
196
+ The annotation of the permissible upper and lower signs was performed by the authors.
197
+
198
+ #### Personal and Sensitive Information
199
+
200
+ <!-- State whether the dataset contains data that might be considered personal, sensitive, or private (e.g., data that reveals addresses, uniquely identifiable names or aliases, racial or ethnic origins, sexual orientations, religious beliefs, political opinions, financial or health data, etc.). If efforts were made to anonymize the data, describe the anonymization process. -->
201
+
202
+ The dataset contains no data that might be considered personal, sensitive, or private.
203
 
204
  ## Bias, Risks, and Limitations
205
 
206
+ <!-- This section is meant to convey both technical and sociotechnical limitations. -->
207
+
208
+ - **Traffic Signs:** The wear and tear generation is limited to artifacts such as color fading, scratches, screw holes, and sticker residues.
209
+ Complex stickers, graffiti, or dirt are not included. Retroreflector patterns are excluded, and retroreflection is not simulated.
210
+ The traffic signs are solely mounted on metallic traffic sign poles.
211
+
212
+ - **Environment:** Environmental variation includes no adverse weather conditions (snow, raindrops, fog, ...).
213
+
214
+ - **Occlusions:** All included occlusions or shadows stem from a single 3D tree geometry.
215
+
216
+ - **Camera:** Only one set of intrinsic camera parameters is used, and only a single camera lens type (based on a Tamron M112FM35 35 mm lens) is simulated.
217
+ It can be assumed that the set of simulated imaging artifacts is not complete.
218
+
219
  ### Recommendations
220
 
221
  <!-- This section is meant to convey recommendations with respect to the bias, risk, and technical limitations. -->
 
223
  <!-- Users should be made aware of the risks, biases and limitations of the dataset. More information needed for further recommendations. -->
224
 
225
  It is recommended to use the dataset primarily for scientific research. Application to practical real-world use cases should include
226
+ human oversight and exhaustive evaluation of the fitness for the respective purpose, including the impact of domain shifts.
227
+
228
+ <!--
229
+ ## Glossary [optional]
230
+
231
+ If relevant, include terms and calculations in this section that can help readers understand the dataset or dataset card.
232
+
233
+ [More Information Needed]
234
+
235
+ ## More Information [optional]
236
+
237
+ [More Information Needed]-->
238
 
239
  ## Dataset Card Contact
240