In the previous Notebook, we demonstrated two different strategies for scaling our coastline extraction algorithm to run over a full image strip. The result was a Python function that we can point at any (coastal) image and efficiently delineate the coastlines, either in downsampled resolution or full resolution.
The execution of that function was conducted within our Notebook, which is convenient for hands-on development and testing, but not necessarily ideal for production-level analysis. For example, what if we wanted to run the analysis over multiple strips at the same time? Or set up a recurring job that runs on every new strip that comes in over a given area? Handling production of coastline features from the Notebook in these cases would be relatively cumbersome.
At this point in the development process, it's important to consider moving our algorithm from the Notebook environment to the GBDX Platform by deploying it as a GBDX Task. A GBDX Task is simply a stored version of an algorithm (or tool, or methodology, or really any operation) that we can execute on the GBDX Platform. The code itself isn't run locally; instead, it runs as part of a Workflow in the cloud. This means we can execute the same Task against multiple images all at the same time: each will be kicked off as a separate, parallel workflow, without being constrained to the computational limits of a single machine (or GBDX Notebook Kernel).
In this Notebook, we provide a walkthrough of how to deploy our coastline extraction algorithm as a GBDX Task, using some helpful tools built right into the GBDX Notebooks interface. We also do a quick test of our new task and review the results to make sure it works.