This section describes the features which make up OS MasterMap Highways Network - Paths. The attributes associated with these feature types are listed below along with a brief description of their data properties.

Feature type attribute information

Name and Definition

The name of the attribute and what it is describing.

Data type

The nature of the attribute, for example a numeric value or a code list value.

Size:

The length of the attribute provided (optional).

Multiplicity

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.

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

OS MasterMap Highways Network is the authoritative highway network for Great Britain. It brings together Ordnance Survey’s large-scale roads and paths 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 the following 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 (RAMI)

• OS MasterMap Highways Network – Paths

This technical specification will cover the OS MasterMap Highways Network – Paths (from here referred to as Path Network) product specification. For details on the Roads or RAMI products' specifications, see their respective Technical Specifications.

Identifiers

All features that comprise the OS MasterMap Highways Network – Paths will be assigned a persistent identifier; in most instances this is an Ordnance Survey TOID (Topographic Identifier). For features which have originated from the National Street Gazetteer, the persistent identifier will be either a Unique Street Reference Number (USRN) for Street features or a unique ID for Maintenance, Reinstatement, Special Designation and Highway Dedication.

Identifiers shall be encoded in three properties in the data:

1. gml:id – This is a feature identifier comprised of the shorthand prefix namespace and local identifier which is used to uniquely identify and reference the feature within the dataset.

Example: osgb4000000009461245

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

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

<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 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 20 characters which consist of 2 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 12 characters which consist of 2 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 to 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 seventeen 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

Example: esu4720_4280330430163_8, esu4720_4280340431456_11

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

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 the 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 extends the INSPIRE specifications (coloured orange). All code lists 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

1. Class names are conceptually meaningful names (singular noun) in UpperCamelCase.

2. Class names end in “Value” where the class is assigned the stereotype <<CodeList>> or <<Enumeration>>.

3. Class names shall end in “Type” where the class is assigned the stereotype <<DataType>>.

4. 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 class diagrams. 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: This is used to denote either:

  • An extension relationship: where 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 defined 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: These 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 does the product fit together?

• Change-Only Update Supply

• Feature types

• Structured data types

• Data types

• Code lists and Enumerations

• GML Overview

• GeoPackage overview

• Vector tiles overview

• GML examples

OS MasterMap Highways Network – Paths is a relational product. This results in there being relationships between different feature types. This section summarises how the different feature types relate to one another, and which attributes are the primary and foreign keys.

The below table identifies how the feature types relate to one another and which attributes are the primary and foreign keys. This is also represented diagrammatically below. The attribute at the arrowhead is the primary key and the attribute at the base of the arrow is the foreign key.

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

• PathLink – A line segment representing the general alignment of the path.

• PathNode – A node connecting to at least one PathLink, providing network connectivity.

• ConnectingLink – A logical indicator of the connection between the Path Network and the Road Network.

• ConnectingNode – A node which connects the Road Network to the Path Network.

• Path – A Path defines the complete collection of references to PathLink features which share the same path name, for example, Three Brooks Walk.

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

• FerryLink – A feature which represents a ferry route between two FerryNodes.

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

• FerryTerminal – A feature representing the point at which pedestrians transfer from the Ferry Network to the Path Network or vice versa.

• Maintenance – Identifies what the maintenance status is of a Street.

• Reinstatement – A feature which identifies how a Street should be re-instated after street works.

• Special Designation – A feature which identifies if there is additional information about the Street.

• Highway Dedication – A feature which identifies the type of Highway user that has access to that particular section of the Highway.

The relationships between Path feature types are shown below:

