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...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
The Road Network is a topologically structured link and node network made up of the following feature types:
| Feature type | Description |
|---|---|
OS MasterMap Highways Network has been built with the INSPIRE Transport Networks Data Specification as a basis. This has been extended to include the additional properties required by BS 7666-1:2006, defined within the NSG to ensure that conformance to both INSPIRE and BS7666-1:2006 can be achieved.
Each feature within the OS MasterMap Highways Network will have the following common attribution:
gml:id, gml:identifier and inspireId
beginLifespanVersion
inNetwork – this shall always be set to “OSHighwayNetwork”
reasonForChange
validFrom
This is assigned a nilReason value “unknown” for most features.
In addition, many of the attributes which have been inherited from the INSPIRE Transport Network model have a stereotype of ‘voidable’, for example “beginLifespanVersion”. Where these attributes have not been populated there is a requirement to give a reason for this. This will be specified in the GML through an attribute called “nilReason”.
The OS MasterMap Highways Network – Roads can be ordered as either Full Supply or Change Only Update. The GeoPackage and vector tiles files are full GB coverage so are not available as a COU. The GML structures for Full Supply and COU are different. The differences are fundamentally the open and closing tags which will have an impact on how you choose to load the product. Examples of the different opening and closing tags can be found on the GML examples page. If a customer wishes to move their order from Full Supply to COU, they will need to receive an initial supply first and apply the COU file to that initial supply. The COU should not be applied to a Full Supply order.
When an order for Full Supply is placed, the product will contain all features for the customer’s area of interest. When a product refresh is ordered, for this type of order, the supply will contain all the features for the area of interest which will include features that have not changed. This supply mechanism will not explicitly identify which features are new, have been modified or have been removed. This can still be identified by querying the reasonForChange and the beginLifespanVersion attribute.
When an order is placed for COU the first order received will be an initial supply. Initial supply refers to the first order that a customer takes of OS MasterMap Highways Network under the COU order type. An initial supply contains all features for the complete area covered by the order, and every feature will be an “insert”. Updates, which contain the latest changes to the features are automatically sent out.
Following the initial order, a COU will be supplied, at the selected update schedule of the customer. COU only contains new features, new versions of features and information about deleted features. A feature can be deleted from the customers holdings for two reasons; the feature has been deleted and the id will no longer exist in the product, or the feature has moved outside of the customers area of interest but still exists in the national product and therefore could be reinstated in a customer’s holdings. To identify the difference between the two deletes the reasonForChange can be used. If the value is “end of life” then this feature has been permanently deleted whilst any other change value would indicate the feature has moved outside of the holdings and could be reinstated in future. Any feature within the area of interest that has not undergone any change will not be supplied.
The features within the initial supply and COU are provided as transactions. A transaction identifies if the feature is new, modified or removed from the product. The three types of transactions are:
<os:insert>
These are features which have been newly inserted into the product or the customer’s area of interest since the last product supply.
<os:replace>
These are features which have had either a geometry change or an attribute change since the last product supply. The whole feature will be supplied, not just the changed attributes. The recommended action would be to completely replace the feature which currently exists in the customer’s holdings.
<os:delete>
These are features which have ceased to exist in the last product release or have moved out of the customer’s area of interest. Features which have been deleted will be supplied with the entire feature’s attribution. These features should be removed from the customer’s live data holding.
The initial supply will contain an insert transaction for all features in the customer’s holdings. The following COU supplies will have insert and replace transactions in one GML file and deleted features will be supplied in a separate file. Where a delete file has been supplied, this must be loaded before the file containing inserted and replaced features. There are examples in on the GML examples page of the different types of transactions.
OS MasterMap Highways Network – Roads is supplied in three formats: Geography Markup Language (GML 3.2.1), GeoPackage and vector tiles. All formats are compressed into a regular zip file (.zip).
There have been small enhancements to the OS MasterMap Highways Network. This section will outline the main changes to the Road Network product. For changes to the Routing and Asset Management Information product, please see the Routing and Asset Management Information Technical Specification.
RoadJunction feature has been populated.
RoadLink and RoadNode ‘z’ values have been enhanced to reduce discrepancies when the road passes over a structure, for example, a bridge.
The “OperationalState” attribute on the Street features has introduced a new value, “Addressing Only”, into the “OperationalStateValue” codelist.
Corrected wrong multiplicity value for minimum width attribute within the “RoadWidthType” Data Type. This had the incorrect value of ‘1’ this has been corrected to ‘0..1’.
RoadLink
A line segment representing the general alignment of the carriageway of the road.
RoadNode
A point connecting to at least one RoadLink, providing network connectivity.
Road
A Road defines the complete collection of references to RoadLink features defining the network topology which share the same road name and/or road classification number. For example, the A38 or Romsey Road.
Street
A Street feature is the definition of the street as defined in the National or Scottish Street Gazetteer, made up of aggregated geometry with a unique identifier (USRN).
RoadJunction
A collection of RoadNodes that make up a named or numbered road junction.
FerryLink
A feature which represents a ferry route between two FerryNodes.
FerryNode
A feature representing the point at which a vehicle ferry route or section of ferry route starts or ends.
FerryTerminal
A feature representing the point at which vehicle transfers from the ferry network to the road network or vice versa.
This technical specification provides detailed technical information about OS MasterMap Highways Network – Roads. It is targeted at technical users and software developers.
The OS MasterMap Highways Network is the authoritative highway network for Great Britain. It brings together Ordnance Survey’s large-scale road content, the National Street Gazetteer (NSG), the Trunk Road Street Gazetteer (TRSG) and the Scottish Street Gazetteer (SSG).
OS MasterMap Highways Network is made up of four product schemas: Linear Highway Network, Highways Dedication, Routing and Asset Management Information and Highways Water Transport Network. These four schemas create three products which are a part of the OS MasterMap Highways Network family:
OS MasterMap Highways Network – Roads
OS MasterMap Highways Network – Routing and Asset Management Information
OS MasterMap Highways Network – Paths
This technical specification will cover the OS MasterMap Highways Network – Roads (from here referred to as Road Network) product.
All features that comprise the OS MasterMap Highways Network – Roads will be assigned a persistent identifier, which in most instances is an Ordnance Survey TOID (Topographic Identifier). For features which have originated from the National Street Gazetteer or Scottish Street Gazetteer, the persistent identifier will be either a Unique Street Reference Number (USRN) for Street features or a unique ID for Maintenance, Reinstatement, and Special Designation.
Identifiers shall be encoded in three properties in the data:
gml:id – this is a feature identifier comprising the shorthand prefix namespace and local identifier used to uniquely identify and reference the feature within the dataset. Example: osgb4000000009461245.
gml:identifier – this is a global feature identifier and can be used to identify and reference the feature within other datasets. Example: http://data.os.uk/id/4000000009461245.
inspireID – this is a complex property made up of a localId, namespace and versionId which uniquely identifies the feature and version within an INSPIRE dataset. The versionId will not be populated in the OS MasterMap Highways Network products.
An example of a full identifier is given below:
Where features have come from the same source as the OS MasterMap ITN Layer, the identifier will be persistent and correspond to the same feature in ITN.
The gml:id is used throughout the OS MasterMap Highways Network products as the identifier used to reference to other features.
TOIDs (Topographic Identifiers) are strings of up to twenty characters which consist of two parts:
Namespace: This is either a HTTP URI, (http://data.os.uk/) or shorthand prefix (‘osgb’)
Local identifier: 16-digit numeric string (0-9)
gml:id – ‘osgb4000000009461245’
localId – ‘4000000009461245’
identifier - ‘http://data.os.uk/4000000009461245’
USRNs (Unique Street Reference Numbers) are strings of up to twelve characters which consist of two parts:
Namespace: This is either a HTTP URI (http://data.os.uk/) or shorthand prefix (‘usrn’)
Local identifier: Up to an 8-digit numeric string (0-9)
gml:id – ‘usrn82101225’
localId – ‘82101225’
identifier - ‘http://data.os.uk/82101225’
Although the gml:id is the identifier used for referencing features in OS MasterMap Highways Network products, the localId is the identifier used by the National Street Gazetteer, National Land and Property Gazetteer and the OS AddressBase family of products.
Unique IDs for Maintenance, Reinstatement, Special Designation are strings of up to 17 characters which consist of two parts:
Namespace: This is either a HTTP URI (http://data.os.uk/) or shorthand prefix (‘id_’)
Local identifier: 14 alphanumeric string
The ID for HighwayDedication is a string of up to 25 characters comprised of the characters “esu” followed by three parts separated by “_”:
LHA authority code
ESU it references
dedication code in the NSG
For example, esu4720_4280330430163_8, esu4720_4280340431456_11
gml:id – ‘id_3700MA01862142’ or ‘esu4720_4280330430163_8’
localId – ‘3700MA01862142’ or ‘esu4720_4280330430163_8’
identifier - ‘http://data.os.uk/3700MA01862142’ or ‘https://data.os.uk/id/ esu4720_4280330430163_8’
OS MasterMap Highways Network– Roads and OS MasterMap Highways Network – Paths will be supplied in three formats: Geography Markup Language (GML 3.2.1), GeoPackage and vector tiles. All formats are compressed into a regular zip file (.zip).
OS MasterMap Highways Network– RAMI will be supplied in two formats: Geography Markup Language (GML 3.2.1) and GeoPackage. All formats are compressed into a regular zip file (.zip).
OS MasterMap Highways Network extends the INSPIRE Transport Networks (Road and Water) Technical Specification (version 3.2).
OS MasterMap Generic Network model extends the INSPIRE Base Models - Generic Network Model (version 3.0rc3).
OS MasterMap Highways Network extends the INSPIRE specification to include the additional properties required by BS 7666-1:2006 defined within the National Street Gazetteer (NSG) Data Transfer Format (DTF) and Scottish DTF (SDTF) to ensure that conformance to both INSPIRE and BS7666-1:2006 can be achieved.
The data structure is described by means of UML class diagrams and accompanying data dictionary tables. The specification conforms to the rules for application schema specified in ISO 19103 Conceptual schema language and ISO 19109 Rules for application schema, as adopted by INSPIRE.
Colour conventions have been used in the diagrams and tables to allow users to easily distinguish the INSPIRE feature classes (coloured grey) from the Ordnance Survey feature classes which extend the INSPIRE specifications (coloured orange). All code list classes are coloured blue, enumeration classes are green and data types/union classes are purple.
The data dictionary tables use orange for a feature type, blue for a code list, green for enumerations, and purple for data types.
Class names are conceptually meaningful names (singular noun) in UpperCamelCase.
Class names end in “Value” where the class is assigned the stereotype <<CodeList>> or <<Enumeration>>.
Class names shall end in “Type” where the class is assigned the stereotype <<DataType>>.
Property names (attributes and associations) are in lowerCamelCase.
The following stereotypes are used on UML elements:
Constraints are defined on the Class using human readable language only. Constraints are displayed on the class diagram included below. These constraints are used to define co-constraints or restrict INSPIRE properties only.
There are three key types of relationship defined between classes:
Generalisation/Specialisation – Used to denote either:
An extension relationship. The target class represents the same real-world entity and is extending it to include additional properties not defined on the parent class.
A sub-typing relationship – The target class defines a specialised sub-type of parent feature. For example, TransportNode is a specialised sub-type of a generic Node class.
This class has the same name as the class it is extending.
Directed Association – Used to denote relationships between features. These relationships are encoded as references to the related feature via the identifier assigned in the gml:id. The directed end shall be assigned a name which describes the relationship between the two features and a multiplicity.
Aggregation – Used to denote part-of relationships. Aggregations are used to describe loose part-of relationships. If the parent feature ceases to exist, then the part feature can continue to exist. For example, a Road Name may cease to exist, but the Road will still exist.
This technical specification includes the following sections:
A navigable road network dataset with detailed information about planned roads and roads under construction for Great Britain.
This product is updated monthly.
For all highways stakeholders, OS MasterMap Highways Network is data you can trust. It draws on authoritative sources and helps underpin the common operational picture that leads to faster, better decisions.
A common highways dataset means a common understanding of the existing network, enabling better decision and policy making.
Highly detailed road geometry supplied with essential unique identifiers, including the Unique Street Reference Numbers (USRNs) and Topographic Identifiers (TOIDs), which enable linking and sharing of data against the road and street networks.
Get detailed information about planned roads and roads under construction helping you to better understand the roads of today and the roads of tomorrow.
OS MasterMap Highways Network – Roads combines high-quality, accurately surveyed data with features from the National Street Gazetteer; the Local Highways Authorities road name, numbering and maintenance; the Trunk Road Street Gazetteer collected by Highways England and Welsh Government; and the Scottish Street Gazetteer containing information from Scottish local authorities and Transport Scotland.
OS MasterMap Highways Network – Roads can be used for:
Source for legal road identifications
Costings or benefits of road policies
Calculating funding allocations
Evidence-based policy making
Journey and transport planning
Emergency Service planning
Enforcement regulation
Traffic statistics
School allocation
Smart cities
Access: Download
Category: Networks
Data theme: Transport
Data structure: Vector – Topologically structured link and node network
Coverage: Great Britain
Scale: 1:1 250 to 1:10 000
Format: GML 3.2.1, GeoPackage, vector tiles
Ordering area: All of Great Britain or a customisable area (user-defined polygon)
OS Data Hub plan: Premium Plan, Public Sector Plan, Energy & Infrastructure Plan
Access to this product is free for PSGA Members. Find out if you are a PSGA Member or download a sample of OS MasterMap Highways Network – Roads by accessing the product page here with links to all of the relevant resources. Alternatively, you can try out the full product by applying for a Data Exploration license.
OS MasterMap Highways Network – Roads is a relational product. This results in there being relationships between different feature types.
The table below identifies how the feature types relate to one another, and which attributes are the primary and foreign keys. This is also represented in the image below. The attribute at the arrowhead is the primary key and the attribute at the base of the arrow is the foreign key.
| Source Feature Information | Foreign Key Attribute | Destination Feature Information | Primary Key Attribute |
|---|---|---|---|
This section describes the features which make up OS MasterMap Highways Network - Roads. The attributes associated with these feature types are listed below along with a brief description of their data properties.
Many of the attributes which have been inherited from the INSPIRE Transport Network model have a stereotype of ‘voidable’, for example, “beginLifespanVersion”. Where these attributes have not been populated then there is a requirement to give a reason for this. This will be specified in the GML through an attribute called “nilReason”.
| Stereotype | UML Element | Description |
|---|---|---|
<<ApplicationSchema>>
Package
Parent package containing sub-packages and elements that comprise part of the modular specification.
<<FeatureType>>
Class
A spatial object type. [ISO 19136].
<<Type>>
Class
A structured data type with identity.
<<DataType>>
Class
A structured data type without identity. [ISO/TS 19103].
<<Union>>
Class
A structured data type without identity where exactly one of the properties of the type is present in any instance.
<<Enumeration>>
Class
A fixed controlled set of values for a free text data type.
<<CodeList>>
Class
A controlled set of values for a free text data type that may be extended.
<<Voidable>>
Property
A property that is required but is either not currently captured (unknown) or is partially populated (unpopulated).
<<LifecycleInfo>>
Property
Property considered part of the life cycle information.
The Identifier is an INSPIRE data type and its elements make up the “inspireId” attribute which can be found across all feature types in the OS MasterMap Highways Network.
An external unique object identifier published by the responsible body may be used by external applications to reference the spatial object.
The local identifier is unique within the namespace, that is no other spatial object carries the same unique identifier.
Attribute name: localId
Type: CharacterString
Size: 16
Multiplicity: [1]
Namespace uniquely identifying the data source of the spatial object.
Attribute name: namespace
Type: CharacterString
Size: 18
Multiplicity: [1]
Streets are attributed with an “operationalState” with a data type of “OperationalStateType”. The attribution of this data type is detailed below.
Indicator identifying the physical nature of the road, e.g. Under Construction, as reported by the highway authority.
Attribute name: state
Type: OperationalStateValue
Size: 19
Multiplicity: [1]
If known, the real-world start and end date/times when the state applies.
Attribute name: validTime
Type: TM_Period
Multiplicity: [0..1]
When a street has been closed a short description of the reason for closure.
Attribute name: reason
Type: CharacterString
Size: 120
Multiplicity: [0..1]
Feature Type
—
Feature Type
—
RoadLink
startNode
RoadNode
id
RoadLink
endNode
RoadNode
id
RoadLink
relatedRoadArea
TopographicArea
TOID
RoadLink
formsPartOf
Road
id
RoadLink
formsPartOf
Street
id
RoadNode
relatedRoadArea
TopographicArea
TOID
Road
link
RoadLink
id
Street
link
RoadLink
id
RoadJunction
node
RoadNode
id
FerryTerminal
element
RoadNode
id
FerryTerminal
element
FerryNode
id
FerryTerminal
refToFunctionalSite
FunctionalSite
id
FerryLink
startNode
FerryNode
id
FerryLink
endNode
FerryNode
id
A point spatial object that is used to break up the road network for connectivity. The road network splits for the following circumstances:
The location where an attribute recorded on the road link changes for example its name or form.
The intersection or crossing of Roads (including bridges, flyovers and tunnels where there is no connectivity).
The start/end of a Road.
Where a One-Way Routing feature starts or ends.
Where a tunnel starts or ends.
Where there is a connection to the Path Network.
The context diagram below shows how the RoadNode has been inherited from INSPIRE and the attribution held on the RoadNode.
A point representing either the start/end of a road, the connectivity between two or more roads or where one of the recorded attributes changes along a road.
Constraints: formOfRoadNode shall never be voidable
Unique identifier, for RoadNode this is a TOID
Attribute name: gml_id (GML), toid (GeoPackage), toid (VectorTiles)
Type: CharacterString
Size: 20
Multiplicity: [1]
Uniform Resource Identifier
Attribute name: identifier (GML), identifier (GeoPackage), Not provided (VectorTiles)
Type: CharacterString
Size: 37
Multiplicity: [1]
External object identifier of the spatial object.
Attribute name: inspireId
Type: Identifier
Multiplicity: [0..1]
Date and time at which this version of the spatial object was inserted or changed in the spatial data set. Note: The time part is always set to zero.
Attribute name: beginLifespanVersion
Type: DateTime
Multiplicity: [1]
The time when the transport node started to exist in the real world. Note: The time part is always set to zero.
Attribute name: validFrom
Type: DateTime
Multiplicity: [1]
The three-dimensional location of the node. For nodes representing grade separated intersections the elevation is of the lower road
Attribute name: geometry
Type: GM_Point
Multiplicity: [1]
Description of the function of a road node in the road transport network.
Attribute name: formOfRoadNode (GML), form_of_road_node (GeoPackage), form_of_road_node (VectorTiles)
Type: FormOfRoadNodeValue
Size: 21
Multiplicity: [1]
Further specialisation of the form of road node.
Attribute name: classification (GML), classification (GeoPackage), Not provided (VectorTiles)
Type: RoadNodeClassificationValue
Size: 19
Multiplicity: [0..1]
Point where vehicles can either exit or enter a controlled-access highway. Note: Values not populated in the initial release.
Attribute name: access
Type: AccessPointValue
Size: 5
Multiplicity: [0..1]
The name of any junction that the node represents part of. Note: Where a feature has more than one name, the language of each name is provided as a 3-digit ISO 639-2 code (‘eng’, ‘cym’, ‘gla’).
Attribute name: junctionName (GML), junction_name (GeoPackage), junction_name (VectorTiles)
Type: LocalisedCharacterString
Size: 120
Multiplicity: [0..2]
The number of any motorway junction that the node represents part of, for example M3 J12.
Attribute name: junctionNumber (GML), junction_number (GeoPackage), junction_number (VectorTiles)
Type: CharacterString
Size: 30
Multiplicity: [0..2]
The reason for a change made to a feature.
Attribute name: reasonForChange (GML), reason_for_change (GeoPackage), Not provided (VectorTiles)
Type: ChangeValue
Size: 32
Multiplicity: [1]
Reference to the topographic representation(s) of the same part of the road.
Attribute name: reasonForChange (GML), reason_for_change (GeoPackage), Not provided (VectorTiles)
Size: 20
Multiplicity: [1..*]
A Street feature is the definition of the street as defined in the National or Scottish Street Gazetteer. A Street includes aggregated geometry. Where possible, the geometry of streets captured by a Roads or Highway Authority is spatially matched to the geometry of OS RoadLinks.
If any of the Street’s Elementary Street Unit(s) (ESUs) have been matched to a RoadLink(s) then the aggregated geometry of the RoadLink(s) will be provided.
If none of the Street’s ESUs have been matched to a RoadLink then the aggregated geometry of the ESUs will be provided.
The provenance of this geometry can be identified through the “geometryProvenance” attribute. They will represent either the complete Street or a section of a Street within an Administrative Unit, Town, or Locality and provides additional information about who is responsible for its naming and or numbering. A RoadLink can be referenced by multiple Street features.
The Street extends the Road to provide the additional attribution required to adhere to BS 7666:
USRN: The Unique Street Reference Number is the unique and persistent identifier of a Street assigned by the Roads or Highway Authority.
Street Type: The type of Gazetteer record for which the USRN relates. It is mandatory for all USRNs to be assigned a Street Type.
Operational State: indicates whether the Street is proposed, under construction, open, or closed (permanently or temporarily).
Responsible Authority: reference to the authority who performs an administrative function – notably naming and numbering.
A Street will split when it crosses the boundary of an Administrative Area where the local maintenance responsibility changes. A Street could also split at a town or locality boundary to allow properties to be located uniquely upon a street via a unique identifier (i.e. USRN).
In the definitions below, users should read the term Highways as Roads when applied to streets in Scotland.
Any road, footway, path, cycletrack, track or passageway that forms a highway. A highway represents individual subsections of Road which are managed (naming/numbering) by a specified responsible authority.
Constraints: A Street shall have at least one of designatedName (Type 1), descriptor (Type 2), nationalRoadCode (Type 3), localRoadCode (Type 3), or localName (Type 4). If a Street has a descriptor, it shall not have a designatedName. If geometryProvenance does not = "Ordnance Survey" then 'link' shall be null. If the roadClassification = "Motorway" or "A Road" or "B Road" then the nationalRoadCode shall not be null.
Unique identifier, for Street the characters “USRN” appended with the USRN e.g. USRN12345678
Attribute name: gml_id (GML), usrn (GeoPackage), usrn (VectorTiles)
Type: CharacterString
Size: 12
Multiplicity: [1]
Uniform Resource Identifier
Attribute name: identifier (GML), identifier (GeoPackage), Not provided (VectorTiles)
Type: CharacterString
Size: 29
Multiplicity: [1]
External object identifier of the spatial object. Note: This is the USRN from the NSG or TRSG or SSG.
Attribute name: inspireId
Type: Identifier
Multiplicity: [0..1]
Date and time at which this version of the spatial object was inserted or changed in the spatial data set. Note: The time part is always set to zero.
Attribute name: beginLifespanVersion
Type: DateTime
Multiplicity: [1]
The time when the transport link set started to exist in the real world. Note: The time part is always set to zero.
Attribute name: validFrom
Type: DateTime
Multiplicity: [1]
Identification code assigned to the road by the local road authority. Note: This is only used for classified unnumbered roads.
Attribute name: localRoadCode
Type: CharacterString
Size: 120
Multiplicity: [0..1]
The national number of the road.
Attribute name: nationalRoadCode
Type: CharacterString
Size: 10
Multiplicity: [0..1]
Official name assigned to the highway by the Street Naming Authority.
Attribute name: designatedName (GML), designated_name (GeoPackage), designated_name (VectorTiles)
Type: DesignatedNameType
Multiplicity: [0..2]
Unofficial local name associated to the highway. Note: Where a feature has more than one name, the language of each name is provided as a 3-digit ISO 639-2 code (‘eng’, ‘cym’, ‘gla’).
Attribute name: localName (GML), local_name (GeoPackage), Not provided (VectorTiles)
Type: LocalisedCharacterString
Size: 120
Multiplicity: [0..2]
Street description allocated by a Street Naming Authority or Highway Authority used to identify a street that does not have a designated name. Note: Where a feature has more than one name, the language of each name is provided as a 3-digit ISO 639-2 code (‘eng’, ‘cym’, ‘gla’).
Attribute name: descriptor (GML), descriptor (GeoPackage), Not provided (VectorTiles)
Type: LocalisedCharacterString
Size: 120
Multiplicity: [0..2]
The reason for a change made to a feature.
Attribute name: reasonForChange (GML), reason_for_change (GeoPackage), Not provided (VectorTiles)
Size: 32
Multiplicity: [1]
The national classification of the road.
Attribute name: roadClassification (GML), road_classification (GeoPackage), road_classification (VectorTiles)
Type: RoadClassificationValue
Size: 21
Multiplicity: [0..1]
Classification of the type of Street from the National Street Gazetteer.
Attribute name: streetType (GML), street_type (GeoPackage), street_type (VectorTiles)
Type: StreetTypeValue
Size: 35
Multiplicity: [1]
Indicator identifying the physical nature of the road e.g. Under Construction.
Attribute name: operationalState (GML), operational_state (GeoPackage), Not provided (VectorTiles)
Type: OperationalStateType
Multiplicity: [0..1]
The Populated Place representing the locality that the Street is located within. Note: Where a feature has more than one name, the language of each name is provided as a 3-digit ISO 639-2 code (‘eng’, ‘cym’, ‘gla’).
Attribute name: locality (GML), locality (GeoPackage), Not provided (VectorTiles)
Type: LocalisedCharacterString
Size: 35
Multiplicity: [0..2]
The settlement that the Street falls within. Note: Where a feature has more than one name, the language of each name is provided as a 3-digit ISO 639-2 code (‘eng’, ‘cym’, ‘gla’).
Attribute name: town (GML), town (GeoPackage), Not provided (VectorTiles)
Type: LocalisedCharacterString
Size: 30
Multiplicity: [0..2]
The administrative area that the Street is located within. Note: Where a feature has more than one name, the language of each name is provided as a 3-digit ISO 639-2 code (‘eng’, ‘cym’, ‘gla’).
Attribute name: administrativeArea (GML), administrative_area (GeoPackage), Not provided (VectorTiles)
Type: LocalisedCharacterString
Size: 30
Multiplicity: [1..2]
Reference to the authority that has current responsibility for naming and numbering.
Attribute name: responsibleAuthority (GML), responsible_authority (GeoPackage), responsible_authority (VectorTiles)
Type: ResponsibleAuthority
Multiplicity: [1]
Identify where the geometry of the feature originated.
Attribute name: geometryProvenance (GML), geometry_provenance (GeoPackage), Not provided (VectorTiles)
Type: ProvenanceSourceValue
Size: 23
Multiplicity: [1]
The aggregated geometry of either the matched RoadLinks or the Elementary Street Units.
Attribute name: geometry (GML), Not provided (GeoPackage), Not provided (VectorTiles)
Type: GM_MultiCurve
Multiplicity: [1]
A reference to the unique identifier of administrative areas managed by the Office for National Statistics. Role is used to describe the authority - 'Upper Tier Local Authority', 'Lower Tier Local Authority' and 'Unitary Local Authority'
Attribute name: gssCode (GML), gss_code (GeoPackage), Not provided (VectorTiles)
Size: 9
Multiplicity: [0..2]
The reference to the RoadLink features which builds up the Street feature. Where the Street has not been matched to a RoadLink this attribute will be voided.
Attribute name: link (GML), link (GeoPackage), Not provided (VectorTiles)
Size: 20
Multiplicity: [1..*]
A RoadJunction feature is a collection of RoadNode features that share the same road junction name or number. The collection of RoadNodes will include all RoadNodes that constitute part of a “slip road” or other link between two or more crossing road features. A RoadNode could be referenced by multiple RoadJuntion features.
Motorway Junctions will be populated completely, other junctions are being supplied as data is improved for future releases. Highlighted red for clarification only.
The context diagram below shows how the RoadJunction feature relates back to the Network Elements.
A compound feature that represents a road junction with a name or number.
Unique identifier, for RoadJunction this is a TOID
Attribute name: gml_id (GML), toid (GeoPackage), Not provided (VectorTiles)
Type: CharacterString
Size: 20
Multiplicity: [1]
Uniform Resource Identifier
Attribute name: identifier (GML), identifier (GeoPackage), Not provided (VectorTiles)
Type: CharacterString
Size: 37
Multiplicity: [1]
External object identifier of the spatial object.
Attribute name: inspireId
Type: Identifier
Multiplicity: [0..1]
Date and time at which this version of the spatial object was inserted or changed in the spatial data set. Note: The time part is always set to zero.
Attribute name: beginLifespanVersion (GML), begin_lifespan_version (GeoPackage), Not provided (VectorTiles)
Type: DateTime
Multiplicity: [1]
The reason for a change made to a feature.
Attribute name: reasonForChange (GML), reason_for_change (GeoPackage), Not provided (VectorTiles)
Type: ChangeValue
Size: 32
Multiplicity: [1]
A classification for the Road Junction.
Attribute name: junctionType (GML), junction_type (GeoPackage), Not provided (VectorTiles)
Type: JunctionTypeValue
Size: 26
Multiplicity: [1]
The name of the junction. For numbered junctions, this will provide a description of the junction, for example, M6 Junction 6. Note: Where a feature has more than one name, the language of each name is provided as a 3-digit ISO 639-2 code (‘eng’, ‘cym’, ‘gla’).
Attribute name: junctionName (GML), junction_name (GeoPackage), Not provided (VectorTiles)
Type: LocalisedCharacterString
Size: 120
Multiplicity: [1..2]
The official road number assigned by the appropriate authority. For example, M6.
Attribute name: roadClassificationNumber (GML), road_classiffication_number (GeoPackage), Not provided (VectorTiles)
Type: CharacterString
Size: 5
Multiplicity: [0..1]
The number of the junction. For example, 6.
Attribute name:junctionNumber (GML), junction_number (GeoPackage), Not provided (VectorTiles)
Type: CharacterString
Size: 3
Multiplicity: [0..1]
The reference to the RoadNode features which builds up the RoadJunction feature.
Attribute name: node (GML), node (GeoPackage), Not provided (VectorTiles)
Size: 20
Multiplicity: [1..*]
A Road feature is a link set which represents a collection of RoadLink features used primarily by motorised vehicles that share the same name (e.g. Bilston Road) or classification number (e.g. A41). A Road will reference the complete collection of RoadLink features irrespective of which authority boundary it falls within. The feature will include Motorways, A Roads, B Roads and Named Thoroughfares (roads), as illustrated above.
The link set may not be contiguous across junctions or where a classified road consists of separate sections, which may be separated by some considerable distance. In addition, the same RoadLink feature may be referenced by multiple Road features.
The context diagram shows how the Road has been inherited from INSPIRE and the attribution held on the Road.
A compound feature that represents a road with a name or number. This may be a classified road, such as the A38, or a named road such as Romsey Road. This references a collection of RoadLinks.
Constraints: If the roadClassification = "Motorway" or "A Road" or "B Road" then the nationalRoadCode shall not be null.
Unique identifier, for Road this is a TOID
Attribute name: gml_id (GML), toid (GeoPackage), Not provided (VectorTiles)
Type: CharacterString
Size: 20
Multiplicity: [1]
Uniform Resource Identifier
Attribute name: identifier (GML), identifier (GeoPackage), Not provided (VectorTiles)
Type: CharacterString
Size: 37
Multiplicity: [1]
External object identifier of the spatial object.
Attribute name: inspireId
Type: Identifier
Multiplicity: [0..1]
Date and time at which this version of the spatial object was inserted or changed in the spatial data set. Note: The time part is always set to zero.
Attribute name: beginLifespanVersion
Type: DateTime
Multiplicity: [1]
The time when the transport link set started to exist in the real world. Note: The time part is always set to zero.
Attribute name: validFrom
Type: DateTime
Multiplicity: [1]
Identification code assigned to the road by the local road authority.
Attribute name: localRoadCode
Type: CharacterString
Size: 10
Multiplicity: [0..1]
The national number of the road.
Attribute name: nationalRoadCode
Type: CharacterString
Size: 10
Multiplicity: [0..1]
The national classification of the road.
Attribute name: roadClassification (GML), road_classification (GeoPackage), road_classification (VectorTiles)
Type: RoadClassificationValue
Size: 21
Multiplicity: [0..1]
Official name assigned to the highway by a designated Street Naming Authority. Note: On the Road feature this will always be the OS name.
Attribute name: designatedName (GML), designated_name (GeoPackage), Not provided (VectorTiles)
Type: DesignatedNameType
Multiplicity: [0..2]
The reason for a change made to a feature.
Attribute name: reasonForChange (GML), reason_for_change (GeoPackage), Not provided (VectorTiles)
Type: ChangeValue
Size: 32
Multiplicity: [1]
The reference to the RoadLink features which builds up the Road feature.
Attribute name: link
Size: 20
Multiplicity: [1..*]
A RoadLink is a linear spatial object that defines the geometry and connectivity of a road network between two points in the network. Road links can represent single carriageways, dual carriageways, slip roads, roundabouts and indicative trajectories across traffic squares. RoadLinks will be split for connectivity purposes (for example at junctions) and RoadNodes will connect the RoadLinks together. Each RoadLink will provide a reference to the RoadNodes at the start and end of the RoadLink.
RoadLinks will split where two links cross over or under one another when there is no connectivity, for example at bridges and flyovers. Therefore, the attributes “startGradeSeparation” and “endGradeSeparation” have been populated on the RoadLink. The Grade Separation attribute will indicate where there is or is not a physical connection between the roads in the real world. Grade Separation will determine if a RoadLink is above another; if the two RoadLinks, when referencing the same RoadNode, have different values then it is not possible to move between them at that point.
Where a RoadLink crosses a PathLink at a different level, both the RoadLink and PathLink will split. The attributes “startGradeSeparation” and “endGradeSeparation” will be populated on the RoadLink and PathLink. The Grade Separation attribute will indicate where there is or is not a physical connection between the road and path in the real world. Where the two links cross, the Road Node and Path Node will have the same identifier. Grade Separation will determine if one link is above another. If the two links, when referencing a Road Node and Path Node with the same TOID, have different grade separation values then it is not possible to move between them at that point.
The context diagram shows how the RoadLink has been inherited from INSPIRE and the attribution held on the RoadLink.
A feature that represents a part or all of a highway.
Constraints: If the roadClassification is either Motorway, A Road or B Road then roadClassificationNumber shall not be null.
Unique identifier, for RoadLink this is a TOID
Attribute name: gml_id (GML), toid (GeoPackage), toid (VectorTiles)
Type: CharacterString
Size: 20
Multiplicity: [1]
Uniform Resource Identifier
Attribute name: identifier (GML), identifier (GeoPackage), Not provided (VectorTiles)
Type: CharacterString
Size: 37
Multiplicity: [1]
External object identifier of the spatial object.
Attribute name: inspireId
Type: Identifier
Multiplicity: [0..1]
Date and time at which this version of the spatial object was inserted or changed in the spatial data set. Note: The time part is always set to zero.
Attribute name: beginLifespanVersion
Type: DateTime
Multiplicity: [1]
The three-dimensional geometry that represents the alignment of the section of road.
Attribute name: centrelineGeometry
Type: GM_Curve
Multiplicity: [1]
Indicator that the centreline geometry of the link is a straight line with no intermediate control points – unless the straight line represents the geography in the resolution of the data set appropriately.
Attribute name: fictitious
Type: Boolean
Size: 5
Multiplicity: [1]
The time when the transport link started to exist in the real world. Note: The time part is always set to zero.
Attribute name: validFrom
Type: DateTime
Multiplicity: [1]
The reason for a change made to a feature.
Attribute name: reasonForChange (GML), reason_for_change (GeoPackage), Not provided (VectorTiles)
Type: ChangeValue
Size: 32
Multiplicity: [1]
The official designated importance of a road that provides an indication of its expected usage and importance.
Attribute name: roadClassification (GML), road_classification (GeoPackage), road_classification (VectorTiles)
Type: RoadClassificationValue
Size: 21
Multiplicity: [1]
A classification of the road designed to give the most appropriate route.
Attribute name: routeHierarchy (GML), route_hierarchy (GeoPackage), route_hierarchy (VectorTiles)
Type: RoadFunctionValue
Size: 32
Multiplicity: [1]
A description of the road based on its nature or use.
Attribute name: formOfWay (GML), form_of_way (GeoPackage), form_of_way (VectorTiles)
Type: FormOfWayTypeValue
Size: 42
Multiplicity: [1]
States if the RoadLink forms part of the Trunk Road network
Attribute name: trunkRoad (GML), trunk_road (GeoPackage), trunk_road (VectorTiles)
Type: Boolean
Size: 5
Multiplicity: [1]
States if the RoadLink forms part of the Primary Route network
Attribute name: primaryRoute (GML), primary_route (GeoPackage), primary_route (VectorTiles)
Type: Boolean
Size: 5
Multiplicity: [1]
The official road number assigned by the appropriate authority. Note that this includes at least one letter. For example, ‘A329(M)’
Attribute name: roadClassificationNumber (GML), road_classification_number (GeoPackage), road_classification_number (VectorTiles)
Type: CharacterString
Size: 10
Multiplicity: [0..1]
The name of the road the feature is part of. When a RoadLink is referenced by a Street with a streetStateType of Designated Street Name this is the name used else the name is from Road. Note: Where a feature has more than one name, the language of each name is provided as a 3-digit ISO 639-2 code (‘eng’, ‘cym’, ‘gla’).
Attribute name: roadName (GML), road_name (GeoPackage), road_name (VectorTiles)
Type: LocalisedCharacterString
Size: 255
Multiplicity: [0..2]
Another name for the road the feature is part of, this is populated with the name captured by Ordnance Survey when it differs from that in Street. Note: Where a feature has more than one name, the language of each name is provided as a 3-digit ISO 639-2 code (‘eng’, ‘cym’, ‘gla’).
Attribute name: alternateName (GML), alternate_name (GeoPackage), alternate_name (VectorTiles)
Type: LocalisedCharacterString
Size: 255
Multiplicity: [0..2]
Indicator identifying the construction status of the road
Attribute name: operationalState (GML), operational_state (GeoPackage), Not provided (VectorTiles)
Type: OperationalStateValue
Size: 19
Multiplicity: [1]
The origin and derivation of the three-dimensional geometry of the RoadLink.
Attribute name: provenance (GML), provenance (GeoPackage), Not provided (VectorTiles)
Type: ProvenanceSourceValue
Size: 23
Multiplicity: [1]
Indication of the direction of traffic flow. The directionality indicates the direction of traffic flow in relation to the direction of digitisation. A road node that is ‘in direction’ means that the traffic moves from start to end node, but ‘against direction’ means the traffic moves from end node to start node. The start and end nodes indicate the direction of digitisation.
Attribute name: directionality (GML), directionality (GeoPackage), Not provided (VectorTiles)
Type: LinkDirectionValue
Size: 21
Multiplicity: [1]
The calculated two-dimensional length of the RoadLink in metres. Note: A Unit of Measure (uom) is provided as part of the attribute which will always be ‘m’.
Attribute name: length (GML), length (GeoPackage), Not provided (VectorTiles)
Type: Measure
Size: 7,2
Multiplicity: [1]
Indicates whether the feature has been matched to a feature in the NSG.
Attribute name: matchStatus(GML), match_status(GeoPackage), Not provided (VectorTiles)
Type: MatchStatusValue
Size: 39
Multiplicity: [1]
Identifier(s) of the Elementary Street Unit from NSG or TRSG.
Attribute name: alternateIdentifier(GML), alternate_identifier(GeoPackage), Not provided (VectorTiles)
Type: ThematicIdentifier
Size: 20
Multiplicity: [0..*]
The relative level of the link at the startNode.
Attribute name: startGradeSeparation (GML), start_grade_separation (GeoPackage), Not provided (VectorTiles)
Type: Integer
Multiplicity: [1]
The relative level of the link at the endNode.
Attribute name: endGradeSeparation (GML), end_grade_separation (GeoPackage), Not provided (VectorTiles)
Type: Integer
Multiplicity: [1]
Identifies if this section of road passes through or over a physical structure.
Attribute name: roadStructure (GML), roadStructure (GeoPackage), road_structure (VectorTiles)
Type: RoadStructureValue
Size: 14
Multiplicity: [0..1]
Identifies if the RoadLink has facilities for a cyclist.
Attribute name: cycleFacility(GML), cycle_facility (GeoPackage), cycle_facility (VectorTiles)
Type: CycleFacilityType
Multiplicity: [0..1]
An indication of the width of the road carriageway as recorded in the OS MasterMap Topography layer, this must not be used to identify whether individual vehicles can use a route.
Attribute name: roadWidthAverage (GML), road_width_average (GeoPackage), road_width_average (VectorTiles)
Type: RoadWidthType
Multiplicity: [0..1]
The elevation gain is calculated from three-dimensional geometry to define the total ascent experienced when passing along a RoadLink feature. The value is expressed both with and against the coordinate order.
Attribute name: elevationGainInDirection (GML), elevationGainInOppositeDirection (GML), elevation_gain_in_direction (GeoPackage), elevation_gain_in_opposite_direction (GeoPackage), Not provided (VectorTiles), Not provided (VectorTiles)
Type: ElevationGainType
Multiplicity: [0..1]
Identifier of the Road or Street to which the RoadLink forms part of.
Attribute name: formsPartOf (GML), forms_part_of (GeoPackage), Not provided (VectorTiles)
Multiplicity: 0..*
Size: 20
The node coincident with the first vertex of the geometry attribute.
Attribute name: startNode
Multiplicity: 0..1
Size: 20
The node coincident with the last vertex of the geometry attribute.
Attribute name: endNode
Multiplicity: 0..1
Size: 20
Reference to the topographic representation(s) of the same part of the road.
Attribute name: relatedRoadArea (GML), related_road_area (GeoPackage), Not provided (VectorTiles)
Multiplicity: 1..*
Size: 20
This section describes the structured data types which make up OS MasterMap Highways Network - Roads. The attributes associated with these data types are listed below along with a brief description of their data properties.
A FerryLink is a linear spatial object which represents the connectivity of a vehicular ferry route across a body of water. A FerryLink will only be captured where both terminals are within Great Britain, and there is a timetabled service which is available to the public. Ferry routes with a terminal outside of Great Britain are not captured, for example Dover to Calais, or where the service is not available to the public.
The context diagram shows how the FerryLink has been inherited from INSPIRE, the attribution held on the FerryLink and how it relates to the other Ferry components.
A network link representing a route for a vehicular or pedestrian ferry route.
Unique identifier, for FerryLink this is a TOID
Attribute name: gml_id (GML), toid (GeoPackage), toid (VectorTiles)
Type: CharacterString
Size: 20
Multiplicity: [1]
Uniform Resource Identifier
Attribute name: identifier (GML), identifier (GeoPackage), Not provided (VectorTiles)
Type: CharacterString
Size: 37
Multiplicity: [1]
External object identifier of the spatial object.
Attribute name: inspireId
Type: Identifier
Multiplicity: [1]
Date and time at which this version of the spatial object was inserted or changed in the spatial data set. Note: The time part is always set to zero.
Attribute name: beginLifespanVersion (GML), begin_lifespan_version (GeoPackage), Not provided (VectorTiles)
Type: DateTime
Multiplicity: [1]
The three-dimensional geometry that represents the connection between the ferry terminals. Where a detailed alignment is provided it is only an indication of the route a vessel would take. The third dimension is only provided for connectivity and does not reflect any real-world value.
Attribute name: centrelineGeometry
Type: GM_Curve
Multiplicity: [1]
Indicator that the centreline geometry of the link is a straight line with no intermediate control points – unless the straight line represents the geography in the resolution of the data set appropriately.
Attribute name: fictitious
Type: Boolean
Size: 5
Multiplicity: [1]
The time when the transport node started to exist in the real world. Note: The time part is always set to zero.
Attribute name: validFrom
Type: DateTime
Multiplicity: [1]
An indicator if this FerryLink represents a ferry that can be used by vehicles.
Attribute name: vehicularFerry (GML), vehicular_ferry (GeoPackage), vehicula_ferry (VectorTiles)
Type: Boolean
Size: 5
Multiplicity: [1]
The URL of the operator of this Ferry route.
Attribute name: vehicularFerry (GML), vehicular_ferry (GeoPackage), vehicula_ferry (VectorTiles)
Type: CharacterString
Size: 250
Multiplicity: [0..1]
The reason for a change made to a feature.
Attribute name: reasonForChange (GML), reason_for_change (GeoPackage), Not provided (VectorTiles)
Type: ChangeValue
Size: 32
Multiplicity: [1]
The node coincident with the first vertex of the geometry attribute.
Attribute name: startNode (GML), start_node (GeoPackage), Not provided (VectorTiles)
Size: 20
Multiplicity: [0..1]
The node coincident with the last vertex of the geometry attribute.
Attribute name: startNode (GML), start_node (GeoPackage), Not provided (VectorTiles)
Size: 20
Multiplicity: [0..1]
A FerryNode is a point spatial object which is used to represent the connectivity where the FerryLink features start and end. A FerryNode feature may serve multiple FerryLink features if more than one destination is served from the same location. FerryNodes will always be referenced by at least one FerryLink.
The context diagram above shows how the FerryNode has been inherited from INSPIRE, the attribution held on the FerryNode and how it relates to the other Ferry components.
A feature representing the point at which a vehicular or pedestrian ferry route or section of ferry route starts or ends.
Unique identifier, for FerryNode this is a TOID
Attribute name: gml_id (GML), toid (GeoPackage), toid (Vector Tiles)
Type: CharacterString
Size: 20
Multiplicity: [1]
Uniform Resource Identifier
Attribute name: identifier (GML), identifier (GeoPackage), Not provided (Vector Tiles)
Type: CharacterString
Size: 37
Multiplicity: [1]
External object identifier of the spatial object.
Attribute name: inspireId INSPIRE
Type: Identifier
Multiplicity: [0..1]
Date and time at which this version of the spatial object was inserted or changed in the spatial data set.
The time part is always set to zero.
Attribute name: beginLifespanVersion (GML), begin_lifespan_version (GeoPackage), Not provided (VectorTiles)
Type: DateTime
Multiplicity: [1]
The location of the node.
Attribute name: geometry (GML), Not provided (GeoPackage), Not provided (Vector Tiles)
Type: GM_Point
Multiplicity: [1]
The time when the transport node started to exist in the real world.
The time part is always set to zero.
Attribute name: validFrom (GML), valid_from (GeoPackage), Not provided (Vector Tiles)
Type: DateTime
Multiplicity: [1]
Description of the function of a waterway node in the water transport network.
Attribute name: formOfWaterwayNode (GML), form_of_waterway_node (GeoPackage), form_of_waterway_node (VectorTiles)
Type: FormOfWaterwayNodeValue
Size: 14
Multiplicity: [1]
The reason for a change made to a feature.
Attribute name: reasonForChange (GML), reason_for_change (GeoPackage), Not provided (VectorTiles)
Type: ChangeValue
Size: 32
Multiplicity: [1]
The ferry and road network elements are linked together through a FerryTerminal feature. A FerryTerminal is a logical connection between the two networks and therefore there is no geometry supplied with these features. They will reference one RoadNode and one FerryNode. The FerryTerminals will also provide a reference to the OS MasterMap Site feature.
The context diagram above shows how the FerryTerminal has been inherited from INSPIRE, the attribution held on the FerryTerminal and how it relates to the other Ferry components.
A logical connection between a PathNode or RoadNode and the FerryNode. It represents the connection between the Road or Path network and the Ferry network.
Unique identifier, for FerryTerminal this is a TOID
Attribute name: gml_id (GML), toid (GeoPackage), Not provided (VectorTiles)
Type: CharacterString
Size: 20
Multiplicity: [1]
Uniform Resource Identifier
Attribute name: identifier (GML), identifier (GeoPackage), Not provided (VectorTiles)
Type: CharacterString
Size: 37
Multiplicity: [1]
External object identifier of the spatial object.
Attribute name: inspireId
Type: Identifier
Multiplicity: [0..1]
Date and time at which this version of the spatial object was inserted or changed in the spatial data set.
The time part is always set to zero.
Attribute name: beginLifespanVersion (GML), begin_lifespan_version (GeoPackage), Not provided (VectorTiles)
Type: DateTime
Multiplicity: [1]
Categorisation of the network connection.
Attribute name: type (GML), type (GeoPackage), Not provided (VectorTiles)
Type: ConnectionTypeValue
Size: 10
Multiplicity: [1]
The name of the Ferry Terminal. Note: Where a feature has more than one name, the language of each name is provided as a 3-digit ISO 639-2 code (‘eng’, ‘cym’, ‘gla’).
Attribute name: ferryTerminalName (GML), ferry_terminal_name (GeoPackage), ferry_terminal_name (VectorTiles)
Type: LocalisedCharacterString
Size: 120
Multiplicity: [0..2]
The recognised NaPTAN code of the Ferry Terminal.
Attribute name: ferryTerminalCode (GML), ferry_terminal_code (GeoPackage), ferry_terminal_code (VectorTiles)
Type: CharacterString
Size: 10
Multiplicity: [0..1]
The reason for a change made to a feature.
Attribute name: reasonForChange (GML), reason_for_change (GeoPackage), Not provided (VectorTiles)
Type: ChangeValue
Size: 32
Multiplicity: [1]
Reference to the Site representation of the Ferry Terminal in OS MasterMap Sites Layer.
Association: refToFunctionalSite (GML), ref_to_functional_site (GeoPackage), Not provided (VectorTiles)
Size: 20
Multiplicity: [0..1]
The reference to the RoadNode or PathNode and the FerryNode. The type of node the element is referencing will be identified through the xlink:title.
Aggregation: elementId (GML), element_id (GeoPackage), Not provided (VectorTiles)
Size: 20
Multiplicity: [2..*]
A code list or enumeration is a controlled set of values which can be used to populate a specific column.
RoadLink, Road and Street are attributed with a “designatedName” with a data type of “DesignatedNameType”. The attribution of this data type is detailed below.
The name assigned to the road or street by a designated Street Naming Authority.
Official name assigned to the highway by a designated Street Naming Authority. Note: Where a feature has more than one name, the language of each name is provided as a 3-digit ISO 639-2 code (‘eng’, ‘cym’, ‘gla’).
Attribute name: name
Type: LocalisedCharacterString
Size: 255
Multiplicity: [1]
The local authority that assigned the designatedName.
Attribute name: namingAuthority
Type: ResponsibleAuthority
Multiplicity: [1]
RoadLink and Street are attributed with “designatedName” and Street is attributed with a “responsibleAuthority” with a data type of “ResponsibleAuthority”. The attribution of this data type is detailed below.
The authority responsible for the street naming and numbering or maintenance.
The code used to identify the authority. Example: 0114
Attribute name: identifier
Type: CharacterString
Size: 4
Multiplicity: [1]
Official name of the authority. Example: Bath and North East Somerset
Attribute name: authorityName
Type: CharacterString
Size: 100
Multiplicity: [1]
A RoadLink could be attributed with “cycleFacility” with a data type of “CycleFacilityType”. The attribution of this data type is detailed below.
The cycle amenity available along the link.
Attribute name: cycleFacility
Type: CycleFacilityValue
Size: 45
Multiplicity: [1]
Identifies if the facility applies to entirety of the link.
Attribute name: wholeLink
Type: Boolean
Size: 5
Multiplicity: [1]
A RoadLink could be attributed with “roadWidth” with a data type of “RoadWidthType”. The attribution of this data type is detailed below. This value is based upon the Topographic Area features supplied in OS MasterMap Topography Layer and must not be used to indicate if a vehicle of a specific width can use a particular section of road.
The average width of the road carriageway.
Attribute name: averageWidth
Type: Measure
Multiplicity: [1]
The minimum width of the topographic area feature the RoadLink is representing.
Attribute name: minimumWidth
Type: Measure
Multiplicity: [0..1]
Records the original capture specification for the OS MasterMap Topography layer feature used to indicate the width of the carriageway. This provides an indication of the confidence that can be placed in the value provided.
Attribute name: confidenceLevel
Type: RoadWidthConfidenceLevelValue
Size: 27
Multiplicity: [1]
Total increase in height experienced when passing along the link from the start to the end.
Attribute name: inDirection
Type: Measure
Multiplicity: [1]
Total increase in height experienced when passing along the link from the end to the start.
Attribute name: inOppositeDirection
Type: Measure
Multiplicity: [1]
Road classification is used by government to ensure that there is a feasible, logical road network throughout the country. Road classifications are set to take into account the traffic management goals and road categorisation approach of the Local Highway Authority (LHA) in England and Wales. Currently, in Scotland only Motorway A Road and B Road classifications are provided.
RoadLink, Road and Street features are attributed with a “roadClassification” with a data type of “RoadClassificationValue”. The table below describes the codes which will be used to populate this field and the description for each code.
| Code | Description |
|---|---|
| Code | Description |
|---|
Matched
The RoadLink has been matched with an Elementary Street Unit from the NSG.
No Match
The RoadLink has not been matched with an Elementary Street Unit from the NSG which has been accepted.
Not Matched Awaiting Review
The RoadLink has not been matched with an Elementary Street Unit from the NSG and is waiting to be manually reviewed to identify if there is an Elementary Street Unit it should have been matched too.
Matched With Attribute Discrepancy
The RoadLink has been matched with an Elementary Street Unit from the NSG and there is a discrepancy between the attribution supplied by the NSG and information from OS.
Unclassified | Roads intended for local traffic. NOTE 1: These may be designated Unofficial local road classifications. For example: D, E, F and G roads. |
Not Classified | Roads that have not been assigned a road classification at national or local level by a designation authority. |
Unknown | The classification of the road is unknown because the RoadLink is not a Motorway, A or B road and the RoadLink has not been matched to the National Street Gazetteer. |
RoadLink is attributed with "operationalState" with a data type of "OperationslStateValue" and Street is attributed with an “operationalState” with a data type of “OperationalStateType”. This data type has the attribute of ‘state’ with a data type of “OperationalStateValue”. The table below describes the codes which will be used to populate attributes with the data type “OperationalStateValue”.
The RoadLink feature is attributed with a “routeHierarchy” with a data type of “RoadFunctionValue”. The table below describes the codes used to populate this field and the description for each code. In addition, INSPIRE provides an attribute “Functional Road Class” which identifies the importance of the role that the road performs in the road network. Therefore, these values have been mapped to the INSPIRE values.
| Code | Description |
|---|---|
| Code | Description | Functional Road Class |
|---|---|---|
| Code | Description |
|---|---|
| Code | Description |
|---|
Prospective
Plans have been submitted for development, but construction has not commenced.
Under Construction
Construction has commenced but the road cannot be used.
Open
Open
Temporarily Closed
The way has been temporarily closed for a specified reason under Road Traffic Regulation Act 1984 Section 14 1(b): • Strewetworks; • likelihood of danger to public; and • Litter clearing or cleaning (duty imposed by section 89(1)(a) or (2) of the Environmental Protection Act 1990 (litter clearing and cleaning) to be discharged). Note: The operationalState shall only be set to Temporarily Closed when the duration of the closure is intended to last more than 4 weeks.
Permanently Closed
A Street that has been permanently blocked up according to a Stopping Up Order Constraint: If the Street operationalState = Permanently Closed then the endLifespanVersion shall be set.
Addressing Only
A street which has been created for addressing purposes of the Local Land and Property Gazetteer (LLPG).
Motorway
A multi-carriageway public road connecting important cities.
mainRoad
A Road Primary
A major road intended to provide the principal link between the most significant destinations in the country, as defined by the DfT, and that is currently classified by the DfT as an A Road.
firstClass
A Road
A major road intended to provide large-scale transport links within or between areas.
secondClass
B Road Primary
A major road intended to provide the principal link between the most significant destinations in the country, as defined by the DfT, and that is currently classified by the DfT as a B Road.
firstClass
B Road
A road intended to connect different areas, and to feed traffic between A roads and smaller roads on the network.
thirdClass
Minor Road
A public road that provides interconnectivity to higher classified roads or leads to a point of interest.
fourthClass
Local Road
A public road that provides access to land and/or houses, usually named with addresses. Generally, not intended for through traffic.
fifthClass
Local Access Road
A road intended for the start or end of a journey, not intended for through traffic but will be openly accessible.
sixthClass
Restricted Local Access Road
A road intended for the start or end of a journey, not intended for through traffic and will have a restriction on who can use it.
seventhClass
Secondary Access Road
A road that provides alternate/secondary access to property or land not intended for through traffic.
ninthClass
Restricted Secondary Access Road
A road that provides alternate/secondary access to property or land, not intended for through traffic and will have a restriction on who can use it.
ninthClass
New
New feature has been added.
Modified Geometry
The geometry of the feature has been altered.
Modified Attributes
One or more attribute properties have been altered.
Modified Geometry And Attributes
Geometry and attribution properties have been altered.
End of Life
The feature has been removed from Ordnance Surveys master database. This value will only be used with Change Only Update orders.
Highways England | The source for the geometry of the feature is Highways England. |
Local Highway Authority | The source for the geometry of the feature is Local Highways Authority. |
Ordnance Survey | The source for the geometry of the feature is Ordnance Survey. |
Transport Scotland | The source for the geometry of the feature is Transport Scotland. |
Welsh Government | The source for the geometry of the feature is Welsh Government. |
OS Urban And OS Height | Data captured to 0.5m planimetric accuracy and elevation obtained from drape of OS detailed height content. |
OS Rural And OS Height | Data captured to 1.1 planimetric accuracy and elevation obtained from drape of OS detailed height content. |
OS Moorland And OS Height | Data captured to 4.1m planimetric accuracy and elevation obtained from drape of OS detailed height content. |
OS Urban And Interpolated OS Height | Data captured to 0.5m planimetric accuracy and elevation interpolated from OS detailed height content and other OS data. |
OS Rural And Interpolated OS Height | Data captured to 1.1m planimetric accuracy and elevation interpolated from OS detailed height content and other OS data. |
OS Moorland And Interpolated OS Height | Data captured to 4.1m planimetric accuracy and elevation interpolated from OS detailed height content and other OS data. |
OS Urban And Low Confidence OS Height | Data captured to 0.5m planimetric accuracy, elevation obtained from drape of OS detailed height content but expected to be low quality. |
OS Rural And Low Confidence OS Height | Data captured to 1.1m planimetric accuracy, elevation obtained from drape of OS detailed height content but expected to be low quality. |
OS Moorland And Low Confidence OS Height | Data captured to 4.1m planimetric accuracy, elevation obtained from drape of OS detailed height content but expected to be low quality. |
The RoadLink feature is attributed with a “directionality” property and the “NumberOfLanesType” data type has “direction” with the data type of LinkDirectionValue. The following table describes the codes used to populate this field.
The code list has been inherited from INSPIRE and is not extendable.
List of values for directions relative to a link
| Code | Description |
|---|
| Code | Description |
|---|
both directions | In both directions. |
In direction | In direction of the link. |
In opposite direction | In the opposite direction of the link. |
Single Carriageway | A road consisting of one carriageway with traffic in one or both directions. There may be more than one lane in any particular direction. |
Dual Carriageway | A road consisting of two separate carriageways with separate flow directions. The carriageways are partitioned by physical features, such as a barrier and/or verge. |
Slip Road | A road that provides exit from or entry to another road. |
Roundabout | A method of controlling traffic flow by allowing vehicles from a particular direction priority. |
Service Road | Road running parallel to and connecting to a road with a relatively high connectivity function, which is especially designed to enable access from the connecting roads to roads with a low connectivity function in its vicinity. |
Enclosed Traffic Area | Area with no internal structure of legally defined driving directions. At least two roads are connected to the area, for example, a car park. |
Traffic Island Link At Junction | Where an island that is over 8m² exists in the middle of a road on the approaches to a junction, the road link is split around it. |
Traffic Island Link | Where an island that is over 8m² exists in the middle of a road, the road link is split around it. |
Entrance Way | Link that provides entry to a site (e.g. Car Park, Hospital, Police Station or Ambulance Station). |
Entrance Or Exit Way | Link that provides access in both directions (entry and exit) to a site (e.g. Car Park, Hospital, Police Station, or Ambulance Station). |
Exit Way | Link that provides exit from a site (e.g. Car Park, Hospital, Police Station or Ambulance Station). |
Layby | An area at the side of the road where vehicles can stop on an ad hoc basis usually for a short time. |
Track | An unmade way for a vehicle. |
Guided Busway | A specially constructed or modified route for passenger road vehicles that have been built or adapted to be steered by external means. Typically, along guided busways, a raised kerb acts upon small wheels protruding from the sides of the modified vehicle. This classification is only for the specific cases where buses run along specifically designed tracks or channels that remove the need for steering. |
Shared Use Carriageway | Roads that have been altered for use principally by pedestrians but may provide some access for certain types of vehicle. |
The “CycleFacilityType” data type is attributed with a “cycleFacility” property with the data type of “CycleFacilityValue”. The following table describes the codes used to populate this field.
This value is provided from the National Street Gazetteer. Currently only “Unknown Type Of Cycle Route Along Road” is available for population. The other values are for future use.
| Code | Description |
|---|---|
| Code | Description |
|---|---|
| Code | Description |
|---|---|
| Code | Description |
|---|---|
Road In Tunnel
A road which passes underground or water.
Road On Bridge
A road that passes over a river, railway, road or ravine on a structure.
Not Currently used.
Advisory Cycle Lane Along Road
A cycle way along a road carriageway where motorised vehicles are allowed to drive or park. Does not require a Traffic Regulation Order.
Normally indicated by road markings consisting of a broken line.
Mandatory Cycle Lane Along Road
A cycle way along a road carriageway where motorised vehicles are prohibited from driving or parking. Requires a Traffic Regulation Order to prohibit the use by vehicles.
Normally indicated by road markings consisting of a solid line.
Physically Segregated Cycle Lane Along Road
A cycle way along a road carriageway that has been physically separated by kerbs, posts, barriers or similar.
Unknown Type Of Cycle Route Along Road
A cycle way along a road carriageway where the detailed nature is not known.
Signed Cycle Route
A route identified for cyclists along roads that is signed but does not have any significant infrastructure along the road such as road markings or kerbs.
For example, Sustrans routes along quiet roads.
OS Urban And Full Extent
Data captured to 0.5m planimetric accuracy and entire link within relevant Topographic Area.
OS Rural And Full Extent
Data captured to 1.1m planimetric accuracy and entire link within relevant Topographic Area.
OS Moorland And Full Extent
Data captured to 4.1m planimetric accuracy and entire link within relevant Topographic Area.
OS Urban And Part Extent
Data captured to 0.5m planimetric accuracy and part of link not within relevant Topographic Area.
enclosed traffic area
The road node is situated inside and/or represents an enclosed traffic area.
A traffic area is an area with no internal structure of legally defined driving directions. At least two roads are connected to the area.
Junction
Three or more road links intersect at the road node.
level crossing
A railway crosses a road on the same level at the position of the road node.
pseudo node
Exactly two road links connect to the road node.
road end
Only one road link connects to the road node. It signifies the end of a road.
roundabout
The road node represents or is a part of a roundabout.
traffic square
The road node is situated inside and/or represents a traffic square.
A traffic square is an area (partly) enclosed by roads which is used for non- traffic purposes and which is not a roundabout.
road service area
Surface annexed to a road and devoted to offer particular services for it.
The RoadNode feature is attributed with a “classification” property with the data type of RoadNodeClassificationValue. The following table describes the codes used to populate this field.
It is possible for a RoadNode to have more than one RoadNodeClassificationValue, in these rare instances, the highest value in the table below is applied.
Additional classification of the road node.
For example, if a node represents a roundabout it may also be classified as a mini roundabout.
Code
Description
Grade Separation
A RoadNode which represents where there is a difference in physical level of either two RoadLinks, or a RoadLink and a PathLink, and in the real world they do not meet and split here.
Mini Roundabout
A road junction where the effects of a roundabout on traffic flow are recreated by use of a delineated circular area of road markings or surface changes.
Motorway Junction
A named intersection where a vehicle gains access or exits the motorway.
The RoadNode feature is attributed with an “access” property with the data type AccessPointValue. The following table describes the codes used to populate this field.
Not currently populated.
| Code | Description |
|---|
Entry | The junction facilitates entry onto the adjoining link. |
Exit | The junction facilitates exit from the link. |
| Value | Description |
|---|---|
Named Junction
A Road Junction that is officially named. For example, Gravelly Hill.
Numbered Motorway Junction
A Road Junction that is part of a Road classified as Motorway.
Numbered A Road Junction
A Road Junction that is part of a Road classified as A Road.
The FerryTerminal feature is attributed with a “type” property with the data type of ConnectionTypeValue. The following table describes the codes used to populate this field.
The code list has been inherited from INSPIRE and is not extendable.
Types of connections between different networks.
| Code | Description |
|---|---|
| Code | Description |
|---|---|
Designated Street Name
Officially named street
Officially Described Street
Officially Described Street
Numbered Street
Officially numbered street
Unofficial Street Name
Unofficial local name for a street
intermodal
Connection between two network elements in different transport networks that use a different transport mode. The connection represents a possibility for the transported media (people, goods, etc) to change from one transport mode to another.
The FerryNode feature is attributed with a “formOfWaterwayNode” property with the data type of FormOfWaterwayNode Value. The following table describes the codes used to populate this field.
The code list has been inherited from INSPIRE and is not extendable.
Function of a Waterway Node in the water transport network.
| Code | Description |
|---|---|
water terminal
The location where goods are transhipped.
This section describes how OS MasterMap Highways Network is defined in GML. An understanding of XML (Extensible Mark-up Language) and XML schema is required.
GML is an XML 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 define and validate the format and content of GML. The GML 3.2 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 Road Network uses the following application schemas; LinearHighwayNetwork.xsd, HighwaysWaterTransportNetwork.xsd and OSProducts.xsd which are referenced by the data. The LinearHighwaysNetwork.xsd defines the features which make up the Road Network. Therefore, it imports the INSPIRE transport network road application schema. The HighwaysWaterTransportNetwork.xsd defines the features which make up the Ferry Network. Therefore, it imports the INSPIRE transport network water application schema. Through the INSPIRE schemas both the LinearHighwayNetwork.xsd and HighwaysWaterTransportNetwork.xsd import the GML 3.2 schemas. These in turn import schemas produced by the W3C, which are available from the W3C website at The OSProducts.xsd defines the feature collection and feature members. In addition, this application schema will define the transactions used for a Change Only Update supply.
The Linear Highway Network schema document defines the namespace,
this is defined in the XSD at:
The Highways Water Transport Network schema document defines the namespace,
this is defined in the XSD at:
The application schema uses the following XML namespaces and their associated definitions:
| Prefix | Namespace identifier | Definition available at |
|---|
OS MasterMap Highways Network – Roads is supplied as one GeoPackage file for GB. GeoPackage (*.gpkg) 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 can be used in most GIS software in its native format without translation. GeoPackage attribute names are not limited in length. A GeoPackage file has no size limit, and it supports raster, vector and database formats, making it a highly versatile solution.
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. The tables listed in this section 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 not all GML attributes have been mapped to Geopackage. In the GeoPackage attribute tables, a greyed-out box with an asterisk (*) marks a GeoPackage attribute that is not mapped from a GML attribute.
gml |
xsi |
xlink |
net |
tn |
tn-ro |
tn-w |
os |
network |
highway |
ram |
hwtn |
dedication |
Built in to XML
| GML attribute name | GeoPackage attribute name |
|---|---|
| GML attribute name | GeoPackage attribute name |
|---|---|
| GML attribute name | GeoPackage attribute name |
|---|---|
*
id
gml_id
toid
identifier
identifier
localId
local_id
beginLifespanVersion
begin_lifespan_version
type
type
ferryTerminalName
ferry_terminal_name
ferryTerminalNameLang
ferry_terminal_name_lang
ferryTerminalCode
ferry_terminal_code
reasonForChange
reason_for_change
refToFunctionalSite
ref_to_functional_site
elementId
element_id
elementRole
element_role
*
fid
gml_id
toid
identifier
identifier
localId
local_id
beginLifespanVersion
begin_lifespan_version
*
geometry
validFrom
valid_from
formOfWaterwayNode
form_of_waterway_node
reasonForChange
reason_for_change
*
fid
gml_id
toid
identifier
identifier
localId
local_id
beginLifespanVersion
begin_lifespan_version
descriptiveGroup
descriptive_group
descriptiveTerm
descriptive_term
fictitious
fictitious
validFrom
valid_from
vehicularFerry
vehicular_ferry
routeOperator
route_operator
reasonForChange
reason_for_change
startNode
start_node
endNode
end_node
| GML attribute name | GeoPackage attribute name |
|---|---|
*
id
gml_id
toid
identifier
identifier
localId
local_id
beginLifespanVersion
begin_lifespan_version
validFrom
valid_from
localRoadCode
local_road_code
nationalRoadCode
national_road_code
roadClassification
road_classification
designatedName
designated_name
reasonForChange
reason_for_change
link
link
| GML attribute name | GeoPackage attribute name |
|---|---|
*
id
gml_id
toid
identifier
identifier
localId
local_id
beginLifespanVersion
begin_lifespan_version
reasonForChange
reason_for_change
junctionType
junction_type
junctionName
junction_name
junctionNameLang
junction_name_lang
roadClassificationNumber
road_classiffication_number
junctionNumber
junction_number
node
node
| GML attribute name | GeoPackage attribute name |
|---|---|
*
fid
gml_id
toid
identifier
identifier
localId
local_id
beginLifespanVersion
begin_lifespan_version
*
geometry
fictitious
fictitious
validFrom
valid_from
reasonForChange
reason_for_change
roadClassification
road_classification
routeHierarchy
route_hierarchy
formOfWay
form_of_way
trunkRoad
trunk_road
primaryRoute
primary_route
roadClassificationNumber
road_classification_number
roadName
road_name
roadNameLang
road_name_lang
alternateName
alternate_name
alternateNameLang
alternate_name_lang
operationalState
operational_state
provenance
provenance
directionality
directionality
length
length
matchStatus
match_status
alternateIdentifier
alternate_identifier
alternateIdentifierScheme
alternate_identifier_scheme
startGradeSeparation
start_grade_separation
endGradeSeparation
end_grade_separation
roadStructure
road_structure
cycleFacility
cycle_facility
roadWidthAverage
road_width_average
roadWidthMinimum
road_width_minimum
roadWidthConfidenceLevel
road_width_confidence_level
elevationGainInDirection
elevation_gain_in_direction
elevationGainInOppositeDirection
elevation_gain_in_opposite_direction
formsPartOf
forms_part_of
formsPartOfRole
forms_part_of_role
startNode
start_node
endNode
end_node
relatedRoadArea
related_road_area
| GML attribute name | GeoPackage attribute name |
|---|---|
| GML attribute name | Vector tiles attribute name |
|---|
| GML attribute name | GeoPackage attribute name |
|---|
*
fid
gml_id
toid
identifier
identifier
localId
local_id
beginLifespanVersion
begin_lifespan_version
validFrom
valid_from
*
geometry
formOfRoadNode
form_of_road_node
classification
classification
junctionName
junction_name
junctionNameLang
junction_name_lang
junctionNumber
junction_number
reasonForChange
reason_for_change
relatedRoadArea
related_road_area
gml_id | toid |
vehicularFerry | vehicula_ferry |
routeOperator | route_operator |
* | fid |
gml_id | usrn |
identifier | identifier |
localId | local_id |
beginLifespanVersion | begin_lifespan_version |
validFrom | valid_from |
localRoadCode | local_road_code |
nationalRoadCode | national_road_code |
designatedName | designated_name |
namingAuthorityId | naming_authority_id |
namingAuthority | naming_authority |
localName | local_name |
localNameLang | local_name_lang |
descriptor | descriptor |
descriptorLang | descriptor_lang |
reasonForChange | reason_for_change |
roadClassification | road_classification |
streetType | street_type |
operationalState | operational_state |
operationalStateTimePeriodId | operational_state_time_period_id |
operationalStateBeginPosition | operational_state_begin_position |
operationalStateEndPosition | operational_state_end_position |
locality | locality |
localityLang | locality_lang |
town | town |
townLang | town_lang |
administrativeArea | administrative_area |
administrativeAreaLang | administrative_area_lang |
responsibleAuthority | responsible_authority |
responsibleAuthorityId | responsible_authority_id |
geometryProvenance | geometry_provenance |
* | geometry |
gssCode | gss_code |
gssCodeRole | gss_code_role |
link | link |
OSMM Highways Network – Roads 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 naming of attributes between vector tiles and the Geography Markup Language (GML) file is very similar as the vector tiles set within the MBTiles file is not limited in the number of characters for an attribute name. The tables listed in this section map the GML attribute name to the attribute name in the vector tiles. Please note not all GML attributes have been mapped to vector tile attributes.
The vector tiles schema is detailed in the following tables. 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 layer and attribute are mapped within that zoom level.
| Layer | Attribute | Zoom level 0 to 13 | Zoom level 14 | Zoom level 15 |
|---|---|---|---|---|
| Attribute | Zoom level 0 to 13 | Zoom level 14 | Zoom level 15 |
|---|---|---|---|
| Attribute | Zoom level: 0 to 13 | 14 | 15 |
|---|---|---|---|
| Attribute | Zoom level: 0 to 13 | 14 | 15 |
|---|---|---|---|
| Attribute | Zoom level: 0 to 13 | 14 | 15 |
|---|---|---|---|
ferry_link
toid
N
Y
Y
ferry_link
vehicula_ferry
N
Y
Y
ferry_link
route_operator
N
Y
Y
toid
N
Y
Y
form_of_waterway_node
N
Y
Y
ferry_terminal_name
N
Y
Y
ferry_terminal_name_lang
N
Y
Y
ferry_terminal_code
N
Y
Y
toid
N
Y
Y
local_id
N
Y
Y
road_classification
N
Y
Y
route_hierarchy
N
Y
Y
form_of_way
N
Y
Y
trunk_road
N
Y
Y
primary_route
N
Y
Y
road_classification_number
N
Y
Y
road_name
N
Y
Y
road_name_lang
N
Y
Y
alternate_name
N
Y
Y
alternate_name_lang
N
Y
Y
length
N
Y
Y
road_structure
N
Y
Y
cycle_facility
N
Y
Y
road_width_average
N
Y
Y
road_width_minimum
N
Y
Y
toid
N
Y
Y
form_of_road_node
N
Y
Y
classification
N
Y
Y
junction_name
N
Y
Y
junction_name_lang
N
Y
Y
junction_number
N
Y
Y
usrn
N
Y
Y
local_road_code
N
Y
Y
national_road_code
N
Y
Y
designated_name
N
Y
Y
road_classification
N
Y
Y
street_type
N
Y
Y
responsible_authority
N
Y
Y
| GML attribute name | Vector tiles attribute name |
|---|---|
| GML attribute name | Vector tiles attribute name |
|---|---|
| GML attribute name | Vector tiles attribute name |
|---|
| GML attribute name | Vector tiles attribute name |
|---|
| GML attribute name | Vector tiles attribute name |
|---|
gml_id
toid
formOfWaterwayNode
form_of_waterway_node
ferryTerminalName
ferry_terminal_name
ferryTerminalNameLang
ferry_terminal_name_lang
ferryTerminalCode
ferry_terminal_code
gml_id
toid
localId
local_id
roadClassification
road_classification
routeHierarchy
route_hierarchy
formOfWay
form_of_way
trunkRoad
trunk_road
primaryRoute
primary_route
roadClassificationNumber
road_classification_number
roadName
road_name
roadNameLang
road_name_lang
alternateName
alternate_name
alternateNameLang
alternate_name_lang
length
length
roadStructure
road_structure
cycleFacility
cycle_facility
roadWidthAverage
road_width_average
roadWidthMinimum
road_width_minimum
gml_id | toid |
formOfRoadNode | form_of_road_node |
roadClassification | classification |
junctionName | junction_name |
junctionNameLang | junction_name_lang |
junctionNumber | junction_number |
gml_id | toid |
formOfRoadNode | form_of_road_node |
roadClassification | classification |
junctionName | junction_name |
junctionNameLang | junction_name_lang |
junctionNumber | junction_number |
gml_id | usrn |
localRoadCode | local_road_code |
nationalRoadCode | national_road_code |
designatedName | designated_name |
roadClassification | road_classification |
streetType | street_type |
responsibleAuthority | responsible_authority |
This section contains examples of the different GML structure for Full Supply orders and Change Only Update orders and the transactions within.
An example of the Full Supply GML including the opening and closing tags:
An example of the Change Only Update GML including opening and closing tags and the different types of transactions:
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.
This product is available to try out online using one of our three sets of sample data (Exeter, Newport and Inverness) through the OS MasterMap product viewer:
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.
