06 Run Deforestation Metrics

Step 6: Run Deforestation Metrics

Dispatch the deforestation metric job for this upload: PUT /ingestions/assets?filter[assets.task_id]=eq:{{plot_lifecycle_task_id}} with { "metrics": ["deforestation"] }. When the filter resolves to a single task the PUT reuses it and returns its id (captured into {{plot_lifecycle_metrics_task_id}}).

What this step does

It enrols the plots from this upload into deforestation metric processing โ€” a process_locations job (processBatchStats) that computes the deforestation time-series aggregates surfaced later under /metrics/plots/deforestation. It kicks off asynchronous work and hands back a task id to poll.

Why it's needed

Metrics are not produced at upload or by the assessment step โ€” they are a separate, heavier computation, so they're dispatched explicitly here. This is what generates the numeric deforestation series a dashboard renders as a heatmap. Without this step, /metrics/plots/deforestation (step 8) would return nothing for the task.

Why it's distinct from the step-3 assessments

Step 3's art9 produces point-in-time risk values / flags (deforestation_value, deforestation_area_ha) that back the boolean compliance decision. This step produces the time-series aggregates โ€” the numeric surface for visualisation. The two paths are independent: you can run either without the other, and they land in different places (assessments.art9 vs /metrics/plots/deforestation).

Next Step

โ†’ Step 7: Wait For Metrics Processing โ€” poll the metrics task to a terminal state.