Electoral Wards/Divisions are the key building blocks of UK administrative geography. They are the spatial units used to elect local government councillors in metropolitan and non-metropolitan districts, unitary authorities and the London boroughs in England; unitary authorities in Wales; council areas in Scotland; and district council areas in Northern Ireland.

The Wards and Electoral Divisions list contains 9,481 areas of the following constituent geographies:

• 7,218 Census Wards in England
• 453 Census Electoral Divisions in England
• 7 Census Merged Wards in England
• 582 Census Wards in Northern Ireland
• 353 Census Wards in Scotland
• 856 Census Electoral Divisions in Wales
• 12 Census Merged Wards in Wales

Please visit ONS Beginner's Guide to UK Geography for more info.

The boundaries are available as either extent of the realm (usually this is the Mean Low Water mark but in some cases boundaries extend beyond this to include off shore islands) or

clipped to the coastline (Mean High Water mark).

Excel Age-Range creator for 2001 and 2011 Census population figures.

https://s3-eu-west-1.amazonaws.com/londondatastore-upload/census-custom.png" alt="2011 Census custom age tool" />

This Excel-based tool enables users to query the single year of age raw data so that any age range can easily be calculated without having to carry out often complex, and time consuming formulas that could also be open to human error.

Simply select the lower and upper age range for both males and females and the spreadsheet will return the total population for the range.

This file uses the single year of age data from the 2011 Census released on 24 September 2012, which was available for all Local Authorities.

The ward data is currently modelled data for sex, based on single year of age data from Table qs103ew. The final data will be inserted into the tool when it is released in summer 2013.

Also included are the 2001 Census figures for comparison.

This tool was created by the GLA Intelligence Unit.

A seperate Custom Age-Range Tool for Census 2011 Workday population is available below. This is for local authorities and higher geographies only.
Download data from ONS website

Excel Age-Range creator for 2001 and 2011 Census population figures. This Excel-based tool enables users to query the single year of age raw data so that any age range can easily be calculated without having to carry out often complex, and time consuming formulas that could also be open to human error. Simply select the lower and upper age range for both males and females and the spreadsheet will return the total population for the range. This file uses the single year of age data from the 2011 Census released on 24 September 2012, which was available for all Local Authorities. The ward data is currently modelled data for sex, based on single year of age data from Table qs103ew. The final data will be inserted into the tool when it is released in summer 2013. Also included are the 2001 Census figures for comparison. This tool was created by the GLA Intelligence Unit. A seperate Custom Age-Range Tool for Census 2011 Workday population is available below. This is for local authorities and higher geographies only. Download data from ONS website

A set of tools created by the Census Information Scheme that allows users to explore data from 2011 Census Commissioned Table CT0226: Detailed Country of Birth by Ward.

The excel tool allows users to explore the data in four different ways:

• Single Ward Table - a table of the top thirty countries of birth for the selected ward. Also produces a chart of same data.
• All Wards in Borough - a table of the top ten countries of birth in the selected borough broken down by each individual ward.
• Country Table - a table of ward distribution for the selected country in the selected borough. Includes a chart that shows the same data.
• Raw Data - All London data from Commissioned table CT0226

The tableau tool allows users to explore the distribution people born in a selected country using an interactive map.

🇬🇧 United Kingdom English A set of tools created by the Census Information Scheme that allows users to explore data from 2011 Census Commissioned Table CT0226: Detailed Country of Birth by Ward. The excel tool allows users to explore the data in four different ways: Single Ward Table - a table of the top thirty countries of birth for the selected ward. Also produces a chart of same data. All Wards in Borough - a table of the top ten countries of birth in the selected borough broken down by each individual ward. Country Table - a table of ward distribution for the selected country in the selected borough. Includes a chart that shows the same data. Raw Data - All London data from Commissioned table CT0226 The tableau tool allows users to explore the distribution people born in a selected country using an interactive map.

A set of tools created by the Census Information Scheme that allows users to explore data from 2011 Census Commissioned Table CT0225: Age by ethnic group by sex.

The excel tool allows users to explore the data in four different ways:

• Top 10 Ethnic Groups By All Wards In Borough - filter table by borough, age and sex
• Age Comparison - filter by borough, ethnicity and sex
• Sex Comparison - filter by borough, ethnicity and age
• Top 30 Ethnic Groups By Age - Single Ward - filter by ward and sex
• Raw Data - All London data from Commissioned table CT0222

