2 Search Parcels (File Upload)

Submit a parcel search by uploading a GeoJSON file containing point geometries. File uploads always process asynchronously โ€” the response returns immediately with a task ID that you poll for completion.

Supported file formats: CSV, JSON, GeoJSON, Parquet, GeoPackage, Shapefile (ZIP), XLSX, XLS.

What this step does

It is the same parcel search as Step 1, but the points arrive as an uploaded file rather than an inline JSON body. The API parses the file's point geometries, queues a background parcel_search_task, and returns 202 Accepted immediately with the task id โ€” captured here into both {{file_parcel_task_id}} and the shared {{parcel_task_id}} so the rest of the workflow can address it.

Why it's needed

It exists for the batches the inline-JSON path can't comfortably carry: point sets that already live in a spreadsheet, GIS export, or shapefile, and batches large enough that a synchronous response isn't practical. Because the response is 202 (not the synchronous 200 of Step 1), the task is not terminal yet โ€” you must poll Step 3 before results are available.

Why you'd choose this (vs inline JSON)

Choose file upload when your coordinates already exist as a file and re-serialising them into a JSON body would be busywork, or when the batch exceeds what a synchronous call handles. The trade-off is that file uploads always run asynchronously, so this path always requires the poll in Step 3 โ€” whereas a small inline-JSON request comes back complete in one call.

Multipart fields

FieldTypeRequiredDescription
filefileYesGeoJSON or other supported file with point geometries

Next Step

โ†’ Step 3: Poll Task Status (GET /cadastral/tasks/:id)