From 1845 to1930, civil parishes formed part of Scotland’s local government system. The parishes, which had their origins in the ecclesiastical parishes of the Church of Scotland, often overlapped the then existing county boundaries. Parishes have had no direct administrative function in Scotland since 1930. There are 871 civil parishes in Scotland. The initial version of the Civil Parish boundaries was first created by Geography Branch, GROS in the mid-1960s. The boundaries were plotted on to Ordnance Survey 1:10,000 maps using the written descriptions of the parishes. In the late 1980s the boundaries were digitised using the Geographic Information System, called “GenaMap”. In 2006, GenaMap was replaced by ESRI’s ArcGIS product, and the civil parish boundaries were migrated to the new system. In March-April 2009 many of the coastal postcodes were edited to improve their alignment with MasterMap’s coastal detail. As a result, in May 2009 some of the coastal parishes were edited to ensure that all postcodes’ Gridlink points would fall within the limits of the civil parish boundaries. In terms of provenance, the vast majority of the civil parish boundaries date back to their original drawing in the mid-1960s onto OS 1:10,000 maps.

Local Authority is a generic term used to cover London Boroughs, Metropolitan Districts, Non-Metropolitan Districts, and Unitary Authorities in England; Unitary Authorities in Wales; Council Areas in Scotland; and Local Government Districts in Northern Ireland.

The Local Authorities area list contains 404 areas of the following constituent geographies:

• 36 Metropolitan Districts in England
• 201 Non-Metropolitan Districts in England
• 31 London Boroughs in England
• 54 Unitary Authorities in England
• 26 Local Government Districts in Northern Ireland
• 32 Council Areas in Scotland
• 22 Unitary Authorities in Wales
• 2 Census Merged Districts in England

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

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

clipped to the coastline (Mean High Water mark).

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Edge refers to the linear topological primitives that make up MTDB. The All Lines Shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines Shapefile are available in relationship (.dbf) files that users must download separately. The All Lines Shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TIGER/Line identifier (TLID) value.

Counties were formerly administrative units across the whole of the UK. Due to various administrative restructurings, however, the only administrative areas still referred to as 'counties' are the Non-Metropolitan Districts of England. The English Metropolitan Districts, although no longer administrative units, are also used for statistical purposes.

The Counties area list contains 35 areas of the following constituent English geographies:

• 27 Shire counties
• 6 Metropolitan counties
• Inner London and Outer London

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

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

clipped to the coastline (Mean High Water mark).

This dataset contains the boundaries for river catchments in Scotland based on the dataset Hydrological sections for England, Scotland and Wales with associated river catchment 2023, Water Framework Directive (WFD) waterbody and regional information British National Grid (BNG)_ These catchment boundaries have been derived from hydrological sections, have boundaries almost identical to existing Fish Health Inspectorate river catchments, and include complete coverage of the waterbodies under the Water Framework Directive. Note this dataset only includes catchments in Scotland. England and Wales are represented as a single area. For complete coverage of England, Scotland and Wales use Catchment boundaries for England, Scotland and Wales based on existing Fish Health Inspectorate (FHI) and SEPA catchments (BNG) 2023_ There are 2 versions of the dataset; a geographical coordinate reference system (CRS) WGS84 (EPSG 4326) see Catchment boundaries for Scotland based on Scottish Environment Protection Agency (SEPA) catchments (WGS84) 2023_ and this dataset a projected CRS British National Grid (BNG - EPSG 27700) . .. _hydrological sections for england, scotland and wales with associated river catchment 2023, water framework directive (wfd) waterbody and regional information british national grid (bng): https://data.cefas.co.uk/view/21750 .. _catchment boundaries for england, scotland and wales based on existing fish health inspectorate (fhi) and sepa catchments (bng) 2023: https://data.cefas.co.uk/view/21967 .. _catchment boundaries for scotland based on scottish environment protection agency (sepa) catchments (wgs84) 2023: https://data.cefas.co.uk/view/21970

In 2024, there were approximately 650,300 people living in Glasgow, with a further 530,680 people living in the Scottish capital, Edinburgh, the first and second most-populated Scottish council areas respectively. The region of Fife is also heavily populated, with approximately 374,760 people living there. The least populated areas are the islands of Scotland such as Orkney, estimated to have only 22,020 people there.

