Find areas for many points
The same lookup as Find areas at a point, for up to 100 points in one request. Handy for tagging a list of sites or addresses with their ward and council.
/areas:containsBatchGood to know
- Give each point as
point={lng},{lat}, repeated. Add a third number for its accuracy in metres. - Details that are the same for every point, like which boundary release was used, are given once in
releasesrather than repeated per point. - For more than 100 points, send them in batches.
crsstringoptionalThe input coordinate reference system. The default
EPSG:4326useslngandlat;EPSG:27700uses British National Grideastingandnorthingor an Ordnance Surveygridref;EPSG:29902uses Irish Grideastingandnorthing.One ofEPSG:4326EPSG:27700EPSG:29902DefaultEPSG:4326geographystring[]optionalA geography to look the point up in. Repeat it or give a comma-separated list, up to four in total. A geography named only in a pinned
releaseneed not be repeated here.releasestring[]optionalA release to pin, as
{geography}/{release}, such asward/2025-12-uk-bgc, orward/latestfor its newest unambiguous published release. A bare release id is accepted when exactly one geography is requested. A pinned release is used whateverdatesays.datestringoptionalA calendar date as
YYYY-MM-DD, or a month asYYYY-MM. Every geography without a pinned release uses the latest release dated on or before it; without a date it uses the newest unambiguous published release. The country boundaries used to place a point that matches nothing are chosen the same way.accuracynumberoptionalHow far the true position may lie from the coordinate, in metres, such as a GPS fix's reported accuracy. Without it, uncertainty is half the coordinate's last written decimal place, which overstates it where a client drops trailing zeros.
Returns
PointContainmentBatchEnvelopeEach point's containing areas in every requested release.
apiVersionv1requiredatlasReleasestringrequiredThe immutable
/atlas-releasereleaseIdfor the artifacts that produced this response.metaobjectrequiredShowHide1 child field
nextCursorstring | nullrequiredOpaque cursor for the next page, or null at the end.
dataPointContainmentBatchrequiredShowHide6 child fields
datestringoptionalboundaryRuleincludedrequiredreleasesPointLookupRelease[]requiredShowHide12 child fields
geographystringrequiredboundaryReleasestringoptionalhrefstringoptionalselectionobjectrequiredShowHide4 child fields
policystringrequiredOne ofpinnedlatest-release-dated-on-or-beforedatestringoptionalsameMonthbooleanoptionalnextReleaseReference | nulloptional
coverageobjectoptionalShowHide1 child field
countriesstring[]required
boundaryResolutionobjectoptionalHow much the boundary's lines were generalised, read from the ONS release name.
undeclaredwhere the name does not say.ShowHide4 child fields
generalisationstringrequiredextentstringoptionalOne ofclipped-to-coastlinefull-extent-of-realmtoleranceMnumberoptionalbasisons-release-nameoptional
geometrySourceGeometrySourceoptionalWhere the served WGS84 geometry came from.
transformationis present only when the source was reprojected.ShowHide3 child fields
sourceCrsstringrequiredtransformationobjectoptionalcorrectionsobject[]optionalDeclared grid corrections that moved this area before it was reprojected, such as
northern-ireland-offset.
sourceobjectoptionalShowHide2 child fields
publisherstringoptionallicenceobjectoptional
statusstringoptionalambiguous-release,no-release-for-dateorgeometry-unavailablewhen no release could be read. The schema this is combined with lists every status a result may carry.detailstringoptionalchoicesReleaseReference[]optionalShowHide5 child fields
idstringrequiredmonthstringrequiredtitlestringrequiredcountriesstring[]requiredhrefstringrequired
earliestReleaseReferenceoptionalShowHide5 child fields
idstringrequiredmonthstringrequiredtitlestringrequiredcountriesstring[]requiredhrefstringrequired
summaryobjectrequiredShowHide7 child fields
pointsintegerrequiredlookupsintegerrequiredmatchedintegerrequirednoMatchintegerrequiredoutsideCoverageintegerrequiredunresolvedintegerrequiredLookups with no answer about the point, such as an ambiguous release.
nearBoundaryintegerrequired
pointsobject[]requiredShowHide4 child fields
indexintegerrequiredpointLookupPointrequiredShowHide5 child fields
lngnumberrequiredlatnumberrequiredcrsEPSG:4326requiredprecisionobjectrequiredinputobjectoptionalPresent when British National Grid or Irish Grid input was transformed to WGS 84.
countryPointCountryrequiredThe UK country the point lies in.
area-codereads it from a matched area's GSS code;country-boundarytests the point against a country release, and a nullcodethere means no UK country contains it.ShowHide5 child fields
codestring | nullrequiredOne ofGB-ENGGB-NIRGB-SCTGB-WLSnulldeterminedBystringrequiredOne ofarea-codecountry-boundaryundeterminedareastringoptionalboundaryReleasestringoptionaldetailstringoptional
resultsPointLookupResult[]requiredOne per entry in releases, in the same order.
ShowHide7 child fields
geographystringrequiredboundaryReleasestringoptionalstatusstringrequiredOne ofmatchedno-matchoutside-coverageambiguous-releaseno-release-for-dategeometry-unavailablereasonstringoptionalOne ofcountry-not-coveredoutside-uk-boundariesdetailstringoptionalpositionalToleranceMnumberoptionalCoordinate uncertainty, boundary generalisation and transformation accuracy added together, in metres.
matchesobject[]required
notestringrequired
- 400No point is given, more than 100 are, or one is malformed, and the detail names it; or the geographies, releases, date or accuracy are refused as for
areas:contains. - 404No resource matches that identity.
- 503The referenced build artifact has not been built yet.
Every error has the same shape. See Errors for how to handle them.
Show the precise behaviourHide the precise behaviour
The areas:contains lookup for up to 100 points at once, each given in the JSON body's points array as {lng},{lat} or {lng},{lat},{accuracy} in the default WGS 84, as point={easting},{northing} with crs=EPSG:27700 or EPSG:29902, or as one Ordnance Survey reference such as point=TQ3000080000 with crs=EPSG:27700. Geographies, release selection and statuses are exactly as for a single point.
Release-wide facts, including selection, coverage, resolution and geometry provenance, are given once in releases. Each point then lists its country and, per release in the same order, its status and matches; a match carries corrections only where a declared grid correction moved that area. summary counts the lookups by outcome and how many have a match near a boundary.
Every release is read once for all the points, so the cost of a batch grows with its points rather than with its points times its geographies. This is a bounded convenience for a caller's own point dataset, not a bulk geocoder: for more points, page through them in batches.