The tableau tool allows users to explore the distribution people born in a selected country using an interactive map.

A set of ward profiles for Camden's 18 electoral wards drawing upon information released from the 2011 Census. THISA IS A ZIPPED FILE. Save it to your desired location and extract (unzip) the contents.

PAPUA NEW GUINEA 2011 NATIONAL REPORT

Mid-year (30 June) estimates of the usual resident population for electoral wards in England and Wales. Note: this page is no longer updated. Latest estimates, and all data for mid-2012 onwards, are available on the Nomis website.

Census data is an official count of dwelling units and population within those units. The data is physically collected and may be supplemented with other information such as the periodic age/gender distribution data. This additional data allows for better interpretation of the population statistics. Data is presented by ward boundaries, the electoral areas represented by one Alderman.

Excel Age-Range creator for Office for National Statistics (ONS) Mid year population estimates (MYE) covering each year between 1999 and 2016 These files take into account the revised estimates for 2002-2010 released in April 2013 down to Local Authority level and the post 2011 estimates based on the Census results. Scotland and Northern Ireland data has not been revised, so Great Britain and United Kingdom totals comprise the original data for these plus revised England and Wales figures. This Excel based tool enables users to query the single year of age raw data so that any age range can easily be calculated without having to carry out often complex, and time consuming formulas that could also be open to human error. Simply select the lower and upper age range for both males and females and the spreadsheet will return the total population for the range. Please adhere to the terms and conditions of supply contained within the file. Tip: You can copy and paste the rows you are interested in to another worksheet by using the filters at the top of the columns and then select all by pressing Ctrl+A. Then simply copy and paste the cells to a new location. ONS Mid year population estimates Open Excel tool (London Boroughs, Regions and National, 1999-2016) Also available is a custom-age tool for all geographies in the UK. Open the tool for all UK geographies (local authority and above) for: 2010, 2011, 2012, 2013, 2014 and 2015. This full MYE dataset by single year of age (SYA) age and gender is available as a Datastore package here. Ward Level Population estimates Single year of age population tool for 2002 to 2015 for all wards in London. New 2014 Ward boundary estimates Ward boundary changes in May 2014 only affected three London boroughs - Hackney, Kensington and Chelsea, and Tower Hamlets. The estimates between 2001-2013 have been calculated by the GLA by taking the proportion of a the old ward that falls within the new ward based on the proportion of population living in each area at the 2011 Census. Therefore, these estimates are purely indicative and are not official statistics and not endorsed by ONS. From 2014 onwards, ONS began publishing official estimates for the new ward boundaries. Download here.

ONS 2011 Census of Population

Contains 2006 Ward Census data, 2011 Ward Census data, and 2011 Ward National Household Survey (NHS) data.

Source: Statistics Canada, Census and NHS profile data for user-specified ward areas, , 2011 Census and National Household Survey, data received November 2013. Reproduced and distributed on an as is basis with the permission of Statistics Canada.

Accuracy: The 2011 National Household Survey (NHS) may contain bias due to non-response rates, especially for data pertaining to small geographic areas. The average non-response rate for the city of Ottawa was 18.9%. Further information on the NHS can be found on the Statistics Canada web site. http://www12.statcan.gc.ca/nhs-enm/2011/dp-pd/prof/help-aide/aboutdata-aproposdonnees.cfm?Lang=E

Update Frequency:Updated with each five-year national census (next census is undertaken in 2016; updated ward data are expected in 2018).

Attributes:Provides various demographic data broken down by the 23 wards of the City of Ottawa.

Contact: Royce Fu

