05 Get Plot Results GeoJSON

Step 5: Get Plot Results GeoJSON

The same read as step 4, but with Accept: application/geo+json โ€” the handler negotiates content type and returns a GeoJSON FeatureCollection instead of the tabular envelope. Drop the body straight into geojson.io, kepler.gl, or QGIS to see the plots on a map.

What this step does

It returns exactly the plots from step 4, reshaped as GeoJSON: one Feature per plot, with the plot polygon as geometry and the full asset resource inlined under properties (so the JSON envelope's attributes block sits one level deeper โ€” properties.attributes.location_id, etc.). No new query โ€” just the other representation of the same rows.

Why it's needed

Coordinates alone don't tell you whether the geometry is right โ€” overlaps, gaps, mis-projected or wildly-placed polygons are obvious on a map and invisible in a table. This step gives the visual confirmation that the upload staged the plots where they actually are, which is exactly the check the upload-first flow exists to enable before you commit to metrics.

Why you'd choose this (vs the table)

Choose GeoJSON when the question is spatial โ€” "are these the right polygons, in the right place?" โ€” and hand it to any mapping tool. Choose the table when the question is about attributes/values. Same endpoint, same data; the Accept header picks the representation.

Next Step

โ†’ Step 6: Run Deforestation Metrics โ€” dispatch the deforestation metric job now that you've confirmed the plots.