In order to work with the scenario database a technical integration into the tool landscape needs to be established. Therefore the scenario format (required and available within the scenario database) needs to be known, understood and applicable. The format describes the scenarios in a scenario description language (which can be e.g. OpenScenario), see (Weber, H. et al., 2023). The format itself describes the structure of a scenario; a common structure is the 6 layer model created in the PEGASUS project, as described in (Scholtes et al., 2021), but also other structures are possible and available.
Different companies and different research activities have created different formats for scenario description in the last years. Often these formats can be converted and also the description languages can be converted, but this requires additional processing steps and therefore need to be known beforehand.
Main Question
Is a scenario format for the scenarios in the database available?
Alternative Questions:
- Is a required scenario format needed?
- Is the data format for the scenario database known?
References
- Weber, H. et al. (2023) ‘Holistic driving scenario concept for urban traffic’, 2023 IEEE Intelligent Vehicles Symposium (IV). doi: https://doi.org/10.1109/iv55152.2023.10186385
- Scholtes, M. et al. (2021) ‘6-layer model for a structured description and categorization of urban traffic and environment’, IEEE Access, 9, pp. 59131–59147. https://doi.org/10.1109/access.2021.3072739