Election Data Attribute Field Definitions | Wisconsin Cities, Towns, & Villages Data AttributesWard Data Overview: These municipal wards were created by grouping Census 2010 population collection blocks into municipal wards. This project started with the release of Census 2010 geography and population totals to all 72 Wisconsin counties on March 21, 2011, and were made available via the Legislative Technology Services Bureau (LTSB) GIS website and the WISE-LR web application. The 180 day statutory timeline for local redistricting ended on September 19, 2011. Wisconsin Legislative and Congressional redistricting plans were enacted in 2011 by Wisconsin Act 43 and Act 44. These new districts were created using Census 2010 block geography. Some municipal wards, created before the passing of Act 43 and 44, were required to be split between assembly, senate and congressional district boundaries. 2011 Wisconsin Act 39 allowed communities to divide wards, along census block boundaries, if they were divided by newly enacted boundaries. A number of wards created under Wisconsin Act 39 were named using alpha-numeric labels. An example would be where ward 1 divided by an assembly district would become ward 1A and ward 1B, and in other municipalities the next sequential ward number was used: ward 1 and ward 2. The process of dividing wards under Act 39 ended on April 10, 2012. On April 11, 2012, the United States Eastern District Federal Court ordered Assembly Districts 8 and 9 (both in the City of Milwaukee) be changed to follow the court’s description. On September 19, 2012, LTSB divided the few remaining municipal wards that were split by a 2011 Wisconsin Act 43 or 44 district line.Election Data Overview: Election data that is included in this file was collected by LTSB from the Government Accountability Board (GAB)/Wisconsin Elections Commission (WEC) after each general election. A disaggregation process was performed on this election data based on the municipal ward layer that was available at the time of the election. The ward data that is collected after each decennial census is made up of collections of whole and split census blocks. (Note: Split census blocks occur during local redistricting when municipalities include recently annexed property in their ward submissions to the legislature).Disaggregation of Election Data: Election data is first disaggregated from reporting units to wards, and then to census blocks. Next, the election data is aggregated back up to wards, municipalities, and counties. The disaggregation of election data to census blocks is done based on total population. Detailed Methodology:Data is disaggregated first from reporting unit (i.e. multiple wards) to the ward level proportionate to the population of that ward.The data then is distributed down to the block level, again based on total population.When data is disaggregated to block or ward, we restrain vote totals not to exceed population 18 numbers, unless absolutely required.This methodology results in the following: Election data totals reported to the GAB/WEC at the state, county, municipal and reporting unit level should match the disaggregated election data total at the same levels. Election data totals reported to the GAB at ward level may not match the ward totals in the disaggregated election data file.Some wards may have more election data allocated than voter age population. This will occur if a change to the geography results in more voters than the 2010 historical population limits.Other things of note… We use a static, official ward layer (in this case created in 2011) to disaggregate election data to blocks. Using this ward layer creates some challenges. New wards are created every year due to annexations and incorporations. When these new wards are reported with election data, an issue arises wherein election data is being reported for wards that do not exist in our official ward layer. For example, if "Cityville" has four wards in the official ward layer, the election data may be reported for five wards, including a new ward from an annexation. There are two different scenarios and courses of action to these issues: When a single new ward is present in the election data but there is no ward geometry present in the official ward layer, the votes attributed to this new ward are distributed to all the other wards in the municipality based on population percentage. Distributing based on population percentage means that the proportion of the population of the municipality will receive that same proportion of votes from the new ward. In the example of Cityville explained above, the fifth ward may have five votes reported, but since there is no corresponding fifth ward in the official layer, these five votes will be assigned to each of the other wards in Cityville according the percentage of population.Another case is when a new ward is reported, but its votes are part of reporting unit. In this case, the votes for the new ward are assigned to the other wards in the reporting unit by population percentage; and not to wards in the municipality as a whole. For example, Cityville’s ward five was given as a reporting unit together with wards 1, 4, and 5. In this case, the votes in ward five are assigned to wards one and four according to population percentage. Outline Ward-by-Ward Election Results: The process of collecting election data and disaggregating to municipal wards occurs after a general election, so disaggregation has occurred with different ward layers and different population totals. We have outlined (to the best of our knowledge) what layer and population totals were used to produce these ward-by-ward election results.Election data disaggregates from GAB/WEC Reporting Unit -> Ward [Variant year outlined below]Elections 1990 – 2000: Wards 1991 (Census 1990 totals used for disaggregation)Elections 2002 – 2010: Wards 2001 (Census 2000 totals used for disaggregation)Elections 2012: Wards 2011 (Census 2010 totals used for disaggregation)Elections 2014 – 2016: Wards spring 2017 (Census 2010 totals used for disaggregation)Blocks 2011 -> Centroid geometry and spatially joined with Wards [All Versions]Each Block has an assignment to each of the ward versions outlined aboveIn the event that a ward exists now in which no block exists (Occurred with spring 2017) due to annexations, a block centroid was created with a population 0, and encoded with the proper Census IDs.Wards [All Versions] disaggregate -> Blocks 2011This yields a block centroid layer that contains all elections from 1990 to 2016Blocks 2011 [with all election data] -> Wards 2011 (then MCD 2011, and County 2011) All election data (including later elections such as 2016) is aggregated to the Wards 2011 assignment of the blocksNotes:Population of municipal wards 1991, 2001 and 2011 used for disaggregation were determined by their respective Census.Population and Election data will be contained within a county boundary. This means that even though municipal and ward boundaries vary greatly between versions of the wards, county boundaries have stayed the same. Therefore, data totals within a county should be the same between 2011 wards and 2018 wards.Election data may be different for the same legislative district, for the same election, due to changes in the wards from 2011 and 2018. This is due to (a) boundary corrections in the data from 2011 to 2018, and (b) annexations, where a block may have been reassigned.

