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

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.

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.

Size

The length of the attribute provided (optional).

The RAMI product contains the base road network and RAMI features, which reference back to the network. The base road network features are detailed in the Roads Technical Specification. The current specification focuses on RAMI.

RAMI has been categorised into the following themes:

• Rights and Restrictions: Defines properties that restrict, regulate or prohibit the use of the network by traffic such as turn restrictions, or access and use restrictions which may affect the allowable route for users.

• Advisory Information: These provide additional information that may affect a driver’s preferred choice of route or highlight potential hazards such as the presence of a toll, ford, or level crossing.

• Asset Management: Provides additional information to support the management of Highways Assets by Highways and Roads Authorities such as detailed physical characteristics relating to the asset (reinstatement), road maintenance responsibility, and whether it has any special designations

Network referencing

RAMI is related back to features in the OS MasterMap Highways Network – Roads product using Network Referencing, through the networkRef attribute. All RAMI features extend the INSPIRE NetworkProperty class. This allows several types of Network Referencing to relate the RAMI to the relevant feature:

• Network Reference: This is used to relate the information to a Street.

• Node Reference: This is used to relate the information to a RoadNode.

• Link Reference: This is used to relate the information to a complete RoadLink.

• Multiple Link Reference: This is used to relate the information to more than one complete RoadLink.

• Point Reference: This is used when the information is related to a specific point along a RoadLink.

• Linear Reference: This is used to relate the information to a specific section of a RoadLink. This type of referencing is not used in the RAMI specification.

The different types of Network Referencing all extend the INSPIRE Network Reference data type.

In the INSPIRE specification, the networkRef is a voidable field. For all features in the RAMI specification, the networkRef will never be voided.

There have been small enhancements to the OS MasterMap Highways Network Version 2.2 to enable the release of new features and functionality. This page will outline the main changes to the RAMI product. For changes to the Roads or Paths products, please see their respective Technical Specifications.

Features

• Added new feature type, HighwayDedication, to denote dedications of highways as defined in the Highway Act 1980 and Countryside and Rights of Way Act 2000.

• Added new code list, DedicationValue, for HighwayDedication features.

Code lists, data types, and enumerations

• March 2021 – The ReinstatementTypeValue code list has been updated with four new values added to include Scottish codes.

• March 2021 – The SpecialDesignationTypeValue code list has been updated with five new values added to include Scottish codes.

• The NetworkReferenceLocation has been further extended to accept additional geometry types, lines and polygons, in addition to start and end points. This affects Maintenance, Reinstatement and Special Designation and the information provided on their location for partial records.

• The SpecialDesignationTypeValue code list has been updated with multiple new values added.

• The MaintenanceValue enumeration has been updated with two values added.

Schema changes

• v2.1 RAMI schema is being released which will enable the code list and enumerations described above to be delivered.

• v1.0 Highways Dedication schema has been introduced which defines the Highways Dedication feature.

The Network Reference references the feature back to the network element. The Network Reference has been extended and the feature types which solely 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 / SSG.

The feature types which use the Network Reference Location are Maintenance, Reinstatement, Special Designation, and HighwayDedication.

NetworkReferenceLocation attributes

Element

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

• Size: 20

• Multiplicity: [1]

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]

OS MasterMap Highways Network – RAMI 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 for the RAMI feature. For information on the Roads features, please see the Roads Technical Specification.

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

OS MasterMap Highways Network – Routing and Asset Management Information (RAMI) integrates data from Ordnance Survey's large-scale road and path data with additional street data held within the National Street Gazetteer (NSG), the Trunk Road Street Gazetteer (TRSG) and the Scottish Street Gazetteer (SSG). The routing information covers such aspects as vehicle restrictions, covering access, manoeuvres, and physical characteristics. The asset management information provides details on the authority responsible for maintaining a road, how a road should be restored following street works and if there are any unusual conditions that the local highway authority have associated with a road.

For vehicle routing and navigation software providers, this data gives you all you need to get your users safely to their destinations: turn, height, weight and width restrictions – and even bollards and traffic calming.

How to get this product

Access to this product is free for PSGA Members. Find out if you are a PSGA Member or try out a sample of OS MasterMap Highways Network – RAMI data by accessing the product page here with links to all of the relevant resources. Alternatively, you can try out the full product by applying for a Data Exploration license.

Visualise OS MasterMap Highways Network – Routing and Asset Management Information online

