04 Get Plot Results Table
โถStep 4: Get Plot Results Table
Read the staged plots back as a tabular JSON envelope โ
GET /ingestions/assets/{{plot_lifecycle_task_id}}?include=normalised_data,assessments
with Accept: application/json. One row per plot, each carrying top-level
location_id / location_type and the assessments relationship
populated by step 3.
โถWhat this step does
It projects the ingestion task's plots into a flat, one-row-per-location
view. The include=normalised_data,assessments hint attaches the parsed
input and the validation results, so each row shows the core confidence
(confidence_score / confidence_level) plus any EUDR add-ons that step 3
produced. This is the "table" half of the review โ the shape you'd render
as a grid or export to a spreadsheet.
โถWhy it's needed
This is where you actually see what the workflow produced: that the
plots staged correctly and that the assessments you opted into in step 3
landed on them. In the upload-first flow it's also the checkpoint that
confirms the deferred validation paid off โ before this step the
assessments.* slots were null; after step 3 they carry real
confidence and add-on values. If core is still absent here, step 3
didn't run against these plots (wrong filter / task).
โถWhy you'd choose this (vs the GeoJSON view)
Choose the table when you want the attributes โ confidence, flags,
per-plot assessment values โ in a form that's easy to scan, sort, or feed
a report. When you instead want to see the plots on a map, step 5 returns
the identical data as a GeoJSON FeatureCollection. They're the same
endpoint and the same rows; only the Accept header differs.
โถNext Step
โ Step 5: Get Plot Results GeoJSON โ the same data as a map-ready FeatureCollection.