Analysis unit

Persons and households

UNITS IDENTIFIED: - Dwellings: no - Vacant Units: no - Households: yes - Individuals: yes - Group quarters: no

UNIT DESCRIPTIONS: - Dwellings: Dwellings generally have one or more than one room or floor, outer walls of concrete or mud wall with raw materials, a roof and are used by people for dwelling purposes. - Households: A household is a group of people living together based on the same source of income who take their meals in the same kitchen. In a household there might be only one person or many person, relatives or not relatives as well. The main basis for identifying household members is the shared income and kitchen concept. - Group quarters: Group quarters are considered instituational households such as jails, orphanages, mental hospitals, army and police barracks, cantonments, foster homes, hostels, old age homes, or rehabilitation centers.

Universe

All individuals residing within the kingdom

Kind of data

Population and Housing Census [hh/popcen]

Sampling procedure

MICRODATA SOURCE: Central Bureau of Statistics

SAMPLE SIZE (person records): 3238842.

SAMPLE DESIGN: Systematic sampling is used to draw sample households from all areas except in 6 districts (Rasuwa , Mugu, Humla, Dolpa, Mustang and Manang) and 52 (out of 58) municipalities, which were instead fully enumerated. In this sampling, the first serial number of house is randomly selected by the supervisor, and other numbers are selected by systematically mathematical procedure. The sampling rate is 1:8 for all ward/sub wards. IPUMS subsampled fully enumerated geographies to achieve approximately the equivalent of a 1:8 sample.

Mode of data collection

Face-to-face [f2f]

Research instrument

There are two forms used. Schedule 1 (Short form) is used to collect the information of all households and individuals. Schedule 2 (Long form) is used to collect information of the households and individuals from the sampled households.

