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.

Full supply

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.

COU supply

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.

Supply format

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.

Features

• 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.

Code lists, data types and enumerations

• 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’.

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”.

The Road Network is a topologically structured link and node network made up of the following feature types:

Roads feature types

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.

Common attribution

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

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”.

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.

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.

Identifiers

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:

<highway:Road gml:id="osgb4000000009461245">
<gml:identifier codeSpace="
http://inspire.jrc.ec.europa.eu/ids
">
http://data.os.uk/id/4000000009461245<
/gml:identifier>
<net:beginLifespanVersion>2010-04-01T00:00:00.000</net:beginLifespanVersion>
<net:inspireId>
<base:Identifier>
<base:localId>4000000009461245</base:localId>
<base:namespace>
http://data.os.uk/
</base:namespace>
<base:versionId>16</base:versionId>
</base:Identifier>
</net:inspireId>

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

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)

Examples

• gml:id – ‘osgb4000000009461245’

• localId – ‘4000000009461245’

• identifier - ‘http://data.os.uk/4000000009461245’

USRNs

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)

Examples

• 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

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

Examples (examples given for both unique ID formats)

• 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’

Available formats

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).

Adherence to standards

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).

Extending INSPIRE specification

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.

Notation

UML diagram and table conventions

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.

Lexical conventions

• 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.

Stereotypes

The following stereotypes are used on UML elements:

Constraints

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.

Relationships and associations

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.

• 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.

Index

This technical specification includes the following sections:

• Specification changes

• Structure

• How the product fits together

• Change Only Update (COU) Supply

• Feature types

• Structured data types

• Code lists and Enumerations

• GML overview

• Vector tiles overview

• GML examples

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.

Road Attributes

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.

id

Unique identifier, for Road this is a TOID

• Attribute name: gml_id (GML), toid (GeoPackage), Not provided (VectorTiles)

• Type: CharacterString

• Size: 20

• Multiplicity: [1]

identifier

Uniform Resource Identifier

• Attribute name: identifier (GML), identifier (GeoPackage), Not provided (VectorTiles)

• Type: CharacterString

• Size: 37

• Multiplicity: [1]

inspireId INSPIRE

External object identifier of the spatial object.

• Attribute name: inspireId

• Type: Identifier

• Multiplicity: [0..1]

beginLifespanVersion «lideCycleInfo» «voidable» INSPIRE

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]

validFrom «voidable» INSPIRE

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]

localRoadCode «voidable» INSPIRE

Identification code assigned to the road by the local road authority.

• Attribute name: localRoadCode

• Type: CharacterString

• Size: 10

• Multiplicity: [0..1]

nationalRoadCode «voidable» INSPIRE

The national number of the road.

• Attribute name: nationalRoadCode

• Type: CharacterString

• Size: 10

• Multiplicity: [0..1]

roadClassification

The national classification of the road.

• Attribute name: roadClassification (GML), road_classification (GeoPackage), road_classification (VectorTiles)

• Type: RoadClassificationValue

• Size: 21

• Multiplicity: [0..1]

designatedName

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]

reasonForChange

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]

link INSPIRE

The reference to the RoadLink features which builds up the Road feature.

• Attribute name: link

• Size: 20

• Multiplicity: [1..*]

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.

RoadNode Attributes

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

id

Unique identifier, for RoadNode this is a TOID

• Attribute name: gml_id (GML), toid (GeoPackage), toid (VectorTiles)

• Type: CharacterString

• Size: 20

• Multiplicity: [1]

identifier

Uniform Resource Identifier

• Attribute name: identifier (GML), identifier (GeoPackage), Not provided (VectorTiles)

• Type: CharacterString

• Size: 37

• Multiplicity: [1]

inspireId INSPIRE

External object identifier of the spatial object.

• Attribute name: inspireId

• Type: Identifier

• Multiplicity: [0..1]

beginLifespanVersion «lifeCycleInfo» «voidable» INSPIRE

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]

validFrom «voidable» INSPIRE

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]

geometry INSPIRE

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]

formOfRoadNode «voidable» INSPIRE

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]

classification

Further specialisation of the form of road node.

• Attribute name: classification (GML), classification (GeoPackage), Not provided (VectorTiles)

• Type: RoadNodeClassificationValue

• Size: 19

• Multiplicity: [0..1]

access

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]

junctionName

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]

junctionNumber

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]

reasonForChange

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]

relatedRoadArea

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 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.

RoadJunction Attributes

A compound feature that represents a road junction with a name or number.

id

Unique identifier, for RoadJunction this is a TOID

• Attribute name: gml_id (GML), toid (GeoPackage), Not provided (VectorTiles)

• Type: CharacterString

• Size: 20

• Multiplicity: [1]

identifier

Uniform Resource Identifier

• Attribute name: identifier (GML), identifier (GeoPackage), Not provided (VectorTiles)

• Type: CharacterString

• Size: 37

• Multiplicity: [1]

inspireId INSPIRE

External object identifier of the spatial object.

• Attribute name: inspireId

• Type: Identifier

• Multiplicity: [0..1]

beginLifespanVersion «lifeCycleInfo» «voidable» INSPIRE

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]

reasonForChange

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]

junctionType

A classification for the Road Junction.

• Attribute name: junctionType (GML), junction_type (GeoPackage), Not provided (VectorTiles)

• Type: JunctionTypeValue

• Size: 26

• Multiplicity: [1]

junctionName

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]

roadClassificationNumber

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]

junctionNumber

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]

node

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 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.

1. 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.

2. 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).

Street Attributes

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.

id

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]

identifier

Uniform Resource Identifier

• Attribute name: identifier (GML), identifier (GeoPackage), Not provided (VectorTiles)

• Type: CharacterString

• Size: 29

• Multiplicity: [1]

inspireId INSPIRE

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]

beginLifespanVersion «lifeCycleInfo» «voidable» INSPIRE

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]

validFrom «voidable» INSPIRE

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]

localRoadCode «voidable» INSPIRE

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]

nationalRoadCode «voidable» INSPIRE

The national number of the road.

• Attribute name: nationalRoadCode

• Type: CharacterString

• Size: 10

• Multiplicity: [0..1]

designatedName

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]

localName

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]

descriptor

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]

reasonForChange

The reason for a change made to a feature.

• Attribute name: reasonForChange (GML), reason_for_change (GeoPackage), Not provided (VectorTiles)

• Size: 32

• Multiplicity: [1]

roadClassification

The national classification of the road.

• Attribute name: roadClassification (GML), road_classification (GeoPackage), road_classification (VectorTiles)

• Type: RoadClassificationValue

• Size: 21

• Multiplicity: [0..1]

streetType

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]

operationalState

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]

locality

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]

town

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]

administrativeArea

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]

responsibleAuthority

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]

geometryProvenance

Identify where the geometry of the feature originated.

• Attribute name: geometryProvenance (GML), geometry_provenance (GeoPackage), Not provided (VectorTiles)

• Type: ProvenanceSourceValue

• Size: 23

• Multiplicity: [1]

geometry

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]

gssCode

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]

link <> INSPIRE

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 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.

RoadLink Attributes

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.

id

Unique identifier, for RoadLink this is a TOID

• Attribute name: gml_id (GML), toid (GeoPackage), toid (VectorTiles)

• Type: CharacterString

• Size: 20

• Multiplicity: [1]

identifier

Uniform Resource Identifier

• Attribute name: identifier (GML), identifier (GeoPackage), Not provided (VectorTiles)

• Type: CharacterString

• Size: 37

• Multiplicity: [1]

inspireId INSPIRE

External object identifier of the spatial object.

• Attribute name: inspireId

• Type: Identifier

• Multiplicity: [0..1]

beginLifespanVersion «voidable» «lifeCycleInfo» INSPIRE

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]

centrelineGeometry INSPIRE

The three-dimensional geometry that represents the alignment of the section of road.

• Attribute name: centrelineGeometry

• Type: GM_Curve

• Multiplicity: [1]

fictitious INSPIRE

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]

validFrom «voidable» INSPIRE

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]

reasonForChange

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]

roadClassification

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]

routeHierarchy

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]

formOfWay

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]

trunkRoad

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]

primaryRoute

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]

roadClassificationNumber

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]

roadName

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]

alternateName

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]

operationalState

Indicator identifying the construction status of the road

• Attribute name: operationalState (GML), operational_state (GeoPackage), Not provided (VectorTiles)

• Type: OperationalStateValue

• Size: 19

• Multiplicity: [1]

provenance

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]

directionality

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]

length

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]

matchStatus

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]

alternateIdentifier

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..*]

startGradeSeparation

The relative level of the link at the startNode.

• Attribute name: startGradeSeparation (GML), start_grade_separation (GeoPackage), Not provided (VectorTiles)

• Type: Integer

• Multiplicity: [1]

endGradeSeparation

The relative level of the link at the endNode.

• Attribute name: endGradeSeparation (GML), end_grade_separation (GeoPackage), Not provided (VectorTiles)

• Type: Integer

• Multiplicity: [1]

roadStructure

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]

cycleFacility

Identifies if the RoadLink has facilities for a cyclist.

