Surrounding parcels: source-native topology plus nested distance rings
Resolve a subject parcel, then return bounded county/state parcel context from explicit PARCEL_SOURCES geometry capabilities (AR statewide; Chatham County, NC; Clark County, NV; Dallas County, TX; Davidson County, TN; Iredell County, NC; Los Angeles County, CA; MT statewide; Maricopa County, AZ; NC statewide; Philadelphia County, PA; VT statewide; Wake County, NC): bounded centroid/source-point rings within 100 m, 250 m, 500 m, and 1,000 m; aggregate counts are null when the requested evidence window does not cover the full ring. Includes verified source-native topology only while the current topology release gate is active. When that gate is inactive, proximity remains available and exact topology is labeled release_gate_inactive. Mapped parcel contact groups verified edge_touch and point_touch while retaining each exact subtype. Only verified edge_touch is adjacent; point_touch is not. Generic Intersects stays geometry_intersection_unclassified. Point-only sources retain proximity with topology unsupported. No owner/mailing fields, assessed-value aggregates, common-ownership inference, development probability, neighborhood score, or value prediction. Direct flat-body route for this one free resource; no API key, payment, or catalog wrapper. Return only the cited bounded evidence described here; this route never produces a paid brief or full report.
Request
- Base URL: https://api.locus.report
- URL: https://api.locus.report/api/locus_surrounding_parcels
- Auth: none required
Request body
Response
Free cited evidence response.
Changes
No recorded changes to this operation across all 1 revision of this API.