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...
This technical specification provides detailed technical information about OS MasterMap Sites Layer . It is targeted at technical users and software developers.
OS MasterMap Sites Layer provides a nationally consistent polygonised representation of areas or extents of particular function or activity, and which are attributed to best reflect that function. It also contains access points and routing points to navigate in and out of the captured sites. These access points reference the OS MasterMap Highways Network product for easy interoperability between the two products.
All the source data used in the creation of OS MasterMap Topography Layer contains insight about a site’s function or purpose, and the Sites Layer is intended to not only make this information available, but to enhance its analytical capabilities. OS MasterMap Sites Layer features are a representation of the boundary of real-world facilities, such as a school, where the site consists of more than an addressable main building.
The features are derived from Ordnance Survey’s highly detailed core data, and therefore the classification and grouping of features is dependent upon the source data capture specification. The product contains three feature types:
Functional site polygons (FunctionalSite)
Functional site access points (AccessPoint)
Functional site routing points (RoutingPoint)
These three types are defined in this document in INSPIRE-compatible terms, with reference to the INSPIRE data specifications for facilities. The attribute naming convention also takes into consideration consistency with attribute names in other OS MasterMap layers and products.
It is important to note that the attribute naming has been carried over from the former OS MasterMap Integrated Transport Network (ITN) Layer. This has been done to minimise the impact of the implementation of OS MasterMap Highways Network.
The components that make up these features, and their relationships are shown in the product’s logical model diagram below.
A main premise of the OS MasterMap product family is that layers of the differing products can be integrated with each other.
Layers are integrated by the sharing of common coordinate systems and contextual identifiers. Except for the Imagery Layer, the TOID feature identification attribute provides a unique feature-level reference that can be used to identify and track a feature between related OS MasterMap layers. For example, in OS MasterMap Sites Layer, there is an explicit link between the access point feature and the OS MasterMap Highways Network Layer road node that is closest to it.
The 'accessMechanism', 'accessDirection', 'accessUseRestriction', 'dateTimeQualifier', 'heightQualifier', 'widthQualifier', 'weightQualifier', 'lengthQualifier' and 'natureOfAccess' attribute values are currently not populated in OS MasterMap Sites Layer.
The OS MasterMap Sites Layer product is supplied in three different formats:
Geography Markup Language (GML) version 3.2.1
GeoPackage
Vector tiles (MBTiles)
The OS MasterMap Sites Layer technical specification contains the following sections:
This theme includes sites associated with movement of passengers and goods by air, or where aircraft take off and land.
| Functional site | Description |
|---|---|
Only clearly defined helicopter stations and heliports outside of airfields and airports are to be captured.
All active air transport features (including military sites) will be captured as indicated below unless they fall out of scope (for example, a private property) or are described as disused sites.
The following features are included in the captured extent:
Buildings for the handling of air passengers and goods.
Buildings for the storage and maintenance of aircraft.
Aircraft landing and taxiing surfaces (man-made or natural).
Site access roads and paths.
Structures associated with the operation of the site.
Car parks for air passengers.
Areas of man-made and natural surface totally surrounded by included areas.
Areas of man-made and natural surface abutting included areas along a non-obstructing edge.
The following features are not included in the captured extent:
Aircraft-related services outside of perimeter fence (for example, warehouses or catering).
Public through-roads and pavements.
Hotels adjacent to site and their car parks.
This theme includes sites that focus on the provision of secondary medical care services.
| Functional site | Description |
|---|---|
All medical care sites will be captured as indicated below unless they fall out of scope; for example, a private property labelled as ‘The Blue Hospital’.
The following features are included in the captured extent:
Main buildings.
Site-specific service buildings and structures.
Access roads and paths.
Site-specific car parks.
Areas of man-made and natural surface surrounded by included areas.
The following features are not included in the captured extent:
Buildings not specifically related to the operation of the site (for example, children’s nursery).
Public through-roads and their pavements; and public pedestrian through-routes.
This data specification works within the existing structure of OS MasterMap as represented in the Unified Modelling Language (UML) class diagram below:
A layer is a set of related geospatial data which is then divided into one or more themes (much like OS MasterMap Topography Layer). These themes can be used together to form an end-user application.
Within the Sites Layer, features belong to only one theme. A theme is a logical collection of features that have been grouped according to their classification or relationships. The primary purpose of themes is to enable easier selection and interrogation of features by the user. Themes do not form part of the classification of a feature and do not affect the feature life cycle rules. The Sites Layer is currently composed of seven themes which are defined fully on the Theme definitions pages.
Features are digital representations of real-world concepts such as a building, road or barrier. The life cycle of a feature, its creation, modification and deletion are managed to most appropriately reflect the life cycle of the abstracted real-world concept that they depict.
An attribute is any item of information contained within an OS MasterMap feature. The TOID and the geometry of the feature are both attributes.
A functional site is a geolocated polygon representing the extent encompassing features with a collective type of function or activity. The functional site is thematically attributed and accompanied by access points. All the source data used in the creation of the OS MasterMap Topography Layer contains information about a feature’s function or purpose. Much of this data has been exposed in the Functional Sites Layer as a means of enhancing its analytical functionality. Functional sites are a representation of an assembly of cartographic features that share a common function (such as a school). It could also be a contiguous collection of features; for example, ‘General Hospital’.
Functional sites are created using the base form and function attributes of topographic areas. Information, such as ownership is not included within those attributes and cannot be used to ascertain extent. Because of this, functional site extents should not be confused with, or applied as legal extents.
A functional site can have multiple functions, or they can share some topographical features with another functional site. Shared topographic features, such as a sports field shared by two schools, will have the field captured to both school functional sites. Should there be a sports club on the grounds, such as a football club, then the field will be captured to this as well.
Rules have been developed for defining the differing types of functional site based on their function and the Topographic features that are visible from aerial photography. These rules specify what area features will be included within a functional site and how the boundary extent of the site can be delineated.
For example, the figure below demonstrates the extent of a simple functional site using OS MasterMap Topography Layer area features to identify and capture its extent. This is done by assessing a group of features that appear within a recognisable obstructing boundary and assigning them to the same functional site. This is also ratified using stereo aerial imagery and investigation through Change Intelligence. In the example shown below, this methodology has been used to assign all the features within the fence to a common function, in this case, a gas hub.
Each functional site has its own unique TOID and will be maintained throughout its lifecycle including versioning, changes and updates to its component features and alterations to its extent should they be warranted (for instance if the site increases in size due to land purchase). In addition, private roads that are wholly contained within a functional site and support the function are included in the extent.
It is important to note that obscured and underground features are not captured. This is because the OS MasterMap Topography Layer is captured at ground level from what is visible by aerial photography. However, all above ground features will be captured as normal.
While typically a functional site will usually be a connecting collection of polygons from OS MasterMap Topography layer, it is also possible for the functional site to consist of one or more disparate extents. Some sites, such as university campuses, will be a collection of several functional site extents belonging to a single stakeholder. These will be captured as one or more functional sites depending on the distance between the captured extents.
The stakeholder name will be captured if it is clear and unambiguous and is obtained through investigation where possible. The primary use of the stakeholder attribute is to define extensive and widely dispersed sites that come under the control of a single stakeholder; for example, universities.
In instances where multiple stakeholders exist for a given site, they will be listed in alphabetical order in the Stakeholder 1 attribute. Each new stakeholder will be separated with ‘+’. The Stakeholder 1 attribute will continue to hold only one role. The Stakeholder 2 attribute and role should not be populated.
The attributes currently not populated have been greyed out in the attribute definitions table in the following section.
This theme includes sites involved in the transfer of passengers or goods onto vessels for transport across water.
| Functional site | Description |
|---|
The following features are included in the captured extent:
Port buildings (for example, customs office, ticket office, waiting room)
Vehicle parking/waiting areas
Structures for loading people, vehicles or goods onto vessels
Access roads and paths
Areas of man-made and natural surface surrounded by included areas The following features are not included in the captured extent:
Public roads and pavements
A theme is a set of features that have been grouped together for the convenience of customers and to provide a high-level means of dividing the data in the layer logically. Features belong to only one theme.
Below are descriptions of the themes that are currently included in OS MasterMap Sites Layer and examples of functional sites that are represented within these themes. Also provided is an explanation of the features included or excluded during the capture process of an extent.
OS MasterMap Sites Layer provides seven themes:
This theme includes sites where the following activities take place:
The principles of chemistry are applied to materials to create different materials on a large scale.
Energy (that is, electricity, gas or oil) is produced, refined, distributed or stored.
The following features are included in the captured extent:
Internal site access roads and paths.
Buildings and structures associated with the operation of the site.
Areas of man-made and natural surface totally surrounded by included areas.
Areas of man-made and natural surface abutting included areas along a non-obstructing edge.
For marine oil terminals, include related berthing structures physically connected to the site The following features are not included in the captured extent:
Site-related areas outside of perimeter fence (for example, car parking).
Isolated mooring structures.
An access point refers to a functionally designed and maintained location where pedestrians and/or vehicles can enter or leave a site. Access points are initially captured from a visual inspection of OS MasterMap Topography and Imagery Layers. Further access points can also be captured and maintained through customer feedback and field survey.
Access points are point features which have been positioned on the boundary of the functional site extent to which they belong (see figure below). There are circumstances where access points do not lie on the site boundary; for example, underground or obscured access into a site, and these will be captured in their true position or within five metres of the functional site extent boundary.
Where there are several access types that are located next to each other; for example, a road with a pavement on one or more sides, a single ‘combined access’ point will be created to indicate that it is possible to access the site by foot and by vehicle at that location.
Access points are linked to functional site extents during their capture. They can also retain additional access information such as height and time or vehicular restrictions. The access point also references the nearest OS Highways Network Layer link TOID. This allows the user to easily integrate the data with other OS Datasets such as the OS MasterMap Highways Network Layer.
Each access point will have its own unique TOID and will be subject to a managed life cycle process, controlled by changes to attributes as well as changes to its associated Functional Site’s attributes.
Some of the access points have restrictions which cannot be ascertained from aerial imagery. As such, they are not currently available in OS MasterMap Sites Layer. The attributes currently not populated have been greyed out in the attribute definitions table in the following section.
| Functional site | Description |
|---|
Chemical works | A site where the principles of chemistry are applied to materials to create different materials. |
Electricity distribution | A site used to handle electricity as part of the process of distributing electricity nationally. If the site is for domestic electricity supply then it is considered to be an electricity sub-station site and not captured as part of the initial release. |
Electricity production | A site where electricity is generated on a large scale. |
Gas distribution or storage | A site associated with the storing or supply of gas to users. |
Oil distribution or storage | A depot where oil is stored. |
Oil refining | A site where crude oil is refined. |
Oil terminal | A storage point and distribution centre at the head of an oil pipeline |
This section defines the attributes associated with the RoutingPoint feature. It is important to note that UML notation has been used to show the multiplicity for an attribute. These indicate whether an attribute is optional (0), has a single value (1), or can have either / or (0..1) where ‘or’ is represented by double dots (..).
Subtype of: Node, TransportNode
The spatial object type defining point/node feature, which would normally lie on a Highways RoadLink and would be referenced by a particular access point.
The coordinate geometry defining the position of the routingPoint. The geometry is projected in two-dimensions (2D).
Attribute Name: geometry
Value type: GM_Point
Size: One coordinate set
Multiplicity: [1]
A unique identifier for a routingPoint, which is maintained along with the version number and version date to reflect the life cycle of the feature. NOTE: equivalent to INSPIRE identifier.
Attribute Name: toid
Value type: Text
Size: 20
Multiplicity: [1]
The version number of the data representation of the persisting routingPoint feature.
Attribute Name: version
Value type: Integer
Size: 3
Multiplicity: [1]
The date on which the current version of the routingPoint was created.
Attribute Name: versionDate
Value type: Date
Size: NA
Multiplicity: [1]
Reason for the current version of the routingPoint to be created. The valid reasons for change are defined in the ReasonForChangeValue code list.
Attribute Name: reasonForChange
Value type: ReasonForChangeValue
Size: 20
Multiplicity: [1]
The unique identifier (TOID) of the Highways road link feature that the routingPoint is related to.
Attribute Name: refToITNRoadLink
Value type: Text
Size: 20
Multiplicity: [1]
The date on which the current version of the Highways Road Link was created. A default value of ‘1900-01-01’ will be used to indicate where the date of this feature has not been captured.
Attribute Name: itnRoadLinkVersionDate
Value type: Date
Size: NA
Multiplicity: [1]
The distance (m) from the start of the referenced Network RoadLink feature to the vertex where the RoutingPoint is positioned. The startDistance is calculated in two-dimensions (2D).
Attribute Name: startDistance
Value type: Length
Size: 7.2
Multiplicity: [1]
This section defines and describes the values that are used by the product attributes to describe the functional site, access point, and routing point features. There are some attribute values currently not populated in OS MasterMap Sites Layer. These features are listed below the tables they feature in.
Airfield
An area of ground where aircraft take off and land. It may have some permanent buildings, but it is smaller than an airport and may be for private use only.
Airport
A feature where aircraft land and take off and which provides facilities for handling passengers, air freight and servicing aircraft.
Helicopter station*
A feature from where bodies such as the police or ambulance service operate helicopter operations.
Heliport*
An airport specifically designed for use by helicopters.
Hospice
A hospital for patients with terminal illnesses.
Hospital
A medical facility that provides secondary level care.
Medical care accommodation
A feature that provides both long term medical accommodation and medical care.
Vehicular ferry terminal | A site facilitating the embarkation and disembarkation of ferry passengers and their vehicles. |
Passenger Ferry Terminal | A site facilitating the embarkation and disembarkation of pedestrian ferry passengers |
Port Consisting of Docks and Nautical Berthing | A site on a waterway with facilities for loading and unloading ships. |
To meet customer needs a fully routable modal network is being created. A key element of this is to provide more usable data about the access to destinations. As a result, we are now directly splitting our road, track and path data where Access Links connect to the network. This will allow users to more easily route into sites using OS network data.
As nodes have now been created within the networks data, where Access Link features connect, there is now no requirement for Decision Node features and they are being removed from the Sites products.
The OS MasterMap Sites Layer data model is designed to integrate with OS MasterMap Highways Network. Routing points are intended to provide users with a reference to the position that is close to an access point, which can be used to aid navigation to the access point via the Highways road network. The routing points are provided where there is no viable Highways Network road node feature to refer to directly from an access point.
Routing points are currently being created by an automated process that performs a spatial query to identify the nearest position on the closest Highways Network road link feature. The process also ensures that there is no viable road node on the selected road link using a 5-metre tolerance before generating a routing point.
Routing points supplied in the initial release of OS MasterMap Sites Layer are created from the
product but still reference the ITN road network. In addition to the OS MasterMap Highways Network – Roads data, we have applied data.
The process will be subject to continuous revision between releases to improve its results.
This section describes the features which make up OS MasterMap Sites Layer, giving high level following information about each attribute.
This theme includes a very broad group of sites with a common high-level primary function of providing education (either state-funded or fee-paying).
| Main function | Functional site attribution | Description |
|---|
The table above shows how the main function of a site has been mapped across to the equivalent functional site attribution, for example, a first school will be attributed as ‘primary education’.
Where a school is described with one or more functions and it is not possible to ascertain which buildings relate to which function, the entire site will be captured once for each function present. There will also be instances where there are several functions associated to a single site.
In some cases, it may be possible to determine which buildings are related to the different functional sites, but not possible to divide the playing fields; as a result, the playing fields will be captured for each function and will overlap.
The following features are included in the captured extent:
All teaching and assembly buildings supporting education functions.
Ancillary buildings and structures directly enabling the site to operate (for example, boiler house, kitchens and waste disposal areas).
Site access roads and paths.
Recreational areas associated with the site (for example, playgrounds and playing fields).
Areas of man-made and natural surface totally surrounded by included areas.
For schools: areas of man-made and natural surface abutting included areas along a non-obstructing edge.
The following features are not included in the captured extent:
Public roads and pavements.
Pedestrian through-routes.
Separately addressed properties as indicated by house numbers.
Universities or higher education sites that have extensive and regionally disparate sites will be associated together using the stakeholder attribute, to specify a relationship between such sites that come under the control of a single stakeholder. This attribute is currently not populated but will be implemented in subsequent releases of the product.
Sites associated with professional bodies or work places will not be captured, for example, ‘Dance School’ or ‘Performing Arts School’.
This theme includes sites associated with the movement of passengers and goods by road.
| Functional site | Description |
|---|
All road transport sites will be captured as indicated below unless they fall out of scope (for example, a private property).
The following features are included in the captured extent:
Bus/coach station buildings (for example, ticket office, waiting room)
Bus/coach station shelters
Car/bus/coach parking areas
Buildings for bus/coach storage, maintenance and cleaning
Access roads and paths
Areas of man-made and natural surface surrounded by included areas The following features are not included in the captured extent:
Public roads and pavements
Pedestrian through-routes
This section defines the attributes associated with the FunctionalSite feature. It is important to note that UML notation has been used to show the multiplicity for an attribute. These indicate whether an attribute is optional (0), has a single value (1), or can have either/or (0..1) where ‘or’ is represented by double dots (..).
Subtype of: ActivityComplex Feature
A spatial area object that describes the geometry, extent and function of a real-world feature.
The coordinate geometry defining the area of the functionalSite. This relates to multi-part geometry. The geometry is projected in two dimensions (2D).
Attribute Name: geometry
Value type: GM_Object
Size: Minimum of 3 vertices
Multiplicity: [1]
A unique identifier for a functionalSite that is maintained along with the version number and version date to reflect the life cycle of the feature. NOTE: equivalent to INSPIRE identifier.
Attribute Name: toid
Value type: Text
Size: 20
Multiplicity: [1]
The version number of the data representation of the persisting functionalSite feature.
Attribute Name: version
Value type: Integer
Size: 3
Multiplicity: [1]
The date on which the current version of the functionalSite was created.
Attribute Name: versionDate
Value type: Date
Size: NA
Multiplicity: [1]
Reason for the current version of the functionalSite to be created. The valid reasons for change are defined in the ReasonForChangeValue code list.
Attribute Name: reasonForChange
Value type: ReasonForChangeValue
Size: NA
Multiplicity: [1]
This refers to the INSPIRE Activity Complex Status. This refers to a description of the state of a functionalSite. The valid states are defined in the FunctionStatusValue code list.
Attribute Name: functionStatus
Value type: FunctionStatusValue
Size: NA
Multiplicity: [1]
A description of the theme that a particular site falls under (that is, air transport, education, medical care and so on). The valid themes are defined in the FunctionThemeValue code list.
Attribute Name: functionTheme
Value type: FunctionThemeValue
Size: NA
Multiplicity: [1]
A description of the actual function of a site (that is, airfield, junior school, hospital and so on). The valid themes are defined in the FunctionValue code list. For sites with multiple functions, the values will be provided together and separated by a ‘,’. Valid multiple functions are described in the Function combination table.
Attribute Name: function
Value type: FunctionValue
Size: NA
Multiplicity: [1]
The perimeter (m) of the site or sum of the sites for a non-contiguous feature. The perimeter is projected in two dimensions (2D).
Attribute Name: perimeter
Value type: Length
Size: 10.2
Multiplicity: [1]
The area (m2) of the site or sum of the sites for a non-contiguous feature. The area is projected in two dimensions (2D).
Attribute Name: area
Value type: Real
Size: 16.6
Multiplicity: [1]
The name of the site (for example, ‘Brighton College’). Note this may be null if the captured value is a house number.
Attribute Name: distinctiveName1
Value type: Text
Size: 99
Multiplicity: [0..1]
A second name of the site, if applicable. Note this may be null if the captured value is a house number.
Attribute Name: distinctiveName2
Value type: Text
Size: 99
Multiplicity: [0..1]
A third name of the site, if applicable. Note this may be null if the captured value is a house number.
Attribute Name: distinctiveName3
Value type: Text
Size: 99
Multiplicity: [0..1]
A fourth name of the site, if applicable. Note this may be null if the captured value is a house number.
Attribute Name: distinctiveName4
Value type: Text
Size: 99
Multiplicity: [0..1]
Unique Property Reference Number (UPRN) assigned by the local custodian or Ordnance Survey to the primary building within a functional site (for example, main building in a school).
Attribute Name: primaryAddressBaseUPRN
Value type: Integer
Size: 12
Multiplicity: [0..1]
Information on parties related to the functionalSite. It is open to many different roles, such as owners, operators or competent authorities. Where more than one stakeholder exists, this field contains multiple stakeholders separated by ‘ + ‘.
Attribute Name: stakeholder1
Value type: Text
Size: 99
Multiplicity: [0..1]
Information on parties related to the functionalSite. It is open to many different roles, such as owners, operators or competent authorities. Currently not populated.
Attribute Name: stakeholder2
Value type: Text
Size: 99
Multiplicity: [0..1]
Information on the different roles of stakeholders for a particular functionalSite, such as users, owners, operators or competent authorities. The valid roles are defined in the StakeholderRoleValue code list.
Attribute Name: stakeholder1Role
Value type: StakeholderRoleValue
Size: NA
Multiplicity: [0..1]
Information on the different roles of stakeholders for a particular functionalSite, such as users, owners, operators or competent authorities. The valid roles are defined in the StakeholderRoleValue code list. Currently not populated.
Attribute Name: stakeholder2Role
Value type: StakeholderRoleValue
Size: NA
Multiplicity: [0..1]
This describes the nature of the defined extent of the functionalSite at the time of capture. The valid roles are defined in the ExtentDefinitionValue code list.
Attribute Name: extentDefinition
Value type: ExtentDefinitionValue
Size: 20
Multiplicity: [1]
The 'stakeholder2' and 'stakeholder2Role' attribute values are currently not populated in OS MasterMap Sites Layer
This section defines and describes the values that are used by the product attributes to describe the functional site, access point, and routing point features. There are some attribute values currently not populated in OS MasterMap Sites Layer. These features are listed below the tables they feature in.
This section defines the attributes associated with the AccessPoint feature. It is important to note that UML notation has been used to show the multiplicity for an attribute. These indicate whether an attribute is optional (0), has a single value (1), or can have either/or (0..1) where ‘or’ is represented by double dots (..).
Subtype of: Node, TransportNode
The spatial object type defining a point where there is access into and/or out of a site.
The coordinate geometry defining the position of the accessPoint. The geometry is projected in two dimensions (2D).
Attribute Name: geometry
Value type: GM_Point
Size: One coordinate set
Multiplicity: [1]
A unique identifier for an accessPoint, which is maintained along with the version number and version date to reflect the life cycle of the feature. NOTE: equivalent to INSPIRE identifier.
Attribute Name: toid
Value type: Text
Size: 20
Multiplicity: [1]
The version number of the data representation of the persisting accessPoint feature.
Attribute Name: version
Value type: Integer
Size: 3
Multiplicity: [1]
The date on which the current version of the accessPoint was created.
Attribute Name: versionDate
Value type: Date
Size: NA
Multiplicity: [1]
Reason for the current version of the accessPoint to be created. The valid reasons for change are defined in the ReasonForChangeValue code list.
Attribute Name: reasonForChange
Value type: ReasonForChangeValue
Size: NA
Multiplicity: [1]
The unique identifier (TOID) of the functional site to which the accessPoint relates.
Attribute Name: refToFunctionalSite
Value type: Text
Size: 20
Multiplicity: [1]
This describes the nature of the access permitted at the accessPoint. The valid access types are defined in the AccessTypeValue code list. Where there is more than one type of access, the values will be provided together and separated by a ‘,’. Currently only Pedestrian and Motor Vehicles access types are populated.
Attribute Name: accessType
Value type: AccessTypeValue
Size: 30
Multiplicity: [1]
This describes the mechanism used to access the functional site through the accessPoint. The valid AccessMechanismValue are defined in the AccessMechanismValue code list. Where there is more than one type of access mechanism, the values will be provided together and separated by a ‘,’. Currently not populated.
Attribute Name: accessMechanism
Value type: AccessMechanismValue
Size: NA
Multiplicity: [0..1]
This refers to the direction of travel that is permitted through the accessPoint. The valid access direction values are defined in the AccessDirectionValue code list. Currently not populated.
Attribute Name: accessDirection
Value type: AccessDirectionValue
Size: NA
Multiplicity: [0..1]
This refers to the nature of any access restriction. The valid restrictions are defined in the AccessUseRestrictionValue code list. Where there is more than one type of restriction, the values will be provided together and separated by a ‘,’. Currently not populated.
Attribute Name: accessUseRestriction
Value type: AccessUseRestrictionValue
Size: NA
Multiplicity: [0..1]
The unique identifier (TOID) of the related routingPoint feature, if there is one.
Attribute Name: refToRoutingPoint
Value type: Text
Size: 20
Multiplicity: [0..1]
The unique identifier (TOID) of the related OS MasterMap Network Layer road node feature; if this is used rather than a routing point. The Network layers road node is used in an identical manner to that of the previous OSMM ITN version.
Attribute Name: refToITNRoadNode
Value type: Text
Size: 20
Multiplicity: [0..1]
The date on which the current version of the OS MasterMap Highways Network Layer road node was created. A default value of ‘1900-01-01’ will be used to indicate where the date of this feature has not been captured. The Network layers road node is used in an identical manner to that of the previous OSMM ITN version.
Attribute Name: itnRoadNodeVersionDate
Value type: Date
Size: NA
Multiplicity: [0..1]
This refers to the dates or times that access is permitted through the accessPoint.
Attribute Name: dateTimeQualifier
Value type: Text
Size: 20
Multiplicity: [0..1]
This refers to the maximum vehicle height that is permitted through the accessPoint.
Attribute Name: heightQualifier
Value type: Distance
Size: 4.2
Multiplicity: [0..1]
This refers to the maximum vehicle width that is permitted through the accessPoint.
Attribute Name: widthQualifier
Value type: Distance
Size: 4.2
Multiplicity: [0..1]
This refers to the maximum vehicle weight that is permitted through the accessPoint.
Attribute Name: weightQualifier
Value type: Real
Size: 4.2
Multiplicity: [0..1]
This refers to the maximum vehicle length that is permitted through the accessPoint.
Attribute Name: lengthQualifier
Value type: Distance
Size: 4.2
Multiplicity: [0..1]
This describes the physical form of enforcement to expect at the accessPoint. The valid nature of access values is defined in the NatureOfAccessValue code list. Where there is more than one nature of access, the values will be provided together and separated by a ‘,’. Currently populated as Unknown.
Attribute Name: natureOfAccess
Value type: NatureOfAccessValue
Size: NA
Multiplicity: [1]
Further education | Further education | An educational site for academic and vocational qualifications below degree level. |
Higher education | Higher or university education | A feature where students study at National Qualifications Framework level 4 and above. |
University | Higher or university education | An institution of higher education. |
Non state primary or preparatory school | Non state primary education | An educational establishment for children from the ages of seven to eleven that is not funded by the state. |
Non state secondary school | Non state secondary education | An educational establishment for children of eleven years and over that is not funded by the state. |
First school | Primary education | An educational establishment for children from the ages of four to eight. |
Infant school | Primary education | An educational establishment for children from the ages of five to seven. |
Junior school | Primary education | An educational establishment for children from the ages of seven to eleven. |
Middle school | Primary education | An educational establishment for children from the ages of eight to twelve or nine to thirteen. |
Primary school | Primary education | An educational establishment for children from the ages of seven to eleven that is funded principally by the state. |
Secondary school | Secondary education | Educational establishment for children over 11 years old. |
Special needs education | Special needs education | A specialist school for the teaching of those with disabilities. |
Coach station | A place where coaches begin, break or end a journey and at which passengers may embark or disembark. A coach station may consist of buildings or may simply be an area specifically set aside with shelters and signage. |
Bus station | A place where buses begin, break or end their journey and at which passengers may embark or disembark. A bus station may consist of buildings or may simply be an area specifically set aside with shelters and signage. |
Road user services | An area for the supply of fuel, refreshments and so on near a road or motorway. |
This theme includes sites associated with movement of passengers and goods by rail.
| Functional site | Description |
|---|---|
All rail transport sites will be captured as indicated below unless they fall out of scope; for example, a private property labelled as ‘Railway Station Bungalow’.
The following features are included in the captured extent:
Station buildings
Station shelters
Platform areas
Access roads and paths
Station footbridges and associated structures
Station car parks
Areas of man-made and natural surface surrounded by included areas
Areas of man-made and natural surface abutting included areas along a non-obstructing edge The following features are not included in the captured extent:
Railway buildings (for example, signal boxes and maintenance huts)
Railway track areas (made-way)
Man-made and natural areas alongside tracks
Public roads and footpaths
It is important to note that functional sites in the rail transport theme are often not contiguous and may be constrained of the structure of polygons in the Topography Layer.
This section defines the geometric data types used by features of the OS MasterMap Sites Layer. A UML diagram is used to support the data type descriptions.
The following table details the data type of the geometric attributes of OS MasterMap Site Layer features. Each feature type has a spatial attribute called ‘geometry’. The data type of this attribute is given in the third column of the table.
| Feature type | Spatial attribute | Data type of geometry attribute | For details, see: |
|---|
A point is used to specify a single horizontal location by a coordinate pair in a given spatial reference system.
Example
A point defined in the BNG reference system has easting and northing coordinates in units of metres, where the easting is in the range 0 to 700000 and the northing is in the range 0 to 1300000.
Example class model
A polygon is a single closed region on the spatial reference system projection plane, defined by a set of geometric rings that represent the boundaries. A polygon has one outer boundary and zero or more inner boundaries (holes in the polygon). The inner boundaries must not cross each other or contain other inner boundaries. Coordinates in outer boundaries are oriented in an anticlockwise direction; coordinates in inner boundaries are oriented in a clockwise direction. In the Geography Markup Language (GML) data, these are implemented as a Surface containing a single Polygon Patch, with the exterior and any interior boundaries represented as a LinearRing.
Example
Example class model
A multi-polygon is used where a single functional site consists of separate areas, such as a school on both sides of a road. Each polygon is as described above. In GML, this is represented with a gml:MultiSurface having a number of ‘surface members’ each of which is a single gml:Surface.
GML is an XML (Extensible Mark-up Language) grammar for expressing geographic features. GML serves as a modelling language for geographic systems as well as an open interchange format for geographic transactions on the Internet.
More information can be found on the Open Geospatial Consortium (OGC):
The XML specifications that GML is based on are available from the World Wide Web Consortium (W3C):
Information about Unicode and UTF-8, the character encoding we have chosen, is available on the Unicode Consortium website:
XML schemas are used to validate the format and content of the GML. The GML 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 Ordnance Survey application schemas that are referenced by the data are available from our website at:
These schemas make use of XML Schema Definitions (XSDs) and Document Type Definitions (DTDs) produced by the W3C that are available from the W3C website at:
xlink –
gml –
osgb –
xml –
Operational
Site is in operational use.
Out of Service
Site is out of service or not in operational use.
Cycles
Access point permits access to cycles.
Horse Drawn Vehicles
Access point permits access to horse-drawn vehicles.
Mopeds
Access point permits access to mopeds.
Motor Vehicles
Access point permits access to motor vehicles.
Motorcycles
Access point permits access to motorcycles.
Pedestrian
Access point permits access to pedestrians.
Ridden or Accompanied Horses
Access point permits access to ridden or accompanied horses.
Undefined
Access point type is undefined.
Fully Defined
The supplied extent is, as far as can be ascertained, fully defined in this release.
Partially Defined
The extent is known to be incomplete due to a known issue with the extent or because of restrictions to capture.
Undefined
The extent is unknown or has not been defined in this release. This will also apply to sites where their full definition is underground or wholly obscured.
In
Inbound access is permitted at this point.
Out
Outbound access is permitted at this point.
In and Out
Inbound and outbound access is permitted at this point.
Administered By
Site is administered by stakeholder.
Owner Of
Site is owned by stakeholder.
Principal User Of
Site is principally used by stakeholder.
Religious Interest In
Site is of religious interest to stakeholder.
New
This is a new feature in the database.
Modified
The feature has been edited by an operator. Used in the following cases:
1. The geometry of a topographic feature is changed following real-world change (applicable to point, line and text features only and not polygons).
2. The geometry of a non-topographic feature, for example, inferred link or BoundaryLine feature is changed.
3. A cartographic symbol feature is repositioned.
4. A CartographicText feature is repositioned.
Reclassified
The descriptive attributes of a feature have changed. The feature code may have changed.
Attributes
Applied to features that have had only attributes changed, except those covered by TextChange and Reclassified values.
Position
Feature has changed geometry and/or position due to an improvement in its absolute accuracy; that is, its relationship to the National Grid (relevant for the positional accuracy improvement programme which is now complete). This type of feature change is not associated with real-world change.
Software
Feature has been adjusted by an automatic software process. Includes geometric adjustment, cleaning, squaring, paralleling (text and lines) and reversing direction of digitising.
Door
Access is via a door.
Gate
Access is via a gate.
Manned Barrier
Access is via a manned barrier.
Monitored Rising Barriers
Access is via a monitored rising barrier.
Monitored Rising Bollards
Access is via monitored rising bollard(s).
Moveable Barrier
Access is via a moveable barrier.
Opening
Access is through a non-restricted opening.
Revolving Door
Access is via a revolving door.
Rising Barrier
Access is via a rising barrier.
Rising Bollards
Access is via rising bollard(s).
Shutter
Access is via a shutter.
Steps
Access is via a flight of steps.
Turnstile
Access is via a turnstile.
Unknown
Access enforcement is unknown.
Disabled
Access is restricted except for disabled access.
Emergency Access
Access is restricted except for emergencies at this point.
Guests
Access is restricted except for guests at this point.
Official Business
Access is restricted except for official business at this point.
Patrons
Access is restricted except for patrons at this point.
Residents
Access is restricted except for residents at this point.
Through Traffic
Access to through traffic is permitted at this point.
Air Transport | Airfield Airport Helicopter station Heliport |
Education | Non-state primary education
Special needs education Primary education
Further education
|
Medical Care | Hospice Hospital Medical care accommodation |
Rail Transport | Railway station Vehicular rail terminal Tram station |
Road Transport | Bus station Coach station Road user services |
Water Transport | Vehicular ferry terminal Passenger ferry terminal Port consisting of docks and nautical berthing |
Utility or Industrial | Chemical works Electricity distribution Electricity production Gas distribution or storage Oil distribution or storage Oil refining Oil terminal |
Bus station, coach station |
Further education, higher or university education |
Further education, non-state primary education, non-state secondary education |
Further education, non-state primary education, secondary education |
Further education, non-state secondary education |
Further education, primary education |
Further education, primary education, secondary education |
Further education, primary education, secondary education, special needs education |
Further education, secondary education |
Further education, special needs education |
Hospital, medical care accommodation |
Non-state primary education, non-state secondary education |
Non-state primary education, non-state secondary education, special needs education |
Non-state primary education, secondary education |
Non-state secondary education, primary education |
Non-state secondary education, special needs education |
Passenger ferry terminal, vehicular ferry terminal |
Primary education, secondary education |
Primary education, secondary education, special needs education |
Primary education, special needs education |
Secondary education, special needs education |
Appointment | Access is only available by a pre-arranged appointment. |
Official Pass | Access is only available by production of an official pass. |
Pay and Display | Access is only available by pay and display mechanism. |
Pay on Foot | Access is only available by pay on foot mechanism. |
Payment | Access is only available by a payment. |
Valid Ticket | Access is only available by production of a valid ticket. |
Air Transport | Sites used for air transport. |
Education | Sites used for education. |
Medical Care | Sites used for medical care. |
Rail Transport | Sites used for rail transport. |
Road Transport | Sites used for road transport. |
Water Transport | Sites used for water transport. |
Utility or Industrial | Sites used for utility or industrial purposes. |
Railway station
A feature by a light railway network or railway network where a light rail vehicle or train may stop to pick up goods or passengers.
Vehicular rail terminal
A facility where freight vehicles may be transferred to or from the rail network.
Tram station
A stop/station for trams. Tram systems are defined as light rail systems with some shared running over roads.
functionalSite | geometry | Polygon |
accessPoint | geometry | Point |
routingPoint | geometry | Point |
| GML Attribute | GeoPackage Attribute |
|---|---|
| GML Attribute | GeoPackage Attribute |
|---|---|
| GML Attribute | GeoPackage Attribute |
|---|---|
OS MasterMap Sites Layer is supplied as a national vector tiles set in a single MBTiles file. This is a lightweight set of tiles that are efficient and fast to render in your software, and which 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 table. In the zoom levels columns within the table, the letter N indicates that the specified layer and attribute are not mapped within that zoom level, whereas the letter Y indicates that the specified later and attribute are mapped within that zoom level.
| Attribute | Zoom level: 0 to 11 | 12 | 13 | 14 | 15 |
|---|---|---|---|---|---|
GeoPackage (*.gpkg) is an open, non-proprietary, platform-independent, standards-based data format for geographic information systems (GIS), as 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 is natively supported by numerous software applications.
The naming of attributes between GeoPackage and the Geography Markup Language (GML) file is very similar as GeoPackage files are not limited in the number of characters for an attribute name.
Therefore, the following tables map the GML attribute name to the attribute name in the GeoPackage files. The GML contains an attribute which describes the geometry of the feature; this is not applicable for a GeoPackage file as they are separated by their geometry.
Please note that the use of an asterisk symbol (*) in the following tables indicates that a particular attribute is not mapped to GML.
| Attribute | Zoom level: 0 to 11 | 12 | 13 | 14 | 15 |
|---|---|---|---|---|---|
| Attribute | Zoom level: 0 to 11 | 12 | 13 | 14 | 15 |
|---|---|---|---|---|---|
*
fid
gml_id
toid
pointgeometry
geometry
version
version
versionDate
version_date
reasonForChange
reason_for_change
refToITNRoadLink
ref_to_itn_road_link
itnRoadLinkVersionDate
itn_road_link_version_date
startDistance
start_distance
*
fid
gml_id
toid
pointgeometry
geometry
version
version
versionDate
version_date
reasonForChange
reason_for_change
refToFunctionalSite
ref_to_functional_site
accessType
access_type
accessMechanism
access_mechanism
accessDirection
access_direction
accessUseRestriction
access_use_restriction
refToRoutingPoint
ref_to_routing_point
refToITNRoadNode
ref_to_itn_road_node
itnRoadNodeVersionDate
itn_road_node_version_date
dateTimeQualifier
date_time_qualifier
heightQualifier
height_qualifier
widthQualifier
width_qualifier
weightQualifier
weight_qualifier
lengthQualifier
length_qualifier
natureOfAccess
nature_of_access
*
fid
gml_id
toid
multipolygongeometry
geometry
version
version
versionDate
version_date
reasonForChange
reason_for_change
functionStatus
function_status
functionTheme
function_theme
function
function
perimeter
perimeter
area
area
distinctiveName1
distinctive_name_1
distinctiveName2
distinctive_name_2
distinctiveName3
distinctive_name_3
distinctiveName4
distinctive_name_4
primaryAddressBaseUPRN
primary_addressbase_uprn
stakeholder1
stakeholder_1
stakeholder2
stakeholder_2
stakeholder1Role
stakeholder_1_role
stakeholder2Role
stakeholder_2_role
extentDefinition
extent_definition
toid
N
Y
Y
Y
Y
polygon
N
Y
Y
Y
Y
function_status
N
Y
Y
Y
Y
function_theme
N
Y
Y
Y
Y
function
N
Y
Y
Y
Y
perimeter
N
Y
Y
Y
Y
Area
N
Y
Y
Y
Y
distinctive_name_1
N
Y
Y
Y
Y
distinctive_name_2
N
Y
Y
Y
Y
primary_addressbase_uprn
N
Y
Y
Y
Y
stakeholder_1
N
Y
Y
Y
Y
stakeholder_1_role
N
Y
Y
Y
Y
Toid
N
Y
Y
Y
Y
Point
N
Y
Y
Y
Y
ref_to_functional_site
N
Y
Y
Y
Y
access_type
N
Y
Y
Y
Y
access_mechanism
N
Y
Y
Y
Y
access_direction
N
Y
Y
Y
Y
access_use_restriction
N
Y
Y
Y
Y
ref_to_routing_point
N
Y
Y
Y
Y
ref_to_itn_road_node
N
Y
Y
Y
Y
height_qualifier
N
Y
Y
Y
Y
width_qualifier
N
Y
Y
Y
Y
weight_qualifier
N
Y
Y
Y
Y
length_qualifier
N
Y
Y
Y
Y
nature_of_access
N
Y
Y
Y
Y
Toid
N
Y
Y
Y
Y
Point
N
Y
Y
Y
Y
ref_to_itn_road_link
N
Y
Y
Y
Y
start_distance
N
Y
Y
Y
Y
The name of the attribute and what it is describing.
The nature of the attribute, for example a numeric value or a code list value.
The length of the attribute provided (optional).
Describes how many times this element is expected to be populated in the data. An attribute may be optional or mandatory within the product. These are denoted by:
‘1’ – there must be a value.
‘0..1’ – population is optional but a maximum of one attribute will be returned These values may be used in combination.
The Geography Markup Language (GML) and GeoPackage formats use the British National Grid (BNG) spatial reference system. BNG uses the OSGB36 geodetic datum and a single Transverse Mercator projection for the whole of Great Britain. Positions on this projection are described using easting and northing coordinates in units of metres.
Vector tile format is supplied in Web Mercator projection (EPSG:3857). Web Mercator projection uses WGS84 geodetic datum to render the vector tiles.
A general guide to cartography is available on our More than Maps platform here.
A general introductory guide to BNG is provided at:
For information on how to open, use and understand a GeoPackage dataset, please refer to our Getting Started with GeoPackage guide. For further information on GeoPackage, please see the GeoPackage website.
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*
It supports raster, vector and database formats, making it a highly versatile solution.
It is an OGC standard.
In most cases, it is a plug-and-play format.
* A file size limit might be imposed by the file system to which the file is written.
