Output Area (2011) to Workplace Zone to LAD (December 2011) Exact 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 Workplace Zone to LAD (December 2011) Exact Fit Lookup in EW API!

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

Dataset information

Country of origin
Updated
2024.10.09 13:44
Created
2022.07.22
Available languages
English
Keywords
Local Authority, Workplace Zones, LAD, 2011, LUP_OA, LUP_OA_WZ_LAD, Local Authority Districts, Workplace Zone, OA, Output Areas, England and Wales, Lookup, Output Area, Census Lookups, DEC_2011, WZ, LUP_CEN, EXACT_FIT_LU_OA_2011, Local Authority District
Quality scoring

Dataset description

<span style='font-size: 17px; 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 !important;'>A lookup file between Output Areas (OA), Workplace Zones (WZ) and local authority districts (LAD) as at 31 December 2011 in England and Wales. </span><div style='font-size: 17px; 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 !important;'><span><br /></span></div><div style='font-size: 17px; 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 !important;'><span>This lookup has been provided with an 'indicator' field, that define the lookup between 2011 OA and WZ. There are four designated categories to describe the changes, and these are as follows: - E - Where an OA is the same as a WZ. - S - Split. This is where the OA has been split into two or more WZ. There will be one record for each OA that has been split into a WZ. - M - Merged. This is where two or more OA have been merged to form a WZ. - X - The relationship between the OA and the WZ is irregular and fragmented. There are instances where an OA has not exactly matched to a WZ. This is where the OA may have been either split then merged or merged then split, but into fragments that do not allow exact joining between OA and WZ. The constraints on WZ creation were to ensure a minimum of 100 workers and three workplace postcodes, and to constrain within MSOA. The 'X' code indicates it was not possible to meet these constraints and to create WZ purely through splits or mergers of OA. (File Size 8.7MB).</span></div><div style='font-size: 17px; 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 !important;'><span><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, WZ11CD, LAD11CD, LAD11NM, LAD11NMW, IND</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</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, 9, 36, 36, 1</span></p></span></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_WZ11_LAD11_EW_LU_1e30e50424db4e97818d93e28fd2de3f/FeatureServer' target='_blank' rel='nofollow ugc noopener noreferrer'>https://services1.arcgis.com/ESMARspQHYMw9BZ9/arcgis/rest/services/OA11_WZ11_LAD11_EW_LU_1e30e50424db4e97818d93e28fd2de3f/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