Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Release notes for the Boundary-Line product
This release note provides information about the June 2024 release of Boundary-Line.
This document contains additional theoretical information related to Boundary-Line. All users will find the Product Information document useful and informative.
Boundary-Line has three feature classes:
Administrative units with attributes
Polygon features with attributes
Polyline features with attributes
Each feature has the following component:
Feature attribute data
Each geometric feature has an additional component:
Feature position
The geometry of map features is defined in terms of coordinates. All coordinates used in Boundary-Line are based on the Ordnance Survey National Grid (NG) coordinate referencing system and are quoted to a 0.1 m resolution. Despite this, Boundary-Line data can be no more accurate than its source, primarily the generalised 1:10 000 scale mapping.
There will be positional differences between the boundaries in Boundary-Line and Ordnance Survey large-scale topographic products. This is due to the large-scale products being surveyed to a higher degree of accuracy and associated to ground surface features, at scales such as 1:1 250 and 1:2 500.
Boundary-Line has been created as a more generalised set of administrative and electoral boundaries for the whole of Great Britain. It has been digitised against Ordnance Survey (generalised) 1:10 000 scale OS VectorMap Local mapping. The process of generalising for 1:10 000 scale mapping may have caused certain features to be moved from their true ground position for the purposes of map clarity. The result being that Boundary-Line and large-scale boundaries will not always be coincident.
An attribute is the descriptive characteristic of a feature, that is, a non-spatial element. In Ordnance Survey map data terms, an attribute can be a feature type (these are character codes), or a distinctive name, number or code, for example, Bassett Ward or 145.232 hectares.
Each administrative unit is classified by means of an area code (AC). These area codes are allocated when each feature is initially interpreted and captured from source. This means that a county is distinguished from a ward by the area code allocated to it. The polygon features can be classified by tracing their relationships to administrative units. Consequently, links can be classified by tracing their relationships to polygons.
It is possible, with appropriate software, for you to add other names or values of your own choice as attributes of features.
There are two identifiers in Boundary-Line that help you identify features, and which are provided to create consistent references between successive releases of Boundary-Line data. They are unique within each feature type throughout the whole dataset and maintained through successive annual updates. These identifiers are never modified – only created or deleted. If a feature is deleted from the Boundary-Line database, then the identifier ceases to exist.
The two attributes are LINK_ID and POLYGON_ID.
There is no direct cartographic text in Boundary-Line. Names, area values and GSS codes are held as attributes.
Agriculture, forestry and woodland account for 90% of Wales’s land use, generating a wealth of insightful statistical information. The Senedd Cymru / Welsh Parliament uses this data to inform policy, assist decision-making and help deliver a wide range of services to rural communities.
NHS North West was established under government policy to strengthen primary care trusts (PCTs) and give GPs greater ability to commission or purchase health services directly for their patients. The organisation replaced the three former strategic health authorities in Cumbria and Lancashire, Cheshire and Merseyside, and Greater Manchester. The Association of Greater Manchester PCTs is taking forward a data analysis and reporting tool called the TIS Analyser, which was developed by Greater Manchester health organisations as part of the Tactical Information Service (TIS).
INSPIRE compliant metadata in conjunction with UK Location Programme is available to access as either:
The Boundary-Line product supplies the administrative area relationships.
A district is a division of a county; a civil parish is a division of a district. A county is divided for voting purposes into electoral divisions (EDs) and a district is divided for voting purposes into district wards.
With the introduction of unitary authorities, there are now two- and three-tier local government hierarchies. The three-tier system remains unchanged. The two-tier system has unitary authorities replacing the county and district levels of administration.
Unitary authorities may be divided into civil parishes or communities (except in Scotland), and unitary authority wards or unitary authority EDs for voting purposes. In Wales, the voting area is the unitary authority ED; in Scotland it is the unitary authority ward and in England it is the unitary authority ward or unitary authority ED.
England also has metropolitan districts; these have no county administration. These districts are divided for voting purposes into metropolitan district wards.
With the introduction of the regional government for London, in this document called the Greater London Authority, the proportional representation voting area for this new administration is the Greater London Authority Assembly constituency. The existing London borough structure also has a relationship with the new Greater London Authority and each London borough is divided for voting purposes into London borough wards.
Scotland is divided into parliamentary constituencies for voting purposes to elect Members of the Scottish Parliament (MSPs). The Scottish Parliament electoral region is a grouping of Scottish Parliament constituencies.
Wales is divided into parliamentary constituencies for voting purposes to elect parliamentary members (MS) to the Welsh Parliament. The Welsh Parliament electoral region is a grouping of Welsh Parliament constituencies.
The exit of the United Kingdom from the European Union on 01 January 2021 resulted in the repeal of the European Regions as active electoral areas. For the purposes of Boundary Review, the original European Regions in England have been retained as nine English Regions in the Boundary-Line product. A frozen layer of European Region features, preserved as of 01 April 2021, is available as a supplementary historical dataset.
England, Scotland and Wales are divided into parliamentary constituencies for voting purposes to elect members (MPs) to the Westminster Parliament. Parliamentary constituencies are made up of combinations of wards (or electoral divisions in Wales).
The closeness of the results of observations, computations or estimates to the true values or the values accepted as being true. Accuracy relates to the exactness of the result and is the exactness of the operation by which the result is obtained.
A blanket term used by Ordnance Survey to refer to all public administrative areas, specifically local government management and electoral areas.
A single administrative area.
A spatial extent is defined by circumscribing lines that form a closed perimeter that does not intersect itself.
An attribute is a property of an entity, usually used to refer to a non-spatial qualification of a spatially referenced entity. For example, a name or descriptive code indicating what an entity represents or how it should be portrayed.
Boundaries define the areas of the various national, local government and some European authorities.
An alphanumeric attribute code used in digital map data to describe each feature in terms either of the object surveyed or its representation on the map (or both).
Allocation of a feature code to a feature being created from constituent construction data: points and/or segments; with optional linking to an existing feature of the same feature code.
Pairs of numbers expressing horizontal distances along original axes. Alternatively, triplets of numbers measuring horizontal and vertical distances. Row and column numbers of pixels from raw imagery are not considered coordinates for the purpose of the standard.
An expression of the up-to-dateness of data.
The defined logical arrangement of data as used by a system for data management; a representation of a data model in computer form.
A text feature consisting of a text string(s) which form(s) a proper name.
Something about which data is stored in a databank or database, for example, boundary and name. The data may consist of relationships, attributes, positional and shape information and so on. Often synonymous with feature.
Data that is directly represented in digital form. For example, the relationship between two objects is explicit if recorded by such means as pointers and does not have to be deduced by further analysis of the data.
An item of detail within a map that can be a point and/or symbol, text or line.
A system for capturing, storing, checking, integrating, analysing and displaying data that is spatially referenced to the Earth. This is normally considered to involve a spatially referenced computer database and appropriate application software.
A subset of digital map data selected on a basis other than position. For example, one layer might consist of all features relating to counties and another to wards. Also known as a level.
A level corresponds to a single type of administrative unit (for example, a ward or a district) and is conceptual in form. See also layer.
A series of connected coordinated points forming a simple feature with homogeneous attribution.
The spatial abstraction of an object in one dimension. Lines may intersect with other lines. They are defined as a series of two or more coordinate pairs and may be curved or straight. Curved lines consist of a series of very short straight-line segments. As an object abstraction, a line has no width.
Links are the representation of line features. They are made up of one or more consecutive
non-intersecting link segments with common attributes between two terminating nodes. Links have no connection with other links except at the start or end, via common (shared) terminating nodes (points). All links contain their terminating coordinates. Links may form the boundaries of polygons and may be shared between polygons.
The proper name or label of an object (real world) or feature (object abstraction). The descriptive name might consist of one or more text strings or be an attribute of the object or object abstraction.
A unique referencing system that can be applied to all Ordnance Survey maps of Great Britain (GB) at all scales. It is used by Ordnance Survey on all post-war mapping to provide an unambiguous spatial reference in Great Britain for any place or entity whatever the map scale. The National Grid is defined by the OSGB36 spheroid.
A collection of entities which form a higher-level entity within a specific data model.
A recognisable discrete part of the real world.
The date the order was made; not necessarily the day it becomes ‘live and in use’.
The zero point in a system of rectangular coordinates.
Polygons are a representation of areas. A polygon is defined as a closed line or perimeter completely enclosing a contiguous space and is made up of one or more links. At least one node occurs on the perimeter of a polygon where the bounding link completes the enclosure of the area. There may be many nodes connecting the bounding links of a polygon. Links may be shared between polygons. Polygons may wholly contain other polygons; or be contained within other polygons.
The degree to which the coordinates define a point’s true position in the world, directly related to the spheroid and/or projection on which the coordinate system is based.
A set of related data fields grouped for processing.
Also known as X-Y coordinates and as eastings and northings. These are two-dimensional coordinates that measure the position of any point relative to an arbitrary origin on a plane surface, for example, a map projection.
The measure of the internal consistency of the positional measurements in a dataset. For many local area purposes (for example, records of utility plant), relative accuracy is more important than absolute accuracy. In this case, accurate measurement of offsets from fixed points is required rather than knowledge of the true position in space.
A measure of the ability to detect quantities. High resolution implies a high degree of discrimination but has no implication as to accuracy. For example, in a collection of data in which the coordinates are rounded to the nearest metre, resolution is 1 metre, but the accuracy may be ± 5 metres or worse.
A chord defined by two consecutive coordinates in a line string.
An order made by a Minister under delegated power from Parliament. Contains changes to boundary information, the alignment, type or relationship to a named area (amalgamation) or a change of name to an area are made by order.
The format used to transfer data between computer systems. In general usage, this can refer not only to the organisation of data, but also to the associated information, such as attribute codes, which are required in order to successfully complete the transfer.
A straight line joining two data points.
The following subsections describe the content of the Shapefile, TAB and GKPG supply.
Area features are polygons with attributes added.
The following schema applies for all area features in the Polling Districts England
folder of the shapefile, MapInfo TAB and GeoPackage data supply.
The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.
Feature identifier added by the software.
Attribute Name: Not provided (GKPG), OBJECTID (TAB), OBJECTID (Shapefile)
Multiplicity: [1]
Identifier comprising 1 to 10 characters.
Attribute Name: PD_ID (GKPG), PD_ID (TAB), PD_ID (Shapefile)
Data Type: char
Size: 10
Multiplicity: [1]
The name of the county_region
that the feature is inside (includes Greater London Authority).
Attribute Name: County (GKPG), County (TAB), County (Shapefile)
Data Type: char
Size: 100
Multiplicity: [1]
The name of the district_borough_unitary_region
that the feature is inside.
Attribute Name: Distric_Bo (GKPG), Distric_Bo (TAB), Distric_Bo (Shapefile)
Data Type: char
Size: 100
Multiplicity: [1]
The name of the district_borough_unitary_ward_region
that the feature is inside.
Attribute Name: Ward (GKPG), Ward (TAB), Ward (Shapefile)
Data Type: char
Size: 100
Multiplicity: [1]
The name of the parish_region
where Area_Description
='Civil Parish Or Community
' that the feature is inside.
Attribute Name: Parish (GKPG), Parish (TAB), Parish (Shapefile)
Data Type: CharacterString
Size: 100
Multiplicity: [0..1]
Area features are polygons with attributes added.
The following schema applies for all area features in the Wales
folder of the shapefile, MapInfo TAB and GeoPackage data supply.
The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.
Feature identifier added by the software.
Attribute Name: fid (GKPG), Not provided (TAB), Not provided (Shapefile)
Multiplicity: [1]
The name of the community ward.
Attribute Name: Name (GKPG), Name (TAB), NAME (Shapefile)
Data Type: char
Size: 100
Multiplicity: [0..1]
The classification of the community ward.
Attribute Name: Area_Description (GKPG), Area_Description (TAB), DESCRIPTIO (Shapefile)
Data Type: char
Size: 3
Multiplicity: [1]
The name of the parish_region
that the ward is inside.
Attribute Name: Community (GKPG), Community (TAB), COMMUNITY (Shapefile)
Data Type: char
Size: 100
Multiplicity: [1]
The name of district_borough_unitary_region
that the community ward is inside; written in UPPERCASE with underscores.
Attribute Name: File_Name (GKPG), File_Name (TAB), FILE_NAME (Shapefile)
Data Type: char
Size: 100
Multiplicity: [1]
Boundary-Line is the key dataset of administrative and voting boundaries in Great Britain. It is a representation in computer-readable form of a specialist large-scale map, including real-world objects, which may be tangible (such as the mean high water mark) or intangible (such as a district boundary).
GIS software provides the functionality to store, manage and manipulate this digital map data. The properties of the data make it suitable as a key base for users wishing to develop applications. Boundary-Line is also suitable for use within other digital mapping systems. It's coordinated on the National Grid, which allows for the easy superimposition of other datasets.
Polygons are continuous areas defined by sets of bounding closed lines. They are representational of areas, such as electoral wards, and have relationships to administration collection features in order to convey descriptive characteristics of the polygon. These are explicit within the data and can be viewed and manipulated with appropriate software.
Boundary-Line is currently updated by mapping against OS VectorMap Local (1:10 000 scale) and, in certain cases, large-scale sources.
A list of the features within Boundary-Line includes:
Area measurements
Civil parish (England) and community (Wales)
County
Distinctive names
District
Electoral division (county and unitary)
English region
Extent of the realm (EOR): either mean low water mark (England and Wales), mean low water springs mark (Scotland) or seaward boundary extensions
Greater London Authority
Greater London Authority Assembly constituencies (the London proportional representation voting areas)
GSS codes in England, Wales and Scotland for all units, with the exception of Greater London Authority, county electoral divisions and non-civil-parish areas
London borough (including the county of the City of London)
Mean high water mark (England and Wales) and / or mean high water springs mark (Scotland): both are abbreviated to MHW in product documentation
Metropolitan district
Scottish parliamentary constituency and electoral region
Unitary authority
Unique administrative unit, link and polygon identifiers
Ward (district, unitary, metropolitan and London borough)
Welsh Parliament constituency and electoral region
Westminster (parliamentary) constituency
There are several supplementary layers included alongside the main Boundary-Line product. These supplementary layers sit separately to the main GB Boundary-Line folder and are included as separate directories in the shapefile and MapInfo TAB file formats.
Features included as supplementary in the supplementary directory are:
Historical counties
Ceremonial counties
Historical European regions (frozen as of 1 April 2021)
Country
This section explains the representation of features in Boundary-Line and describes various definitions and exceptions.
This term is used by Ordnance Survey to refer to all public administrative areas. For the Boundary-Line dataset, the following are included under this term:
County
Unitary authority
Metropolitan district
District
Civil parish (Note: Depicted if appropriate notification has been received. Not all parishes have councils.)
English region
Parliamentary (Westminster) constituency
Electoral division (of county or unitary authority)
Ward (of district, metropolitan district, London borough, unitary authority)
London borough (including the county of the City of London)
Greater London Authority
Greater London Authority Assembly constituency
Unitary authority
Community (Note: Depicted if appropriate notification has been received.)
Parliamentary (Westminster) constituency
Electoral division (of unitary authority)
Welsh Parliament constituency
Welsh Parliament electoral region
Unitary authority
Parliamentary (Westminster) constituency
Ward (of unitary authority)
Scottish Parliament constituency
Scottish Parliament electoral region
Area values exist for every polygon in Boundary-Line; area values are quoted to the current Department for Communities and Local Government (DCLG) specification of 0.001 hectare. The value is subject to the inherited accuracies of the generalised 1:10 000 scale published mapping used as the source for Boundary-Line.
A boundary is the limit of a pre-set and established area whose limit is determined by one or more lines. For example, in Boundary-Line, an administrative unit boundary is represented by a county area boundary.
A ceremonial county is an area that has an appointed Lord Lieutenant and High Sheriff. Ceremonial counties are not explicitly represented in Boundary-Line.
Complex polygons are polygons that wholly enclose other polygons. They only occur when an administrative unit wholly encloses one or more others at the same level, for example, a rural district surrounding an urban district.
The description ‘Detached (Det)’, only applies to portions of local government or parliamentary constituency areas which are separated from the main area, being completely surrounded by other local government or parliamentary constituency areas and not connected by direct access on the ground.
The description will not be applied to islands or parts of islands in the sea. Detached parts have the same GSS code (where applicable) as the main area.
Part of a boundary separated from another, originally on the same alignment. Divorcements are created by the revision of one boundary and not the other.
The figure above shows a boundary divorcement. The unitary boundary between Vale of Glamorgan and Cardiff has been realigned, whilst the parliamentary (Westminster) constituency boundary has remained in its original position. It is likely that the parliamentary (Westminster) constituency boundary will also be realigned at some time in the future.
These are the dates on which an Act, Order or Statutory Instruments are ‘effective’. They may or may not be the same as the operative date or the appointed day or days. The term is particularly applied to parliamentary (Westminster) constituency changes that are effective at the date of the next general election after the operation of the order making change. This is the ‘effective’ date, that is, the date of the proclamation dissolving an existing Parliament and calling a new Parliament.
The following are specific exceptions to the normal rules:
Greater London and the metropolitan counties:
Greater London covers the area of the 32 London boroughs plus the City and county of the City of London.
Greater London is no longer a county. The Greater London Authority, which has no authority over the autonomous London boroughs, is held as one named file with all the sub-levels of boundary within it.
The London boroughs and the City and county of the City of London have been classified as London boroughs.
The metropolitan districts within the former metropolitan counties (disbanded in 1985) are classified as metropolitan districts:
Greater Manchester
Merseyside
South Yorkshire
West Yorkshire
Tyne and Wear
West Midlands
Government Office Regions (GORs) in England are not represented as specific boundary features in Boundary-Line; however, the boundaries that are used to define the GORs are represented as English Regions. A full list of the counties and unitary authorities that represent each English Region which the GORs are based on can be found in the Boundary-Line release note.
The Government Office Network closed on 31 March 2011.
Honorary titles granted to local government areas such as city and town are not included in Boundary-Line.
Boroughs in England have been identified, as from the October 2006 release, with (B) in the file name and
(B) in the Name attribute, for example:
The borough (B) will only be depicted on unitary authorities, district and metropolitan districts. This addition is to purely denote which boundaries have borough status in England without creating polygons or altering the specification in any way.
The boundaries between England and Wales and England and Scotland are represented by the boundaries between countries in the supplementary Country layer. These are maintained boundary extents based off local authority boundaries.
Government Statistical Service (GSS) codes are a unique system of referencing for administrative units.
All types of units are coded in Boundary-Line except for Greater London Authority, county electoral divisions and non-civil-parish areas. The County ED code for Greater London Authority is set at 999999999. The code is blank when the administrative unit does not have a code, for example, non-civil- parish areas.
The codes are allocated by the Office for National Statistics (ONS) for England and Wales and by the General Register Office for Scotland (GROS) for Scottish areas.
This is a calendar date, given in an Order, Act or Statutory Instrument, on which the specified boundary changes will come into operation. Dates given may be up to four years after the publication of the Order, Act or Statutory Instrument and may apply to any type of boundary other than parliamentary or European regions.
The Westminster (parliamentary) constituency boundaries have an Effective date, rather than an Operative Date ‘The Effective Date will be the date of a general election, meaning any changes to these boundaries will apply as and from the date of the next election.’
The represented boundaries and administrative unit names are defined and modified by Orders, Acts and Statutory Instruments (SIs). A document signed by the relevant Secretary of State or a local authority letter describing and giving legal authority for boundary changes.
Orders, Acts and SIs, in exceptional circumstances due to processing or constitutional constraints, may be excluded until the next suitable release.
This is the last date on which a boundary was current. Where an effective date applies, the superseded date will be the day before the next dissolution of Parliament.
Boundaries are no longer shown in Boundary-Line if they have been superseded at the time of the annual snapshot of boundaries that each release of Boundary-Line represents.
When changes occur to tidelines, rivers or streams caused by natural and gradual forces, any boundaries that are linked to these altered features will move with them. When the movement of a boundary, MHW or EOR alignment in Boundary-Line reflects such changes, this will be noted in the update notes that accompany each release of Boundary-Line.
This is an area within the realm that is not included in all the relevant administrative units. The area will remain unannexed until further legislation changes its situation and the polygon represents a hole in that level of administration.
Unitary authorities and counties effectively create a contiguous layer of administrative units throughout the whole of Great Britain. They represent single-tier administrations with responsibility for all areas of local government.
Area features are polygons with attributes added.
The following schema applies to all area features in the GB
folder of the shapefile, MapInfo TAB and GeoPackage data supply, and for all area features in the Supplementary_Country
folder of the shapefile, MapInfo TAB and GeoPackage data supply.
The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.
Feature identifier added by the software.
Attribute Name: fid (GKPG), Not provided (TAB), Not provided (Shapefile)
Multiplicity: [1]
Feature geometry.
Attribute Name: Not provided (GKPG), Not provided (TAB), SHAPE (Shapefile)
Data Type: Polygon
Multiplicity: [1]
Name of the administrative area.
Attribute Name: Name (GKPG), Name (TAB), NAME (Shapefile)
Data Type: char
Size: 100
Multiplicity: [0..1]
A code describing the level.
Attribute Name: Area_Code (GKPG), Area_Code (TAB), AREA_CODE (Shapefile)
Size: 3
Multiplicity: [1]
Full name of the Area_Code.
Attribute Name: Area_Description (GKPG), Area_Description (TAB), DESCRIPTIO (Shapefile)
Data Type: char
Size: 50
Multiplicity: [1]
Name of the Principal Area which the boundary sits within.
This may be the same boundary level as the boundary itself, for example, a Greater London Authority boundary will have ‘Greater London Authority’ present in this field. But for more granular boundaries, this field will show the principal boundary which is at the principal level.
Attribute Name: File_Name (GKPG), File_Name (TAB), FILE_NAME (Shapefile)
Data Type: char
Size: 100
Multiplicity: [1]
Serial Number applied to the Boundary Feature during the production of the product.
This is not the unique key for this product and is not maintained.
Attribute Name: Feature_Serial_Number (GKPG), Feature_Serial_Number (TAB), NUMBER (Shapefile)
Data Type: Integer (TAB), Double (Shapefile)
Size: 11 (TAB), n/a (Shapefile)
Multiplicity: [1]
Collection Serial Number applied to the Boundary Feature during the production of the product.
This is not the unique key for this product and is not maintained.
Attribute Name: Collection_Serial_Number (GKPG), Collection_Serial_Number (TAB), NUMBER0 (Shapefile)
Data Type: Integer (TAB), Double (Shapefile)
Size: 11 (TAB), n/a (Shapefile)
Multiplicity: [1]
A globally unique sequential integer-maintained identifier.
Attribute Name: Global_Polygon_ID (GKPG), Global_Polygon_ID (TAB), POLYGON_ID (Shapefile)
Data Type: Integer (TAB), Double (Shapefile)
Size: 11 (TAB), n/a (Shapefile)
Multiplicity: [1]
A globally unique sequential integer-maintained feature identifier. There are two cases where multiple records have the same UNIT_ID:
When portions of local government or parliamentary constituency areas are separated from the main area, being completely surrounded by other local government or parliamentary constituency areas and not connected by direct access on the ground. Not applied to islands or parts of islands in the sea. Detached parts have the same attributes as the main area, except the POLYGON_ID and the Name which has a ‘(DET)’ suffix. In all the existing examples, there is exactly one detached part.
In Scotland, two examples where the boundary has thousands of parts, so the multi-polygon is broken into simple polygons to make it easier to handle. The examples are the supplementary country_region layer where NAME=‘SCOTLAND_COUNTRY’ and scotland_and_wales_region where NAME='Highlands and Islands PER'.
Attribute Name: Admin_Unit_ID (GKPG), Admin_Unit_ID (TAB), UNIT_ID (Shapefile)
Data Type: Integer (TAB), Double (Shapefile)
Size: 11 (TAB), n/a (Shapefile)
Multiplicity: [1]
Set to the Census / GSS Code for the boundary, for example, E10000014.
Attribute Name: Global_Polygon_ID (GKPG), Global_Polygon_ID (TAB), CODE (Shapefile)
Data Type: Char
Size: 9
Multiplicity: [0..1]
Set to the Census / GSS Code for the boundary, for example, E10000014.
Attribute Name: Hectares (GKPG), Hectares (TAB), HECTARES (Shapefile)
Data Type: Char
Size: 9
Multiplicity: [1]
Amount of area within the boundary which is not considered ‘inland’. Non-inland areas are calculated by comparing the Boundary-Line polygons with the Mean High Water lines. The value is in hectares and represents the area between the Mean High Water line and the seaward limit of the boundary denoting Mean Low Water.
Attribute Name: Non_Inland_Area (GKPG), Non_Inland_Area (TAB), AREA (Shapefile)
Data Type: Decimal (TAB), Double (Shapefile)
Size: 12 (TAB), n/a (Shapefile)
Multiplicity: [1]
Code depicting whether the boundary is part of a Civil Administration Area, a Civil Voting Area.
Attribute Name: Area_Type_Code (GKPG), Area_Type_Code (TAB), TYPE_CODE (Shapefile)
Size: 2
Multiplicity: [1]
Full description of TYPE_CODE.
Attribute Name: Area_Type_Description (GKPG), Area_Type_Description (TAB), DESCRIPT0 (Shapefile)
Data Type: Char
Size: 25
Multiplicity: [0..1]
Shouldn’t be populated.
Attribute Name: Non_Area_Type_Code (GKPG), Non_Area_Type_Code (TAB), TYPE_COD0 (Shapefile)
Data Type: Char
Size: 3
Multiplicity: [0..1]
Shouldn’t be populated.
Attribute Name: Non_Area_Type_Description (GKPG), Non_Area_Type_Description (TAB), DESCRIPT1 (Shapefile)
Data Type: Char
Size: 36
Multiplicity: [0..1]
This release note provides information about the June 2024 release of Boundary-Line.
Due to the recent coastline improvements that have been made, there are additional polygon vertices present in this release. If this causes any issues for you when loading the data, please let us know.
An error was found in the May 2024 v.1 release of the Boundary-Line product. The error meant that expected changes on the ward layer for Worcester City were not present in that release. This has since been corrected and is now present in the Boundary-Line product.
In the previous May release, due to an internal update to a system, the Unit ID were all been changed. These IDs have now been restored.
The attribute order found in the Shapefile format of this release have been updated to meet the attribute order stated in the product spec.
In line with the exit of the United Kingdom from the European Union, the European Region layer has been frozen as of 1 April 2021 (no edits have been made to the European Region extents since 31 December 2020, but there were some minor coastline edits up to 1 April 2021). This frozen layer is available as a supplementary Historical European Region layer within Boundary-Line.
For the purposes of Boundary Review, the extents of the European Regions in England have been retained in the Boundary-Line product and will be maintained as an English Region layer.
For customers who used the European Region layer to represent a national extent for Scotland and Wales, a new Country Region layer is available as a supplementary layer in Boundary-Line. This will be a maintained layer and represents the national extents of England, Scotland and Wales.
Boundary-Line is now released in vector tile (MBTiles) format as of October 2021.
Boundary-Line has updated the legal name of the National Assembly for Wales to Senedd Cymru/the Welsh Parliament.
The relevant legislation and Statutory Instruments (SIs) can be found here:
Legislation 1
Legislation 2 (Amended Wales Act(2006) with changed constituency name references)
The Global_Polygon_ID attribute is not present in the vector tile format of Boundary-Line at this release. All other formats are unaffected by this issue. This will be rectified for the subsequent release of Boundary-Line.
The Westminster Constituency Boundaries created by the National Boundary Commissions were based on the Ordnance Survey Boundary-Line product data in place on 1st December 2020. As this does not take account of any subsequent amendments to this product, there will be some variation between the boundaries displayed in the Boundary Line product and the Final Recommendations:
The Ordnance Survey has captured the Westminster Constituency features based on the Boundary-Line product electoral boundaries from the latest release and has corrected any minor errors to the Boundary Commission’s final recommendations. The types of corrections made would typically be as a result of administration changes due to electoral reviews, or geographical changes such as to coastline or rivers.
The Ordnance Survey Westminster Constituency Boundary between Stoke-on-Trent Central and Stoke on Trent North Constituencies has been amended at 26-45 Forest Edge, Sneyd Street Stoke-on Trent, ST6 2PY, and does not follow the boundary between the Moorcroft and Sneyd Green and Birches Head and Northwood electoral Wards. The Ordnance Survey Westminster Constituency boundary has been amended at this location and is consistent with the constituency boundary created by the Boundary Commission for England, this has been carried out to ensure that the properties indicated are located in the correct Westminster Constituency.
Ordnance Survey Westminster Constituency boundaries and Government Statistic Service (GSS) codes for the Ayr, Carrick and Cumnock / Berwickshire, Roxburgh and Selkirk / Central Ayrshire / Kilmarnock and Loudoun / West Aberdeenshire and Kincardine constituencies were amended following consultation with the Boundary Commission for Scotland and Government of Scotland.
The boundaries of these Westminster constituencies have been amended to ensure the consistency with local electoral boundaries, and as no electors were involved in any changes this did not affect the electoral totals. To indicate that these constituencies had been amended and were no longer the same as the current constituencies (dated 2007), and to prevent any confusion, new GSS codes were allocated to provide a unique identifier for the new parliamentary constituencies.
Residual Statutory Instruments (SIs) and non-SIs Boundary-Line only represents the boundaries that are currently operational; future dated or unsigned SIs will not be included. This ensures that the boundary information currency is correct at the time of the dataset release. SIs that are operational in May and or October but signed off too late for inclusion in the May or October products would be included in the next suitable release.
Each table summarises the County, Unitary Authority and Metropolitan District boundaries within each Government Office Region.
Bedford
Central Bedfordshire
Cambridgeshire county
Essex county
Hertfordshire county
Norfolk county
Suffolk county
City of Peterborough
Luton
Southend-on-Sea
Thurrock
Derbyshire county
Leicestershire county
Lincolnshire county
Northamptonshire county
Nottinghamshire county
City of Derby
City of Leicester
City of Nottingham
Rutland
Kingston upon Thames London borough
Croydon London borough
Bromley London borough
Hounslow London borough
Ealing London borough
Havering London borough
Hillingdon London borough
Harrow London borough
Brent London borough
Barnet London borough
Lambeth London borough
Southwark London borough
Lewisham London borough
Greenwich London borough
Bexley London borough
Barking and Dagenham London borough
City of London
Enfield London borough
Waltham Forest London borough
Redbridge London borough
Sutton London borough
Richmond upon Thames London borough
Merton London borough
Wandsworth London borough
Hammersmith and Fulham London borough
Kensington and Chelsea London borough
City of Westminster London borough
Camden London borough
Tower Hamlets London borough
Islington London borough
Hackney London borough
Haringey London borough
Newham London borough
Cheshire West and Chester
Cheshire East
Cumbria county
Lancashire county
Bolton metropolitan district
Bury metropolitan district
Knowsley metropolitan district
Liverpool metropolitan district
Manchester metropolitan district
Oldham metropolitan district
Rochdale metropolitan district
Salford metropolitan district
Sefton metropolitan district
Stockport metropolitan district
St. Helens metropolitan district
Tameside metropolitan district
Trafford metropolitan district
Warrington
Wigan metropolitan district
Wirral metropolitan district
Blackburn with Darwen
Blackpool
Halton
County Durham
Northumberland
Gateshead metropolitan district
Newcastle upon Tyne metropolitan district
North Tyneside metropolitan district
South Tyneside metropolitan district
Sunderland metropolitan district
Darlington
Hartlepool
Middlesbrough
Redcar and Cleveland
Stockton-on-Tees
Angus
West Dunbartonshire
Clackmannanshire
West Lothian
Dundee City
Highland
East Ayrshire
Moray
East Dunbartonshire
Orkney Islands
East Renfrewshire
Na h-Eileanan an Iar
Falkirk
Argyll and Bute
Glasgow City
Aberdeenshire
Inverclyde
Fife
Midlothian
Aberdeen City
North Lanarkshire
City of Edinburgh
Perth and Kinross
East Lothian
Renfrewshire
Shetland Islands
Scottish Borders
North Ayrshire
South Lanarkshire
Dumfries and Galloway
Stirling
South Ayrshire
Buckinghamshire
Milton Keynes
East Sussex county
Reading
Hampshire county
Slough
Kent county
The City of Brighton and Hove
Oxfordshire county
West Berkshire
Surrey county
Windsor and Maidenhead
West Sussex county
Wokingham
Bracknell Forest
Isle of Wight
City of Southampton
City of Portsmouth
Medway
Dorset
Bournemouth, Christchurch and Poole
Gloucestershire county
City of Bristol
Somerset county
South Gloucestershire
Wiltshire
Swindon
Devon county
Torbay
Cornwall
North Somerset
Isles of Scilly
City of Plymouth
Bath and North East Somerset
Abertawe – Swansea
Sir Ddinbych – Denbighshire
Blaenau Gwent – Blaenau Gwent
Sir Fynwy – Monmouthshire
Bro Morgannwg – the Vale of Glamorgan
Sir Gaerfyrddin – Carmarthenshire
Caerffili – Caerphilly
Sir y Fflint – Flintshire
Casnewydd – Newport
Tor-faen – Torfaen
Castell-nedd Port Talbot – Neath Port Talbot
Wrecsam – Wrexham
Conwy – Conwy
Sir Ynys Mon – Isle of Anglesey
Merthyr Tudful – Merthyr Tydfil
Gwynedd – Gwynedd
Pen-y-bont ar Ogwr – Bridgend
Caerdydd – Cardiff
Powys – Powys
Sir Ceredigion – Ceredigion
Rhondda Cynon Taf – Rhondda Cynon Taff
Sir Benfro – Pembrokeshire
Shropshire
Dudley metropolitan district
Staffordshire county
Sandwell metropolitan district
Warwickshire county
Solihull metropolitan district
Worcestershire county
Walsall metropolitan district
Birmingham metropolitan district
City of Stoke-on-Trent
City of Wolverhampton metropolitan district
County of Herefordshire
Coventry metropolitan district
Telford and Wrekin
North Yorkshire county
Sheffield metropolitan district
Barnsley metropolitan district
Wakefield metropolitan district
Bradford metropolitan district
City of Kingston upon Hull
Calderdale metropolitan district
East Riding of Yorkshire
Doncaster metropolitan district
North East Lincolnshire
Kirklees metropolitan district
North Lincolnshire
Leeds metropolitan district
York
Rotherham Metropolitan District
Previously, the reference to boroughs has not been included in the Boundary-Line product. In striving to improve the product and at the request of the end users, the inclusion of a reference to the boroughs will enable users to search within their GIS and locate them more easily. This addition was introduced in October 2006.
These additions only apply to England and affect the districts that have been granted Charters of Incorporation (CoI), unitary authorities that have been created from previous districts with CoI, and metropolitan districts that have borough status. The tables below identify where (B) has been added to the file name and (B) to the boundary data. This addition does not affect the structure or specification of the product and will not impact on your GIS or translation software.
BARNSLEY DISTRICT: Y
BIRMINGHAM DISTRICT: Y
BOLTON DISTRICT: Y
BRADFORD DISTRICT: Y
BURY DISTRICT: Y
CALDERDALE DISTRICT: Y
CITY OF WOLVERHAMPTON DISTRICT: Y
COVENTRY DISTRICT: Y
DONCASTER DISTRICT: Y
DUDLEY DISTRICT: Y
GATESHEAD DISTRICT: Y
KIRKLEES DISTRICT: Y
KNOWSLEY DISTRICT: Y
LEEDS DISTRICT: Y
LIVERPOOL DISTRICT: Y
MANCHESTER DISTRICT: Y
NEWCASTLE UPON TYNE DISTRICT: Y
NORTH TYNESIDE DISTRICT: Y
OLDHAM DISTRICT: Y
ROCHDALE DISTRICT: Y
ROTHERHAM DISTRICT: Y
SALFORD DISTRICT: Y
SANDWELL DISTRICT: Y
SEFTON DISTRICT: Y
SHEFFIELD DISTRICT: Y
SOLIHULL DISTRICT: Y
SOUTH TYNESIDE DISTRICT: Y
ST. HELENS DISTRICT: Y
STOCKPORT DISTRICT: Y
SUNDERLAND DISTRICT: Y
TAMESIDE DISTRICT: Y
TRAFFORD DISTRICT: Y
WAKEFIELD DISTRICT: Y
WALSALL DISTRICT: Y
WIGAN DISTRICT: Y
WIRRAL DISTRICT: Y
ADUR: N
ARUN: N
ASHFIELD: N
BABERGH: N
BASSETLAW: N
BLABY: N
BOLSOVER: N
BRAINTREE: N
BRECKLAND: N
BROADLAND: N
BROMSGROVE: N
CANNOCK CHASE: N
CHERWELL: N
CHICHESTER: N
COTSWOLD: N
DERBYSHIRE DALES: N
DOVER: N
EAST CAMBRIDGESHIRE: N
EAST DEVON: N
EAST HAMPSHIRE: N
EAST HERTFORDSHIRE: N
EAST LINDSEY: N
EAST SUFFOLK: N
EPPING FOREST: N
FENLAND: N
FOLKESTONE AND HYTHE: N
FOREST OF DEAN: N
HARBOROUGH: N
HARLOW: N
HART: N
HORSHAM: N
HUNTINGDONSHIRE: N
LEWES: N
LICHFIELD: N
MALVERN HILLS: N
MANSFIELD: N
MID DEVON: N
MID SUFFOLK: N
MID SUSSEX: N
MOLE VALLEY: N
NEW FOREST: N
NEWARK AND SHERWOOD: N
NORTH DEVON: N
NORTH EAST DERBYSHIRE: N
NORTH HERTFORDSHIRE: N
NORTH KESTEVEN: N
NORTH NORFOLK: N
NORTH WEST LEICESTERSHIRE: N
ROCHFORD: N
ROTHER: N
SEVENOAKS: N
SOUTH CAMBRIDGESHIRE: N
SOUTH DERBYSHIRE: N
SOUTH HAMS: N
SOUTH HOLLAND: N
SOUTH KESTEVEN: N
SOUTH NORFOLK: N
SOUTH OXFORDSHIRE: N
SOUTH STAFFORDSHIRE: N
STAFFORDSHIRE MOORLANDS: N
STRATFORD-ON-AVON: N
STROUD: N
TANDRIDGE: N
TEIGNBRIDGE: N
TENDRING: N
THANET: N
THREE RIVERS: N
TORRIDGE: N
UTTLESFORD: N
VALE OF WHITE HORSE: N
WARWICK: N
WEALDEN: N
WEST LINDSEY: N
WEST OXFORDSHIRE: N
WEST SUFFOLK: N
WYCHAVON: N
WYRE FOREST: N
AMBER VALLEY: Y
ASHFORD: Y
BASILDON: Y
BASINGSTOKE AND DEANE: Y
BOSTON: Y
BRENTWOOD: Y
BROXBOURNE: Y
BROXTOWE: Y
BURNLEY: Y
CAMBRIDGE: Y
CANTERBURY: Y
CASTLE POINT: Y
CHARNWOOD: Y
CHELMSFORD: Y
CHELTENHAM: Y
CHESTERFIELD: Y
CHORLEY: Y
COLCHESTER: Y
CRAWLEY: Y
DACORUM: Y
DARTFORD: Y
EASTBOURNE: Y
EASTLEIGH: Y
EAST STAFFORDSHIRE: Y
ELMBRIDGE: Y
EPSOM AND EWELL: Y
EREWASH: Y
EXETER: Y
FAREHAM: Y
FYLDE: Y
GEDLING: Y
GLOUCESTER: Y
GOSPORT: Y
GRAVESHAM: Y
GREAT YARMOUTH: Y
GUILDFORD: Y
HASTINGS: Y
HAVANT: Y
HERTSMERE: Y
HIGH PEAK: Y
HINCKLEY AND BOSWORTH: Y
HYNDBURN: Y
IPSWICH: Y
KING'S LYNN AND WEST NORFOLK: Y
LANCASTER: Y
LINCOLN: Y
MAIDSTONE: Y
MALDON: Y
MELTON: Y
NEWCASTLE-UNDER-LYME: Y
NORTH WARWICKSHIRE: Y
NORWICH: Y
NUNEATON AND BEDWORTH: Y
OADBY AND WIGSTON: Y
OXFORD: Y
PENDLE: Y
PRESTON: Y
REDDITCH: Y
REIGATE AND BANSTEAD: Y
RIBBLE VALLEY: Y
ROSSENDALE: Y
RUGBY: Y
RUNNYMEDE: Y
RUSHCLIFFE: Y
RUSHMOOR: Y
SOUTH RIBBLE: Y
SPELTHORNE: Y
ST ALBANS: Y
STAFFORD: Y
STEVENAGE: Y
SURREY HEATH: Y
SWALE: Y
TAMWORTH: Y
TEST VALLEY: Y
TEWKESBURY: Y
TONBRIDGE AND MALLING: Y
TUNBRIDGE WELLS: Y
WATFORD: Y
WAVERLEY: Y
WELWYN HATFIELD: Y
WEST DEVON: Y
WEST LANCASHIRE: Y
WINCHESTER: Y
WOKING: Y
WORCESTER: Y
WORTHING: Y
WYRE: Y
Information published by the Office for National Statistics (ONS) identifies the European classification system called NUTS (Nomenclature of Units for Territorial Statistics). This information provides a breakdown of UK regions and countries, allowing for a comparable view of economic activity across the European Union.
NUTS1 – English Government Office Regions, Wales, Scotland and Northern Ireland.
NUTS2 – 37 areas, mainly groups of counties and unitary authorities.
NUTS3 – 133 areas, principally individual counties and unitary authorities.
Area features are polygons with attributes added.
The following schema applies for all area features in the english_region_region
and english_region
layers in the GB
folder of the shapefile, MapInfo TAB and GeoPackage data supply, respectively.
The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.
Feature identifier added by the software.
Attribute Name: fid (GKPG), Not provided (TAB), Not provided (Shapefile)
Multiplicity: [1]
Feature geometry.
Attribute Name: Not provided (GKPG), Not provided (TAB), SHAPE (Shapefile)
Data Type: Polygon
Multiplicity: [1]
Name of the administrative area.
Attribute Name: Name (GKPG), Name (TAB), NAME (Shapefile)
Data Type: char
Size: 100
Multiplicity: [0..1]
A code describing the level.
Attribute Name: Area_Code (GKPG), Area_Code (TAB), AREA_CODE (Shapefile)
Data Type: char
Size: 3
Multiplicity: [1]
Full name of the Area_Code
.
Attribute Name: Area_Description (GKPG), Area_Description (TAB), DESCRIPT0 (Shapefile)
Data Type: char
Size: 50
Multiplicity: [1]
Name of the Principal Area which the boundary sits within.
This may be the same boundary level as the boundary itself, for example, a Greater London Authority boundary will have ‘Greater London Authority’ present in this field. But for more granular boundaries, this field will show the principal boundary which is at the principal level.
Attribute Name: File_Name (GKPG), File_Name (TAB), FILE_NAME (Shapefile)
Data Type: char
Size: 100
Multiplicity: [1]
Serial Number applied to the Boundary Feature during the production of the product.
This is not the unique key for this product and is not maintained.
Attribute Name: Feature_Serial_Number (GKPG), Feature_Serial_Number (TAB), NUMBER (Shapefile)
Data Type: Integer (TAB), Double (Shapefile)
Size: 11 (TAB), n/a (Shapefile)
Multiplicity: [1]
Collection Serial Number applied to the Boundary Feature during the production of the product.
This is not the unique key for this product and is not maintained.
Attribute Name: Collection_Serial_Number (GKPG), Collection_Serial_Number (TAB), NUMBER0 (Shapefile)
Data Type: Integer (TAB), Double (Shapefile)
Size: 11 (TAB), n/a (Shapefile)
Multiplicity: [1]
A globally unique sequential integer-maintained identifier.
Attribute Name: Global_Polygon_ID (GKPG), Global_Polygon_ID (TAB), POLYGON_ID (Shapefile)
Data Type: Integer (TAB), Double (Shapefile)
Size: 11 (TAB), n/a (Shapefile)
Multiplicity: [1]
A globally unique sequential integer-maintained feature identifier. There are two cases where multiple records have the same UNIT_ID:
When portions of local government or parliamentary constituency areas are separated from the main area, being completely surrounded by other local government or parliamentary constituency areas and not connected by direct access on the ground. Not applied to islands or parts of islands in the sea. Detached parts have the same attributes as the main area, except the POLYGON_ID and the Name which has a ‘(DET)’ suffix. In all the existing examples, there is exactly one detached part.
In Scotland, two examples where the boundary has thousands of parts, so the multi-polygon is broken into simple polygons to make it easier to handle. The examples are the supplementary country_region layer where NAME=‘SCOTLAND_COUNTRY’ and scotland_and_wales_region where NAME='Highlands and Islands PER'.
Attribute Name: Admin_Unit_ID (GKPG), Admin_Unit_ID (TAB), UNIT_ID (Shapefile)
Data Type: Integer (TAB), Double (Shapefile)
Size: 11 (TAB), n/a (Shapefile)
Multiplicity: [1]
Set to the Census / GSS Code for the boundary, for example, E10000014.
Attribute Name: Global_Polygon_ID (GKPG), Global_Polygon_ID (TAB), CODE (Shapefile)
Data Type: Char
Size: 9
Multiplicity: [0..1]
Set to the Census / GSS Code for the boundary, for example, E10000014.
Attribute Name: Hectares (GKPG), Hectares (TAB), HECTARES (Shapefile)
Data Type: Char
Size: 9
Multiplicity: [1]
Amount of area within the boundary which is not considered ‘inland’. Non-Inland Areas are calculated by comparing the Boundary-Line polygons with the Mean High Water lines. The value is in hectares and represents the area between the Mean High Water line and the seaward limit of the boundary denoting Mean Low Water.
Attribute Name: Non_Inland_Area (GKPG), Non_Inland_Area (TAB), AREA (Shapefile)
Data Type: Decimal (TAB), Double (Shapefile)
Size: 12 (TAB), n/a (Shapefile)
Multiplicity: [1]
Code depicting whether the boundary is part of a Civil Administration Area, a Civil Voting Area.
Attribute Name: Area_Type_Code (GKPG), Area_Type_Code (TAB), TYPE_CODE (Shapefile)
Size: 2
Multiplicity: [1]
Full description of TYPE_CODE.
Attribute Name: Area_Type_Description (GKPG), Area_Type_Description (TAB), DESCRIPT0 (Shapefile)
Data Type: Char
Size: 25
Multiplicity: [0..1]
Shouldn’t be populated.
Attribute Name: Non_Area_Type_Code (GKPG), Non_Area_Type_Code (TAB), TYPE_COD0 (Shapefile)
Data Type: Char
Size: 3
Multiplicity: [0..1]
Shouldn’t be populated.
Attribute Name: Non_Area_Type_Description (GKPG), Non_Area_Type_Description (TAB), DESCRIPT1 (Shapefile)
Data Type: Char
Size: 36
Multiplicity: [0..1]
This overview introduces Boundary-Line and gives context for all users – highlighting key features, providing examples of potential uses, and listing details such as file sizes, supply formats, etc.
Boundary-Line provides a representation of the hierarchy of administrative and electoral boundaries and their names for England, Scotland and Wales. Boundary-Line for England and Wales was initially digitised from Ordnance Survey’s boundary record sheets at 1:10 000 scale (or, in some cases, at larger scales).
The Government Statistical Service (GSS) codes are supplied by the Office for National Statistics (ONS) and General Register Office for Scotland (GROS).
Appropriate software is needed to use the data for your intended application.
The high specification of Boundary-Line offers you the following benefits:
Full coverage of Great Britain, supplied as England, Scotland and Wales.
The key boundary dataset for Great Britain, suited to multiple applications using a geographical information system (GIS) and other digital mapping systems.
The full hierarchy of boundaries.
Structured vector format, offering great functionality.
GSS codes, where available, which allow you to link Boundary-Line polygons with GSS information.
Area values for every polygon.
Mean high water (springs) mark, which enables you to build and explicitly identify dry land areas within coastal polygons.
Documented updates via bi-annual releases allow you to easily identify relevant changes.
Unique administrative area identifiers are retained at each update, allowing revised boundaries to be related to your existing data.
Boundary-Line can be used for GIS analysis to support a wide range of business decision-making, such as:
Political analysis
Environmental analysis
Statistical analysis for social or marketing decision-making
Geo-demographic analysis
Asset management
Planning applications
Legal work
Reference and research
Customised graphic output
Boundary-Line is available in the following formats:
Esri shapefile
MapInfo TAB file
GeoPackage
Geography Markup Language (GML)
Vector tiles (MBTiles)
Boundary-Line can be freely downloaded under the Open Government Licence. Data can be downloaded in various formats from the Ordnance Survey Data Hub.
Boundary-Line is updated twice a year, in spring and autumn, allowing a choice as to which update is preferred.
The spring update represents boundaries (as defined and modified by Orders, Acts and Statutory Instruments) at the date of the May local elections.
The autumn update also represents boundaries at the date of the May local elections and is operative from the previous spring / May to autumn / October release.
Unlike changes to other boundaries, changes to Westminster constituency (parliamentary) boundaries do not come into operation on a defined date, and it is therefore difficult to timetable such changes into the spring or autumn updates. Therefore, any forthcoming Westminster constituency (parliamentary) boundary changes that have been approved by Government will be supplied as a separate file (in MapInfo TAB or Esri shapefile formats only) as part of the updates until they are included in the product.
Boundary-Line provides a representation of the hierarchy of administrative and electoral boundaries and their names for England, Scotland and Wales. Boundary-Line for England and Wales was initially digitised from Ordnance Survey’s boundary record sheets at 1:10 000 scale (or, in some cases, at larger scales).
This product is updated twice a year.
Public bodies release a wealth of data via data.gov.uk, census results and other sources. By illustrating your analysis on maps created with Boundary-Line, you'll be able to highlight the social and economic trends shaping changes in how we live and work.
As an addition to the core Boundary-Line product, which is updated twice a year, you can download data showing historical county boundaries from the late 19th Century. This is ideal for historians who need to analyse old census records and archives.
Monitoring outcomes by area is key for public bodies. Boundary-Line gives you a robust analytical framework to ensure the right communities get the right resources.
Mapped at a scale of 1:10 000, Boundary-Line is quality-assured to the same standard as our premium products. But since it's covered by the Open Government Licence (OGL), you can download it for free and use it in a wide range of ways.
Boundary-Line brings the statistics in your reports to life. It lets you show differences between regions or councils using easy-to-read shaded maps.
When you're consulting on updating boundaries to take account of population change, Boundary-Line lets you show on a map where the line's being drawn, right down to the level of individual properties.
Boundary-Line can be used for GIS analysis to support a wide range of business decision-making, such as:
Political analysis
Environmental analysis
Statistical analysis for social or marketing decision-making
Geo-demographic analysis
Asset management
Planning applications
Legal work
Reference and research
Customised graphic output
Access: Download
Data theme: Administrative and Statistical Units
Data structure: Vector - Polygons
Coverage: Great Britain
Scale: 1:10 000
Format: Vector Tiles, GeoPackage, ESRI Shapefile, MapInfo TAB, GML 3.2.1
Ordering area: All of Great Britain
Publication months: May, October
OS Data Hub plan: OS OpenData Plan (FREE), Public Sector Plan, Premium Plan, Energy & Infrastructure Plan
Access to OS OpenData is free through the OS Data Hub.
Boundary-Line data is output in a layered structure. This is a simplified file structure whereby the boundaries are supplied as individual files; for example, the county file contains only counties.
Ceremonial and Historical counties are provided in separate directories called Supplementary_Ceremonial and Supplementary_Historical, respectively. Historic European Regions are provided in a separate Supplementary_Historic_European_Region directory and Country outlines are provided in a separate Supplementary_Country directory.
The ‘places’ known as ‘The Inner and Middle Temples’ are within the City of London only for some purposes. They are not shown in Boundary-Line, but their areas have been wholly included within the city and its wards for this dataset. There are two distinct areas with other areas held jointly, and the boundaries are so intermixed that they have never been published by Ordnance Survey separately. A record of these boundaries is, however, held in the Boundary Record Library for reference purposes.
Divisions of parishes (England) and communities (Wales) not included in Boundary-Line.
These are areas where the limits of the parishes concerned have not been determined and the area itself is common to (or belongs to) two or more parishes. In Boundary-Line, they are classified as separate parishes with the name LANDS COMMON TO THE PARISHES OF… applied (sometimes abbreviated to LCPs…).
The boundary between Wirral metropolitan district in the former county of Merseyside and Cheshire West and Chester unitary authority in the former county of Cheshire and the Flintshire unitary authority area has not been determined, and the line adopted in Boundary-Line is for the purposes of Ordnance Survey only, so that polygons can be created.
Certain sections of the boundary between the former county of Merseyside (containing the metropolitan districts of Liverpool and Wirral), and in the former county of Cheshire, now Cheshire West and Chester, and Halton have never been determined.
For the purposes of Boundary-Line and by agreement with DCLG:
The district boundaries of those parts of Cheshire West and Chester that abut the Mersey estuary have been made coincident with the limits of the relevant district’s wards at the centre of the channel at high water (CCHW).
The undetermined part of the southern boundary of Liverpool district, in the Mersey estuary, has been made coincident with the limits of that district’s wards at the CCHW.
The undetermined part of the county boundary between the former county of Merseyside and the former county of Cheshire in that part of the estuary between the new Cheshire West and Chester and Liverpool has been made coincident with the limits of the wards at the CCHW.
The northern limit of the parliamentary constituency of Ellesmere Port and Neston is the mean high-water mark on the south side of the Mersey estuary.
These ‘wards’, which include the personal apartments of the Sovereign have no relevance to the election of councillors to electoral areas and are wholly included within the district of Windsor and Maidenhead and its wards.
This section details the features for ESRI Shapefile, MapInfo TAB and GeoPackage only. Please see and for information about working with these formats.
This section describes the features for ESRI shapefile, MapInfo TAB and GeoPackage which make up the Boundary-Line product, giving the following information about each attribute:
The name of the attribute and what it is describing.
A condition associated with the attribute (Optional).
The nature of the attribute, for example, a numeric value or a code list value.
Describes how many times this element is expected to be populated in the data. An attribute may be optional or mandatory within the Boundary-Line product. These are denoted by:
‘1’ – Mandatory – There must be a value.
‘0..1’ – Optional – If populated, a maximum of one attribute will be returned.
These values may be used in combination.
The external bounding line of the Boundary-Line dataset is the extent of the realm (EOR). This means the boundary extent is digitised on the alignment of the mean low water (springs) (MLWS) for the seaward extent. Boundary-Line does not contain a separate mean low water (springs) (MLWS), only CODE 0071 representing the mean high water (MHW).
To display the EOR, both MHW and another type of boundary (for example, European electoral region or Westminster constituency) need to be displayed together.
The Territorial Waters Jurisdiction Act 1878 and the Territorial Waters Order in Council 1964 confirm that the EOR of Great Britain as used by Ordnance Survey is properly shown to the limit of mean low water for the time being, except where extended by Parliament.
This means that the EOR will be:
The mean low water mark (mean low water springs in Scotland) except when landward of a seaward extension or as shown in Figure 5a and indicated as Point B.
The mean high water mark (mean high water springs in Scotland), where coincident with mean low water or mean low water springs, but not when landward of a seaward extension or Point B.
Point B
Seaward extensions
In the figure below, the EOR follows mean low water (springs), crossing the estuaries at LWL.
The figure below shows how these features are represented in Boundary-Line.
The foreshore is taken to be the area of land between mean high water (springs) mark and the EOR which will include:
Tidal water within a seaward extension.
Tidal water above Point B, to the normal tidal limit (NTL), together with the area between mean high water (springs) mark and the edge of the channel at mean low water (springs).
Mean high water (springs) mark is represented in Boundary-Line by a polyline feature with CODE 0071. Mean low water (springs) mark is not shown, although it is generally coincident with the EOR.
The area of non-inland is referenced within each administrative unit using the NA attribute.
The following rules govern the representation in Boundary-Line of offshore islands and rocks in the sea:
Offshore rocks and islands will be shown if 0.4 hectares or more in area at high tide.
Offshore islands with buildings will always be shown, irrespective of size.
Offshore islands or rocks will not be shown if they are:
Beyond the defined EOR, irrespective of size.
Covered at high tide.
If an offshore island or rock is shown, it will be contained within all the relevant administrative unit collections.
The mean high water (springs) mark is shown to NTL.
Areas of salt marsh, mudflats and so on often have very complicated tide lines. For ease of digitising and to reduce data volumes, mean high water may be generalised in these areas (not Scotland).
Mean high water (springs) mark is represented in Boundary-Line by a polyline feature with CODE 0071.
Mean high water (springs) mark is subject to continuous change but the captured alignment of a tide line is a snapshot on one day. It is not practical to revise tide lines very frequently.
Mean low water (springs) mark is shown as the EOR, except when contained within a seaward extension, when it is then omitted.
Banks of sand, mud, shingle or rock separated from the main line of mean low water (springs), and covered at high tide, are not shown. When there are large areas of these banks separated from the main foreshore by narrow channels, the channels are ignored and the whole bounded by mean low water (springs).
The extension of the line of mean low water (springs) into a channel above Point B becomes edge of channel and is not shown.
Mean low water (springs) mark, and hence EOR is subject to continuous change but the captured alignment of a tide line is a snapshot on one day. It is not practical to revise tide lines very frequently.
The normal tidal limit (NTL) is the point at which the level of a river or stream ceases to be affected by the tidal flow. This point is often an artificial barrier such as a lock or weir.
A pier under which water flows is not normally considered to be within the realm. There are some cases, however, where a structure has specifically been included within the realm by act or order, in which case mean high water (springs) mark and EOR are shown around the limits of the structure.
This is the intangible line across a channel where the level of the river meets the level of the sea at low water.
Within large channels or estuaries, Point B is defined on the source documents for Boundary-Line and is therefore shown as the EOR.
In small channels, Point B is not shown on the source documents, so is assumed to be along the general line of low water and is shown as the EOR.
These are artificial extensions to the realm that have been made by an Act of Parliament. They extend the local government and parliamentary areas seaward of mean low water (springs) mark.
Breakwaters are structures of wood, stone, metal or other material built to break the force of waves. They can be separate from or joined to the mainland. If joined, they are generally included in the local government and parliamentary areas. If separate, they are not part of the local government and parliamentary area unless they are placed therein by legislation of some kind; for example, Plymouth breakwater is included in the local government area, whilst the centre portion of the Portland Harbour breakwater is not.
Permanent or solid structures in the sea, such as the forts in the Solent off Portsmouth Harbour and Brighton Marina, are usually included in local government and parliamentary areas.
This technical specification provides detailed technical information about Boundary-Line. It is targeted at technical users and software developers.
Boundary-Line provides a representation of the hierarchy of administrative and electoral boundaries and their names for England, Scotland and Wales. Boundary-Line for England and Wales was initially digitised from Ordnance Survey’s boundary record sheets at 1:10 000 scale (or, in some cases, at larger scales).
The Government Statistical Service (GSS) codes are supplied by the Office for National Statistics (ONS) and General Register Office for Scotland (GROS).
Appropriate software is needed to use the data for your intended application.
This technical specification includes the following sections:
Additional GOR information can be found at and This will identify the GORs defined by the Office for National Statistics (ONS), which only covers England.
Code List Name:
Code List Name:
County Boundary Type | District, Borough, Unitary Authority | Operative date | SI date: if applicable | SI number: if applicable | Comments |
---|
County Boundary Type | District, Borough, Unitary Authority | Operative date | SI date: if applicable | SI number: if applicable | Comments |
---|
Unitary Authority | Borough Status |
---|
NUTS 1 | NUTS 2 | NUTS 3 | LAU 1 Areas |
---|
Code List Name:
N/A | PARISH BUCKINGHAMSHIRE | 1 APRIL 2019 | N/A | N/A | WYCOMBE RCG 2019 |
SUFFOLK | PARISH WEST SUFFOLK | 26 SEPTEMBER 2023 | N/A | N/A | MILDENHALL NAME CHANGE LETTER |
N/A | WESTMINSTER PARLIAMENTARY CONSTITUENCIES | 31 MAY 2024 | 15 NOVEMBER 2023 | 1230 | THE PARLIAMENTARY CONSTITUENCIES ORDER 2023 |
N/A | N/A | N/A | N/A | N/A | N/A |
BATH AND NORTH EAST SOMERSET | N |
BOURNEMOUTH, CHRISTCHURCH AND POOLE | N |
BUCKINGHAMSHIRE | N |
CENTRAL BEDFORDSHIRE | N |
CORNWALL | N |
COUNTY DURHAM | N |
COUNTY OF HEREFORDSHIRE | N |
CUMBERLAND | N |
DORSET | N |
EAST RIDING OF YORKSHIRE | N |
ISLE OF WIGHT | N |
ISLES OF SCILLY | N |
NORTH NORTHAMPTONSHIRE | N |
NORTH SOMERSET | N |
NORTH YORKSHIRE | N |
NORTHUMBERLAND | N |
RUTLAND | N |
SHROPSHIRE | N |
SOMERSET | N |
SOUTH GLOUCESTERSHIRE | N |
WESTMORLAND AND FURNESS | N |
WEST BERKSHIRE | N |
WILTSHIRE | N |
BEDFORD | Y |
BLACKBURN WITH DARWEN | Y |
BLACKPOOL | Y |
BRACKNELL FOREST | Y |
BRIGHTON AND HOVE | Y |
CHESHIRE EAST | Y |
CHESHIRE WEST AND CHESTER | Y |
CITY OF BRISTOL | Y |
CITY OF DERBY | Y |
CITY OF KINGSTON UPON HULL | Y |
CITY OF LEICESTER | Y |
CITY OF NOTTINGHAM | Y |
CITY OF PETERBOROUGH | Y |
CITY OF PLYMOUTH | Y |
CITY OF PORTSMOUTH | Y |
CITY OF SOUTHAMPTON | Y |
CITY OF STOKE-ON-TRENT | Y |
DARLINGTON | Y |
HALTON | Y |
HARTLEPOOL | Y |
LUTON | Y |
MEDWAY | Y |
MIDDLESBROUGH | Y |
MILTON KEYNES | Y |
NORTH EAST LINCOLNSHIRE | Y |
NORTH LINCOLNSHIRE | Y |
READING | Y |
REDCAR AND CLEVELAND | Y |
SLOUGH | Y |
SOUTHEND-ON-SEA | Y |
STOCKTON-ON-TEES | Y |
SWINDON | Y |
TELFORD AND WREKIN | Y |
THURROCK | Y |
TORBAY | Y |
WARRINGTON | Y |
WEST NORTHAMPTONSHIRE | N |
WINDSOR AND MAIDENHEAD | Y |
WOKINGHAM | Y |
YORK | Y |
South West | Gloucestershire, Wiltshire and North Somerset | Bristol, city of | Bristol, city of |
Bath and North East Somerset, North Somerset and South Gloucestershire | Bath and North East Somerset, North Somerset, South Gloucestershire |
Gloucestershire | Cheltenham, Cotswold, Forest of Dean, Gloucester, Stroud, Tewkesbury |
Swindon | Swindon |
Wiltshire | Wiltshire |
Dorset and Somerset | Bournemouth, Christchurch and Poole | Bournemouth, Poole |
Dorset | Christchurch, East Dorset, North Dorset, Purbeck, West Dorset, Weymouth and Portland |
Somerset | Mendip, Sedgemoor, South Somerset, Somerset West and Taunton |
Cornwall and Isles of Scilly | Cornwall and Isles of Scilly | Cornwall, Isles of Scilly |
Devon | Plymouth | Plymouth |
Torbay | Torbay |
Devon CC | East Devon, Exeter, Mid Devon, North Devon, South Hams, Teignbridge, Torridge, West Devon |
South East | Berkshire, Northamptonshire and Oxfordshire | Berkshire | Bracknell Forest, Reading, Slough, West Berkshire, Windsor and Maidenhead, Wokingham |
Milton Keynes | Milton Keynes |
Buckinghamshire CC | Aylesbury Vale, Chiltern, South Bucks, Wycombe |
Oxfordshire | Cherwell, Oxford, South Oxfordshire, Vale of White Horse, West Oxfordshire |
Surrey, East and West Sussex | Brighton and Hove | Brighton and Hove |
East Sussex CC | Eastbourne, Hastings, Lewes, Rother, Wealden |
Surrey | Elmbridge, Epsom and Ewell, Guildford, Mole Valley, Reigate and Banstead, Runnymede, Spelthorne, Surrey Heath, Tandridge, Waverley, Woking |
West Sussex | Adur, Arun, Chichester, Crawley, Horsham, Mid Sussex, Worthing |
Hampshire and Isle of Wight | Portsmouth | Portsmouth |
Southampton | Southampton |
Hampshire CC | Basingstoke and Deane, East Hampshire, Eastleigh, Fareham, Gosport, Hart, Havant, New Forest, Rushmoor, Test Valley, Winchester |
Isle of Wight | Isle of Wight |
Kent | Kent CC | Ashford, Canterbury, Dartford, Dover, Folkestone and Hythe, Gravesham, Maidstone, Medway, Sevenoaks, Swale, Thanet, Tonbridge and Malling, Tunbridge Wells |
East of England | East Anglia | Peterborough | Peterborough |
Cambridgeshire CC | Cambridge, East Cambridgeshire, Fenland, Huntingdonshire, South Cambridgeshire |
Norfolk | Breckland, Broadland, Great Yarmouth, King's Lynn and West Norfolk, North Norfolk, Norwich, South Norfolk |
Suffolk | Babergh, East Suffolk, Ipswich, Mid Suffolk, West Suffolk |
Bedfordshire and Hertfordshire | Luton | Luton |
Bedford | Bedford, Central Bedfordshire |
Hertfordshire | Broxbourne, Dacorum, East Hertfordshire, Hertsmere, North Hertfordshire, St Albans, Stevenage, Three Rivers, Watford, Welwyn Hatfield |
Essex | Southend-on-Sea | Southend-on-Sea |
Thurrock | Thurrock |
Essex CC | Basildon, Braintree, Brentwood, Castle Point, Chelmsford, Colchester, Epping Forest, Harlow, Maldon, Rochford, Tendring, Uttlesford |
East Midlands | Derbyshire and Nottinghamshire | Derby | Derby |
East Derbyshire | Bolsover, Chesterfield, North East Derbyshire |
South and West Derbyshire | Amber Valley, Derbyshire Dales, Erewash, High Peak, South Derbyshire |
Nottingham | Nottingham |
North Nottinghamshire | Ashfield, Bassetlaw, Mansfield, Newark and Sherwood |
South Nottinghamshire | Broxtowe, Gedling, Rushcliffe |
Leicestershire, Rutland and Northamptonshire | Leicester | Leicester |
Leicestershire CC and Rutland | Blaby, Charnwood, Harborough, Hinckley and Bosworth, Melton, North West Leicestershire, Oadby and Wigston, Rutland |
Northamptonshire | Corby, Daventry, East Northamptonshire, Kettering, Northampton, South Northamptonshire, Wellingborough |
Lincolnshire | Lincolnshire | Boston, East Lindsey, Lincoln, North Kesteven, South Holland, South Kesteven, West Lindsey |
London | Inner London | Inner London – West | Camden, City of London, Hammersmith and Fulham, Kensington and Chelsea, Wandsworth, Westminster |
Inner London – East | Hackney, Haringey, Islington, Lambeth, Newham, Southwark, Lewisham, Tower Hamlets |
Outer London | Outer London – East and North-East | Barking and Dagenham, Bexley, Enfield, Greenwich, Havering, Redbridge, Waltham Forest |
Outer London – South | Bromley, Croydon, Kingston upon Thames, Merton, Sutton |
Outer London – West and North-West | Barnet, Brent, Ealing, Harrow, Hillingdon, Hounslow, Richmond upon Thames |
North West | Cumbria | West Cumbria | Allerdale, Barrow-in-Furness, Copeland |
East Cumbria | Carlisle, Eden, South Lakeland |
Cheshire | Halton and Warrington | Halton, Warrington |
Cheshire West and Chester | Cheshire West and Chester |
Ceshire East | Ceshire East |
Greater Manchester | Greater Manchester South | Manchester, Salford, Stockport, Tameside, Trafford |
Greater Manchester North | Bolton, Bury, Oldham, Rochdale, Wigan |
Lancashire | Blackburn with Darwen | Blackburn with Darwen |
Blackpool | Blackpool |
Lancashire CC | Burnley, Chorley, Fylde, Hyndburn, Lancaster, Pendle, Preston, Ribble Valley, Rossendale, South Ribble, West Lancashire, Wyre |
Merseyside | East Merseyside | Knowsley, St. Helens |
Liverpool | Liverpool |
Sefton | Sefton |
The Wirrral | Wirral |
North East | Tees Valley and Durham | Hartlepool and Stockton-on-Tees | Hartlepool and Stockton-on-Tees |
South Teeside | Middlesbrough Redcar and Cleaveland |
Darlington | Darlington |
County Durham | County Durham |
Northumberland and Tyne and Wear | Northumberland | Northumberland |
Tyneside | Gateshead, Newcastle upon Tyne, North Tyneside, South Tyneside |
Sunderland | Sunderland |
Scotland | Eastern Scotland | Angus and Dundee City | Angus, Dundee City |
Clackmannanshire and Fife | Clackmannanshire, Fife |
East Lothian and Midlothian | East Lothian, Midlothian |
Scottish Borders | Scottish Borders |
Edinburgh, City of | Edinburgh, City of |
Falkirk | Falkirk |
Perth & Kinross and Stirling | Perth & Kinross and Stirling |
West Lothian | West Lothian |
Highlands and Islands | Caithness & Sutherland and Ross & Cromarty | Caithness & Sutherland and Ross & Cromarty |
Inverness & Nairn, West Moray and Badenoch & Strathspey | Badenoch and Strathspey, Inverness and Nairn, West Moray |
Lochaber, Skye & Lochalsh, Arran & Cumbrae and Argyll & Bute | Argyle and Bute UA, Islands, Argyll and the islands, LEC Mainland, Arran and the Cumbraes, Lochaber, Skye and Lochalsh |
Eilean Siar (Western Isles) | Eilean Siar (Western Isles) |
Orkney Islands | Orkney Islands |
Shetland Islands | Shetland Islands |
North Eastern Scotland | Aberdeen city, Aberdeenshire and North East Moray | Aberdeen city, Aberdeenshire and North East Moray |
East Dubartonshire, West Dunbartonshire and Helensburgh & Lomond | East Dubartonshire, West Dunbartonshire and Helensburgh & Lomond |
South Western Scotland | Dumfries & Galloway | Dumfries & Galloway |
East Ayrshire and North Ayrshire mainland | East Ayrshire, North Ayrshire mainland |
Glasgow city | Glasgow city |
Inverclyde, East Renfrewshire and Renfrewshire | East Renfrewshire, Inverclyde, Renfrewshire |
North Lanarkshire | North Lanarkshire |
South Ayrshire | South Ayrshire |
South Lanarkshire | South Lanarkshire |
Wales | West Wales and The Valleys | Isle of Angelsey | Isle of Angelsey |
Gwynedd | Gwynedd |
Conwy and Denbigshire | Conwy, Denbigshire |
South West Wales | Carmarthenshire, Ceredigion, Pembrokeshire |
Central Valleys | Merthyr Tydfil, Rhondda, Cynon Taff |
Gwent Valleys | Blaenau Gwent, Caerphilly, Torfaen |
Bridgend and Neath, Port Talbot | Bridgend, Neath Port Talbot |
Swansea | Swansea |
East Wales | Mounmouthshire and Newport | Monmouthshire, Newport |
Cardiff and the Vale of Glamorgan | Cardiff, The Vale of Glamorgan |
Flintshire and Wrexham | Flintshire, Wrexham |
Powys | Powys |
West Midlands | Herefordshire, Worcestershire and Warwickshire | Herefordshire, county of | Herefordshire, county of |
Worcestershire | Bromsgrove, Malvern Hills, Redditch, Worcester, Wychavon, Wyre Forest |
Warwickshire | North Warwickshire, Nuneaton and Bedworth, Rugby, Stratford-on-Avon, Warwick |
Shropshire and Staffordshire | Telford and Wrekin | Telford and Wrekin |
Shropshire | Shropshire |
Stoke-on-Trent | Stoke-on-Trent |
Staffordshire CC | Cannock Chase, East Staffordshire, Lichfield, Newcastle-under-Lyyme, South Staffordshire, Stafford, Staffordshire Moorlands, Tamworth |
West Midlands | Birmingham | Birmingham |
Solihull | Solihull |
Coventry | Coventry |
Dudley and Sandwell | Dudley Sandwell |
Walsall and Wolverhampton | Walsall, Wolverhampton |
Yorkshire and The Humber | East Yorkshire and North Lincolnshire | Kingston upon Hull, city of | Kingston upon Hull, city of |
East Riding of Yorkshire | East Riding of Yorkshire |
North and North-East Lincolnshire | North-East Lincolnshire, North Lincolnshire |
North Yorkshire | York | York |
North Yorkshire CC | Craven, Hambleton, Harrogate, Richmondshire, Ryedale, Scarborough, Selby |
South Yorkshire | Barnsley, Doncaster and Rotherham | Barnsley, Doncaster, Rotherham |
Sheffield | Sheffield |
West Yorkshire | Bradford | Bradford |
Leeds | Leeds |
Calderdale, Kiklees and Wakefield | Calder, Kirklees, Wakefield |
Links represent all linear features; that is boundaries, extent of the realm (EOR) and mean high water (springs) mark (MHW). All links are broken when they intersect with one another. The first and last coordinate pairs in a link correspond exactly with the end coordinates of the adjoining link(s). Links may comprise up to several thousand line segments.
The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.
Feature identifier added by the software.
Attribute Name: fid (GKPG), Not provided (TAB), Not provided (Shapefile)
Multiplicity: [0..1]
Feature geometry.
Attribute Name: Not provided (GKPG), Not provided (TAB), SHAPE (Shapefile)
Data Type: Polyline
Multiplicity: [1]
Code value assigned to the Mean High Water Line polyline. This value will always be set to – 0071
as this is the feature code applicable to a Mean High Water Line feature.
Attribute Name: Feature_Code (GKPG), Feature_Code (TAB), CODE (Shapefile)
Data Type: char
Size: 4
Multiplicity: [1]
Description of the boundary feature. Set to ‘High Water Mark’ (HWM)
Attribute Name: Feature_Description (GKPG), Feature_Description (TAB), DESCRIPT0 (Shapefile)
Data Type: char
Size: 21
Multiplicity: [1]
Name of the boundary polygon that the line is contained by; written in UPPERCASE with underscores.
The high water mark line is split up by every boundary that it crosses. Where the resulting line is contained in multiple polygons, for the product the same geometry is used for multiple features, with the File_Name
referencing the containing boundary polygon, and the same Global_Link_ID
used for all of them.
Attribute Name: File_Name (GKPG), File_Name (TAB), FILE_NAME (Shapefile)
Data Type: char
Size: 100
Multiplicity: [1]
Serial number applied to the polyline feature during the production of the product.
In the current product, this is not unique nor maintained.
Attribute Name: Feature_Serial_Number (GKPG), Feature_Serial_Number (TAB), NUMBER (Shapefile)
Data Type: Integer (TAB), Number (Shapefile)
Size: n/a (TAB), 11 (Shapefile)
Multiplicity: [1]
A maintained sequential integer identifier that is unique, except for records with duplicate geometry referencing multiple boundary polygons.
Attribute Name: Global_Link_ID (GKPG), Global_Link_ID (TAB), LINK_ID (Shapefile)
Data Type: Integer (TAB), Number (Shapefile)
Size: n/a (TAB), 11 (Shapefile)
Multiplicity: [1]
A code list is a controlled set of allowable labels or codes represented as an alphanumeric attribute. The pages in this section show the code lists used within Boundary Line.
The original data sources used for the creation of Boundary-Line was Ordnance Survey’s 1:10 000 scale boundary record sheets and OS Landplan digital data.
The data sources now used are Ordnance Survey’s Topographic Data for Natural Changes and Orders, Acts and Statutory Instruments (SIs).
Boundary-Line is updated twice a year, in spring and autumn. The updated product is a full replacement for all the listed administrative and electoral boundaries. The represented boundaries and administrative unit names are defined and modified by Orders, Acts and Statutory Instruments (SIs). Changes that are operative from the first week of May in the current year of release will be included. Changes to Westminster constituencies that are effective from the date of the next general election will be included as separate files.
In exceptional circumstances due to processing or constitutional constraints, Orders, Acts and Statutory Instruments may be excluded until the next suitable release.
Boundaries are no longer shown in Boundary-Line if they have been superseded at the time of the annual snapshot of boundaries that each release of Boundary-Line represents.
Revisions to Government Statistical Service (GSS) codes are incorporated into Boundary-Line as soon as practicable after the information is made available to Ordnance Survey.
Additional coastline reconciliation with the OS Landplan product was introduced in May 2005. Changes to the Boundary-Line tide lines, plus natural and gradual changes to rivers and streams, have been implemented alongside the previous boundary/coast association to enhance the MHW FC0071.
All boundary alignment changes in Boundary-Line will be reported in the Release Note accompanying each release of Boundary-Line.
The resolution of the coordinate system is 0.1 m. However, it is not possible to calculate meaningful accuracy limits for Boundary-Line data due to both the graphic nature and scale of the primary source 1:10 000 scale published mapping. Such mapping is subject to limited map generalisation, where an impression of the ground detail is made due to the complexity of the detail and importance of certain features such as roads. This means that boundary alignments are cartographically represented in areas where accurate positional representation would be impossible.
Boundary-Line is derived from the basic scale of 1:10 000. The relationship of boundaries to ground detail mirrors the accuracy achieved by mapping against OS VectorMap Local (1:10 000 scale) and, in certain cases, large-scale sources. A consequence of this is that if Boundary-Line is superimposed upon boundaries in OS MasterMap topographic data, variations in the two alignments will be seen.
Completeness is a measure of the correspondence between the real world and the specified data content. During digitising, all Boundary-Line data is checked thoroughly against source documents to ensure as far as reasonably possible that no features have been omitted or misaligned.
Boundary-Line is a structured link and polygon dataset. The data comprises three levels of features:
The administrative unit has attributes that include the administrative unit’s name and GSS code. The administrative unit feature is classified by means of a feature type. It also has explicit pointers to the polygons that define its area.
The polygon includes attributes that define its area value; it also has explicit pointers to the links that chains (or makes up) its edge and may have pointers to holes within the area.
The links have a geometry that defines their shape.
Administrative units, polygons and links are assigned unique identifiers for each release of Boundary-Line.
Real-world administrative and voting units are modelled and named and have explicit pointers to the polygons that define their area of influence.
Each real-world administrative or electoral voting unit is classified by means of an area code. The polygons are classified indirectly by the administrative or electoral voting unit collection in which they appear. These polygons within the data model also have associated attributes which give the entities meaning, representing the geometric characteristic of an entity with items such as area or a unique identity.
Boundary links are classified indirectly by the polygon chains in which they appear.
Administrative or electoral voting units, polygons and links are assigned unique identifiers for each release of Boundary-Line.
Area features are polygons with attributes added.
Links represent all linear features; that is boundaries, extent of the realm (EOR) and mean high water (springs) mark (MHW). All links are broken when they intersect with one another. The first and last coordinate pairs in a link correspond exactly with the end coordinates of the adjoining link(s). Links may comprise up to several thousand line segments.
The coordinate system is National Grid (NG). The National Grid coordinates are to a resolution of 0.1 metres. This is the resolution of the source data.
There are several supplementary layers included alongside the main Boundary-Line product. These supplementary layers sit separately to the main GB
Boundary-Line folder and are included as separate directories in the shapefile and MapInfo TAB file formats.
Features included as supplementary in the supplementary directory are:
Historical counties
Ceremonial counties
Historical European regions (frozen as of 1 April 2021)
Country
The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.
Feature identifier added by the software.
Attribute Name: fid (GKPG), Not provided (TAB), Not provided (Shapefile)
Multiplicity: [1]
Name of the Ceremonial County, Historic County or Historic European Region.
Attribute Name: Name (GKPG), Name (TAB), NAME (Shapefile)
Data Type: char
Size: 100
Multiplicity: [1]
Classification set to Ceremonial County or Historic County or Historic European Region.
Attribute Name: Area_Description (GKPG), Area_Description (TAB), DESCRIPT0 (Shapefile)
Data Type: char
Size: 50
Multiplicity: [1]
Boundary polygon.
Attribute Name: Not provided (GKPG), Not provided (TAB), LINK_ID (Shapefile)
Data Type: GM_Surface
Boundary-Line layers are supplied in Geography Markup Language (GML) v.3.2.1.
GML is based on XML (eXtensible Mark-up Language) and an understanding of the XML schema will be helpful in understanding the GML format.
See the following Geography Markup Language v3.2.1 OpenGIS® Geography Markup Language (GML) Encoding Standard (PDF download) document by the Open Geospatial Consortium (OGC) for full details about GML.
Boundary-Line GML files are only created for the following layers:
County
District_borough_unitary
Parish
XML schemas are used to define and validate the format and content of the GML. The GML v.3.2.1 specification provides a set of schemas that define the GML feature constructs and geometric types. These are designed to be used as a basis for building application-specific schemas, which define the data content.
The AdministrativeUnits.xsd
application schema which is referenced by the data, is available on the INSPIRE website. It imports the GML 3.2 schemas which rely on XML as defined by W3C.
Style sheets have been created and provided for Boundary-Line GML. You can find these in the Ordnance Survey GitHub repository at https://github.com/OrdnanceSurvey/Boundary-Line-stylesheets.
A code list is a controlled set of allowable labels or codes represented as an alphanumeric attribute. The pages in this section show the code lists used within Boundary Line.
Unit of administration where a Member State has and/or exercises jurisdictional rights for local, regional and national governance.
The following page provides details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.
Admin_Unit_ID
from Boundary-Line, which is preceded by osgb7
and enough zeros to make it 16 digits, for example, Admin_Unit_ID=25483
becomes osgb7000000000025483
.
Attribute Name: gml:id
Data Type: CharacterString
Size: 16
Multiplicity: [1]
Use identifier from Boundary-Line linked data. For example, http://data.ordnancesurvey.co.uk/id/7000000000025483
. The number is the Admin_Unit_ID
from Boundary-Line, which is preceded by the number 7 and enough zeros to make it 16 digits, for example, Admin_Unit_ID=25483
becomes 7000000000025483
.
Attribute Name: gml:identifier
Data Type: CharacterString
Size: 16
Multiplicity: [1]
Geometric representation of spatial area covered by this administrative unit. Can be a multi- polygon.
Attribute Name: geometry
Data Type: GM_Surface
Multiplicity: [1]
Set to the Census/GSS Code for the boundary, for example, E10000014.
Attribute Name: nationalCode
Data Type: CharacterString
Size: 8
Multiplicity: [1]
Admin_Unit_ID from Boundary-Line, which is preceded by the number 7 and enough zeros to make it 16 digits, for example, Admin_Unit_ID=25483
becomes 7000000000025483
.
Attribute Name: inspireId.Identifier.localId
Data Type: CharacterString
Size: 16
Multiplicity: [1]
Set to 'http://data.ordnancesurvey.co.uk/id/
'.
Attribute Name: inspireId.Identifier.namespace
Data Type: IdentifierNamespaceValue
Multiplicity: [1]
Set to publication timestamp, for example, '2016-09-20T16:18:19.000
'.
Attribute Name: inspireId.Identifier.versionId
Data Type: DateTime
Multiplicity: [1]
Level in the national administrative hierarchy at which the administrative unit is established. Note that the UK boundary (nationalLevel = 1stOrder) or the boundaries of England/Wales/Scotland (nationalLevel = 2ndOrder) are not included.
Attribute Name: nationalLevel
Code List Name: AdministrativeHierarchyValue
Multiplicity: [1]
Name of the level in the national administrative hierarchy at which the administrative unit is established.
Attribute Name: nationalLevelName
Code List Name: NationalClassificationValue
Multiplicity: [1]
Set to 'UK
'.
Attribute Name: country
Data Type: CountryValue
Multiplicity: [1]
Set to 'true
'.
Attribute Name: name.language.xsi:nil
Data Type: BooleanTrueValue
Multiplicity: [1]
Set to 'unknown
'.
Attribute Name: name.language.nilReason
Data Type: UnknownReasonValue
Multiplicity: [1]
Set to 'endonym
'.
Attribute Name: name.nativeness.xlink:title
Data Type: NativenessValue
Multiplicity: [1]
Set to 'http://inspire.ec.europa.eu/codelist/NativenessValue#endonym
'.
Attribute Name: name.nativeness.xlink:href
Data Type: NativenessNamespaceValue
Multiplicity: [1]
Set to 'official
'.
Attribute Name: name.nameStatus.xlink:title
Data Type: NameStatusValue
Multiplicity: [1]
Set to 'http://inspire.ec.europa.eu/codelist/NameStatusValue#official
'.
Attribute Name: name.nameStatus.xlink:href
Data Type: NameStatusNamespaceValue
Multiplicity: [1]
Set to 'Boundary-Line'
.
Attribute Name: name.sourceOfName
Data Type: SourceOfNameValue
Multiplicity: [1]
Set to 'true
'.
Attribute Name: name.pronunciation.xsi:nil
Data Type: BooleanTrueValue
Multiplicity: [1]
Set to 'missing
'.
Attribute Name: name.pronunciation.nilReason
Data Type: MissingReasonValue
Multiplicity: [1]
Official national geographical name of the administrative unit.
Attribute Name: name.spelling.text
Data Type: CharacterString
Multiplicity: [1]
Set to 'Latn
'.
Attribute Name: name.spelling.script
Data Type: ScriptValue
Multiplicity: [1]
Set to 'true'
.
Attribute Name: residenceOfAuthority.xsi:nil
Data Type: BooleanTrueValue
Multiplicity: [1]
Set to 'unknown
'.
Attribute Name: residenceOfAuthority.nilReason
Data Type: UnknownReasonValue
Multiplicity: [1]
Set to publication timestamp, for example, 2016-09-20T16:18:19.000
.
Attribute Name: beginLifespanVersion
Data Type:
Multiplicity: [1]
Set to 'true'
.
Attribute Name: boundary.xsi:nil
Data Type: BooleanTrueValue
Multiplicity: [1]
Set to 'unknown
'.
Attribute Name: boundary.nilReason
Data Type: UnknownReasonValue
Multiplicity: [1]
Boundary-Line is supplied as a national vector tiles set in a single MBTiles file (combined from individual PBF tiles). This is a lightweight set of tiles that are efficient to render in supported software, provide high-resolution data and give a seamless experience when zooming in and out. The data is supplied in Web Mercator projection (ESPG:3857).
The vector tiles schema is detailed in the following page.
All layers and their attributes are mapped within zoom levels 9 to 14, but not within zoom levels 0 to 8
Layer Name: Boundary_line_ceremonial_counties
Attribute Name:
name
Layer Name: Boundary_line_historic_counties
Attribute Name:
name
Layer Name: community_ward
Attribute Names:
name
community
Layer Name: county
Attribute Names:
name
area_code
global_polygon_id
census_code
hectares
non_inland_area
area_type_code
Layer Name: county_electoral_division
Attribute Name:
name
area_code
global_polygon_id
census_code
hectares
non_inland_area
area_type_code
Layer Name: country_region
Attribute Names:
name
area_code
global_polygon_id
census_code
hectares
non_inland_area
area_type_code
Layer Name: district_borough_unitary
Attribute Names:
name
area_code
global_polygon_id
census_code
hectares
non_inland_area
area_type_code
Layer Name: district_borough_unitary_ward
Attribute Names:
name
area_code
global_polygon_id
census_code
hectares
non_inland_area
area_type_code
Layer Name: english_region
Attribute Names:
name
area_code
global_polygon_id
census_code
hectares
non_inland_area
area_type_code
Layer Name: greater_london_const
Attribute Names:
name
area_code
global_polygon_id
census_code
hectares
non_inland_area
area_type_code
Layer Name: high_water
Attribute Names:
file_name
global_link_id
Layer Name: historic_european_region
Attribute Name:
name
Layer Name: parish
Attribute Names:
name
area_code
global_polygon_id
census_code
hectares
non_inland_area
area_type_code
Layer Name: polling_districts_england
Attribute Names:
pd_id
county
district_borough
ward
parish
Layer Name: scotland_and_wales_const
Attribute Names:
name
area_code
global_polygon_id
census_code
hectares
non_inland_area
area_type_code
Layer Name: scotland_and_wales_region
Attribute Names:
name
area_code
global_polygon_id
census_code
hectares
non_inland_area
area_type_code
Layer Name: unitary_electoral_division
Attribute Names:
name
area_code
global_polygon_id
census_code
hectares
non_inland_area
area_type_code
Layer Name: westminster_const
Attribute Names:
name
area_code
global_polygon_id
census_code
hectares
non_inland_area
area_type_code
GeoPackage (GKPG) is an open, standards-based, data format as is defined by the Open Geospatial Consortium (OGC). It is designed to be a lightweight format that can contain large amounts of varied and complex data in a single, easy-to-distribute and ready-to-use file. GeoPackage offers users the following benefits:
The single file is easy to transfer and offers the end-user a rich experience.
Attribute names are not limited in length, making the format user-friendly.
The file size limit is very large at 140 TB*, so lots of data can be easily accommodated.
It supports raster, vector and database formats, making it a highly versatile solution.
*A file size limit might be imposed by the file system to which the file is written.
Layer | Country | Description |
---|---|---|
Value | Description |
---|---|
The TAB format (MapInfo tables) is the native format of MapInfo. This format can be read into most GIS packages. The TAB format consists of two files for tabular information, similar to a spreadsheet, and two files for geographic display. All four files are needed to display the geometry and attributes of geographically reference features. The four specific file extensions needed to display the geometry are as follows:
.dat
: The dBASE file that stores the attribute information of features.
.id
: The file that stores the index of the feature geometry to the attribute table.
.map
: The file that stores the geographic information to display each feature.
.tab
: The file that links the above three files and holds information about the dataset.
Layer | Country | Description |
---|---|---|
Esri shapefiles are a simple, non-topological format for storing the geometric location and attribute information of geographic features. A shapefile is one of the spatial data formats that you can work with in ArcGIS.
The shapefile format defines the geometry and attributes of geographically referenced features in as many as five files with specific file extensions that should be stored in the same project workspace. The file extensions are as follows:
.shp
: The file that stores the feature geometry.
.shx
: The file that stores the index of the feature geometry.
.dbf
: The dBASE file that stores the attribute information of features.
When a shapefile is added as a theme to a view, this file is displayed as a feature table.
.sbn
and .sbx
: The files that store the spatial index of the features.
These two files only exist if you perform theme-on-theme selection, spatial joins or create an index on a theme's SHAPE field.
.prj
: The file that stores the projection information.
Layer | Country | Description |
---|---|---|
Value | Description |
---|---|
This page identifies the creation process for the ceremonial county boundaries for England, Scotland and Wales.
The current counties of England are defined by the ceremonial counties, a collective name for the county areas to which are appointed a Lord Lieutenant. The office of Lord Lieutenant was created in the reign of Henry VIII. The Lord Lieutenant is the chief officer of the county and representative of the Crown. Whenever the Queen visits an area she will be accompanied by the Lord Lieutenant of that area. Legally the ceremonial counties are defined by the Lieutenancies Act 1997 as ‘Counties and areas for the purposes of the lieutenancies in Great Britain’ with reference to the areas used for local government.
The Lieutenancies Act 1997 defines counties for the purposes of lieutenancies in terms of local government areas created by the Local Government Act 1972 as amended. Although the term is not used in the Act, those counties are sometimes known as ‘Ceremonial Counties’. Schedule 1, paragraphs 2–5 as amended (most recently in 2009) defines them as:
The preserved counties of Wales are the current areas used in Wales for the ceremonial purposes of Lieutenancy and Shrievalty (the office or jurisdiction of a sheriff). They are based on the counties created by the Local Government Act 1972 and used for local government and other purposes between 1974 and 1996.
Name | Area |
---|---|
The Local Government (Wales) Act 1994 abolished the eight county authorities created by the Local Government Act 1972. However, it created the concept of preserved counties based on their areas, to be used for purposes such as Lieutenancy. This usage was consolidated by the Lieutenancies Act 1997.
Certain statutes already in force were amended to include reference to them — as of 16 February 2011, the only remaining provisions still extant are:
The Sheriffs Act 1887 (c. 55) – the counties that High Sheriffs are appointed to are the preserved counties.
The Defence Act 1842 (c. 94) – Lieutenants are those appointed to preserved counties.
The Sea Fisheries (Shellfish) Act 1967 (c. 83) – relevant portions of the sea shore shall be deemed to be within preserved counties.
The preserved counties were originally almost identical to the 1974–96 counties, but with a few minor changes in line with local government boundary changes: Llanrhaeadr-ym-Mochnant, Llansilin and Llangedwyn were transferred from Clwyd to Powys, and Wick, St Brides Major, Ewenny and Pentyrch were transferred from Mid Glamorgan to South Glamorgan. There were however two local government areas, Caerphilly and Conwy and split between preserved counties.
The Local Government Boundary Commission for Wales was instructed by the National Assembly for Wales on 11 March 2002 to undertake a review of preserved county boundaries. In their final proposals the part of the local government area of Caerphilly, which had been in Mid Glamorgan was to be part of Gwent and the part of the local government area of Conwy, which had been in Gwynedd was to be part of Clwyd.
The boundary between Mid Glamorgan and South Glamorgan was also to be re-aligned to reflect small changes in local government boundaries. The Assembly accepted these proposals, such that from 2 April 2003 each preserved county now encompass between one and five whole local government areas. (See SI 2003 No974).
The boundary between Mid Glamorgan and Powys was further modified on 1 April 2010 to reflect the 2009 local government boundary changes in the Vaynor area. (See SI 2010 No 48).
The lieutenancy areas of Scotland are the areas used for the ceremonial Lord Lieutenants, the monarch’s representatives, in Scotland. They are different from the local government council areas, the committee areas, the sheriffdoms, the registration counties, the former regions and districts, the former counties of Scotland, and the various other subdivisions of Scotland.
The Lord Provosts of Aberdeen, Dundee, Edinburgh, and Glasgow also act ex officio as Lord Lieutenants. This is a unique right in the United Kingdom: all other Lord Lieutenants are appointed by the monarch, rather than being elected politicians.
The areas were defined by the Lord Lieutenants (Scotland) Order 1996 as follows:
These are defined in The Lord-Lieutenants (Scotland) Order 1996 (SI 1996/731), and in the Lieutenancies Act 1997 (for the 4 city lieutenancies). Alterations to lieutenancies can be made by Order under the Lieutenancies Act 1997, but no such Orders have been made at the time of writing.
The boundaries in this dataset have been derived from LGBCS datasets showing:
the boundaries of Districts as they existed immediately before abolition in 1995;
the boundaries of the unitary authorities introduced in 1994; and
counties as they existed in 1973
The first two of these have been derived from Boundary-Line. The third of these, the LGBCS county dataset, is generally of Boundary-Line quality, but has a complicated lineage, explained elsewhere. It has been used in making this lieutenancy dataset to define the parts of the boundary between Moray, Banffshire, Aberdeenshire and Kincardineshire lieutenancies which do not coincide with subsequent district or unitary authority boundaries.
There appears to be an error in the definitions of Dunbartonshire and Lanarkshire lieutenancies in SI 1996/731: the definition of Dunbartonshire lieutenancy includes all of Strathkelvin District; the definition of Lanarkshire lieutenancy includes Strathclyde electoral division 46, which was part of Strathkelvin District (resulting from LGBCS report 167 and SI 1993/2439).
We have assumed that the intention of SI 1996/731 is that the lieutenancy boundary should follow the boundary between East Dunbartonshire and North Lanarkshire in this area, since the wording broadly reflects the wording used in the Local Government etc. (Scotland) Act 1994 which established those unitary councils. That in turn would mean that the definition of Dunbartonshire lieutenancy in SI 1996/731 should read “The district of Dumbarton, the district of Clydebank, the district of Bearsden and Milngavie, the district of Cumbernauld and Kilsyth and the following electoral divisions of Strathclyde region, namely electoral division 43 (Kirkintilloch), electoral division 44 (Strathkelvin North), electoral division 45 (Bishopbriggs) and, in electoral division 46 (Chryston), the South Lenzie / Waterside district ward.” — Hugh Buchanan (SBC) December 2011
Levels of administration in the national administrative hierarchy. This code list reflects the level in the hierarchical pyramid of the administrative structures, which is based on geometric aggregation of territories and does not necessarily describe the subordination between the related administrative authorities.
Value | Description |
---|---|
Each feature with the AdministrativeUnit:FeatureCollection
is encapsulated in the following member element according to its feature type:
Member Element | Feature Type |
---|---|
The Admin_Unit_ID
of the feature is provided in the XML attribute of the gml:id
:
A Polling Districts layer is included as a supplementary file within the product. We do not routinely maintain this layer as uptake has been limited and the vast majority of areas are frozen since 2016 when information was sourced through the Boundaries Commission for England (BCE). Changes to Polling Districts are notified exclusively to BCE and OS do not receive the change information from local authorities directly.
In 2021, we completed a task for the BCE to update the following areas all of which are Operational before or on 5 May 2022:
Barking & Dagenham | Barnet | Barnsley | Basingstoke & Deane |
---|
A polling district is a geographical area created by local authorities to assist the administrative process of running an election. Each ward or electoral division in England and Wales is divided into one or more polling districts.
In England, each parish is to be a separate polling district and, in Wales, each community should be a separate polling district, unless there are special circumstances. This means that a parish or community must not be in a polling district which has a part of either a different parish or community within it, or any un-parished part of the local authority area within it, unless special circumstances apply. Those special circumstances could arise if, for example, the parish/community has only a small number of electors and it is not practicable for the parish/community to be its own polling district
The Welsh equivalent (community wards) are also released as a supplementary data set, the Scottish equivalent are not supplied.
Boundary-Line contains all the current (operative) administrative and electoral boundaries for Great Britain.
They consist of:
· Civil parishes
· Wards
· Communities
· Districts
· Counties
· Metropolitan districts
· Unitary authorities
· Parliamentary constituencies
· Electoral divisions
· London boroughs
· Greater London authorities
· Greater London authority assembly constituencies
· European electoral regions
· Welsh assembly constituencies
· Welsh assembly electoral regions
· Scottish parliamentary constituencies
· Scottish parliamentary electoral regions.
The product also contains mean high water mark (MHW), extent of realm (EOR) also census agency codes supplied by the Office for National Statistics (ONS), and the National Records of Scotland (NRS).
Civil parish wards are not shown in Boundary-Line. We only show the parish, we do not show the internal parish wards or any associated council references.
We have polygons in the parish data that do not have any attribution – no records attached, formally known as Non Civil Parishes (NCP's- i.e. Non Parished Areas), these ‘blank’ polygons are shown to complete the parish layer, because a polygon dataset cannot have ‘gaps’.
· Parish polygon attributes will only be populated if Ordnance Survey has the information from the local authority;
· Parishes do not exist as a result of being superseded by other local government units, i.e. unitary authority areas will not have parishes.
The length of time changes to new parishes take to be reflected in Boundary-Line data is based on the following information.
Parishes are created and managed separately from the other electoral and administrative boundaries represented in Boundary-Line. To amend a parish, the Parish councillors make an appropriate submission to their Local Authority.
The information relating to the parish changes should then be sent to Ordnance Survey directly from the Local Authorities, as they are required to inform Ordnance Survey of any name changes under the Local Government Act (1972) and the more recent Local Government and Public Involvement in Health Act (2007) for name and boundary alignments.
On receipt of the parish update information we would expect to capture that in the appropriate Boundary-Line 6 monthly scheduled releases. We can only amend the parish boundaries after receiving this official notification.
Additional parish information updates will be more frequently available, once confirmation is received, as the large scale OS MasterMap Topography boundary information is continuously updated.
Boundary-Line is a separate product from OS MasterMap Topography; the Topography Layer is captured at a different scale and from a different production system.
Only OSMM Topography Layer currently holds the definitive and more accurate boundary information as the boundaries are mered (aligned to) real-world features on the ground. Captured at mapping scales of 1:1 250 (for urban areas), 1:2 500 (for rural) and 1:10k (for mountain and moorland). All electoral and administrative boundaries are contained within the OSMM Topographic layer. It is a point and line structured dataset and does not contain polygons.
Boundary-Line is captured against a lower resolution mapping backdrop and the boundaries are captured to represent the data at a nominal 1:10 000 viewing scale. The process of generalising the data may have caused some features to be moved from their true ground position for the purpose of map clarity. The result is that Boundary-Line and the OSMM Topographic boundaries are not always coincident (when overlaid they will not always have the same alignment). Boundary-Line is a polygon structured dataset.
These datasets are not designed to be used together as they will not give exact replication of boundary position.
The data is supplied by named files, all the named files include all of the other sub‑levels of electoral boundaries that belong under that high level administration (for example, County file) will have the named county, district, district ward, civil parish, county ED contained within. Unitary authorities will have named unitary authority, unitary authority ward or unitary authority ED as appropriate, civil parish where appropriate, together with community in Wales. The nested structure is only available in ESRI Shapefile.
This is a simplified file structure supplying the boundaries as individual files, for example, County file contains only counties, and unitary authorities file contains just unitary authorities. The layered structure is only available in ESRI Shapefile.
Area values of each polygon in Boundary‑Line include the Extent Of Realm (EOR) limit. The total area values are quoted to the current Department for Communities and Local Government (DCLG) specification of 0.001 hectare.
However, other government statistical department data is based on Standard Area Measurements (SAM), which only includes the land area contained within a polygon deleting any inland hydrology or EOR areas.
The boundaries shown in OS MasterMap Topography Layer do not represent legal property extents and are only representative of the electoral and administrative boundaries. For ‘property extents’ it would be advisable to contact Land Registry directly.
There may be three reasons for the boundary at a particular location not aligning where it was presumed it should be:
1. OSMM Topography boundaries were affected by our Positional Accuracy Improvement programme (PAI). This programme enabled Ordnance Survey to produce a more consistent accuracy standard of mapping data, for rural areas and to future-proof the data for the addition of new building development and other feature changes. This meant some realignment of the ground features which meant the associated boundary position had to be moved to match them. Boundary-Line is a boundary dataset that is generally in alignment with the large-scale data positioning, but it may vary slightly due to the PAI giving different positions or that the 1:10000 scale mapping used to digitise Boundary-Line against cannot show the features in detail so giving a best placement based on the textural descriptions and mapping used.
2. It may be that the update cycle for the mapping is less frequent than the boundary data so there may be a difference in the currency of information.
3. Natural and gradual change: In naturally flowing watercourses the bed of the river or stream, through natural action gradually moves by erosion and silting. This may over a lengthy period of time result in considerable change to the position of the watercourse. Where a boundary is defined as being related to the watercourse which slowly and imperceptibly changes its course the boundary will be aligned to the altered channel.
Boundary-Line is updated and released twice a year, in May and October. Each release will have all the new and amended boundaries that are operative (live) within a one year period (1st May to 31st April). We only show the current operative boundaries in the Boundary-Line product.
However, due to market requirements we have supplied alongside the Boundary-Line product future dated (pre-operative) Westminster Parliamentary boundaries. These supplementary files will only be included in the Boundary-Line product at the next suitable release, after the General Election has taken place. This future dated boundary data is part of the specification and so is included in the Boundary-Line licence fee.
Change Only Update data is not available for this product due to the current and future boundary complex relationships within the production system.
The EOR is the seaward limit of the administrative units. The boundary alignment is digitised to the Mean Low Water (springs) MLWS) to represent the seaward extent within Boundary-Line.
Boundary-Line does not show all items that ‘extend’ into the sea. We show structures such as a pier, seaward extension or structure in the sea that has been included in a specific Act of Parliament, and or are a permanent and solid structure (i.e. Brighton marina). Piers and extensions that are elevated over the sea; on stilts or floating pontoons, will only be included if they are identified as being part of the local authority area by an Act of Parliament. Structures in the sea can be separate or joined to the mainland; if they are joined to the mainland they are generally included in local government and parliamentary areas. If separate they are not included unless they are included therein by legislation for example Torbay and Bristol.
Names of the levels in the national administrative hierarchy of administrative units.
Value | Description |
---|
Name | Area |
---|---|
Name | Area |
---|---|
The boundaries of historic counties such as Westmorland, Radnorshire and Wigtownshire from the late Nineteenth Century are available to download as a Shape file or Tab file from the .
The ceremonial county boundaries of Great Britain, such as Bedfordshire, Berkshire and the West Midlands are available to download as a Shape file or Tab file from the .
county (inc GLAs)
E
Polygon
county_electoral_division
E
Polygon
district_borough_unitary
E, S, W
Polygon
district_borough_unitary_ward
E, S
Polygon
english_region
E
Polygon
greater_london_const
E
Polygon
high_water
E, S, W
Polyline
parish
E, S, W
Polygon
unitary_electoral_division
E, W
Polygon
westminster_const
E, S, W
Polygon
scotland_and_wales_const
S, W
Polygon
scotland_and_wales_region
S, W
Polygon
polling_districts_england
E
Polygon
Boundary_line_historic_counties
E, S, W
Polygon
Boundary_line_ceremonial_counties
E, S, W
Polygon
community_ward
W
Polygon
historic_european_region
E, S, W
Polygon
country_region
E, S, W
Polygon
CED
County Electoral Division
CTY GLA
County
DIS LBO MTD
UTA
District Borough Unitary Region
DIW LBW MTW
UTW
District Borough Unitary Ward
ER
English Region
LAC
Greater London Authority Assembly Constituency
CPC NCP
Parish
SPC
Scottish Parliament Constituency
SPE
Scottish Parliament Electoral Region
UTE
Unitary Authority Electoral Division
WPC
Welsh Parliament Constituency
WPE
Welsh Parliament Electoral Region
WMC
Westminster Constituency
county (inc GLAs)
E
Polygon
county_electoral_division
E
Polygon
district_borough_unitary
E, S, W
Polygon
district_borough_unitary_ward
E, S
Polygon
english_region
E
Polygon
greater_london_const
E
Polygon
high_water
E, S, W
Polyline
parish
E, S, W
Polygon
unitary_electoral_division
E, W
Polygon
westminster_const
E, S, W
Polygon
scotland_and_wales_const
S, W
Polygon
scotland_and_wales
S, W
Polygon
polling_districts_england_region
E
Polygon
Boundary_line_historic_counties_region
E, S, W
Polygon
Boundary_line_ceremonial_counties_region
E, S, W
Polygon
community_ward
W
Polygon
historic_european_region
E, S, W
Polygon
country_region
E, S, W
Polygon
county_region (inc GLAs)
E
Polygon
county_electoral_division_region
E
Polygon
district_borough_unitary_region
E, S, W
Polygon
district_borough_unitary_ward_region
E, S
Polygon
english_region_region
E
Polygon
greater_london_const_region
E
Polygon
high_water_polyline
E, S, W
Polyline
parish_region
E, S, W
Polygon
unitary_electoral_division_region
E, W
Polygon
westminster_const_region
E, S, W
Polygon
scotland_and_wales_const_region
S, W
Polygon
scotland_and_wales_region
S, W
Polygon
polling_districts_england_region
E
Polygon
Boundary_line_historic_counties_region
E, S, W
Polygon
community_ward_region
W
Polygon
Boundary_line_ceremonial_counties_region
E, S, W
Polygon
historic_european_region_region
E, S, W
Polygon
country_region
E, S, W
Polygon
AA
Civil Administration Area
SR
Statistical Reporting Area
VA
Civil Voting Area
Clwyd
Conwy, Denbighshire, Flintshire, Wrexham
Dyfed
Carmarthenshire, Ceredigion, Pembrokeshire
Gwent
Blaenau Gwent, Caerphilly, Monmouthshire, Newport, Torfaen
Gwynedd
Gwynedd, Isle of Anglesey
Mid Glamorgan
Bridgend, Merthyr Tydfil, Rhondda Cynon Taf
Powys
Powys
South Glamorgan
Cardiff, Vale of Glamorgan
West Glamorgan
Neath Port Talbot, Swansea
Bedfordshire
Bedford, Central Bedfordshire and Luton
Berkshire
Berkshire
City of Bristol
City of Bristol
Buckinghamshire
Buckinghamshire and Milton Keynes
Cambridgeshire
Cambridgeshire and Peterborough
Cheshire
Cheshire East, Cheshire West and Chester, Halton and Warrington
City of London
City of London
Cornwall
Cornwall and the Isles of Scilly
Cumbria
Cumbria
Derbyshire
Derbyshire and Derby
Devon
Devon, Plymouth and Torbay
Dorset
Dorset, Bournemouth and Poole
Durham
Durham, Darlington, Hartlepool, and Stockton-on-Tees north of the River Tees
East Riding of Yorkshire
East Riding of Yorkshire and Kingston-upon-Hull
East Sussex
East Sussex and Brighton and Hove
Essex
Essex, Southend-on-Sea and Thurrock
Gloucestershire
Gloucestershire and South Gloucestershire
Greater London
Greater London, excluding the City of London
Greater Manchester
Greater Manchester
Hampshire
Hampshire, Southampton and Portsmouth
Herefordshire
Herefordshire
Hertfordshire
Hertfordshire
Isle of Wight
Isle of Wight
Kent
Kent and Medway
Lancashire
Lancashire, Blackburn with Darwen, and Blackpool
Leicestershire
Leicestershire and Leicester
Lincolnshire
Lincolnshire, North Lincolnshire and North East Lincolnshire
Merseyside
Merseyside
Norfolk
Norfolk
North Yorkshire
North Yorkshire, York, Middlesbrough, Redcar and Cleveland, and Stockton-on-Tees south of the River Tees
Northamptonshire
Northamptonshire
Northumberland
Northumberland
Nottinghamshire
Nottinghamshire and Nottingham
Oxfordshire
Oxfordshire
Rutland
Rutland
Shropshire
Shropshire and Telford and Wrekin
Somerset
Somerset, Bath and North East Somerset and North Somerset
South Yorkshire
South Yorkshire
Staffordshire
Staffordshire and Stoke-on-Trent
Suffolk
Suffolk
Surrey
Surrey
Tyne and Wear
Tyne and Wear
Warwickshire
Warwickshire
West Midlands
West Midlands
West Sussex
West Sussex
West Yorkshire
West Yorkshire
Wiltshire
Wiltshire and Swindon
Worcestershire
Worcestershire
Clwyd
Conwy, Denbighshire, Flintshire, Wrexham
Dyfed
Carmarthenshire, Ceredigion, Pembrokeshire
Gwent
Blaenau Gwent, Caerphilly, Monmouthshire, Newport, Torfaen
Gwynedd
Gwynedd, Isle of Anglesey
Mid Glamorgan
Bridgend, Merthyr Tydfil, Rhondda Cynon Taf
Powys
Powys
South Glamorgan
Cardiff, Vale of Glamorgan
West Glamorgan
Neath Port Talbot, Swansea
Aberdeenshire
The county of Aberdeen except those parts of that county which form part of the new local government area of Aberdeen City
Angus
The new local government area of Angus
Argyll and Bute
The district of Argyll and Bute
Ayrshire and Arran
The district of Kilmarnock and Loudoun, the district of Cumnock and Doon Valley, the district of Cunninghame and the district of Kyle and Carrick
Banffshire
The county of Banff
Berwickshire
The district of Berwickshire
Caithness
The district of Caithness
Clackmannan
The district of Clackmannan
Dumfries
The district of Nithsdale and the district of Annandale and Eskdale
Dunbartonshire
The district of Dumbarton, the district of Clydebank, the district of Bearsden and Milngavie, the district of Cumbernauld and Kilsyth and the
South Lenzie/ Waterside district ward in electoral division 46 (Chryston) of Strathclyde region
East Lothian
The district of East Lothian
Fife
Fife region
Inverness
The district of Lochaber, the district of Inverness and the district of Badenoch and Strathspey
Kincardineshire
The county of Kincardine except the electoral division of Nigg
Lanarkshire
The district of Monklands, the district of Motherwell, the district of Hamilton, the district of East Kilbride of Hamilton, the district of Clydesdale and the following electoral divisions of Strathclyde region, namely electoral division 37 (Rutherglen/ Fernhill), electoral division 38 (Cambuslang/ Halfway) and in electoral division 35 (Kingspark/ Toryglen), polling districts RU03, RU04, RU09 and RU18
Midlothian
The district of Midlothian
Moray
The county of Moray except those parts of that county which, on the passing of the Local Government (Scotland) Act 1973, formed part of Highland Region
Nairn
The district of Nairn
Orkney
Orkney Islands area
Perth and Kinross
The new local government area of Perth and Kinross
Renfrewshire
The district of Eastwood, the district of Renfrew and the district of Inverclyde
Ross and Cromarty
The district of Ross and Cromarty and the district of Skye and Lochalsh
Roxburgh, Ettrick and Lauderdale
The district of Roxburgh and the district of Ettrick and Lauderdale
Shetland
Shetland Islands area
Stirling and Falkirk
The district of Stirling and the district of Falkirk
Sutherland
The district of Sutherland
The Stewartry of Kirkcudbright
The district of Stewartry
Tweeddale
The district of Tweeddale
West Lothian
The district of West Lothian
Western Isles
Western Isles Islands area
Wigtown
The district of Wigtown
3rdOrder
Applies to Non-Metropolitan County, Greater London Authority, Metropolitan District and Unitary Authority.
4thOrder
Applies to District and London Borough.
5thOrder
Applies to Civil Parish and Community.
<base:member>
AdministrativeUnit
Bexley | Birmingham | Bolton | Bradford |
Bromley | Buckinghamshire | Bury | Calderdale |
Corby | Coventry | Croydon | Doncaster |
Greenwich | Hackney | Hammersmith & Fulham | Harrow |
Havering | Hillingdon | Hounslow | Islington |
Kensington & Chelsea | Kettering | Kingston upon Thames | Kirklees |
Knowsley | Lambeth | Leeds | Lewisham |
Liverpool | Manchester | Merton | Newcastle upon Tyne |
Newham | North Northamptonshire | North Tyneside | Oldham |
Plymouth | Redbridge | Richmond upon Thames | Rochdale |
Salford | Sandwell | Sefton | Sheffield |
South Lakeland | South Northamptonshire | South Tyneside | Southwark |
St. Helens | Stockport | Sutton | Tameside |
Tower Hamlets | Trafford | Walsall | Wandsworth |
West Berkshire | West Northamptonshire | Wirral | Wolverhampton |
Civil Parish | Parishes are subdivisions of local authorities in many parts of England, and their councils are the most local level of government. Unlike electoral wards/divisions however, parishes are not found in all parts of England. The Welsh equivalents are communities. Note that the full term for administrative parishes is 'civil parishes', to distinguish them from the ecclesiastical parishes which are found in all parts of the UK. |
District | Districts are local administrative units and have at various times been used in all four countries of the UK. The only current references to districts however are found in metropolitan and non-metropolitan districts in England and district council areas in Northern Ireland. |
Greater London Authority | The area covered by the Greater London Authority (GLA). The GLA is the body responsible for strategic citywide government for London and consists of the Mayor of London and the London Assembly. The remit of the GLA covers the Greater London area. |
London Borough | The London boroughs are the local government areas within Greater London. The borough councils are unitary administrations with a status similar to metropolitan districts, but they will also be affected by any policies implemented by the Greater London Authority (GLA). |
Metropolitan District | Metropolitan districts are subdivisions of the six metropolitan county areas of England. Since the abolition of the metropolitan county councils in 1986, the metropolitan district councils have been unitary administrations. |
Unitary Authority | Unitary authorities (UAs) are areas with a single tier of local government (as opposed to the two-tier county:district structure). |
Non-Metropolitan County | Counties were formerly administrative units across the whole UK. Due to various administrative restructurings however, the only administrative areas still referred to as counties are the non- metropolitan (shire) counties of England. The English metropolitan counties, although no longer administrative units, are also used for statistical purposes. |
Community | The Welsh equivalent of Civil Parish. |