The Road and Path Networks are topologically structured together. ConnectingLinks and ConnectingNodes enable a connection between the Road Network and the Path Network. ConnectingLinks are logical connections between the Path Network and the Road Network; they do not represent a feature in the real world. A ConnectingNode is a feature which indicates where the Path will connect with the Road Network. Connecting Nodes are spatially coincident with RoadNodes and can share the same identifier. The ConnectingLink feature will reference the PathNode and ConnectingNode that it connects with, whilst the ConnectingNode will reference one of the RoadLinks that it connects to.

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 (Note: 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 then there is a requirement to give a reason for this. This will be specified in the GML through an attribute called “nilReason”.

Network referencing

The Asset Management features of the Path Network product relate back to the Path Network features using Network Referencing, through the networkRef attribute. All RAMI features extend the INSPIRE NetworkProperty class.

In the Path Network product, only one type of Network Reference is used which is the INSPIRE NetworkProperty class. This class has been extended in cases where the feature only partially references the network feature.

In the INSPIRE specification, the networkRef is a voidable field. For all features in the OS MasterMap Highways Network the networkRef will never be voided.

Network reference

The Network Reference references the feature back to the network element. The Network Reference has been extended and the asset management feature types which use Network Referencing are Maintenance, Reinstatement, Special Designation and Highways Dedication. These features will all reference back to the id of the Street feature, the USRN. Geometry will not be provided. However, where these features do not reference an entire Street feature, and are a partial reference, they will provide a Network Reference Location. This is made up of a locationDescription which provides a textual description of where the feature relates to which will be populated directly from the NSG.

A point spatial object that is used to break up the Path Network for connectivity. The PathNode extends the RoadNode feature in the INSPIRE Transport Network (roads) model. The Path Network splits for the following circumstances:

• The location where an attribute changes.

• The intersection or crossing of PathLinks.

• The start/end of a PathLink.

The context diagram below shows how the PathNode has been inherited from INSPIRE and the attribution held on the PathNode:

PathNode Attributes

A point representing either the start/end of a path, the connectivity between two or more paths, or where one of the recorded attributes changes.

id

Unique identifier; for PathNode, 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

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

• Attribute name: beginLifespanVersion

• Type: DateTime

• Multiplicity: [1]

geometry INSPIRE

The location of the node.

• Attribute name: geometry

• Type: GM_Point

• Multiplicity: [1]

validFrom «voidable» INSPIRE

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

• Attribute name: validFrom

• Type: DateTime

• Multiplicity: [1]

formOfRoadNode «voidable» INSPIRE

Description of the function of a path node in the road transport network.

• Attribute name: formOfRoadNode

• Type: FormOfRoadNodeValue

• Size: 21

• Multiplicity: [1]

reasonForChange

The reason for a change made to a feature.

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

• Type: ChangeValue

• Size: 32

• Multiplicity: [1]

classification

Further specialisation of the form of path node

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

• Type: RoadNodeClassificationValue

• Size: 19

• Multiplicity: [0..1]

A path network dataset for Great Britain showing who is responsible for all the footpaths through towns and cities. The dataset helps you understand how people connect to towns and cities around them. You will see the true time it takes for the citizen to access existing services – as well as the new services required in the community.

How to get this product

Visualise OS MasterMap Highways Network – Paths data online

A ConnectingNode is a point feature that identifies where a Path connects to the Road Network. The ConnectingNode connects to the start or end of one or more RoadLinks and provides a reference to one of the RoadLinks it connects to. Connecting Nodes are spatially coincident with RoadNodes and can share the same identifier. The ConnectingNode is referenced by a .

The context diagram below shows how the ConnectingNode relates to the RoadLink.

Three-dimensional geometry has been applied to ConnectingNode features. This is to facilitate routing that requires coincidence of co-ordinates. Given the nature of connecting feature this geometry is for connectivity purposes only.

ConnectingNode Attributes

A point which connects the Road Network to the Path Network.

id

Unique identifier; for ConnectingNode, 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

• 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 (Vector Tiles)

• Type: DateTime

• Multiplicity: [1]

reasonForChange

The reason for a change made to a feature.

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

• Type: ChangeValue

• Size: 32

• Multiplicity: [1]

geometry

The location of the node which indicates where the Path Network connects to the Road Network.

• Attribute name: geometry

• Type: GM_Point

• Multiplicity: [1]

roadLink «voidable»

A reference to the RoadLink which the ConnectingNode connects to.

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

• Size: 20

• Multiplicity: 1

The OS MasterMap Highways Network – Paths can be ordered as either Full Supply or Change-Only Update (COU). 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 in . If a customer wishes to move their order from Full Supply to COU then they will need to receive an initial supply and apply the COU file to an 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.

Change-Only Update 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 sent out automatically.

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 customer’s 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 customer’s 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:

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

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

1. <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 of the different types of transactions in GML examples.

The Road and Path Network are topologically structured together. ConnectingLinks enable a connection between the Road Network and the Path Network. A ConnectingLink feature is a linear spatial object which represents a logical connection between the Path Network and the Road Network; it does not represent a feature in the real world. A ConnectingLink will always reference a PathNode and a ConnectingNode. The context diagram below shows how the ConnectingLink relates to and .

Three-dimensional geometry has been given to ConnectingLink features. This is to facilitate routing that requires coincidence of co-ordinates. Given the nature of connecting feature, this geometry is for connectivity purposes only.

ConnectingLink Attributes

A ConnectingLink is not a representation of a real-world object. It is a logical indicator of the connection between the Path Network and the Road Network.

id

Unique identifier; for ConnectingLink, 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

• 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

• Type: DateTime

• Multiplicity: [1]

reasonForChange

The reason for a change made to a feature.

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

• Type: ChangeValue

• Size: 32

• Multiplicity: [1]

geometry

The implied connection between the RoadLink and the PathLink. Note, this is represented as a three-dimensional geometry to facilitate connectivity, but it is a logical connection not a physical alignment.

• Attribute name: geometry

• Type: GM_Curve

• Multiplicity: [1]

fictitious

Indicator that the 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 (GML), fictitious (GeoPackage), Not provided (Vector Tiles)

• Type: Boolean

• Size: 5

• Multiplicity: [1]

connectingNode

A reference to the ConnectingNode which the ConnectingLink references.

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

• Size: 20

• Multiplicity: 1

pathNode

A reference to the PathNode which the ConnectingLink references.

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

• Size: 20

• Multiplicity: 1

A PathLink is a linear spatial object that defines the geometry and connectivity of the Path Network between two points in the network. PathLinks will be split for connectivity purposes (for example, at junctions) and PathNodes will connect the PathLinks together. Each PathLink will provide a reference to the PathNodes at the start and end of the PathLink.

A PathLink will be captured where:

• They provide a route that cannot be inferred from the Road Network.

• They provide connectivity between Road Networks.

• There is a canal path or tow path.

• There are paths over footbridges and under subways.

• There are recreational paths in urban, rural and mountain and moorland areas.

PathLinks will not be captured where:

• They run parallel to the Road Network, for example, a pavement.

• They are connected to a Motorway.

• There is a physical obstruction which prevents connectivity.

PathLinks will split where two PathLinks 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 PathLink. The Grade Separation attribute will indicate where there is or is not a physical connection between the Paths in the real world. Grade Separation will determine if a PathLink is above another. If the two PathLinks, when referencing the same PathNode, have different values, then it is not possible to move between them at that point.

Where a PathLink crosses a RoadLink at a different level, both the PathLink and RoadLink will split. The attributes “startGradeSeparation” and “endGradeSeparation” will be populated on the PathLink and RoadLink. The Grade Separation attribute will indicate where there is or is not a physical connection between the path and road 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 below shows how the PathLink has been inherited from INSPIRE and the attribution held on the PathLink.

PathLink Attributes

A linear feature that represents the general alignment of a route used by pedestrians.

id

Unique identifier; for PathLink, 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.

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

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

• Type: DateTime

• Multiplicity: [1]

centrelineGeometry INSPIRE

The three-dimensional geometry that represents the alignment of the path.

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

• 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 (GML), fictitious (GeoPackage), Not provided (VectorTiles)

• 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 (GML), valid_from(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 (Vector Tiles)

• Type: ChangeValue

• Size: 32

• Multiplicity: [1]

formOfWay

A description of the PathLink based on its nature or use.

• Attribute name: formOfWay (GML), form_of_way (GeoPackage), form_of_way (Vector Tiles)

• Type: FormOfWayTypeValue

• Size: 42

• Multiplicity: [1]

pathName

The name of the path the feature is part of, when a PathLink is referenced by a Street with a streetStateType of Designated Street Name this is the name used else the name is from Path. 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: pathName (GML), path_name (GeoPackage), path_name (Vector Tiles)

• Type: LocalisedCharacterString

• Size: 255

• Multiplicity: [0..2]

alternateName

Another name for the path 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: pathName (GML), path_name (GeoPackage), path_name (Vector Tiles)

• Type: LocalisedCharacterString

• Size: 255

• Multiplicity: [0..2]

provenance

The origin and derivation of the three-dimensional geometry of the PathLink.

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

• Type: ProvenanceSourceValue

• Size: 23

• Multiplicity: [1]

surfaceType

Nature of the material that the path is made up of.

• Attribute name: surfaceType(GML), surface_type (GeoPackage), surface_type (Vector Tiles)

• Type: SurfaceTypeValue

• Size: 13

• Multiplicity: [0..1]

cycleFacility

Identifies if the PathLink has facilities for a cyclist.

• Attribute name: cycleFacility(GML), cycle_facility (GeoPackage), cycle_facility (Vector Tiles)

• Type: CycleFacilityType

• Multiplicity: [0..1]

matchStatus

Indication whether the feature has been matched to a feature in the NSG.

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

• Type: MatchStatusValue

• Size: 39

• Multiplicity: [1]

length

The calculated two-dimensional length of the PathLink in metres.

• Attribute name: length (GML), length (GeoPackage), length (Vector Tiles)

• Type: Measure

• Size: 7,2

• Multiplicity: [1]

alternateIdentifier

Identifier(s) of the Elementary Street Unit from NSG or TRSG

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

• 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 (Vector Tiles)

• Type: Integer

• Multiplicity: [1]

endGradeSeparation

The relative level of the link at the endNode.

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

• Type: Integer

• Multiplicity: [1]

elevationGain

The elevation gain is calculated from three-dimensional geometry to define the total ascent experienced when passing along a PathLink feature. The value is expressed both with and against the direction of digitising.

• Attribute name: elevationGainInDirection (GML), elevationGainInOppositeDirection (GML), elevation_gain_in_direction (GeoPackage), elevation_gain_in_opposite_direction (GeoPackage), Not provided (Vector Tiles)

• Type: ElevationGainType

• Multiplicity: [0..1]

formsPartOf

Identifier of the Path or Street to which the PathLink forms part of.

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

• Size: 20

• Multiplicity: 0..*

startNode INSPIRE

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

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

• Size: 20

• Multiplicity: 0..1

endNode INSPIRE

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

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

• Size: 20

• Multiplicity: 0..1

relatedRoadArea

Reference to the topographic representation(s) of the same part of the path.

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

• Size: 20

• 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 the route is limited to pedestrians only and both terminals are within Great Britain, and there is a timetabled service which is open 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 (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

External object identifier of the spatial object.

• Attribute name: inspireId

• Type: Identifier

• Multiplicity: [0..1]

beginLifespanVersion

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 (Vector Tiles)

• Type: DateTime

• Multiplicity: [1]

centrelineGeometry

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: Not provided (GML), geometry (GeoPackage), Not provided (Vector Tiles)

• Type: GM_Curve

• Multiplicity: [1]

fictitious

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 (GML), fictitious (GeoPackage), Not provided (Vector Tiles)

• Type: Boolean

• Size: 5

• Multiplicity: [1]

validFrom

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]

vehicularFerry

An indicator if this FerryLink represents a ferry that can be used by vehicles.

• Attribute name: vehicularFerry (GML), vehicular_ferry (GeoPackage), vehicular_ferry (Vector Tiles)

• Type: Boolean

• Size: 5

• Multiplicity: [1]

routeOperator

The URL to the operator of this Ferry route.

• Attribute name: routeOperator (GML), route_operator (GeoPackage), route_operator (Vector Tiles)

• 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 (Vector Tiles)

• Type: ChangeValue

• Size: 32

• Multiplicity: [1]

startNode

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

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

• Size: 20

• Multiplicity: [0..1]

endNode

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

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

• Size: 20

• Multiplicity: [0..1]

A Path feature is a link set which represents a collection of PathLink features that share the same name (for example, Church Walk). A Path will reference the complete collection of RoadLink features irrespective of which authority boundary it falls within. A PathLink feature may be referenced by multiple Path features.

The context diagram shows how the Path feature has been inherited from INSPIRE and the attribution held on the Path.

Path attributes

A compound feature that represents a path with a name. This references a collection of PathLinks.

id

Unique identifier; for Path, 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

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

• Attribute name: beginLifespanVersion

• Type: DateTime

• Multiplicity: [1]

validFrom «voidable» INSPIRE

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

• 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 (Vector Tiles)

• Type: ChangeValue

• Size: 32

• Multiplicity: [1]

pathName

The name assigned to the feature which all the referenced links have in common.

• Attribute name: pathName (GML), path_name (GeoPackage), path_name (Vector Tiles)

• Type: LocalisedCharacterString

• Size: 255

• Multiplicity: [1..2]

link INSPIRE

The reference to the PathLink features which builds up the Path feature.

• Attribute name: link

• Size: 20

• 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

External unique object identifier published by the responsible body, which 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 (GML), local_id (GeoPackage), Not provided (Vector Tiles)

• Type: CharacterString

• Size: 16

• Multiplicity: [1]

namespace

Namespace uniquely identifying the data source of the spatial object.

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

• Type: CharacterString

• Size: 18

• Multiplicity: [1]

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

cycleFacility attributes

The cycle amenity available along the link.

• Attribute name: cycleFacility (GML), cycle_facility (GeoPackage), cycle_facility (Vector Tiles)

• Type: CycleFacilityValue

• Multiplicity: [1]

wholeLink

Identifies if the facility applies to entirety of the link.

• Attribute name: cycleFacility_wholeLink (GML), cycle_facility_whole_link (GeoPackage), cycle_facility_whole_link (Vector Tiles)

• Type: Boolean

• Multiplicity: [1]

A PathLink could be attributed with “elevationGain” with a data type of “ElevationGainType”. The attribution of this data type is detailed below.

ElevationGainType attributes

inDirection

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

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

• Type: Measure

• Multiplicity: [1]

inOppositeDirection

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

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

• Type: Measure

• 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, for example, Under Construction

• Type: OperationalStateValue

• Size: 19

• Multiplicity: [1]

validTime

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

• Type: TM_Period

• Multiplicity: [0..1]

reason

Short description of the reason for closure.

• Type: CharacterString

• Size: 120

• Multiplicity: [0..1]

The “dateRange” attribute on the ‘TemporalPropertyType’ has a data type of “DateRangeType”. The below table describes how this data type is constructed.

DateRangeType attributes

startDate

The date which the restriction applies starts. This will be in the format YYYY-MM-DD.

• Attribute name: startDate (GML), start_date (GeoPackage), start_date (Vector Tiles)

• Type: Date

• Multiplicity: [0..1]

endDate

The date which the restriction applies ends. This will be in the format YYYY-MM-DD.

• Attribute name: endDate (GML), end_date (GeoPackage), end_date (Vector Tiles)

• Type: Date

• Multiplicity: [0..1]

TemporalPropertyType attributes

The time period which a restriction is in place.

• Constraints: A TermporalPropertyType shall have at least one of namedDate, dateRange, or dayPeriod When namedDate = 'All Dates' no other values for namedDate or dateRange shall be populated

namedDate

The named month or period this time interval applies.

• Type: NamedDateValue

• Multiplicity: [0..*]

dateRange

The range of dates the time restriction is in place for.

• Type: DateRangeType

• Multiplicity: [0..*]

dayPeriod

A restriction which applies on a specified day.

• Type: DayPropertyType

• Multiplicity: [0..*]

The “timeRange” attribute on the ‘TimePropertyType’ has a data type of “TimeRangeType”. The below table describes how this data type is constructed.

timeRangeType attributes

startTime

The time the restriction begins

• Attribute name: startTime (GML), start_time (GeoPackage), start_time (Vector Tiles)

• Type: Time

• Multiplicity: [1]

endTime

The time the restriction ends.

• Attribute name: endTime (GML), end_time (GeoPackage), end_time (Vector Tiles)

• Type: Time

• Multiplicity: [1]

The “timePeriod” attribute on the ‘DayPropertyType’ has a data type of “TimePropertyType”. The below table describes how this data type is constructed.

• Constraints: A TimePropertyType shall have at least one of timeRange, or namedTime. When namedTime = 'All Day' no other values for namedTime or timeRange shall be populated.

TimePropertyType attributes

namedTime

These are named time periods that do not relate to the same time each day.

• Type: NamedTimeValue

• Multiplicity: [0..*]

timeRange

The range of time which a restriction applies.

• Type: TimeRangeType

• Multiplicity: [0..*]

Special Designations are statutory and advisory designations that can be applied to protect a highway when street or road works are to be undertaken.

A Special Designation feature will reference back to the Path Network through Network Reference and will reference a Street Feature. Features which are a partial reference will provide a Network Reference Location.

SpecialDesignation attributes

A description applied to a highway to protect it during Street or Road Works.

Constraints:

• If partialRefernce = true then NetworkReferenceLocation shall be expressed.

id

Unique identifier.

• Attribute name: gml_id (GML), unique_id (GeoPackage)

• Type: CharacterString

• Size: 17

• Multiplicity: [1]

identifier

Uniform Resource Identifier.

• Attribute name: identifier (GML), identifier (GeoPackage)

• Type: CharacterString

• Size: 35

• Multiplicity: [1]

inspireId

External object identifier of the spatial object.

• Attribute name: inspireId

• Type: Identifier

• Multiplicity: [0..1]

beginLifespanVersion

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)

• Type: DateTime

• Multiplicity: [1]

networkRef

Spatial reference of the network-related property.

• Attribute name: networkRef (GML), network_ref (GeoPackage)

• Type: NetworkReference

• Multiplicity: [1..*]

validFrom

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

• Attribute name: validFrom (GML), valid_from (GeoPackage)

• Type: DateTime

• Multiplicity: [1]

validTo

The time from which the transport property no longer exists in the real world.

• Attribute name: validTo (GML), valid_to (GeoPackage)

• Type: DateTime

• Multiplicity: [1]

designation

Type of Special Designation.

• Attribute name: designation (GML), designation (GeoPackage)

• Type: SpecialDesignationTypeValue

• Size: 30

• Multiplicity: [1]

description

Additional information describing the special designation.

• Attribute name: description (GML), description (GeoPackage)

• Type: CharacterString

• Size: 50

• Multiplicity: [0..1]

timeInterval

Time period to which the restriction applies.

• Attribute name: startTime (GML), endTime (GML), start_time (GeoPackage), end_time (GeoPackage)

• Type: TemporalPropertyType

• Multiplicity: [0..1]

contactAuthority

Highway authority to be contacted for further consultation about the special designation.

• Attribute name: contactAuthority (GML), contact_authority (GeoPackage)

• Type: ResponsibleAuthority

• Multiplicity: [0..1]

partialReference

Flag to indicate that the maintenance feature partially references a Street.

• Attribute name: partialReference (GML), partial_reference (GeoPackage)

• Type: Boolean

• Size: 5

• Multiplicity: [1]

reasonForChange

The reason for a change made to a feature.

• Attribute name: reasonForChange (GML), reason_for_change (GeoPackage)

• Type: ChangeValue

• Size: 32

• Multiplicity: [1]

This section describes the structured data types which make up OS MasterMap Highways Network - Paths. The attributes associated with these data types are listed below along with a brief description of their data properties.

SpecialDesignations have a property of ‘timeInterval’ which has the type of ‘TemporalPropertyType’. The below table describes this data type and shows how it is made up. The hierarchical structure of Temporal Properties is shown on the Temporal Properties page.

Structured data type attribute information

Name and Definition

The name of the attribute and what it is describing.

Data type

The nature of the attribute, for example a numeric value or a code list value.

Size

The length of the attribute provided (optional).

Multiplicity

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.

Highway dedication provides an indication of the type of Highway user who has access to that particular section of the Highway.

Against every section of geometry supplied by the local highway authority there will be one of eight different types of Highway Dedication defined in the Highways Act 1980 and the Countryside and Rights of Way Act 2000 which determines the Highway user access.

There can only be one Highway Dedication type applied to the geometry at any given date or time.

It is likely that more than one Highway Dedication type applies to a section of Highway (i.e. a highway open to all vehicles will also have pedestrian way or footway access) so the following is an order of priority where the highway dedications under each is inferred:

• Motorway *

• All Vehicles

• Byway Open to All Traffic

* Motorways and Cycle Tracks (not Cycle Ways) impose restrictions on all other Highway users.

• Restricted Byway

• Cycle Track * or Cycle Way

• Bridleway

• Pedestrian Way or Footpath

The Highway Dedication also identifies if the feature forms part of a National Cycle Route, Public Right of Way, Quiet Route, Physical Obstruction or Planning Order or Vehicular Traffic order exist.

A Highway Dedication feature will reference back to the Path Network through Network Reference and will reference a RoadLink or Street Feature.

The Highway Dedication Feature Type is not extended to Scotland because this information does not exist in the source local authority data.

HighwayDedication Attributes

Definition of which type of Highway user has access to a particular section of the Highway.

id

Unique identifier.

• 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

External object identifier of the spatial object.

• Attribute name: inspireId

• Type: Identifier

• Multiplicity: [0..1]

beginLifespanVersion

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 (Vector Tiles)

• Type: DateTime

• Multiplicity: [1]

networkRef

Spatial reference of the network-related property.

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

• Type: NetworkReference

• Multiplicity: [1..*]

validFrom

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

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

• Type: DateTime

• Multiplicity: [1]

reasonForChange

The reason for a change made to a feature.

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

• Type: ChangeValue

• Size: 32

• Multiplicity: [1]

dedication

The type of Highway Dedication that applies to this section of the Street.

• Attribute name: dedication (GML), dedication (GeoPackage), dedication (Vector Tiles)

• Type: DedicationValue

• Size: 35

• Multiplicity: [1]

timeInterval

Time period to which the dedication applies.

• Attribute name: startTime (GML), start_time (GeoPackage), start_time (Vector Tiles), endTime (GML), end_time (GeoPackage), end_time (Vector Tiles)

• Type: TemporalPropertyType

• Multiplicity: [0..*]

nationalCycleRoute

An indication if the dedication is subject to a formal cycle classification.

• Attribute name: nationalCycleRoute (GML), national_cycle_route (GeoPackage), national_cycle_route (Vector Tiles)

• Type: Boolean

• Size: 5

• Multiplicity: [1]

quietRoute

An indication if the dedication is subject to a quiet route.

• Attribute name: quietRoute (GML), quiet_route (GeoPackage), quiet_route (Vector Tiles)

• Type: Boolean

• Size: 5

• Multiplicity: [0..1]

obstruction

An indication if the dedication contains a physical obstruction to vehicles.

• Attribute name: obstruction (GML), obstruction (GeoPackage), obstruction (Vector Tiles)

• Type: Boolean

• Size: 5

• Multiplicity: [1]

planningOrder

An indication if a pedestrian planning order applies to the dedication.

• Attribute name: planningOrder (GML), planning_order (GeoPackage), planning_order (Vector Tiles)

• Type: Boolean

• Size: 5

• Multiplicity: [0..1]

worksProhibited

An indication if the dedication has a Traffic Regulation Order prohibiting any works in the Highway at all times.

• Attribute name: worksProhibited (GML), works_prohibited (GeoPackage), works_prohibited (Vector Tiles)

• Type: Boolean

• Size: 5

• Multiplicity: [0..1]

geometry

The geometry that represents the centreline of the dedication.

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

• Type: GM_Curve

• Multiplicity: [1]

Reinstatement defines the standard to which the Path must be restored following opening due to works in the highway, as defined in the New Roads and Street Works Act Specification for the Reinstatement of Openings in Highways in England and Wales and the New Roads and Street Works Act 1991 Specification for the Reinstatement of Openings in Roads in Scotland.

A Reinstatement feature will reference back to the Path Network through a Network Reference and will reference a Street Feature. Features which are a partial reference will provide a Network Reference Location.

Reinstatement Attributes

The standard to which the highway must be restored to following street works.

Constraints:

• If partialRefernce = true then NetworkReferenceLocation shall be expressed.

id

Unique identifier.

• Attribute name: gml_id (GML), unique_id (GeoPackage)

• Type: CharacterString

• Size: 17

• Multiplicity: [1]

identifier

Uniform Resource Identifier.

• Attribute name: identifier (GML), identifier (GeoPackage)

• Type: CharacterString

• Size: 35

• Multiplicity: [1]

inspireId

External object identifier of the spatial object.

• Attribute name: inspireId

• Type: Identifier

• Multiplicity: [0..1]

beginLifespanVersion

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)

• Type: DateTime

• Multiplicity: [1]

networkRef

Spatial reference of the network-related property.

• Attribute name: networkRef (GML), network_ref (GeoPackage)

• Type: NetworkReference

• Multiplicity: [1..*]

validFrom

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

• Attribute name: validFrom (GML), valid_from (GeoPackage)

• Type: DateTime

• Multiplicity: [1]

reinstatementType

Reinstatement as defined in the Specification for Reinstatement of Opening in Highways codes of practice in England and Wales and the Specification for the Reinstatement of Openings in Roads in Scotland.

• Attribute name: reinstatementType (GML), reinstatement_type (GeoPackage)

• Type: ReinstatementTypeValue

• Size: 51

• Multiplicity: [1]

partialReference

Flag to indicate that the maintenance feature partially references a Street.

• Attribute name: partialReference (GML), partial_reference (GeoPackage)

• Type: Boolean

• Size: 5

• Multiplicity: [1]

reasonForChange

The reason for a change made to a feature.

• Attribute name: reasonForChange (GML), reason_for_change (GeoPackage)

• Type: ChangeValue

• Size: 32

• Multiplicity: [1]

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

This section describes the data types which make up OS MasterMap Highways Network - Paths. The attributes associated with these data types are listed below along with a brief description of their data properties.

