Ingest Results

Ingest successful parcel search results as locations into the supply chain. This promotes raw parcel polygons into managed supply chain locations (plots or sheds) via the standard ingestion pipeline.

The endpoint reads successful results from the parcel search, converts them to a GeoJSON FeatureCollection, and feeds them into the existing ingestion pipeline (SCO2 normalization, validation, optional metrics).

Returns 409 Conflict if the source task is not yet completed.

How it works

  1. The endpoint reads all successful (completed) results from the specified parcel search task.
  2. Duplicate parcels (same parcel matched by multiple input points) are automatically deduplicated.
  3. Parcel polygons are converted to a GeoJSON FeatureCollection and fed into the standard ingestion pipeline.
  4. The pipeline normalises, validates, and geocodes each parcel as a new location (plot or shed) based on the location_type you specify.
  5. If metrics are included (e.g. deforestation, emissions), batch processing is triggered automatically after ingestion.
  6. Tags from the source search task are merged with any tags you provide in the request body.
  7. The response returns a new ingestion task ID โ€” poll GET /ingestions/:id/summary to track progress.

Use Cases

  • Promote cadastral parcel boundaries into managed supply chain locations.
  • Convert raw cadastral data into monitored plots or sheds with sustainability metrics.
  • Batch-ingest search results without re-uploading geometry data.

Required scope: parcels:write