GBDX

GBDX Usage FAQ

This document describes the GBDX subscription usage categories and provides answers to frequently asked usage data questions.

Last updated: August 5, 2020

GBDX Usage Categories

Your GBDX Subscription Agreement determines your usage allocation in the following categories:

Usage categoryDescription
Premium Imagery AllotmentThis category includes usage of 1B imagery in the workflow system and Raster Data Access (RDA) imagery access. This category may be referred to as "hosting" in your subscription agreement.
ComputeThis category shows the number of hours used to process data using the GBDX Workflow system. See GBDX Compute Hours for more information.
S3 StorageUsage data for this category shows the total amount of s3 storage being used by the account.

View Usage Data for your Account

The GBDX Dashboard displays your account's subscription allocations and usage to date. Sign in to https://dashboard.geobigdata.io and select the Account tab to view this data.

The usage data displayed is for the account, not the individual user. The allotment determined by your subscription agreement is shared by all users associated with that account.

Premium Imagery Usage

This usage category includes imagery acquired from Maxar's satellite constellation in both 1B strip and RDA chip formats.

Premium imagery access refers to accessing imagery using any of the following access methods:

  • Level-1B strip processing in the GBDX Workflow System
  • All data access endpoints for the Raster Data Access (RDA) service
  • The GBDXtools Python Client image access classes (e.g. "CatalogImage")
  • Python code executed in the GBDX Notebooks environment which obtains imagery via the GBDXtools image access classes (e.g. "CatalogImage")

1B Image strips in the GBDX Workflow System

In the GBDX workflow system, charges are incurred when a 1B image strip is accessed by a task in a workflow. It is only counted against the usage allotment the first time it's accessed.

There is one important exception. If an image has not been accessed for 30 days, it is removed from the GBDX platform, according to the Premium Data Retention Policy. Once it's been removed, if it is reordered and used in a task, a charge will be incurred.

RDA image chips

Every time an image is accessed through RDA, a charge is incurred. This is because the chips must be reloaded every time. There are three RDA Operators that result in a premium imagery charge:

  • Plotting (view in IDE)
  • Geotiff (download)
  • Read (a numpy array of image data).

If an RDA image has not been accessed for 30 days, it is removed from the GBDX platform, according to the Premium Data Retention Policy. Once it's been removed, if it is reordered and accessed using one of the operators listed above, a charge will be incurred.

Top customer issues for premium imagery usage

1. When using the image class CatalogImage, viewing or downloading an entire image strip may result in a failure or timeout, but usage is incurred for the data that was downloaded.

Viewing an entire image strip with plot() or downloading with geotiff() will frequently fail due to memory or timeout issues related to various IDEs. However, a charge will be incurred for the data that was processed before failure. To avoid this, limit your request by using a bounding box or AOI in GBDXtools or GBDX Notebooks CatalogImage request. See #2 below for more details and a working example.

2. Use a bounding box or AOI to limit premium imagery access via the catalogImage image class

When accessing premium imagery using the GBDXtools image class catalogImage, we recommend you limit your request with a bounding box or an AOI to avoid timeout issues. This is the only approved method of limiting your download data in order to limit the cost of premium imagery access.

This Notebook illustrates the recommended best practice for limiting premium imagery access when using the CatalogImage image class .

Note: This method only applies to accessing imagery using the GBDXtools CatalogImage image class. You cannot limit premium imagery access in the GBDX Workflow system by applying a bounding box to an ordering request.

3. Limiting the number of bands in a request does not reduce premium imagery usage.

Limiting the number of bands in a request does not reduce usage. All bands within the requested AOI are charged against the subscription.

4. Downloading a smaller file type does not reduce premium imagery usage.

When you download an image using .geotiff(), you have the option to select different .tiff, .png, or .jpeg as the file type. Each option results in a different file size. However, usage is charged for the native file type, .tiff. Choosing a different file type may change the quality of the image, but it does not reduce premium imagery usage.

5. Use of a third party processing module to reduce image size does not reduce premium imagery usage.

When a file size is reduced by a third-party data processing module, this does not impact usage data in the GBDX system. Premium imagery usage is not reduced.

6. When imagery is requested for overlapping AOIs, usage is incurred for both requests.

RDA imagery must be reloaded every time it's accessed, which results in a charge. This includes making consecutive requests with overlapping AOIs.

Compute Usage

This category shows the number of hours used to process data using the GBDX Workflow system. See GBDX Compute Hours for more information on how compute is calculated.

S3 Storage Allocation

To keep your S3 storage allocation usage under 100%, we recommend deleting unused data from your GBDX S3 storage location. To learn how to manage the data in your S3 storage location, read the S3 Access Course.

Updated 2 months ago

GBDX Usage FAQ


This document describes the GBDX subscription usage categories and provides answers to frequently asked usage data questions.

Last updated: August 5, 2020

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.