Key concepts

below follows descriptions of common concepts used by kognic, in the annotation platform and this documentation guideline each project comes with its own guideline it will describe what you want to be annotated/the client wants you to annotate, how to annotate it, and give you visual examples of how to interpret the given instructions input batch and input an input batch is a group of inputs an input is a set of sensor data you want to annotate it usually consists of at least one image/frame it can also contain images from several cameras, a point cloud, a video, or a sequence of images project annotation work on different tasks or task types is always grouped by projects the projects and their content is defined by kognic and its clients (annotation) request annotation request is the major concept in the organization of annotation work at kognic a request can also be viewed as a subproject there can be multiple types of requests in one project the type of request determines what interface and annotation tool you/or the annotators will work in/ with a single request ties together input data with the annotation guideline, the taxonomy, the annotator/reviewer/supervisor team, and configuration of the annotation tool as well as the workflow the request has all the information needed to produce the annotations on the input data workflow stage on the input's way toward getting a delivery ready annotation, it goes through a series of workflow stages each stage corresponds to one action in one of the workflow's different phases, such as the action “correct” in the phase “review” which stages the input goes through depends on the workflow used in the request an input can only be in one workflow stage at a time task tasks are created in each of the request's workflow stages and become available for team members to complete the most common task actions are annotate, correct, and review annotate an annotate task will be assigned with the purpose of being annotated from scratch correct a task where you are asked to correct a task with existing annotations the annotation you are asked to correct can be from someone else or your own in the kognic platform, we have multiple different types of correction tasks, you can read more about them under introduction docid\ bgtv8prkhlmdeoxebbu31 review in a review task, you are asked to determine if an annotation is of acceptable or unacceptable quality if the task is of unacceptable quality you are also expected to provide correction requests and feedback to the annotator so they can improve the quality while becoming a more skilled annotator objects and shapes an object is a unique object in the world that can be annotated in multiple sensors or multiple frames an object has a unique object id, which is visible in the annotation tool's object list a shape is the representation of an object in a specific sensor and in a specific time frame examples if you work in a sequence task with one sensor there can, for one object, exist a maximum of one shape per frame if you work on an image task with one 2d sensor and one 3d sensor there can exist two shapes per object, one in 2d and one in 3d if you work in a sequence task with one 2d sensor and one 3d sensor there can maximum exist two shapes per frame per object