Processing from Storage

Imports asset data from user storage into UP42 for processing.


Analytics platform discontinued after January 31, 2024

The current analytics platform will be discontinued after January 31, 2024, and will be replaced by new advanced processing functionalities. This change will affect projects, workflows, jobs, data blocks, processing blocks, and custom blocks. For more information, see the blog post.

Description

A data block that 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). For more information on how to use images from geospatial collections in a workflow, see Use assets from storage.

See this block on the marketplace.

How it works

Supported JSON parametersDefault valueMinMaxExamples
asset_idsnulln.a.n.a."asset_ids": ["c532cf2f-7027-4da7-9a7b-8e62efd70ac7", "3475e76d-4e04-420e-a683-bc4831df824f", "d266389c-798c-42b5-a164-721caed9b0c5"]

Compatibility

Catalog collections

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: Use assets from storage.

Limitations

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

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 can't be verified. We recommend exploring the capabilities of the corresponding dataset.

Examples

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

Loading...

Capabilities

Output

raster
up42_standard
bands
{
  "or": [
    [
      "red",
      "green",
      "blue",
      "nir",
      "pan"
    ],
    [
      "red",
      "green",
      "blue",
      "nir",
      "rededge",
      "deepblue"
    ],
    [
      "HH"
    ]
  ]
}
dtype
{
  "or": [
    "uint16",
    "uint8"
  ]
}
format
{
  "or": [
    "DIMAP",
    "GTiff",
    "EEC"
  ]
}
sensor
{
  "or": [
    "TerraSAR-X",
    "Pleiades",
    "SPOT",
    "PNEO"
  ]
}
resolution
{
  "or": [
    0.2,
    0.3,
    0.5,
    1.25,
    1.5
  ]
}
processing_levell2
To know more please check the block capabilities specifications.