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_idto narrow down to a single search.
โถFilters
All filters from the per-task endpoint are available:
filter[status]=eq:completedโ only successful resultsfilter[country_code]=eq:USโ filter by countryfilter[parcel_id]=eq:uuidโ find a specific parcelfilter[tags]=contains:solarโ filter by task tagsfilter[raw_properties.owner]=eq:Smithโ filter by raw parcel propertiesfilter[input_properties.ref]=eq:S-001โ filter by input propertiesfilter[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
POST /cadastral/parcels/results/:id/ingestThe 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:
| Condition | What you'll see here |
|---|---|
status == "completed" | attributes.status = "completed" |
| A parcel was matched | attributes.parcel_id is non-null |
| The matched parcel has a polygon | attributes.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") โ thereasonexplains 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 lineDropped N completed result(s) with null/unparseable geometryafter triggering ingest. - Duplicate parcels across input points โ multiple input points can match the same parcel. Ingest deduplicates on
parcel_idso 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