The OS MasterMap Highways Network is the authoritative highway network for Great Britain. It brings together Ordnance Survey’s large-scale road and path 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, shown in the diagram below, 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 covers the OS MasterMap Highways Network – Routing and Asset Management Information (from here, referred to as RAMI) product specification, providing a focus on the RAMI features. To use this product, you will have received the features which make up the Roads product. For further details on the Roads or Paths products, please see their respective Technical Specifications.

• OS MasterMap Highways Network - Roads Technical specification

• OS MasterMap Highways Network - Paths Technical specification

Identifiers

All features that comprise the OS MasterMap Highways Network product 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, 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 Highways Dedication.

Identifiers shall be encoded in three properties in the data:

• gml:id – This feature identifier consists of the shorthand prefix namespace and local identifier which is used to uniquely identify and reference the feature within the dataset, for example, osgb4000000009461245.

• gml:identifier – This is a global feature identifier and can be used to identify and reference the feature within other datasets, for 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.

<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 twenty characters which comprise two parts:

• Namespace: This is either a HTTP URI (http://data.os.uk/) or a shorthand prefix (osgb)

• Local identifier: A 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 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, and 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-character 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 “_” (underscore):

• LHA authority code

• ESU it references

• Dedication code in the NSG

For 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 – RAMI will be supplied in two formats: Geography Markup Language (GML 3.2.1) and GeoPackage. Both formats are compressed into a regular zip file (.zip).

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

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 extend the INSPIRE specifications (coloured orange). All code list classes are coloured blue, enumeration classes are green and data types/union classes are purple (see diagram below).

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

Or:

• 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

• How the product fits together

• Routing and Asset Management feature information

• Common attribution

• Rights and Restrictions

• Advisory information

• Asset management

• Change Only Update (COU) Supply

• Code lists and Enumerations

• Data Types

• GML overview

• GeoPackage overview

• GML examples

When a feature in the RAMI specification occurs at a RoadNode a Node Reference will be provided. As a part of the networkRef an element attribute will be given which defines the id of the RoadNode. A location will be provided for Node References which will be the coordinates of the RoadNode the feature references. Finally, a linkReference will contain a reference to the id of the RoadLinks that are affected by the restriction. In most instances, this will be all the RoadLinks that start or end at the referenced RoadNode. However, when a RoadNode has a classification of Grade Separation, then it will only reference the RoadLinks that are at the same level as the feature. An example of this could be at a bridge with a height restriction. The height restriction will only impact the RoadLinks that are passing under the bridge.

The RoadLinks which are travelling over the bridge are not impacted by the height restriction. Therefore, the NodeReference will provide a reference to the RoadLinks which are passing under the bridge and will not reference all RoadLinks which reference the RoadNode through the start or end node references.

The feature types which use a Node Reference are , , and .

NodeReference attributes

Element INSPIRE

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

• Size: 20

• Multiplicity: [1]

Location

The co-ordinates for the RoadNode the feature is referencing.

• Type: GM_Point

• Multiplicity: [1]

LinkReference

A reference to the RoadLink(s) that the feature effects.

• Size: 20

• Multiplicity: [1..*]

For a feature that happens at a specific point, that is not coincident with a RoadNode, a Point Reference will be used which will reference a RoadLink. The Point Reference will give the location of the point, defined as a distance value in metres from the start of the RoadLink through the atPosition attribute. In addition, the location of the point will be given by a pair of coordinates which are snapped to the RoadLink, through the atPositionGeometry attribute. Finally, the direction along the RoadLink for which the feature applies is given through the applicableDirection. If the feature applies to the RoadLink regardless of which way you travel along it (for example, a Gate), the value will be both directions. If the feature applies to the RoadLink in a specific direction of travel (for example, an Access Restriction), the direction will be defined in relation to the digitisation of the RoadLink (the order of coordinates).

The feature types which use a Point Reference are , ,, and .

PointReference attributes

Element

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

• Size: 20

• Multiplicity: [1]

ApplicableDirection <<voidable>>

The direction of the RoadLink to which the reference applies in relation to the direction the link has been captured in.

• Type: LinkDirectionValue

• Size: 21

• Multiplicity: [1]

AtPosition <<voidable>>

Position of the point, expressed as the distance from the start of the linear network element along its curve geometry.

• Type: Length

• Multiplicity: [1]

ApplicableDirection

The location geometry of the restriction, will be snapped to the RoadLink.

• Type: GM_Point

• Multiplicity: [1]

A Multiple Link Reference is the same as a , except the feature will contain more than one link reference. This referencing will be used when a feature references multiple, complete RoadLinks, for example a No Turn. The order in which these features apply to the RoadLink is important to ensure the feature is being interpreted correctly and therefore the Link References in the product have been ordered to reflect this. In addition to the order, the direction will be provided in relation to the digitisation of the RoadLink and this is important in interpreting the feature. Geometry will not be provided for these features.

The feature types which use a Multiple Link Reference are and .

For a feature that happens at a specific point, that is not coincident with a RoadNode, a Point Reference will be used which will reference a RoadLink. The Point Reference will give the location of the point, defined as a distance value in metres from the start of the RoadLink through the atPosition attribute. In addition, the location of the point will be given by a pair of coordinates which are snapped to the RoadLink, through the atPositionGeometry attribute. Finally, the direction along the RoadLink for which the feature applies is given through the applicableDirection. If the feature applies to the RoadLink regardless of which way you travel along it (for example, a Gate), the value will be both directions. If the feature applies to the RoadLink in a specific direction of travel (for example, an Access Restriction), the direction will be defined in relation to the digitisation of the RoadLink (the order of coordinates).

The feature types which use a Point Reference are , , , and .

PointReference attributes

Element

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

• Size: 20

• Multiplicity: [1]

ApplicableDirection

The direction of the RoadLink to which the reference applies in relation to the direction the link has been captured in.

• Type: LinkDirectionValue

• Size: 21

• Multiplicity: [1]

AtPosition

Position of the point, expressed as the distance from the start of the linear network element along its curve geometry.

• Type: Length

• Multiplicity: [1]

AtPositionGeometry

The location geometry of the restriction, will be snapped to the RoadLink.

• Type: GM_Point

• Multiplicity: [1]

When a feature occurs along a complete single RoadLink, a Link Reference will be used. Geometry is not provided for these features. The direction along the RoadLink for which the feature applies is supplied through the applicableDirection. If the feature applies to the RoadLink, regardless of which direction you travel along it (for example, Traffic Calming), then the value will be both directions. If the feature applies to the RoadLink in a specific direction of travel (for example, a One-Way road), the direction will be given in relation to the digitisation of the RoadLink (the order of coordinates).

The feature types which use a Link Reference are and .

LinkReference attributes

Element

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

• Size: 20

• Multiplicity: [1]

ApplicableDirection <<voidable>>

The direction of the RoadLink to which the reference applies in relation to the direction the link has been captured in.

• Size: 21

• Type: LinkDirectionValue

• Multiplicity: [1]

This section describes the features which make up OS MasterMap Highways Network - Routing and Asset Management rights and restrictions. 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.

Advisory Information provides additional information relating to the highway that affects traffic movement such as:

• Hazards: These are locations which are dangerous, and caution should be taken to ensure safe travel. Examples include Fords and Dangerous Bends.

• Structures: These are built features which relate to the highway. Examples include Barriers, Bridges and Tunnels.

Each feature within the RAMI theme will have the following common attribution:

• gml:id, gml:identifier and inspireId

• beginLifespanVersion

• reasonForChange

• validFrom

Temporal properties

The RAMI product holds 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 figure below Temporal Properties are applied to four Feature Types in RAMI: AccessRestrictions, HighwayDedication, TurnRestrictions and SpecialDesignation.

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. The StartMonthDay and EndMonthDay will always be used for Access Restrictions and Turn Restrictions. These are formatted as --MM—DD, for example, -- 03—23.

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. 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 Rights and Restrictions sub-theme includes properties that prohibit, restrict or regulate the use of the network by traffic. Rights and Restrictions are typically defined through legislation, including the Traffic Regulation Order (TRO) made under the Road Traffic Regulation Act 1984.

The following types of rights and restrictions are in the scope of the current product:

• Access Restrictions

• Turn Restrictions

• Restrictions For Vehicles (Height, Weight, Width and Length restrictions)

• Highways Dedications (indications of Rights of Way)

Simplification and priority of Rights and Restrictions

Rights and Restrictions features record the effect and nature of the real-world restriction or environmental factors. However, this is not always possible as restrictions may manifest in many different ways yet have the same effect.

For example, a single restriction may consist of a one-way street that has a no entry sign, no right/left turn sign and/or mandatory turn signs on the approach roads. This is represented in the simplest way by recording a one-way street. To ensure a level of consistency, a hierarchy is used when more than one restriction that has the same effect occurs at a given location. Only the restriction that has the highest priority will be captured.

Restriction priority table

Therefore, Rights and Restrictions primarily model the effect of any restriction in the simplest possible way and secondary to this is recording the real-world manifestation.

A turn restriction is a restriction based upon a vehicle manoeuvre. This type of restriction includes prohibitive driving instructions, mandatory driving instructions and implicit restrictions. Prohibited instructions are indicated by road signs within a red circle, examples include No U Turn, No Right Turn or No Left Turn. These can include exceptions to the instruction and are typically elements like Except for Buses. Mandatory driving instructions are indicated by road signs within a blue circle or painted on the roadway such as Turn Right, Ahead Only and No Left Turn. Implicit restrictions occur where a turn is not signed as prohibited but would not be a normal manoeuvre. For example, where a road splits around a traffic island or at complex junctions where additional geometry has been captured to reflect the traffic flow. These are not differentiated from actual signed restrictions.

A Turn Restriction will reference back to the Roads product through Link References and Multiple Link References.

TurnRestriction attributes

A restriction on vehicular manoeuvre.

id

Unique identifier, for TurnRestriction this is a TOID.

• Attribute name: id

• Type: CharacterString

• Size: 20

• Multiplicity: [1]

identifier

Uniform Resource Identifier.

• Attribute name: identifier

• 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. Note: The time part is always set to zero.

• Attribute name: beginLifespanVersion

• Type: DateTime

• Multiplicity: [1]

networkRef

Spatial reference of the network-related property.

• Attribute name: networkRef

• Type: NetworkReference

• Multiplicity: [1..*]

validFrom

The time when the transport property started to exist in the real world. Note: The time part is always set to zero.

• Attribute name: validFrom

• Type: DateTime

• Multiplicity: [1]

restriction

Type of turn constraint.

• Attribute name: restriction

• Type: TurnRestrictionValue

• Size: 34

• Multiplicity: [1]

inclusion

Types of vehicle or use that the restriction applies to.

• Attribute name: inclusion

• Type: VehicleQualifier

• Multiplicity: [0..1]

exemption

Types of vehicle or use that are exempt from the turn restriction.

• Attribute name: exemption

• Type: VehicleQualifier

• Multiplicity: [0..1]

timeInterval

Time period to which the restriction applies.

• Attribute name: timeInterval

• Type: TemporalPropertyType

• Multiplicity: [0..1]

reasonForChange

The reason for a change made to a feature.

• Attribute name: reasonForChange

• Type: ChangeValue

• Size: 32

• Multiplicity: [1]

Access to a road or area by vehicles can be legally prohibited. Prohibited access restrictions are indicated by regulatory signs with a red circle or a no entry sign. In addition, access could be limited for use by particular classes of vehicle, these are indicated by regulatory signs with a blue circle. Access restrictions may also include exemptions to the restriction. The Access Restriction feature type comprises of these types of restrictions.

An Access Restriction will reference back to the Roads Product Network through Point Referencing.

AccessRestriction attributes

A restriction based on vehicular access to a highway.

identifier

Uniform Resource Identifier.

• Attribute name: identifier

• 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

• Type: DateTime

• Multiplicity: [1]

networkRef

Spatial reference of the network-related property.

• Attribute name: networkRef

• Type: NetworkReference

• Multiplicity: [1..*]

validFrom

The time when the transport property started to exist in the real world. Note: The time part is always set to zero.

• Attribute name: validFrom

• Type: DateTime

• Multiplicity: [1]

restriction

Nature of the access restriction.

• Attribute name: restriction

• Size: 21

• Multiplicity: [1]

inclusion

Types of vehicle or use that the restriction applies to.

• Attribute name: inclusion

• Multiplicity: [0..1]

exemption

Types of vehicle or use that are exempt from the restriction.

• Attribute name: exemption

• Multiplicity: [0..1]

timeInterval

Time period to which the restriction applies.

• Attribute name: timeInterval

• Multiplicity: [0..*]

trafficSign

A description of the traffic sign indicating the restriction, for example, Access Limited to Buses.

• Attribute name: trafficSign

• Type: CharacterString

• Size: 120

• Multiplicity: [1]

reasonForChange

The reason for a change made to a feature.

• Attribute name: reasonForChange

• Type: ChangeValue

• Size: 32

• Multiplicity: [1]

Highway dedication indicates which types of user have access to the given 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). The following table gives the order of priority where the highway dedications under each is inferred:

