1 Upload Shed
โถStep 1: Upload Shed Polygons
Upload a GeoJSON file containing polygon geometries representing supply shed boundaries. This step only validates the geometries โ metrics processing is triggered separately via a PUT request after validation completes.
โถWhat this step does
It POSTs your shed file to /ingestions/assets and creates an
asset_task that runs the shed validation pipeline asynchronously. The
server parses the file, checks that every feature carries Polygon or
MultiPolygon geometry, and stages the sheds as candidate entities. The
response hands back the task id (captured into {{shed_task_id}}), which
every later step in this workflow addresses.
โถWhy it's needed
Nothing downstream can happen without a task to point at: the validation
poll (Step 2), the validated-asset review (Step 3), and the processing
trigger (Step 4) all key off the shed_task_id this call mints. It is also
the gate that keeps bad geometry out of the pipeline โ because a shed
defines a sourcing area, it must be a polygon, so point or LineString
features are rejected here rather than failing later during metrics
processing.
โถWhy upload is validate-only
This call deliberately does not compute metrics. Metrics processing generates plots inside each shed and runs deforestation/emissions analysis via the sco2 API โ slow, expensive work you should not pay for until you have confirmed the boundaries you uploaded are correct. Splitting validation from processing lets you inspect the staged sheds first (Step 3) and only then commit to the heavy step (Step 4).
Key fields:
location_type: shedโ triggers the shed validation pipelinecommodity_type: timberโ the commodity type for this shed
The server validates that all features have Polygon or MultiPolygon geometry. Point or LineString features will be rejected for shed uploads.
After this step, poll the task status until it reaches "staged".