Data type attribute information

Name and Definition

The name of the attribute and what it is describing.

Data type

The nature of the attribute, for example a numeric value or a code list value.

Size

The length of the attribute provided (optional).

Multiplicity

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.

Data Type attributes

element

The identifier of the feature being referenced; this will always be the gml:id.

• Multiplicity: [1]

• Size: 20

locationDescription

Textual description of the location extent of the referenced property when the feature partially references the network.

• Type: CharacterString

• Multiplicity: [1]

• Size: 250

locationStart

The geometry of where the feature starts.

• Type: GM_Point

• Multiplicity: [0..1]

locationEnd

The geometry of where the feature ends.

• Type: GM_Point

• Multiplicity: [0..1]

locationLine

A linear representation of the feature.

• Type: GM_MultiCurve

• Multiplicity: [0..1]

locationArea

An area representation of the feature.

• Type: GM_MultiSurface

• Multiplicity: [0..1]

The Special Designation and Highways Dedication features contain information on restrictions which apply to a temporal period. The different temporal properties have been categorised and the different categories are detailed below. In addition, they have been given a hierarchy within the RAMI product which is illustrated in the diagram below.

Named Date

A Named Date would be when a restriction applies to a specified date which is named. For example, All Year or January. There are no further sub-categories of a Named Date.

