6 Ingest as Plots
Promote successful parcel results into the supply chain as plots. This takes the parcel
polygons, feeds them through the standard ingestion pipeline (SCO2 normalization,
validation, optional metrics), and creates plot records visible on /locations/plots.
You can choose "plot" or "shed" as the location_type.
After this step completes, the parcels are fully integrated into your supply chain data.
โถWhat this step does
It takes the successful parcel results from the search task and feeds their
polygons into the standard ingestion pipeline โ the same SCO2 normalization,
validation, and optional metrics any upload goes through โ creating plot (or shed)
records that show up on /locations. It returns an asset_task (captured into
{{ingest_task_id}}) whose unique_parcels count reports how many parcels were
ingested.
โถWhy it's needed
Search and review leave the parcels as transient results, not supply-chain locations. This is the step that commits them: it converts the reviewed boundary polygons into first-class plots so they carry through the rest of the platform โ locations listings, metrics, and downstream compliance work. Nothing before this touches your location data; everything after it depends on the plots this call creates.
โถWhy you'd choose this (vs uploading geometries yourself)
Ingesting straight from the parcel results means the plots inherit the official boundary polygons the search resolved, rather than estimated geometries you'd otherwise supply โ the value proposition of the whole workflow for EUDR geolocation and data enrichment. Because it reuses the standard ingestion pipeline, the resulting plots behave exactly like any other imported plot (tags, commodity type, requested metrics all apply).
โถNext Step
โ Step 7: Verify on Locations (GET /locations/plots)