• Attribute name: cycleFacility(GML), cycle_facility (GeoPackage), cycle_facility (VectorTiles)

• Type: CycleFacilityType

• Multiplicity: [0..1]

roadWidth

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]

elevationGain

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]

formsPartOf

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

startNode INSPIRE

The node coincident with the first vertex of the geometry attribute.

• Attribute name: startNode

• Multiplicity: 0..1

• Size: 20

endNode INSPIRE

The node coincident with the last vertex of the geometry attribute.

• Attribute name: endNode

• Multiplicity: 0..1

• Size: 20

relatedRoadArea

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

RoadLink, Road and Street are attributed with a “designatedName” with a data type of “DesignatedNameType”. The attribution of this data type is detailed below.

DesignatedNameType attributes

The name assigned to the road or street by a designated Street Naming Authority.

name

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]

namingAuthority

The local authority that assigned the designatedName.

• Attribute name: namingAuthority

• Type: ResponsibleAuthority

• Multiplicity: [1]

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.

Identifier attributes

An external unique object identifier published by the responsible body may be used by external applications to reference the spatial object.

localId

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

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.

OperationalStateType attributes

state

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]

validTime

If known, the real-world start and end date/times when the state applies.

• Attribute name: validTime

• Type: TM_Period

• Multiplicity: [0..1]

reason

When a street has been closed a short description of the reason for closure.

• Attribute name: reason

• Type: CharacterString

• Size: 120

• Multiplicity: [0..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.

RoadWidthType attributes

averageWidth

The average width of the road carriageway.

• Attribute name: averageWidth

• Type: Measure

• Multiplicity: [1]

minimumWidth

The minimum width of the topographic area feature the RoadLink is representing.

• Attribute name: minimumWidth

• Type: Measure

• Multiplicity: [0..1]

confidenceLevel

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]

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.

ResponsibleAuthority attributes

The authority responsible for the street naming and numbering or maintenance.

identifier

The code used to identify the authority. Example: 0114

• Attribute name: identifier

• Type: CharacterString

• Size: 4

• Multiplicity: [1]

authorityName

Official name of the authority. Example: Bath and North East Somerset

• Attribute name: authorityName

• Type: CharacterString

• Size: 100

• Multiplicity: [1]

A code list or enumeration is a controlled set of values which can be used to populate a specific column.

ElevationGainType attributes

inDirection

Total increase in height experienced when passing along the link from the start to the end.

• Attribute name: inDirection

• Type: Measure

• Multiplicity: [1]

inOppositeDirection

Total increase in height experienced when passing along the link from the end to the start.

• Attribute name: inOppositeDirection

• Type: Measure

• Multiplicity: [1]

A RoadLink could be attributed with “cycleFacility” with a data type of “CycleFacilityType”. The attribution of this data type is detailed below.

CycleFacilityType attributes

cycleFacility

The cycle amenity available along the link.

• Attribute name: cycleFacility

• Type: CycleFacilityValue

• Size: 45

• Multiplicity: [1]

wholeLink

Identifies if the facility applies to entirety of the link.

• Attribute name: wholeLink

• Type: Boolean

• Size: 5

• Multiplicity: [1]

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.

FerryLink Attributes

A network link representing a route for a vehicular or pedestrian ferry route.

id

Unique identifier, for FerryLink this is a TOID

• Attribute name: gml_id (GML), toid (GeoPackage), toid (VectorTiles)

• Type: CharacterString

• Size: 20

• Multiplicity: [1]

identifier

Uniform Resource Identifier

• Attribute name: identifier (GML), identifier (GeoPackage), Not provided (VectorTiles)

• Type: CharacterString

• Size: 37

• Multiplicity: [1]

inspireId INSPIRE

External object identifier of the spatial object.

• Attribute name: inspireId

• Type: Identifier

• Multiplicity: [1]

beginLifespanVersion «lifeCycleInfo» «voidable» INSPIRE

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]

centrelineGeometry INSPIRE

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]

fictitious INSPIRE

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]

validFrom «voidable» INSPIRE

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]

vehicularFerry

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]

routeOperator

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]

reasonForChange

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]

startNode INSPIRE

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]

endNode INSPIRE

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]

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 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.

FerryNode attributes

A feature representing the point at which a vehicular or pedestrian ferry route or section of ferry route starts or ends.

id

Unique identifier, for FerryNode this is a TOID

• Attribute name: gml_id (GML), toid (GeoPackage), toid (Vector Tiles)

• Type: CharacterString

• Size: 20

• Multiplicity: [1]

identifier

Uniform Resource Identifier

• Attribute name: identifier (GML), identifier (GeoPackage), Not provided (Vector Tiles)

