Categories and task attributes
When editing the category and task attribute configuration directly, you need to adhere to the following format:
Configuration format
Name | Type | Description |
---|---|---|
|
| Required. List of all possible categories for a label in this dataset. |
|
| List of image-level attributes. |
|
| The radius of the circle around the ego position in the 3D cuboid and vector interface. Can be used to indicate a region in which objects should be annotated. |
The categories
array should contain at least one category.
Category
Name | Type | Description |
---|---|---|
|
| Required. Name of the category. |
|
| Required. Index of the category. |
|
| RGB color of the category. |
|
| Whether the category contains instances (person, car) or not (sky, road) |
|
| List of object-level attributes. |
|
| |
... | ... | Other key-value pairs can be supplied, but will be ignored. |
Attribute
Name | Type | Description |
---|---|---|
|
| Required. Name of the attribute. |
|
| Required. Type of the attribute. |
|
| Required when |
|
| Valid when |
|
| Valid when |
|
| Valid when |
|
| Default value of the attribute. |
|
| Valid when |
|
| Valid in sequence datasets. Whether an attribute should remain constant across all frames for an object with a certain track ID. If false, the attribute can change each frame. |
Additional examples
Note that the inline comments in the examples should be left out, as comments of the form//…
or /*…*/
are not allowed in JSON.
Last updated