Date Range

A Date Range is provided when a restriction applies between two dates and there will always be a start date and an end date. These two dates can be specified using two different data types: either StartDate and EndDate or StartMonthDay or EndMonthDay.

The StartDate and EndDate will always be used for Date Ranges for Special Designation features. These are formatted as YYYY-MM-DD, for example, 2016-09-20.

Day Period

A Day period would be a restriction which applies on a specified day. A Day Period is made up of the following properties:

• Named Day – A restriction which applies to a specified day which is named, for example, Monday or Weekends

• Named Period – A restriction which applies to a specified period which is named, for example, School Holidays.

• Time Period – A time period is made up of a further two properties:

  • Named Time – A restriction which applies to a specified time period which is named. That does not necessarily relate to the same time each day consistently across the country, for example, Peak Time.

  • Time Range – When a restriction applies between two specified times which will always have a start time and an end time. These data types are formatted as HH:MM:SS and will use the 24hr clock, for example, 16:30:00.

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

The PathLink 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 PathLink and Street feature are attributed with a “provenance” property with the data type of ProvenanceSourceValue. The following table identifies the codes used to populate this field.

Code List: ProvenanceSourceValue

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

Code List: SurfaceTypeValue

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: StreetStateTypeValue

The SpecialDesignation feature has property field ‘designationType’ which has the type allocated from ‘SpecialDesignationTypeValue’. The table below identifies the codes used to populate this field and a description for each code.

