3 Get Validated Assets

Step 3: Get Validated Assets

Retrieve the validated shed entities and visualize them on a map. Each entity should have Polygon geometry from the uploaded shed boundaries. The map shows all validated sheds with their names and commodity types.

What this step does

It reads the staged asset rows for the task (GET /ingestions/assets/{{shed_task_id}}) with include=normalised_data,assessments, so each entity carries its normalised geometry alongside the raw upload. The after-response script renders the sheds as a summary table and a Leaflet map so you can eyeball what validation produced before spending on metrics.

Why it's needed

This is the review checkpoint between the cheap validate step and the expensive processing step. Because metrics processing generates plots inside each shed boundary and runs deforestation analysis, you want to confirm the boundaries are the ones you intended โ€” right shape, right count, right names โ€” before triggering Step 4. Catching a wrong or malformed shed here avoids paying for a full processing run on bad input.

When you can skip it

This step is a human-in-the-loop inspection aid; it changes no server state. An automated pipeline that already trusts its input can go straight from a staged status (Step 2) to the processing PUT (Step 4) without fetching or visualising the validated assets. Keep it when a person is reviewing the upload, or when you want the map/table as a sanity check.