These wards were produced by the Legislative Technology Services Bureau for the 2011 Legislative Redistricting Project. Election data from the current decade is included.Election Data Attribute Field Definitions | Wisconsin Cities, Towns, & Villages Data AttributesWard Data Overview: These municipal wards were created by grouping Census 2010 population collection blocks into municipal wards. This project started with the release of Census 2010 geography and population totals to all 72 Wisconsin counties on March 21, 2011, and were made available via the Legislative Technology Services Bureau (LTSB) GIS website and the WISE-LR web application. The 180 day statutory timeline for local redistricting ended on September 19, 2011. Wisconsin Legislative and Congressional redistricting plans were enacted in 2011 by Wisconsin Act 43 and Act 44. These new districts were created using Census 2010 block geography. Some municipal wards, created before the passing of Act 43 and 44, were required to be split between assembly, senate and congressional district boundaries. 2011 Wisconsin Act 39 allowed communities to divide wards, along census block boundaries, if they were divided by newly enacted boundaries. A number of wards created under Wisconsin Act 39 were named using alpha-numeric labels. An example would be where ward 1 divided by an assembly district would become ward 1A and ward 1B, and in other municipalities the next sequential ward number was used: ward 1 and ward 2. The process of dividing wards under Act 39 ended on April 10, 2012. On April 11, 2012, the United States Eastern District Federal Court ordered Assembly Districts 8 and 9 (both in the City of Milwaukee) be changed to follow the court’s description. On September 19, 2012, LTSB divided the few remaining municipal wards that were split by a 2011 Wisconsin Act 43 or 44 district line.Election Data Overview: Election data that is included in this file was collected by LTSB from the Government Accountability Board (GAB)/Wisconsin Elections Commission (WEC) after each general election. A disaggregation process was performed on this election data based on the municipal ward layer that was available at the time of the election. The ward data that is collected after each decennial census is made up of collections of whole and split census blocks. (Note: Split census blocks occur during local redistricting when municipalities include recently annexed property in their ward submissions to the legislature).Disaggregation of Election Data: Election data is first disaggregated from reporting units to wards, and then to census blocks. Next, the election data is aggregated back up to wards, municipalities, and counties. The disaggregation of election data to census blocks is done based on total population. Detailed Methodology:Data is disaggregated first from reporting unit (i.e. multiple wards) to the ward level proportionate to the population of that ward.The data then is distributed down to the block level, again based on total population.When data is disaggregated to block or ward, we restrain vote totals not to exceed population 18 numbers, unless absolutely required.This methodology results in the following: Election data totals reported to the GAB/WEC at the state, county, municipal and reporting unit level should match the disaggregated election data total at the same levels. Election data totals reported to the GAB at ward level may not match the ward totals in the disaggregated election data file.Some wards may have more election data allocated than voter age population. This will occur if a change to the geography results in more voters than the 2010 historical population limits.Other things of note… We use a static, official ward layer (in this case created in 2011) to disaggregate election data to blocks. Using this ward layer creates some challenges. New wards are created every year due to annexations and incorporations. When these new wards are reported with election data, an issue arises wherein election data is being reported for wards that do not exist in our official ward layer. For example, if "Cityville" has four wards in the official ward layer, the election data may be reported for five wards, including a new ward from an annexation. There are two different scenarios and courses of action to these issues: When a single new ward is present in the election data but there is no ward geometry present in the official ward layer, the votes attributed to this new ward are distributed to all the other wards in the municipality based on population percentage. Distributing based on population percentage means that the proportion of the population of the municipality will receive that same proportion of votes from the new ward. In the example of Cityville explained above, the fifth ward may have five votes reported, but since there is no corresponding fifth ward in the official layer, these five votes will be assigned to each of the other wards in Cityville according the percentage of population.Another case is when a new ward is reported, but its votes are part of reporting unit. In this case, the votes for the new ward are assigned to the other wards in the reporting unit by population percentage; and not to wards in the municipality as a whole. For example, Cityville’s ward five was given as a reporting unit together with wards 1, 4, and 5. In this case, the votes in ward five are assigned to wards one and four according to population percentage. Outline Ward-by-Ward Election Results: The process of collecting election data and disaggregating to municipal wards occurs after a general election, so disaggregation has occurred with different ward layers and different population totals. We have outlined (to the best of our knowledge) what layer and population totals were used to produce these ward-by-ward election results.Election data disaggregates from GAB/WEC Reporting Unit -> Ward [Variant year outlined below]Elections 1990 – 2000: Wards 1991 (Census 1990 totals used for disaggregation)Elections 2002 – 2010: Wards 2001 (Census 2000 totals used for disaggregation)Elections 2012: Wards 2011 (Census 2010 totals used for disaggregation)Elections 2014 – 2016: Wards spring 2017 (Census 2010 totals used for disaggregation)Blocks 2011 -> Centroid geometry and spatially joined with Wards [All Versions]Each Block has an assignment to each of the ward versions outlined aboveIn the event that a ward exists now in which no block exists (Occurred with spring 2017) due to annexations, a block centroid was created with a population 0, and encoded with the proper Census IDs.Wards [All Versions] disaggregate -> Blocks 2011This yields a block centroid layer that contains all elections from 1990 to 2016Blocks 2011 [with all election data] -> Wards 2011 (then MCD 2011, and County 2011) All election data (including later elections such as 2016) is aggregated to the Wards 2011 assignment of the blocksNotes:Population of municipal wards 1991, 2001 and 2011 used for disaggregation were determined by their respective Census.Population and Election data will be contained within a county boundary. This means that even though municipal and ward boundaries vary greatly between versions of the wards, county boundaries have stayed the same. Therefore, data totals within a county should be the same between 2011 wards and 2018 wards.Election data may be different for the same legislative district, for the same election, due to changes in the wards from 2011 and 2018. This is due to (a) boundary corrections in the data from 2011 to 2018, and (b) annexations, where a block may have been reassigned.

The dataset contains the primary census abstract categorised into town village and ward level on states of India, the data given here is of Delhi from the 2011 census

The statistics in this release are a new presentation of the Key Statistics and Quick Statistics for wards and Output areas in England and Wales. They present statistics for parishes (in England), communities (in Wales) and parliamentary constituencies in England and Wales by aggregating the output area material published in the Key Statistics and Quick Statistics for wards and Output areas.

Electoral Ward boundaries at time of the 2011 census

Ethnic group statistics from the 2011 Census