‘SpecialDesignationTypeValue’ coverage varies between LHAs and the individual codes. While coverage for statutory designations is good overall, coverage for some may be sporadic and inconsistent.

Code List: SpecialDesignationTypeValue

Designation of highways that are subject to special controls when undertaking street or road works

OS MasterMap Highways Network – Paths 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 and 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. Therefore, the following tables map the GML attribute name to the attribute name in the GeoPackage files.

The GML contains an attribute which describes the geometry of the feature; this is not applicable for a GeoPackage file as they are separated by their geometry. Please note not all GML attributes have been mapped to GeoPackage. In the tables below a greyed-out box with an asterisk (*) marks a GeoPackage attribute that is not mapped from a GML attribute.

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®). http://www.opengeospatial.org/standards/gml

The XML specifications that GML is based on are available from the World Wide Web Consortium (W3C): http://www.w3.org.

Information about Unicode and UTF-8, the character encoding we have chosen, is available on the Unicode Consortium website: http://www.unicode.org.

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 Path Network uses the following application schemas; LinearHighwayNetwork.xsd, HighwaysWaterTransportNetwork.xsd, RoutingAndAssetManagement.xsd and OSProducts.xsd which are referenced by the data.

• The LinearHighwaysNetwork.xsd defines the features which make up the Path 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.

