Output Area (2011) to Parish (2011) to LAD (December 2011) Best Fit Lookup in EW

Open data API in a single place

Provided by Office for National Statistics

Get early access to Output Area (2011) to Parish (2011) to LAD (December 2011) Best Fit Lookup in EW API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2022.07.22 13:03
Created
2022.07.22
Available languages
English
Keywords
OA, DEC_2011, LUP_BFT_OA11_PARs_LADs, LUP_OA_PAR_LAD, Administrative Lookups, Local Authority Districts, Parishes, Local Authority, Lookup, LUP_OA, Parish, LAD, PAR, Best-fit Statistical Lookups, Local Authority District, England and Wales
Quality scoring

Dataset description

<span style='font-family: &quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, Helvetica, Arial, sans-serif; font-size: 17px;'>A best-fit lookup between Output Areas (OA), civil parishes / communities and local authority districts (LAD) as at 31 December 2011 in England and Wales. This lookup has been provided with a 'small population indicator' field. This field indicates those parishes / communities which have a very small population. There are two designated categories to describe the changes, and these are as follows: - 0 - normal population, - 1 - very small population. Where a parish / community is smaller than an OA and therefore does not contain any OA population weighted centroids, the parish / community is allocated to the OA with its population weighted centroid nearest to any part of the parish / community. The methodology used to create the OA lookups is based on the distribution of 2011 Census population. A median average of each OA's household grid references, weighted by the population at each household has been used to create a population weighted centroid for each OA. This centroid has been used to allocate the OA and all its associated statistics to any higher geographies. (File Size 8.6MB).</span><div><p style='margin-bottom:0cm;margin-bottom:.0001pt;line-height: normal'><span style='font-size: 11.5pt; font-family: Helvetica, sans-serif;'>Field Names – OA11CD, PAR11CD, PAR11NM, PAR11NMW, SMPOPIND, LAD11CD, LAD11NM, LAD11NMW</span></p> <p style='margin-bottom:0cm;margin-bottom:.0001pt;line-height: normal'><span style='font-size: 11.5pt; font-family: Helvetica, sans-serif;'>Field Types – Text, Text, Text, Text, </span><span style='font-family: Helvetica, sans-serif; font-size: 15.3333px;'>Text, Text, Text, Text</span></p> <p style='margin-bottom:0cm;margin-bottom:.0001pt;line-height: normal'><span style='font-size: 11.5pt; font-family: Helvetica, sans-serif;'>Field Lengths – 9, 9, 70, 70, 1, 9, 36, 36</span></p></div><div><br /></div><div><div></div></div><div><br /></div><div><div>REST URL of Feature Access Service – <a href='https://services1.arcgis.com/ESMARspQHYMw9BZ9/arcgis/rest/services/OA11_PAR11_LAD11_EW_LU_ff0c1b98220f4756915b2eaf7510df06/FeatureServer' target='_blank' rel='nofollow ugc noopener noreferrer'>https://services1.arcgis.com/ESMARspQHYMw9BZ9/arcgis/rest/services/OA11_PAR11_LAD11_EW_LU_ff0c1b98220f4756915b2eaf7510df06/FeatureServer</a></div></div>
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks