The bottleneck in Earth observation moved years ago — from getting the data to preparing it. Before a GIS analyst can answer a single question about vegetation, flooding, or land-use change, they download tiles, reconcile coordinate systems, align pixel grids, normalize missing values, and resolve the differences between sensors that were never meant to be compared. Analysts routinely spend 45 to 80 percent of a project not analyzing data, but preparing it.[1]CrowdFlower 2016 / Anaconda 2020CrowdFlower (Forbes, March 2016): 80% on preparation. Anaconda State of Data Science 2020: 45% on preparation.forbes.com ↗
And the knowledge they build doing it — which bands to use, what order to run things in, how to handle the edge cases — stays trapped in one-off scripts and notebooks. Every new project starts from scratch. When an analyst leaves, the workflow leaves with them.
That preparation layer is what M33 builds.