objects
An object represents information about physical entities that exist within a given scene, such as people, cars, or lane markings in the real world.
An object key is composed of various pieces of information, including the object's name, type, and annotation location (like a bounding box location array). Each key uses a unique UUID as its identifier.
The dynamic information related to an object, denoted by ${OBJECT_UUID}, is described under a specific frame. This information encompasses data that changes over time, such as the location, velocity, and orientation of the object within the scene.
Hint
The objects infomation under a specific frame are used to describe dynamic objects. The infomation changes over time, such as the location, velocity, and orientation of the object within the scene.
Schema
Example
#Objects {}
name | description | type | required |
---|---|---|---|
${OBJECT_UUID} | The id of the object. It uses UUID32 as a key. | object | true, unique |
type | The object class name. (ex. people) | string | true |
name | The unique name of this object. (ex. Amy) | string | false |
object_data | It refers to information used to describe a particular object such as annotation shapes, attributes, or metrics. The ${OBJECT_TYPE} can be found in the accompanying documentation: ➤ bbox ➤ cuboid ➤ poly2d ➤ point2d ➤ binary ➤➤ attributes | object | true |
Use Case
More infomation on
pageUse Casebbox
To describe a bbox dataset with one camera sensor:
pagebboxbbox + cuboid (3D)
To describe a dataset with one camera sensor (bbox annotation) and one lidar sensor (cuboid annotation) in the coordinate system of iso8855-1:
pagebbox + cuboid (3d)semantic segmentation
To describe a semantic segmentation dataset with one camera sensor:
pagesemantic segmetationLast updated