List All Results

List all parcel search results across all tasks for the authenticated organisation. Supports the same filters as the per-task results endpoint, plus task_id to scope to a specific task.

Use Cases

  • Browse all parcel results without knowing the task ID.
  • Search across tasks for parcels in a specific country or with specific tags.
  • Filter by task_id to narrow down to a single search.

Filters

All filters from the per-task endpoint are available:

  • filter[status]=eq:completed โ€” only successful results
  • filter[country_code]=eq:US โ€” filter by country
  • filter[parcel_id]=eq:uuid โ€” find a specific parcel
  • filter[tags]=contains:solar โ€” filter by task tags
  • filter[raw_properties.owner]=eq:Smith โ€” filter by raw parcel properties
  • filter[input_properties.ref]=eq:S-001 โ€” filter by input properties
  • filter[task_id]=eq:<uuid> โ€” scope to a specific search task

Response formats

  • Accept: application/json โ€” paginated JSON envelope (default)
  • Accept: application/geo+json โ€” GeoJSON FeatureCollection with parcel polygons

What gets ingested by POST /cadastral/parcels/results/:id/ingest

The list endpoint returns every result row for a task โ€” successful, failed, and (rarely) successful-but-without-a-polygon. The ingest endpoint is stricter. A row from this list is only included in the downstream ingest if it satisfies all of:

ConditionWhat you'll see here
status == "completed"attributes.status = "completed"
A parcel was matchedattributes.parcel_id is non-null
The matched parcel has a polygonattributes.geo is non-null

Rows that fail any of these are excluded by the ingest worker before the GeoJSON is built. Concretely:

  • Failed results (status = "failed") โ€” the reason explains why (rate limit, no parcel found, geometry unsupported, etc.). Never ingested.
  • Completed results with geo == null โ€” the upstream cadastral service returned a parcel record without a polygon. Counted as successful for usage purposes, but ingest skips them since plot/shed creation needs a polygon. Look for the worker log line Dropped N completed result(s) with null/unparseable geometry after triggering ingest.
  • Duplicate parcels across input points โ€” multiple input points can match the same parcel. Ingest deduplicates on parcel_id so the same parcel is written once.

The ingest precheck count (unique_parcels returned by the 202 envelope) reflects the post-filter count, so it matches what the worker actually writes.

Required scope: parcels:read