Spatial Queries

Radius and bounding box spatial queries for finding parcels by location.

Overview

The API supports two types of spatial queries on the dedicated /parcels/spatial endpoint: radius search (point + distance) and bounding box search (rectangular area).

Radius Search

Find all parcels within a given distance of a point:

Code

curl "https://api.aribatax.com/parcels/spatial?lat=38.99252&lng=-84.95673&radius_miles=0.5" \
  -H "Authorization: Bearer your_api_key_here"

| Parameter | Type | Description | |-----------|------|-------------| | lat | number | Latitude of the center point | | lng | number | Longitude of the center point | | radius_miles | number | Search radius in miles (0-50) |

Bounding Box Search

Find all parcels within a rectangular geographic area:

Code

curl "https://api.aribatax.com/parcels/spatial?bbox=-84.96,38.99,-84.95,39.00" \
  -H "Authorization: Bearer your_api_key_here"

The bbox parameter takes four comma-separated values: xmin,ymin,xmax,ymax (min longitude, min latitude, max longitude, max latitude).

Pagination

Both query types support limit (1-100, default 25) and offset:

Code

curl "https://api.aribatax.com/parcels/spatial?lat=38.99252&lng=-84.95673&radius_miles=1&limit=100&offset=100" \
  -H "Authorization: Bearer your_api_key_here"

Response Format

Results are returned as a GeoJSON FeatureCollection, the same shape as /parcels/search:

Code

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "geometry": { "type": "MultiPolygon", "coordinates": ["..."] },
      "properties": {
        "id": "75436466-b2be-474a-96fd-c9f9fd84bc54",
        "stateParcelId": "580223001018000005",
        "propAddress": "8288 Hartford Ridge Rd",
        "avTotal": 78100
      }
    }
  ],
  "meta": { "total": 12, "limit": 25, "offset": 0 }
}

Performance Notes

Small radius searches (under 1 mile) typically return quickly
Larger radii may match thousands of parcels; use limit and offset to paginate
Bounding box queries are most efficient when the box is small (a few city blocks)
Both query types use spatial indexes and perform well even over the full 3.7 million parcel dataset

Point-in-Polygon Overlay Lookups

To check which overlay features (floodplain, soils, aquifers) contain specific points, use POST /overlays/spatial-lookup with a layer slug, an attribute key, and up to 500 points -- see the API Reference for the request schema.