Webinar ASAM OpenLABEL

Our goal is to develop a A public specification, which has been developed by experts in a defined consensus-driven development process and was released by officials that represent a significant share of the industry for which it is targeted, giving the specification the necessary legitimacy to be called a 'Standard'.Standard that is widely used and adopted. For that reason, we are asking for support from all potiantial future users of ASAM OpenLABEL and collect your feedback, ideas and further requirements that need to be considered. 

Why do we think a standard is needed?

From working with different customers, a significant fragmentation emerged in the way each individual organization categorizes and describes the objects populating the driving environment. Such categorizations and descriptions are the fundamental building block of any Autonomous Driving System’s (ADS) perception stack, since it is through them that an ADS comes to a basic and profound understanding of the status of around its surrounding.  

The lack of a common labeling A public specification, which has been developed by experts in a defined consensus-driven development process and was released by officials that represent a significant share of the industry for which it is targeted, giving the specification the necessary legitimacy to be called a 'Standard'.Standard in the industry is the root cause of several different issues:  

• Hampered Vehicle2Vehicle Interaction: The different descriptions and understandings of surroundings may cause casualties in complex situations involving two or more different ADSs 
• Precluded sharing: It is a highly difficult if not impossible task to share data across organizations that adopted different labeling taxonomies and specifications  
• Reduced annotation quality: Each individual labeling task requires ad-hoc training and even development of custom software functions that translate into a higher probability of errors and thus a threat to safety  
• Deprecation of old labels: Long-term operation of ADS development imply changes in quantity and comprehensiveness of labels to be produced considering the evolution of the driving scenes, new sensors, and scenarios. As a consequence, a flexible descriptive language is required to absorb future extensions and modifications of labels and guarantee backward-compatibility

How will ASAM OpenLABEL solve these challenges?

The OpenLABEL A public specification, which has been developed by experts in a defined consensus-driven development process and was released by officials that represent a significant share of the industry for which it is targeted, giving the specification the necessary legitimacy to be called a 'Standard'.Standard particularly focusses on the following topics:

• Objects and Scene Labeling: The standard shall describe how single objects can be labelled and how these labeled objects can be labeled in the context of a scene. This work package has several perspectives: conditional labels, event labels, action labels, relation labels. 
• Coordinate systems and sensor streams synchronization, metadata etc.
• Scenario Tagging: The standard shall define scenario labels on a meta level. This includes labels that can be derived from the content of the scenario as well as labels which are non-derivable.
• Label file format for multisensor data: The standard shall provide a JSON schema based on the input given in the concept paper. The aim is to enrich scenario artifacts (provided in any Scenario Description Language or other representations) with a set of tags to fulfil the use case of organizing, searching and filtering scenarios in scenario databases - such as the www.safeypool.ai Scenario database.

Important Features of ASAM OpenLABEL

JSON Format  
ASAM OpenLABEL will be represented in a JSON format and can therefore be easily parsed by tools and applications. ASAM OpenLABEL will specify which coordinate systems are used as reference for the Denotes the name of ECU data, as it is stored by and displayed in MCD-tools.Label. This already facilitates the conversion a lot.  

Extended Labeling Objects  
ASAM OpenLABEL will also provide methods to Denotes the name of ECU data, as it is stored by and displayed in MCD-tools.Label objects in a scene (one point in time/ frame) as well as across multiple scenes by enhancing the methods to Denotes the name of ECU data, as it is stored by and displayed in MCD-tools.Label actions, intentions and relations between objects.  

Labeling Different Data Types  
The ASAM OpenLABEL format will be capable of managing different types of labeling methods, for different types of data. This includes 2D and 3D bounding boxes, the rotation of 3D bounding boxes, semantic segmentation of images and point clouds. These semantic segmentations can be either instance classes, single/multi-class, partial or full classes.   
It is important that the labeling fits into the taxonomy definitions of a user/company. For that reason, the project group intends to provide ASAM OpenLABEL with the ability to import ontologies and taxonomies for the labeling process. The ASAM OpenLABEL project group is closely interacting with the ASAM OpenXOntology project to align ASAM OpenLABEL with the OpenX domain model and to provide requirements for the ASAM OpenXOntology A public specification, which has been developed by experts in a defined consensus-driven development process and was released by officials that represent a significant share of the industry for which it is targeted, giving the specification the necessary legitimacy to be called a 'Standard'.Standard. 

Please send your feedback to

nicco.dillmann(at)asam.net