Processing from Storage

Introduction

This block brings the geospatial assets delivered in your storage, adds them to workflows and applies further processing. The geospatial assets delivered to storage originate from multiple sources: data purchase through the data platform (collections, catalog or tasking orders) or through the processing platform (data blocks).

Technical information

Asset identifiers

An asset is a unique item generated from a successful job run using a OneAtlas data block, a completed order or a fresh image captured through sensor tasking and it contains the downloadable geospatial dataset.

Every asset gets a unique asset identifier (ID). The newly-generated asset ID is displayed on the storage dashboard, where each asset can be downloaded. These asset IDs can be used to further process your previously delivered datasets on the UP42 platform. For more information: Process datasets from storage.

Compatible datasets

The list of compatible datasets is displayed in the table below. Geospatial assets from other data collections aren't supported.

Compatible blocks

The capabilities are dictated by the selected asset ID. Since each dataset from the previous table has its own block capabilities, we recommend checking the specifications of your selected dataset.

For example, the data block Pléiades Reflectance (Download) is compatible with the processing block Pansharpening. This means that the data block Processing from Storage will be compatible with the processing block Pansharpening if the asset ID originates from a Pléiades Reflectance (Download) image.

Limitations

The block doesn't work with a test query, only with a live job. For more information on job types, see Run job.

When the asset IDs of your geospatial assets are processed with this block, the credit costs for data are 0. However, processing and infrastructure costs may apply. They depend on different parameters, such as runtime and file size. For more information on costs, see Credit consumption.

Please note that the capabilities between this block and the following processing blocks cannot be verified. We recommend exploring the capabilities of the corresponding dataset. For instance, the SPOT 6/7 Display or SPOT 6/7 Reflectance product will have different compatible processing blocks.

How it works

Examples

Example based on a workflow created with the data block Processing from Storage, the processing block Pansharpening and multiple asset IDs:

Capabilities

{
  "or": [
    [
      "red",
      "green",
      "blue",
      "nir",
      "pan"
    ],
    [
      "red",
      "green",
      "blue",
      "nir",
      "rededge",
      "deepblue"
    ],
    [
      "HH"
    ]
  ]
}

{
  "or": [
    "uint16",
    "uint8"
  ]
}

{
  "or": [
    "DIMAP",
    "GTiff",
    "EEC"
  ]
}

{
  "or": [
    "TerraSAR-X",
    "Pleiades",
    "SPOT",
    "PNEO"
  ]
}

{
  "or": [
    0.2,
    0.3,
    0.5,
    1.25,
    1.5
  ]
}

For more information, please refer to the marketplace.