• Type: CharacterString

• Size: 37

• Multiplicity: [1]

inspireId INSPIRE

External object identifier of the spatial object.

• Attribute name: inspireId INSPIRE

• Type: Identifier

• Multiplicity: [0..1]

beginLifespanVersion INSPIRE

Date and time at which this version of the spatial object was inserted or changed in the spatial data set.

• Attribute name: beginLifespanVersion (GML), begin_lifespan_version (GeoPackage), Not provided (VectorTiles)

• Type: DateTime

• Multiplicity: [1]

geometry INSPIRE

The location of the node.

• Attribute name: geometry (GML), Not provided (GeoPackage), Not provided (Vector Tiles)

• Type: GM_Point

• Multiplicity: [1]

validFrom INSPIRE

The time when the transport node started to exist in the real world.

• Attribute name: validFrom (GML), valid_from (GeoPackage), Not provided (Vector Tiles)

• Type: DateTime

• Multiplicity: [1]

formOfWaterwayNode INSPIRE

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]

reasonForChange

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.

FerryTerminal Attributes

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.

id

Unique identifier, for FerryTerminal this is a TOID

• Attribute name: gml_id (GML), toid (GeoPackage), Not provided (VectorTiles)

• Type: CharacterString

• Size: 20

• Multiplicity: [1]

identifier

Uniform Resource Identifier

• Attribute name: identifier (GML), identifier (GeoPackage), Not provided (VectorTiles)

• Type: CharacterString

• Size: 37

• Multiplicity: [1]

inspireId INSPIRE

External object identifier of the spatial object.

• Attribute name: inspireId

• Type: Identifier

• Multiplicity: [0..1]

beginLifespanVersion INSPIRE

Date and time at which this version of the spatial object was inserted or changed in the spatial data set.

• Attribute name: beginLifespanVersion (GML), begin_lifespan_version (GeoPackage), Not provided (VectorTiles)

• Type: DateTime

• Multiplicity: [1]

type INSPIRE

Categorisation of the network connection.

• Attribute name: type (GML), type (GeoPackage), Not provided (VectorTiles)

• Type: ConnectionTypeValue

• Size: 10

• Multiplicity: [1]

ferryTerminalName

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]

ferryTerminalCode

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]

reasonForChange

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]

refToFunctionalSite

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]

element INSPIRE

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..*]

The ‘reasonForChange’ attribute is used across all features found within the OS MasterMap Highways Network. The table below describes the codes which will be used to populate this field and the description for each code.

Code List: ChangeValue

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 List: RoadClassificationValue

The RoadLink feature is attributed with a “roadStructure” property with the data type of RoadStructureValue. The following table describes the codes used to populate this field.

Code List: RoadStructureValue

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 List: RoadFunctionValue

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”.

Code List: OperationalStateValue

The RoadLink and Street feature is attributed with a ‘provenance’ property with the data type of ProvenanceSourceValue. The following table describes the codes used to populate this field.

Code List: ProvenanceSourceValue

The RoadLink feature is attributed with a “matchStatus” with a data type of “MatchStatusValue”. The table below describes the codes used to populate this field and the description for each code.

Code List: MatchStatusValue

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.

Code List: LinkDirectionValue

List of values for directions relative to a link

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 List: CycleFacilityValue

The RoadLink feature is attributed with a “formOfWay” property with the data type of FormOfWayValue. The following table describes the codes used to populate this field.

Code List: FormOfWayValue

The RoadNode feature is attributed with a “formOfRoadNode” property with the data type of FormOfRoadNodeValue. The following table describes the codes used to populate this field.

Code List: FormOfRoadNodeValue

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.

Code List: RoadNodeClassificationValue

Additional classification of the road node.

For example, if a node represents a roundabout it may also be classified as a mini roundabout.

The “RoadWidthType” data type is attributed with a “confidenceLevel” property with the data type of “RoadWidthConfidenceLevelValue”. The following table describes the codes used to populate this field.

Code List: RoadWidthConfidenceLevelValue

The Street feature is attributed with a “streetType” property with the data type of StreetTypeValue. The following table describes the codes used to populate this field.

Code List: StreetTypeValue

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.

The RoadJunction feature is attributed with a “junctionType” property with the data type of JunctionTypeValue. The following table describes the codes used to populate this field.

Code List: JunctionTypeValue

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.

Code List: FormOfWaterwayNodeValue

Function of a Waterway Node in the water transport network.

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.

Code List: ConnectionTypeValue

Types of connections between different networks.

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:

Schema overview and location

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:

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.

Attribute naming differences between GML and GeoPackage formats

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.