Skip to main content

Prerequisites for Annotation

Before scenes can be annotated a few things need to be in place. From a developer perspective there is not too much to do; this is mostly organization and workforce level preparation, but it is good to be aware of the process.

Projects and Requests

A scene is sent for annotation by adding it to a Request, creating what we call and Input, which has its own UUID. This is detailed on the next page.

The request is part of a Batch, itself part of a Project. Projects and initial Requests and Batches may be set up, possibly in conjunction with Perception Experts from Kognic, during the onboarding/setup phase for new customers. They may also be managed independently or in conjunction with a BPO who provides annotation services through the Kognic platform.

  • Projects can be created in the Kognic Platform, under Project Management > Create new project.
  • Requests can be created in the Kognic Platform, under Project Management > Project > (your project) > Create new request.

Taxonomies & Annotation Instruction

The taxonomy defines the "what" of annotation: what is there to annotate, and hence what does the resulting annotation describe? The classes of object and the domain and range of their properties, plus annotatable properties of the scene.

In essence, the Annotation Instruction defines the arrangements for the annotation process itself: for example that polylines are to be drawn to label lane markings.

Annotation instructions can be created in the Kognic Platform, under Project Management > Annotation Instructions.

Projects, Requests, Taxonomies and Annotation Instructions are not required to exist or be completely configured in order to upload scenes. However, the relevant configuration must have been completed in the Kognic Platform before scenes can be added to requests, and hence before they can be annotated.