The block catalog is a complete collection of data and processing blocks that a user can search through when building a workflow through the workflow editor.
To view the block catalog, click on either the Add data or Add processing button in the workflow editor. Depending on if you are searching for data blocks or processing blocks, the block catalog will output search results in either category.
You can only create a workflow using compatible blocks.
A block is defined as a unit that builds up a workflow. There are two types of blocks: data blocks and processing blocks.
Data blocks deliver geospatial data (satellite or aerial images, vector data etc.) that can be directly downloaded, streamed or further analyzed with processing blocks. A data block is always followed by one or more processing blocks. Examples:
Processing blocks apply algorithms that process data and deliver the corresponding outputs. A processing block can follow a data block or a processing block. Examples:
The blocks connect with each other if their input and output capabilities match. For example, a block that outputs a GeoTIFF is compatible with the next block that accepts GeoTIFF as input.
As the first block in the workflow, the data block has only an output capability. The processing block always follows a data block, so it has both an input and an output capability.
For more information, please visit the article Block capabilities.
The block catalog also provides the option to push your own custom block. This option can be found in the tab Custom blocks as shown below. To learn how to push your own custom block, please refer to the article Developing blocks.
Each block provides the user with a generalized overview of the dataset or processing algorithm. This information can be found by selecting any block in the block catalog. Each block summary consists of the following:
The content of each block description vary depending on the data or the processing block. Information that may be pertinent to your specific case study may be found here.
This information may consist of:
- data provider
- use case examples
- license restrictions
- streaming vs. download
- revisit frequencies
- volume discounts
- minimum order sizes
The capabilities section lists in detail the properties of the data or processing block. This section also varies with the block. Processing blocks may contain a supported input block and output section.
This information may consist of:
- the bands that are used in the dataset
- the format (or extension) that the dataset inputs and outputs
- processing level
- data type
- geometry type
For more detailed information on all block capabilities, please refer to our article Block Capabilities.
Some data blocks such as the Airbus Basemap or Getmapping blocks contain an extra pricing section which lists the credits per km2 charged for a given size range for an area of interest. For more information on pricing, please contact our sales team.
We offer sample images for all our data and processing blocks to provide a preview of the imagery or results of processing algorithms. Please be aware that the sample data are only image previews, not downloadable sample datasets.
Sample data can be found in the tab next to Overview as shown below.
More information on the blocks can be found on the blocks themselves once they are selected from the block catalog. This information pertains to the pricing, version number and in some cases, restricted access.
The pricing of a data or processing block can be found next to the icon shown below. Pricing (in credits) may vary between blocks: per km2, MB, quantity, tile, MP, data point, and scene. For more information on pricing, please refer to our article on Credits & Pricing.
The block version number can be found adjacent to the tag icon as shown below. This version number is the version of the block at the time when it is added to the workflow. Hovering over the version tag also shows how many days ago the block was last updated.
Make sure you are using the most up-to-date version of a block in order to avoid any potential job failures. If you are using an outdated version, simply delete the block from your workflow and re-add the block.
Some blocks require an added step of acquiring access prior to usage. Restricted blocks can be easily identified by looking out for the lock icon and Restricted Block tag, both denoted in red, as shown below. If you would like to request access, please refer to steps on requesting access described in Restricted Blocks.