This polygon shapefile contains the Westminster parliamentary constituency boundaries for Great Britain as of 2005. Westminster parliamentary constituencies are the areas used to elect Members of Parliament (MP) to the House of Commons, which is the primary legislative chamber of the UK and is located in Westminster, London. Constituency boundaries are determined by the Boundary Commissions (one each for England, Scotland, Wales and Northern Ireland). The commissions are required to undertake a general review every eight to 12 years to ensure electoral equality – that is, that the sizes of the electorates in each constituency are as similar as possible (currently about 70,000 electors, typically reflecting a total population of 90,000). Constituencies are generally based on whole or part local authority districts unless there is a strong case to straddle boundaries – each case is decided on its merits; constituencies may not, however, split electoral wards/divisions. The Westminster parliamentary constituencies boundaries are based on the fifth Periodical Parliamentary Review that was promulgated in July 2007 (defined in terms of wards as at 12 April 2005). An amending order in July 2008, affected the Welsh Westminster parliamentary constituency boundaries and a further amendment order (operative 18 March 2009) realigning the boundaries for Daventry, South Northamptonshire, Somerton and Frome and Wells has also been applied. Sometimes constituencies are referred to as either borough (burgh in Scotland) or county constituencies. Borough constituencies are predominantly urban whereas county constituencies are partly or mostly rural. There will be no changes for the May 2015 General Election. This layer is part of the Office of National Statistics (ONS) Boundary Dataset supply, 2001-2011.

This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). The MTS represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The All Roads shapefile includes all features within the MTS Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in the MTS that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, stairways, and winter trails.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). The MTS represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Edges refer to the linear topological primitives that make up the MTS. The All Lines shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines shapefile are available in relationship (.dbf) files that users must download separately. The All Lines shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TIGER/Line identifier (TLID) value.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The Address Ranges Feature Shapefile (ADDRFEAT.dbf) contains the geospatial edge geometry and attributes of all unsuppressed address ranges for a county or county equivalent area. The term "address range" refers to the collection of all possible structure numbers from the first structure number to the last structure number and all numbers of a specified parity in between along an edge side relative to the direction in which the edge is coded. Single-address address ranges have been suppressed to maintain the confidentiality of the addresses they describe. Multiple coincident address range feature edge records are represented in the shapefile if more than one left or right address ranges are associated to the edge. The ADDRFEAT shapefile contains a record for each address range to street name combination. Address range associated to more than one street name are also represented by multiple coincident address range feature edge records. Note that the ADDRFEAT shapefile includes all unsuppressed address ranges compared to the All Lines Shapefile (EDGES.shp) which only includes the most inclusive address range associated with each side of a street edge. The TIGER/Line shapefile contain potential address ranges, not individual addresses. The address ranges in the TIGER/Line Files are potential ranges that include the full range of possible structure numbers even though the actual structures may not exist.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national filewith no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independentdata set, or they can be combined to cover the entire nation. Linear Water Features includes single-line drainage water features and artificial path features that run through double-line drainage features such as rivers and streams, and serve as a linear representation of these features. The artificial path features may correspond to those in the USGS National Hydrographic Dataset (NHD). However, in many cases the features do not match NHD equivalent feature and will not carry the NHD metadata codes. These features have a MAF/TIGER Feature Classification Code (MTFCC) beginning with an "H" to indicate the super class of Hydrographic Features.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Edge refers to the linear topological primitives that make up MTDB. The All Lines Shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines Shapefile are available in relationship (.dbf) files that users must download separately. The All Lines Shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TIGER/Line identifier (TLID) value.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The Address Range / Feature Name Relationship File (ADDRFN.dbf) contains a record for each address range / linear feature name relationship. The purpose of this relationship file is to identify all street names associated with each address range. An edge can have several feature names; an address range located on an edge can be associated with one or any combination of the available feature names (an address range can be linked to multiple feature names). The address range is identified by the address range identifier (ARID) attribute that can be used to link to the Address Ranges Relationship File (ADDR.dbf). The linear feature name is identified by the linear feature identifier (LINEARID) attribute that can be used to link to the Feature Names Relationship File (FEATNAMES.dbf).