Key | Description |
---|---|
objectHash | The unique ID of the object instance. Two instances of the same object have different object hashes |
Object name | The name of the object as defined in the Ontology. For example “Chicken”. |
featureHash | The unique ID of the Ontology element. For example, the object “Chicken” in the Ontology. All instances have the same featureHash. |
uid | The unique identifier for the object instance. Two instances of the same object have different uids. |
Object color | The color used to label the object, as defined in the Ontology and seen in the Encord platform. |
Ontology shape | The shape used to label the object, as defined in the Ontology. For example, polygon. |
Classification name | The name of the Classification, as defined in the Ontology. For example “Day or night?” |
Classification answer | The value of the Classification, as defined in the Ontology. For example “Day” |
classificationHash | The unique identifier for the Classification instance. |
Classification answer hash | The unique identifier for the Classification value |
Attribute name | The name of the attribute, as defined in the Ontology. For example “Standing or sitting?” |
Attribute answer | The name of the attribute value, as defined in the Ontology. For example “Sitting” |
Attribute answer featureHash | The unique identifier for the attribute value. |
<file-path-to-ssh-key>
with the full path to your SSH private key.<project-id>
with the hash of your Project.<file-path>
with the file path to save the JSON file, with your labels.<private_key_path>
with the full path to your private key.<project_id>
with the ID of the Project you want to export attributes for.<task_name>
with the name of the data unit you want to export attributes for. Remove data_title_eq="<task_name>"
if you want to export attributes for all tasks.<private_key_path>
with the full path to your private key.<project_id>
with the ID of your Project.<task_name>
with the name of the task you want to export labels for (if using the task-specific script).<start_frame_number>
with the first frame of the range you want to export labels for.<end_frame_number>
with the last frame of the range you want to export labels for.[10, 20, 30, 40]
with the frames you want to export labels for.ffmpeg
can be used to save all frames with labels as an image, to be used in machine learning applications. The script below shows how this is done when exporting a list of non-consecutive frames from a specific video.
<output_folder_path>
with the full path to the output folder you want the output image files to be saved.<private_key_path>
with the full path to your private key.<project_id>
with the ID of your Project.<task_name>
with the name of the file in Encord you want to export labels for.<path_to_your_video_file>
with the full path to the video file you are exporting labels for.def get_video_path
function to return your actual video path corresponding to the label row.[10, 20, 30, 40]
with the frames you want to export labels for.include_all_branches=True
.
Make sure you:
<private_key_path>
with the full path to your private key.<project_id>
with the ID of your Project.include_all_label_branches=True
.<private_key_path>
with the full path to your private key.<project-id>
with the ID of the Project you want to export labels for.#Perform label row operation before in this loop
with the label row operations you want to perform.BUNDLE_SIZE
to suit your needs. We strongly recommend NOT bundling more than 1000 operations at once, because bundling more than 1000 operations can reduce performance instead of improving performance.<private-key-path>
with the full path to your private key for authentication.<project-id>
with the ID of the Project for which you want to export labels.