Highway Dedication user priorities

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

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

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

• Type: CharacterString

• Size: 20

• Multiplicity: [1]

identifier

Uniform Resource Identifier

• Attribute name: identifier

• 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

• Type: DateTime

• Multiplicity: [1]

networkRef

Spatial reference of the network-related property.

• Attribute name: networkRef

• Multiplicity: [1..*]

validFrom

The time when the transport property 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

• Size: 32

• Multiplicity: [1]

dedication

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

• Attribute name: dedication

• Size: 35

• Multiplicity: [1]

timeInterval

Time period to which the dedication applies.

• Attribute name: timeInterval

• Multiplicity: [0..*]

publicRightOfWay

An indication if the dedication is subject to a public right of way.

• Attribute name: publicRightOfWay

• Type: Boolean

• Size: 5

• Multiplicity: [1]

nationalCycleRoute

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

• Attribute name: nationalCycleRoute

• Type: Boolean

• Size: 5

• Multiplicity: [1]

quietRoute

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

• Attribute name: quietRoute

• Type: Boolean

• Size: 5

• Multiplicity: [0..1]

obstruction

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

• Attribute name: obstruction

• Type: Boolean

• Size: 5

• Multiplicity: [1]

planningOrder

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

• Attribute name: planningOrder

• 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

• Type: Boolean

• Size: 5

• Multiplicity: [0..1]

geometry

The geometry that represents the centreline of the dedication.

• Attribute name: geometry

• Type: GM_Curve

• Multiplicity: [1]

RestrictionForVehicles are constraints that apply to the vehicles based on their physical characteristics: height, weight, width and length. These are required to protect structures such as bridges and tunnels from damage, or to restrict/prohibit use by vehicles that exceed specific dimensions, usually for environmental reasons.

RestrictionForVehicles has been extended to support the full definition of height, weight, width and length restrictions as defined in the UK to ensure that they can:

• Apply to specific vehicle types only.

• Relate to a structure for which the restriction is designed to protect (for example, a Bridge).

A RestrictionForVehicles will reference back to the Roads product through either a Node Reference or a Point Reference.

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

RestrictionForVehicles

Height, Weight, Width and Length restrictions (HWWL) for vehicles. Measure shall be defined in metric units for width, height and length restrictions. For all weight restrictions, measure will be defined in tonnes and measure2 will not be supplied.

id

Unique identifier, for RestrictionForVehicle this is a TOID.

• Attribute name: id

• Type: CharacterString

• Size: 20

• Multiplicity: [1]

identifier

Uniform Resource Identifier.

• Attribute name: identifier

• Type: CharacterString

• Size: 37

• Multiplicity: [1]

inspireId

External object identifier of the spatial object.

• Attribute name: inspireId

• Multiplicity: [0..1]

beginLifespanVersion

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]

networkRef

Spatial reference of the network-related property.

• Attribute name: networkRef

• Type: NetworkReference

• Multiplicity: [1..*]

validFrom

The time when the transport property started to exist in the real world. Note: The time part is always set to zero.

• Attribute name: validFrom

• Type: DateTime

• Multiplicity: [1]

measure

The measure for the restriction which will be given in metres. Note: A Unit of Measure (uom) is provided as part of the attribute.

• Attribute name: measure

• Type: Measure

• Size: 6,1

• Multiplicity: [1]

restrictionType

The type of restriction.

• Attribute name: restrictionType

• Size: 26

• Multiplicity: [1]

sourceOfMeasure

Indicates if the measure value is from a sign or has been converted from a different unit of measure.

• Attribute name: sourceOfMeasure

• Type: CharacterString

• Size: 10

• Multiplicity: [1]

measure2

The measure for the restriction in imperial units and will be in inches. It will only be provided if the imperial restriction is present on the sign.

• Attribute name: measure2

• Type: Measure

• Size: 4

• Multiplicity: [0..1]

inclusion

Vehicle types or uses that the restriction applies to.

• Attribute name: inclusion

• Multiplicity: [0..1]

exemption

Vehicle types or uses that are exemptions to the restriction.

• Attribute name: exemption

• Multiplicity: [0..1]

structure

Description of the structure to which the restriction applies.

• Attribute name: structure

• Size: 40

• Multiplicity: [0..1]

trafficSign

A description of the traffic sign indicating the restriction, for example, Maximum Height Restriction 6'-6".

• Attribute name: trafficSign

• Type: CharacterString

• Size: 120

• Multiplicity: [1..2]

trafficRegulationOrder

Reference to the Traffic Regulation Order that formally created the restriction. Note: This is not currently populated.

• Attribute name: trafficRegulationOrder

• Size: 250

• Multiplicity: [0..1]

reasonForChange

The reason for a change made to a feature.

• Attribute name: reasonForChange

• Size: 32

• Multiplicity: [1]

This section describes the features which make up OS MasterMap Highways Network - Routing and Asset Management advisory information. 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.

Asset management information provides additional information describing the network to support its long- term operation and maintenance which has been sourced from the road or highways authorities. This includes Maintenance, Reinstatement and Special Designation.

This section describes the features which make up OS MasterMap Highways Network - Asset Management. 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.

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

These indicate the location of key structures related to the highway network. These may be:

• Barriers: Structures or equipment constructed to control, obstruct or prevent passage or access

• Bridges and Tunnels

• Crossings and Signals: Equipment such as traffic signals, and locations that control the flow of traffic

A Structure will reference back to the Roads product through a Node Reference, Link Reference or Point Reference.

Structure attributes

A built feature with relation to the highway network.

id

Unique identifier, for Structure this is a TOID.

• Attribute name: id

• Type: CharacterString

• Size: 20

• Multiplicity: [1]

identifier

Uniform Resource Identifier.

• Attribute name: identifier

• 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. Note: The time part is always set to zero.

• Attribute name: beginLifespanVersion

• Type: DateTime

• Multiplicity: [1]

networkRef

Spatial reference of the network-related property.

• Attribute name: networkRef

• Type: NetworkReference

• Multiplicity: [1..*]

validFrom

The time when the transport property started to exist in the real world. Note: The time part is always set to zero.

• Attribute name: validFrom

• Type: DateTime

• Multiplicity: [1]

structure

Type of built feature.

• Attribute name: structure

• Type: StructureTypeValue

• Size: 39

• Multiplicity: [1]

description

Additional information describing the structure.

• Attribute name: description

• Type: CharacterString

• Size: 50

• Multiplicity: [0..1]

reasonForChange

The reason for a change made to a feature.

• Attribute name: reasonForChange

• Type: ChangeValue

• Size: 32

• Multiplicity: [1]

Maintenance provides information about whether the road is maintained at public expense by a national or local highway authority, a road authority, or is maintained by another responsible organisation (i.e. not maintained at public expense). If a path is prospectively maintainable at public expense, then this is not currently maintained by a road or highway authority, but the responsible organisation has started the process for a highway or road authority to become responsible for the maintenance of the street at public expense.

A Maintenance feature will reference back to the Roads product through Network Reference and will reference a Street Feature. Features which are a partial reference will provide a Network Reference Location. For more information on Network References, see Routing and Asset Management feature information.

Maintenance attributes

Indication of whether the highway is maintained by a Highways Authority, Local Highways Authority, Road Authority or privately.

id

Unique identifier.

• Attribute name: id

• Type: CharacterString

• Size: 17

• Multiplicity: [1]

identifier

Uniform Resource Identifier.

• Attribute name: identifier

• 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. Note: The time part is always set to zero.

• Attribute name: beginLifespanVersion

• Type: DateTime

• Multiplicity: [1]

networkRef

Spatial reference of the network-related property.

• Attribute name: networkRef

• Type: NetworkReference

• Multiplicity: [1..*]

validFrom

The time when the transport property started to exist in the real world. Note: The time part is always set to zero.

• Attribute name: validFrom

• Type: DateTime

• Multiplicity: [1]

maintenanceResponsibility

Indication of whether the highway is maintainable at public expense.

• Attribute name: maintenanceResponsibility

• Type: MaintenanceValue

• Size: 44

• Multiplicity: [1]

maintenanceAuthority

Authority responsible for maintenance of the highway.

• Attribute name: maintenanceAuthority

• Type: ResponsibleAuthority

• Multiplicity: [0..1]

partialReference

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

• Attribute name: partialReference

• Type: Boolean

• Size: 5

• Multiplicity: [1]

highwayAuthority

The authority which the highway resides in. Note: When the maintenanceAuthoirty is Highways England, then highwayAuthority will be set to Highways England. When maintenanceResponsibility = Not Maintained at Public Expense, then this is the authority the works operator must contact when applying to carry out works on this street.

• Attribute name: highwayAuthority

• Type: ResponsibleAuthority

• Multiplicity: [1]

reasonForChange

The reason for a change made to a feature.

• Attribute name: reasonForChange

• Type: ChangeValue

• Size: 32

• Multiplicity: [1]

These are locations which are hazardous, and caution should be taken to ensure safe travel. Hazards are usually signed using the warning sign through a red triangle.

A Hazard will reference back to the Roads product through a Node Reference, Point Reference or Multiple Link Reference. For more information on these different types of Network References, see the common attribution page.

Hazard attributes

A location where a threat is imposed and caution should be taken.

id

Unique identifier, for Hazard this is a TOID.

• Attribute name: id

• Type: CharacterString

• Size: 20

• Multiplicity: [1]

identifier

Uniform Resource Identifier.

• Attribute name: identifier

• 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. Note: The time part is always set to zero.

• Attribute name: beginLifespanVersion

• Type: DateTime

• Multiplicity: [1]

networkRef

Spatial reference of the network-related property.

• Attribute name: networkRef

• Type: NetworkReference

• Multiplicity: [1..*]

validFrom

The time when the transport property started to exist in the real world. Note: The time part is always set to zero.

• Attribute name: validFrom

• Type: DateTime

• Multiplicity: [1]

hazard

Classification of the type of risk that applies that may impact choice of route or where caution should be observed.

• Attribute name: hazard

• Type: HazardTypeValue

• Size: 15

• Multiplicity: [1]

description

Additional information describing the hazard.

• Attribute name: description

• Type: CharacterString

• Size: 50

• Multiplicity: [0..1]

reasonForChange

The reason for a change made to a feature.

• Attribute name: reasonForChange

• Type: ChangeValue

• Size: 32

• Multiplicity: [1]

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

Code List: ChangeValue

The OS MasterMap Highways Network – RAMI can be ordered as either full supply or change-only update (COU). The GML structure for full supply and COU is 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.

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 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 as follows:

• <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 of the different types of transactions.

Supplied formats

OS MasterMap Highways Network – RAMI is supplied in two formats: Geography Markup Language (GML 3.2.1) and GeoPackage. All formats are compressed into a regular zip file (.ZIP).

The UseTypeValue is used to describe exceptions to a specific use, for example, no entry except for access. This code list is used for the property ‘use’ within the data type VehicleQualifier. The following table lists the codes which can be found.

Code List: UseTypeValue

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 Roads product through Network Reference and will reference a Street Feature. Features which are a partial reference will provide a Network Reference Location. For more information on Network References see .

SpecialDesignation attributes

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

id

Unique identifier.

• Attribute name: id

• Type: CharacterString

• Size: 17

• Multiplicity: [1]

identifier

Uniform Resource Identifier.

• Attribute name: identifier

• Type: CharacterString

• Size: 35

• Multiplicity: [1]

inspireId

External object identifier of the spatial object.

• Attribute name: inspireId

• Multiplicity: [0..1]

beginLifespanVersion

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]

networkRef

Spatial reference of the network-related property.

• Attribute name: networkRef

• Type: NetworkReference

• Multiplicity: [1..*]

validFrom

The time when the transport property started to exist in the real world. Note: The time part is always set to zero.

• Attribute name: validFrom

• Type: DateTime

• Multiplicity: [1]

validTo

The time from which the transport property no longer exists in the real world. Note: The time part is always set to zero.

• Attribute name: validTo

• Type: DateTime

• Multiplicity: [0..1]

designation

Type of Special Designation.

• Attribute name: designation

• Size: 65

• Multiplicity: [1]

description

Additional information describing the special designation.

• Attribute name: description

• Type: CharacterString

• Size: 250

• Multiplicity: [0..1]

timeInterval

Time period to which the restriction applies.

• Attribute name: timeInterval

• Multiplicity: [0..1]

contactAuthority

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

• Attribute name: contactAuthority

• Multiplicity: [0..1]

partialReference

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

• Attribute name: partialReference

• Type: Boolean

• Size: 5

• Multiplicity: [1]

reasonForChange

The reason for a change made to a feature.

• Attribute name: reasonForChange

• Size: 32

• 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 in Highways in England and Wales and the in Scotland.

A Reinstatement feature will reference back to the Road Network through a Network Reference and will reference a Street Feature. Features which are a partial reference will provide a Network Reference Location. For more information on Network References see .

Reinstatement attributes

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

id

Unique identifier.

• Attribute name: id

• Type: CharacterString

• Size: 17

• Multiplicity: [1]

identifier

Uniform Resource Identifier.

• Attribute name: identifier

• Type: CharacterString

• Size: 35

• Multiplicity: [1]

inspireId

External object identifier of the spatial object.

• Attribute name: inspireId

• Multiplicity: [0..1]

beginLifespanVersion

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]

networkRef

Spatial reference of the network-related property.

• Attribute name: networkRef

• Type: NetworkReference

• Multiplicity: [1..*]

validFrom

The time when the transport property started to exist in the real world. Note: The time part is always set to zero.

• Attribute name: validFrom

• 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

• Size: 51

• Multiplicity: [1]

partialReference

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

• Attribute name: partialReference

• Type: Boolean

• Size: 5

• Multiplicity: [1]

reasonForChange

The reason for a change made to a feature.

• Attribute name: reasonForChange

• Size: 32

• Multiplicity: [1]

The NamedDayValue is used to name specific days a restriction may apply. This code list is used for the property ‘namedDay’ within the data type DayPropertyType. The following table lists the codes which can be found.

Code List: NamedDayValue

The VehicleTypeValue is used to describe exceptions to specific vehicles, for example no access, except for buses. This code list is used for the property ‘vehicle’ within the data type VehicleQualifier. The following table lists the codes which can be found.

Code List: VehicleTypeValue

The NamedDateValue is used to name specific dates a restriction may apply. This code list is used for the property ‘namedDate’ within the data type TemporalPropertyType. The following table lists the codes which can be found.

Code List: NamedDateValue

The NamedTimeValue is used to name specific time periods when a restriction may apply. This code list is used for the property ‘namedTime’ within the data type TimePropertyType. The following table lists the codes which can be found.

Code List: NamedTimeValue

The NamedPeriodValue is used to name specific periods when a restriction may apply. This code list is used for the property ‘namedPeriod’ within the data type DayPropertyType. The following table lists the codes which can be found.

Code List: NamedPeriodValue

The LoadTypeValue is used to describe exceptions to specific loads a vehicle may carry. This code list is used for the property ‘load’ within the data type VehicleQualifier. The following table lists the codes which can be found.

Code List: LoadTypeValue

The Hazard feature type has the property ‘hazard’, which has the type HazardTypeValue. The following table identifies the codes used to populate this field.

Code List: HazardTypeValue

The TurnRestriction feature type has the property ‘restriction’, which has the type TurnRestrictionValue. The following table identifies the codes used to populate this field.

Code List: TurnRestrictionValue

Prohibitive instruction (signs with red circles) or positive instruction (signs with blue circles) for regulating manoeuvres or turns.

The AccessRestriction feature type has a property of ‘restriction’, which has the type AccessRestrictionValue. The following table describes the codes which will be used to populate this field and the description for each code.

Code List: AccessRestrictionValue

Types of access restrictions for a transport element.

The RestrictionForVehicles feature type has the property ‘restrictionType’, which has the type RestrictionTypeValue. The following table identifies the codes used to populate this field and a description for each code.

Code List: RestrictionTypeValue

Possible restrictions on vehicles that can access a transport element. http://inspire.ec.europa.eu/codelist/RestrictionTypeValue/

The HighwayDedication feature has the field ‘dedication’, which has the value populated from DedicationValue. The following table identifies the codes used to populate this field and a description for each code. These codes conform to the legal categories of highway as defined in the Highway Act 1980 and Countryside and Rights of Way Act 2000, with the exception of No Dedication Or Dedication Unknown.

Dedications indicate the legal access status for a given feature only; no indication as to its physical accessibility is made in this attribute.

Code List: DedicationValue

The Structure and RestrictionForVehicles feature type has the property ‘structure’, which has the type StructureTypeValue. The following table identifies the codes used to populate this field.

Code List: StructureTypeValue

The Reinstatement feature type has the property ‘reinstatementType’, which has the type ReinstatementTypeValue. The following table identifies the codes used to populate this field.

Code List: ReinstatementTypeValue

Features which use either Point Referencing, Link Referencing or Multiple Link Referencing will include an applicableDirection attribute. The LinkDirectionValue code list are the codes used to populate this attribute.

Code List: LinkDirectionValue

List of values for directions relative to a link.

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

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

Code List: MaintenanceValue