Exporting Labels
Exporting labels from Annotation Projects (Workflows)
To train your models you must export your labels.
- Navigate to Labels and export on the Project Dashboard
- Select the Data tab.
- Select the data units you want to export labels for.
- Click the Export and save button. A pop-up appears.
- Give this label version a name.
- Select whether you want your labels to be exported in JSON or COCO format.
- Toggle this if you want to include signed URLs in your export.
- Select which label status(es) to include in the export.
- Select what objects to include in the export.
- Click Export and save to export your labels.
Exporting labels from Manual QA Projects
Learn how to export data Manual QA Projects by watching this video.
The Export tab is where you export the labels and classifications created in a Project.
A. Select the files you want to export labels for by clicking the checkboxes next to the files you’d like to include in your export. Click the Export to export the selected data.
B. Select the format for your exported data; COCO or JSON.
C. Toggle this switch if you want to include signed URLs in your export.
D. Select the label status of the annotations you want to be included in the export.
E. Select the objects you want to include in the export.
F. Select which classifications to include in the export.
After the Export button is pressed, progress can be monitored using the notification bell icon in the top-right of the page.
Once the process completes a notification will appear in the top-right corner of your screen telling you the export is complete. Click Click to download to download your labels.
Label editor coordinates
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 any normalized coordinates, multiply them by the width or height of the label (given in pixels).
- “x” and “h” coordinates of a label should be multiplied by the pixel width.
- ”y” and “w” coordinates of a label should be multiplied by the pixel height.
Export data format
All labels export to a single JSON or COCO file and both formats contain the exact same information. The information below uses the JSON format as an example. Refer to the COCO documentation for details on the COCO format.
The tables below provide descriptions of all values contained in the exported files.
data_type
is deleted
, while image groups and image sequences will only contain a single data_unit
.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.
Key | Description | Notes |
---|---|---|
label_hash | The Label Row hash | The ‘hash’ represents a unique identifier |
created_at | Time and date the label was created | |
last_edited_at | Time and date the label was last edited | |
dataset_hash | The Dataset’s hash | The ‘hash’ represents a unique identifier |
data_type | The data unit’s file format | Always “video” for videos |
is_image_sequence | ”true” when the data unit is an image sequence | Always “null” for images |
video_link | Contains a private cloud URL for videos | Always “null” for images |
data_units | List of all files the data unit is composed of | Details of the export information for `data_units“ can be found below. |
object_answers | All the attributes in this data unit | The object attributes are identified using their hash |
classification_answers | All the classifications in a particular data unit | The classification labels are identified using their hash |
object_actions | The number of states a dynamic attribute can be in. | A change in state occurs each time the attribute answer changes. The objectHash within the object_actions is the attribute answer’s ID. |
label_status | Indicates whether the data unit has been labeled. | |
export_history | Contains a record of the export history for this data unit | Exporting labels to confirm export history generates an export history entry. |
export_hash | The hash for this particular export instance | The ‘hash’ represents a unique identifier |
exported_at | The date and time when a particular export instance took place. | |
annotation_task_status | Shows the task status of Manual QA Projects. | annotation_task_status is only applicable for Manual QA Projects and will be deprecated in January 2024. |
Image groups and 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.
Key | Description | Notes |
---|---|---|
label_hash | The Label Row hash | The ‘hash’ represents a unique identifier |
created_at | Time and date the label was created | |
last_edited_at | Time and date the label was last edited | |
dataset_hash | The dataset’s hash | The ‘hash’ represents a unique identifier |
data_type | The data unit’s file format | Always “img_group” for image groups and image sequences |
is_image_sequence | true when the data unit is an image sequence | false for all other types of data, including image groups. This is what distinguishes image groups and image sequences in your export |
video_link | Contains a link to file storage location if file is a video | Always “null” for image groups and image sequences |
data_units | List of all files the data unit is composed of | Details of the export information for data units can be found below. |
object_answers | All the attributes in this data unit | The object attributes are identified using their hash |
classification_answers | All the classifications in a particular data unit | The classification labels are identified using their hash |
object_actions | The number of states a dynamic attribute can be in. | A change in state occurs each time the attribute answer changes. The objectHash within the object_actions is the attribute answer’s ID. |
label_status | Indicates whether the data unit has been labeled. | |
export_history | Contains a record of the export history for this data unit | Exporting labels to confirm export history generates an export history entry. |
export_hash | The hash for this particular export instance | The ‘hash’ represents a unique identifier |
exported_at | The date and time when a particular export instance took place. | |
annotation_task_status | Shows the task status of Manual QA Projects. | annotation_task_status is only applicable for Manual QA Projects and will be deprecated in January 2024. |
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.
Key | Description | Notes |
---|---|---|
label_hash | The Label Row hash | The ‘hash’ represents a unique identifier |
created_at | Time and date the label was created | |
last_edited_at | Time and date the label was last edited | |
dataset_hash | The Dataset’s hash | The ‘hash’ represents a unique identifier |
data_type | The data unit’s file format | Always “video” for videos |
is_image_sequence | ”true” when the data unit is an image sequence | Always “null” for videos |
video_link | Link to the video saved on your private cloud | Always “null” for all other file types |
data_units | List of all files the data unit is composed of | Details of the export information for `data_units“ can be found below. |
object_answers | All the attributes in this data unit | The object attributes are identified using their hash |
classification_answers | All the classifications in a particular data unit | The classification labels are identified using their hash |
object_actions | The number of states a dynamic attribute can be in. | A change in state occurs each time the attribute answer changes. The objectHash within the object_actions is the attribute answer’s ID. |
label_status | Indicates whether the data unit has been labeled. | |
export_history | Contains a record of the export history for this data unit | Exporting labels to confirm export history generates an export history entry. |
export_hash | The hash for this particular export instance | The ‘hash’ represents a unique identifier |
exported_at | The date and time when a particular export instance took place. | |
annotation_task_status | Shows the task status of Manual QA Projects. | annotation_task_status is only applicable for Manual QA Projects and will be deprecated in January 2024. |
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.
Key | Description | Notes |
---|---|---|
label_hash | The Label Row hash | The ‘hash’ represents a unique identifier |
created_at | Time and date the label was created | |
last_edited_at | Time and date the label was last edited | |
dataset_hash | The dataset’s hash | The ‘hash’ represents a unique identifier |
data_type | The data unit’s file format | Always “dicom” in a DICOM series |
is_image_sequence | ”true” when the data unit is an image sequence | Always “null” for a DICOM series |
video_link | Link to the video or image sequence | Always “null” for a DICOM series |
data_units | List of all files the data unit is composed of | Details of the export information for `data_units“ can be found below. |
object_answers | All the object attributes in this data unit | The object attribute are identified using their hash |
classification_answers | All the classifications in a particular data unit | The classification labels are identified using their hash |
object_actions | The number of states a dynamic attribute can be in. | A change in state occurs each time the attribute answer changes. The objectHash within the object_actions is the attribute answer’s ID. |
label_status | Indicates whether the data unit has been labeled. | |
export_history | Contains a record of the export history for the data unit | Exporting labels to confirm export history generates an export history entry. |
export_hash | The hash for this particular export instance | The ‘hash’ represents a unique identifier |
exported_at | The date and time when a particular export instance took place. | |
annotation_task_status | Shows the task status of Manual QA Projects. | annotation_task_status is only applicable for Manual QA Projects and will be deprecated in January 2024. |
Ontology shapes
All ontology shapes can be represented within an export.
Exporting Bitmasks
Bitmask labels are exported as rleString
s. See our SDK documentation to learn how to decode an rleString
.
Exporting data using the Python SDK
Go here to learn how to export JSON files from Encord’s Python SDK. Reach out to us to if you need to export COCO labels.
Was this page helpful?