• The RoutingAndAssetManagement.xsd defines the asset management features of the Path Network. Through the INSPIRE schemas both the LinearHighwayNetwork.xsd HighwaysWaterTransportNetwork.xsd and the RoutingAndAssetManagement.xsd import the GML 3.2 schemas. These in turn import schemas produced by the W3C, which are available from the W3C website at http://www.w3.org/XML/1998/namespace.html.

• 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 http://namespaces.os.uk/mastermap/highwayNetwork/2.0 namespace, this is defined in the XSD at: http://www.os.uk/xml/schema/highwaysnetwork/2.0/linearhighwaynetwork.xsd.

The Highways Water Transport Network schema document defines the http://namespaces.os.uk/mastermap/highwaysWaterTransportNetwork/1.0 namespace.

This is defined in the XSD at: https://www.os.uk/xml/schema/highwaysnetwork/1.0/HighwaysWaterTransportNetwork.xsd.

The RAMI schema document defines the http://namespaces.os.uk/mastermap/routingAndAssetManagement/2.1 namespace.

This is defined in the XSD at: http://www.os.uk/xml/schema/highwaysnetwork/2.1/RoutingAndAssetManagement.xsd

The Highways Dedication schema document defines the http://namespaces.os.uk/mastermap/highwayDedication/1.0 namespace.

This is defined in the XSD at: https://www.ordnancesurvey.co.uk/xml/schema/highwaysnetwork/1.0/HighwayDedication.xsd

The application schema uses the following XML namespaces, for which definitions are available here:

The Maintenance feature type has the property ‘maintenanceResponsibility’ which has the type ‘MaintenanceValue’. The table below identifies the codes used to populate this field and a description for each code.

MaintenanceValue attributes

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.

http://inspire.ec.europa.eu/codelist/FormOfWaterwayNodeValue

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.