2c Search Parcels (Segmentation)

Submit a parcel search with "geometry_source": "segmentation". Instead of the cadastral (Regrid / BC-WFS) parcel lookup, each point's geometry is derived from imagery segmentation: AEF watershed gives the plot boundary texture, ESRI Living Atlas land cover restricts it to canopy, and Overture roads/waterways split the segment. The point's own forest segment is returned when it is on forest, otherwise the nearest canopy-covered segment.

Use this when the cadastral parcel is unhelpful โ€” no county data, or an over-large ownership tract โ€” and a forest-stand boundary is wanted instead. A point that lands on no segmentable canopy returns a per-point miss (null geometry), not a forced polygon.

geometry_source defaults to "cadastral" (today's behaviour, unchanged), so this flag is purely additive. It is mutually exclusive with the cadastral path; forest_fallback is moot when geometry_source is "segmentation".

The task id is captured into {{segmentation_parcel_task_id}}, so it does not replace the {{parcel_task_id}} that Steps 3โ€“7 address. Inspect the result via GET /cadastral/parcels/results/{{segmentation_parcel_task_id}} โ€” the segmentation row carries raw_properties.source of aef-watershed-canopy.

See Search Parcels for the full contract.

What this step does

It runs the parcel search with geometry_source: "segmentation", which swaps the cadastral parcel lookup for a geometry derived from imagery segmentation: AEF watershed gives the boundary texture, ESRI Living Atlas land cover restricts it to canopy, and Overture roads/waterways split the segment. Each point resolves to its own forest segment when it sits on forest, otherwise to the nearest canopy-covered segment; a point on no segmentable canopy returns a null-geometry miss.

Why it's needed

The cadastral parcel is not always the boundary you want. A point may have no county data, or the registered parcel may be an over-large ownership tract that says nothing about the actual forest stand. Segmentation exists to produce a forest-stand boundary in those cases โ€” a geometry shaped by what's on the ground rather than by land registry lines.

Why you'd choose this

Reach for segmentation when a forest-stand boundary is more useful than an official parcel โ€” for example when the cadastral lookup is unhelpful or missing. It is purely additive: geometry_source defaults to "cadastral" (today's unchanged behaviour), so you only opt in when you want it. The two paths are mutually exclusive โ€” segmentation does not use the cadastral lookup, and forest_fallback has no effect here.

Next Step

โ†’ Step 3: Poll Task Status for the main search