A workflow is a Directed Acyclic Graph (DAG) of data and processing blocks. A workflow encompasses the data sources to be used, the algorithms to process the data and the order of the blocks. A workflow always starts with a data block and continues with one or more processing blocks. One block can be used in multiple workflows.
Building a workflow requires that the capabilities of the data and processing blocks match.
Workflows can be built by first creating a project and selecting Create Workflow.
The workflow editor is a tool for the user to:
- Provide a name to a workflow.
- Combine compatible data and processing blocks to build a template for jobs.
Workflows come in all different shapes and sizes. While every workflow must have a data block, not all workflows need to have processing blocks. Below we have an example workflow that only consists of a data block, which in this case is Pléiades Reflectance (Download).
A standard workflow consists of a data block and processing block(s). Below is an example of a workflow consisting of the Pléiades Reflectance block with the Pan-sharpening and NDVI processing blocks.
Workflows can be as complex as you need them to be. The following workflow is aimed to detect cars in a Pléiades Display (Download) image. Some blocks such as Car Detection will require some preparation on the input image. In this case, in order for the car detection block to work, we added the DIMAP to GeoTIFF, Raster CRS conversion, and Raster Tiling blocks for the input image to be in the correct format for further processing.
Always make sure that you are using the most up-to-date version of a block. Jobs can fail when an outdated block is used. To check the version number, look for the tag icon located next to the block's pricing in the work editor.