5 View Results + Map

Retrieve parcel results and render them as:

  1. Summary stats โ€” total results, successful, failed, input point count
  2. Results table โ€” status, parcel ID, country, label, area, owner, land use
  3. Interactive Leaflet map โ€” parcel polygon boundaries (blue) with input points (blue circles for success, red for failed). Click features for popup details.

The map auto-fits to the extent of all features. Parcel polygons are semi-transparent blue with 2px borders. Input points are circle markers.

What this step does

It fetches the individual parcel_result rows for the completed task โ€” the actual polygons, parcel ids, country, label, area, owner, and land use for each input point โ€” and renders them as a table and an interactive map. Failed lookups are shown as red markers so you can see exactly which points didn't resolve.

Why it's needed

The summary in Step 4 only counts successes and failures; this is where you see what was actually resolved. Reviewing the polygons on a map before ingesting is the point of keeping search and ingest as separate steps โ€” you can confirm the boundaries look right (correct location, sensible size, not an over-large ownership tract) and spot failures, rather than blindly promoting every lookup into your supply chain in Step 6.

When you can skip it

The visual review is optional for automated pipelines that trust the search output and go straight to ingest. Keep it whenever a human is in the loop or the parcel geometries feed something consequential (e.g. EUDR geolocation), where eyeballing the result before committing it is worth the extra call.

Next Step

โ†’ Step 6: Ingest as Plots (POST /cadastral/parcels/results/:id/ingest)