Skip to main content
If using Windows, we recommend using 7-Zip to unzip the exported labels.

Label Coordinates

In the JSON format, label coordinates are normalized to be between 0 and 1. This means that the corners of the frame or image correspond to the coordinates (1,1), (1,0), (0,0), (0,1) regardless of frame dimensions. To get the pixel values of normalized coordinates:
  • The x and h coordinates of a label should be multiplied by the pixel width of the frame or image.
  • The y and w coordinates of a label should be multiplied by the pixel height of the frame or image.

Format of Exported Labels

The last_edited_by and last_edited_at fields are updated only when the label or its nested attributes are modified in the Label Editor. If the SDK is used to update the label, these fields must be updated manually.
The tables below provide descriptions of all values contained JSON format exports.
Exports of label versions for which the data unit was deleted vary from the examples shown below - the data_type is deleted, while image groups and image sequences only contain a single data_unit.
Exported labels include several unique identifiers that nest. The root of each label starts with the object_hash for the Ontology object or classification. Exported Label Structure

Single Images

The export contains a list of JSON objects, with each JSON object representing a single data unit and containing detailed information for all exported labels. The example below describes all the keys for a single exported data unit.
The data_units key contains all files that compose the data unit. For a given image there is only ever a single element in this list. This element contains the following information.
data_units here refer to individual files that compose a data unit, as defined in our glossary, and are not to be confused with data units elsewhere in the platform. Encord will update this nomenclature soon, but we always communicate changes to all customers first.
labels contains all object labels, classification labels, and attributes present in the image.
objects contains all object label information for the image. A key with the name of the object shape is always present - bounding_box in the example below. All shapes contain coordinates for each vertex.
Navigate to the ontology shapes section to see how all ontology classes are represented in the exported file.
The example below shows a single object instance.
KeyDescriptionNotes
objectHashThe specific label’s hashThe ‘hash’ represents a unique identifier
featureHashThe Ontology object’s hashCorresponds to the FeatureNodeHash in the ontology
nameThe object’s nameAs specified in the ontology
valueThe name given to the object
colorThe color used to draw the objectAs specified in the ontology
shapeThe Ontology class used to create the objectAs specified in the ontology
confidenceThe confidence score for this objectA confidence score of 1 is given for all labels created manually. More info can be found here
frameThe frame number of the data unit where the label appearsA frame number of 0 represents the first frame of the data unit. Images always have a frame number of 0.
createdByThe email of the user that created this object
createdAtDate and time the object was created
lastEditedByThe email of the user that last edited this object
lastEditedAtDate and time the object was last edited
manualAnnotationA field indicating whether the object was drawn manually or nottrue means it was drawn manually, while false means it was created using a model or an automated labeling technique
boundingBoxA list containing the coordinates for the bounding boxRefer to the Ontology shapes section for more details
classifications contains all classification information for the image.The following example shows a single object instance.
object_answers is a list of objects that have at least one nested attribute and contains information for all attributes. Expanding object_answers reveals the following:
Contains a list of classifications that apply to entire frames or slices. classification_answer is represented by its hash. Expanding classification_answers reveals the following:
The export_history contains a list of all exports for this data unit, the first entry being the current export. Each instance contains the following:

Image Groups & Image Sequences

The export contains a list of JSON objects, with each JSON object representing a single image group or image sequence, and containing detailed information for all exported labels. The example below describes all the keys for a single exported data unit.

The data_units key contains a list of all files that compose the image group or image sequence (sometimes referred to as frames). It contains the following information.
data_units here refer to individual files that compose a data unit, as defined in our glossary, and are not to be confused with data units elsewhere in the platform. Encord will update this nomenclature soon, but we always communicate changes to all customers first.
Each number within labels represents an individual frame within the image group or sequence. Each frame contains the following:
objects contains label information for all object instances in a frame. A key with the name of the object shape is always present - bounding_box in the example below. All shapes contain coordinates for each vertex.
Navigate to the Ontology shapes section to see how all Ontology classes are represented in the exported file.
The example below shows a single object instance.
classifications contains all frame level classification information for the image group or sequence.The example below shows a single classification instance.
object_answers is a list of objects that have at least one nested attribute and contains information for all attributes. Expanding object_answers reveals the following:
Contains a list of classifications that apply to entire frames or slices. classification_answer is represented by its hash. Expanding classification_answers reveals the following:
The export_history contains a list of all exports for this data unit, the first entry being the current export. Each instance contains the following:

Videos

The export contains a list of JSON objects, with each JSON object representing a single data unit and containing detailed information for all exported labels. The example below describes all the keys for a single exported data unit.

The data_units key contains all files that compose the data unit. For a given video there is only a single element in this list. This element contains the following information.
data_units here refer to individual files that compose a data unit, as defined in our glossary, and are not to be confused with data unit elsewhere in the platform. Encord will update this nomenclature soon, but we always communicate changes to all customers first.
Each number within labels represents an individual frame within the data unit. Each frame contains the following:
objects contains label information for all object instances in a frame. A key with the name of the object shape is always present - bounding_box in the example below. All shapes contain coordinates for each vertex.
Navigate to the Ontology shapes section to see how all Ontology classes are represented in the exported file.
The following example shows a single object instance.
classifications contains all frame level classification information for the video.The example below shows a single classification instance.
object_answers is a list of objects that have at least one nested attribute and contains information for all attributes. Expanding object_answers reveals the following:
Contains a list of classifications that apply to entire frames or slices. classification_answer is represented by its hash. Expanding classification_answers reveals the following:
The export_history contains a list of all exports for this data unit, the first entry being the current export. Each instance contains the following:

DICOM

The export contains a list of JSON objects, with each JSON object representing a single data unit and containing detailed information for all exported labels. The following example describes all the keys for a single exported data unit.

The data_units key contains all files that compose the data unit.
data_units here refer to individual files that compose a data unit, as defined in our glossary, and are not to be confused with data units elsewhere in the platform. Encord will update this nomenclature soon, but we always communicate changes to all customers first.
Each number within labels represents an individual slice or frame within the data unit. Each slice or frame contains the following:
objects contains label information for all object instances in a frame. A key with the name of the object shape is always present - polygon in the example below. All shapes contain coordinates for each vertex.
Navigate to the Ontology shapes section to see how all Ontology classes are represented in the exported file.
The example below shows a single object instance.
classifications contains all frame level classification information for the slice.The example below shows a single classification instance.
The slice metadata contains information on the DICOM study, the DICOM series, as well as the patient.
object_answers is a list of objects that have at least one nested attribute and contains information for all attributes. Expanding object_answers reveals the following:
classification_answers a list of frame classifications in which each classification is represented by its hash. Expanding classification_answers reveals the following:
The export_history contains a list of all exports for this data unit, the first entry being the current export. Each instance contains the following:

Audio

The export contains a list of JSON objects, with each JSON object representing a single data unit and containing detailed information for all exported labels. The example below describes all the keys for a single exported data unit.
classification_answers a list of frame classifications in which each classification is represented by its hash. Expanding classification_answers reveals the following:
The data_units key contains all files that compose the data unit. For a given image there is only ever a single element in this list. This element contains the following information.
data_units here refer to individual files that compose a data unit, as defined in our glossary, and are not to be confused with data units elsewhere in the platform. Encord will update this nomenclature soon, but we always communicate changes to all customers first.
object_answers contains all the object labels that have at least one nested attribute and contains information for all attributes. Expanding object_answers reveals the following:

Text

The export contains a list of JSON objects, with each JSON object representing a single data unit and containing detailed information for all exported labels. The example below describes all the keys for a single exported data unit.
classification_answers a list of frame classifications in which each classification is represented by its hash. Expanding classification_answers reveals the following:
The data_units key contains all files that compose the data unit. For a given image there is only ever a single element in this list. This element contains the following information.
data_units here refer to individual files that compose a data unit, as defined in our glossary, and are not to be confused with data units elsewhere in the platform. Encord will update this nomenclature soon, but we always communicate changes to all customers first.
object_answers contains all the object labels that have at least one nested attribute and contains information for all attributes. Expanding object_answers reveals the following:

PDF

The data_units key contains all files that compose the data unit. For a given image there is only ever a single element in this list. This element contains the following information.
data_units here refer to individual files that compose a data unit, as defined in our glossary, and are not to be confused with data units elsewhere in the platform. Encord will update this nomenclature soon, but we always communicate changes to all customers first.

PCD

The data_units key contains all files that compose the data unit. For a given image there is only ever a single element in this list. This element contains the following information.
data_units here refer to individual files that compose a data unit, as defined in our glossary, and are not to be confused with data units elsewhere in the platform. Encord will update this nomenclature soon, but we always communicate changes to all customers first.

Ontology Shapes

Exports contain the Ontology shape coordinates used to create the label.
x and y represent coordinates of the top-left corner of the box. h and w respectively represent the height and width of the box.
This is a legacy field used by existing customers. We recommend new customers use the polygons field below.
The polygon list contains the x and y coordinates for all vertices in a simple polygon. For complex polygons, see the polygons field below.
Polygons can have complex shapes, including being enclosed in one another, and encompassing separate regions. In each case the polygon’s coordinates are arranged in a different way.
Polylines contain the x and y coordinates for each vertex.
Keypoints are represented in the export using only x and y coordinates.
x and y represent the coordinates of the top-left corner of the unrotated box. h and w respectively represent the height and width of the box, while theta represents the angle of clockwise rotation of the bounding box about the center of the box.
The rleString encodes the Bitmask label, and has to be decoded. See our SDK documentation to learn how to decode an rleString.
Object primitives are referred to as skeletons in the export. Each point on the object primitive is represented in the export using x and y coordinates.Below is an example of an object primitive with 3 points.
Cuboid labels are 3D labels and therefore contain the position, orientation, and dimensions of the cuboid.
Segmentations are exported as rleStrings. See our section on exporting Bitmasks & Segmentations to learn more.

Export Bitmasks & Segmentations

Bitmask labels are exported as rleStrings. See our SDK documentation to learn how to decode an rleString.
We strongly recommend exporting Bitmask labels using the Encord SDK. Bitmasks are exported in the JSON format.

Exporting Data Groups

When exporting Data Group labels, 1 JSON file the Data Group plus 1 JSON for each data unit in the Data Group are generated.
Data Groups Label Export

Multi-Layer Data Groups

Multi-layer Data Groups contain a root key that contains properties pertaining to the Data Group as a whole.

Exporting Labels using the SDK

Go here to learn how to export labels using SDK.

Label Branches

The branch associated with the labels is specified using the branch_name key. The main branch is always displayed first and is identified by the following value: