Skip to main content

Open in Colab

GitHub

To export data via the SDK, use export(), a scalable and efficient method that allows streaming of unlimited data rows while providing a unique task object for tracking progress.

export_v2() is deprecated

The previously available export_v2() method has been deprecated and will be removed in version 7.0 of the SDK. If you’re currently using export_v2(), we strongly encourage you to switch to export() for its enhanced streamable implementation.
To learn how to export data rows from a project via the app UI, visit Export labels from project.

Export specifications

There are three ways to export data from Labelbox: export from Catalog, export from a labeling project, and export from a model run.

Required & optional fields

Below is the complete list of required and optional fields supported for exports.
To include the location.token field in your export of text data, set data_row_details to True.

Optional parameters and filters

Parameters

When you export data rows from a project, a model run, or Catalog, you can set parameters to include optional fields in the exports. The table below expresses the parameters available for each type of export. For explanations of each field and subfield, see Export glossary. For a detailed explanation of the project_ids, model_run_ids, all_projects, and all_model_runs parameters, see Export data rows from Catalog below. To learn how to apply these filters, see the below sections specific to each export type.

Filters

You can use filters to select a subset of data rows to export. The table below contains the filters supported for each export type. You can apply multiple supported filters to the same export. Combinations of filters apply AND operator logic. The last_activity_at and label_created_at filters take the structure of [<start_date>, <end_date>] and can have the following formats:
  • YYYY-MM-DD(this is an alias of YYYY-MM-DD 00:00:00)
  • YYYY-MM-DD hh:mm:ss
  • YYYY-MM-DDThh:mm:ss±hhmm (ISO 8601)
  • None
The ISO 8601 format allows you to specify the timezone, while the other two formats assume the timezone from the user’s workspace settings.

Last activity at

The last_activity_at filter captures only the data rows where the following changes have been made in the specified time frame:
  • Changes update a data row’s data (rowData), external ID (externalId), or global key (globalKey)
  • Changes are made to annotations, attachments, embeddings, or metadata
  • Data rows are added to batches
  • Data row labeling tasks change
  • Labels, reviews, comments, or issues are added to a project containing the data row
Data rows in multiple projects update last_activity_at when such changes occur in any project containing the data rows.

Label created at

The label_created_at filter captures only the data rows where labels have been created in the specified time frame.

Workflow status

The workflow_status filter allows you to export only the data rows in a specific status of a project’s workflow. The filter accepts the following values:
  • ToLabel
  • InReview
  • InRework
  • Done
This filter only accepts one value. For example, filters = {"workflow_status": "InReview"}.

Batch IDs

The batch_ids filter allows you to export only the data rows in a specific batch or batches. This filter accepts a list of batch IDs. For example, filters = {"batch_ids": ["batch_id_1", "batch_id_2"]}. To get the batches sent to a project and their associated information, you can use the project.batches() method. For more information, see Get the batches.

Global keys

The global_keys filter allows you to export only the data rows with the specified global keys within a project or dataset. This filter accepts a list containing up to 2,000 values. For example, filters = {"global_keys": ["global_key_1", "global_key_2"]}.

Data row IDs

The data_row_ids filter allows you to export only the data rows with the specified IDs within a project or dataset. This filter accepts a list containing up to 2,000 values. For example, filters = {"data_row_ids": ["data_row_id_1", "data_row_id_2"]}.

Streamable exports

Streamable exports (compatible with SDK versions 3.56 and above) allow you to get real-time data flow and updates using any of the following streamable export methods:
  1. data_row.export()
  2. dataset.export()
  3. model_run.export()
  4. project.export()
  5. slice.export()
The return type of these methods is an object of the class ExportTask. This class serves as a wrapper around a Task Objects. Because of this relationship, most of the features present in the Task class are also available in the ExportTask class. ExportTask supports the following methods and properties from Task:
  • uid
  • deleted
  • wait_till_done
  • completion_percentage
  • created_at
  • name
  • status
  • type
  • updated_at
  • get_task
  • organization
  • created_by

Creating an ExportTask instance

An instance of an ExportTask can be obtained via the export() method on the classes mentioned above, or by executing the following:

Checking for results and errors

To check if a task has a result/errors, the following methods can be executed:

Streaming results

To stream the results of exported data rows:

Simplified usage

For fine-grained control over the streaming process, you can use a for loop to iterate through the converted items in the stream. This allows you to implement custom streaming logic, process partial results, or apply additional filtering.

Start streaming at an offset or line

You can define a particular offset to initiate streaming. In the given example, the stream will start from offset 25,548.

Note:

Selecting a random offset might result in positioning within the middle of a JSON string, and this behavior is entirely acceptable. The impact of this choice will become apparent in the output as soon as the streaming starts.
Likewise, a specific line can be specified. In the following example, the stream will skip the first 348 lines and start with the 349th line, where a single JSON string is considered a line.

Note:

offsets and lines are indexed starting from 0, thus with_line(3) will start streaming from the 4th line.
The offset within with_offset() cannot exceed the total size, and line in with_line() cannot exceed the total number of lines returned by these methods; otherwise, a ValueError exception will be raised. ExportTask has two methods to output the total size of the exported file and the total number of lines it contains:

Save export results and log errors

You can store export results in a JSON file and log any errors for monitoring or further processing, like the following example:

Cancel export tasks

You can cancel an ongoing export task before it completes, like the following example:

Export data rows from a project

When you export data rows from a project, you can narrow down your data rows by label status, metadata, batch, annotations, and workflow history. Then, when you export from a project, you may choose to include or exclude certain attributes in your export. See the table at the top of this page to find the JSON export formats for each data type.

Export from a project

Export data rows from Catalog

You can export data rows and all their information from a Dataset or a Catalog Slice. When exporting from Catalog, you can include information about a data row from all projects and model runs to which it belongs. Specifically, you can export the labels from multiple projects and/or the predictions from multiple model runs for the selected data rows. You can use the all_projects and all_model_runs parameters to get information from all projects and model runs attached to your data row. As shown below, the project_ids and model_run_ids parameters accept a list of IDs. See the table at the top of this page to find the JSON export formats for each data type.

Export from a dataset

Export a list of selected data rows from a dataset

Export from a slice

Export your entire Catalog

Export data rows from a model run

See the table at the top of this page to find the JSON export formats for each data type.