Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
The data is supplied as a link and node model similar to that used for the OS MasterMap Highways Networks products.
Route Links represent the general alignment of roads, tracks, paths and rights of way and Route Nodes are used to record the connectivity between links explicitly. A Route feature, that records collections of links or link sets, is used to record recognised named routes as single features.
OS Detailed Path Network contains three feature types (Route, RouteLink and RouteNode); the product's structure is demonstrated in Figure 1.
A Route is a feature representing a named entity that forms a recognised and signed route that the public can use. For example, a National Trail, such as the Pennine Way, or one of Scotland’s Great Trails, such as the West Highland Way.
A route can include references to different types of RouteLink, for example, a route may include sections of paths, tracks and public roads to create a continuous named trail.
The Route feature is not included in the vector tiles format, as these would directly overlay and replicate the RouteLink features referenced by a single route.
See the Route feature type page for more details.
A RouteLink is a feature that represents all or part of a road, track, path or right of way that can be used by pedestrians, cyclists and horse riders.
See the RouteLink feature type page for more details.
A RouteNode is a feature at the end of one or more RouteLinks. It allows software to quickly identify connections by using references to the unique identifier. The RouteNode also indicates:
The junction of three or more RouteLink features.
A change in real-world information (for example, the route type) that requires the creation of two RouteLink features with different attribution.
The start or end of a RouteLink feature.
See the RouteNode feature type page for more details.
This technical specification provides detailed technical information about OS Detailed Path Network. It is targeted at technical users and software developers.
The OS Detailed Path Network product is a topologically connected link and node network for roads, tracks, paths and rights of way within the National Parks of Great Britain. The product has been created from a number of existing Ordnance Survey data sources, including OS MasterMap Topography Layer, OS MasterMap Highways Network, 1:25 000 Scale Colour Raster, OS Terrain 5 and OS Terrain 50. The data is intended to provide sufficient detail for routing pedestrians, cyclists and horse riders when using mobile devices, with a typical positional accuracy of 10m.
OS Detailed Path Network is a derived product that has been designed with consideration of the Transport Networks Data Specification, although INSPIRE does not apply to off road transport. Due to the process of deriving OS Detailed Path Network, feature instances and their identifiers will be regenerated at each data refresh.
This technical specification includes the following sections:
The LevelCode value is used to indicate when a route is above or below normal ground level. The attribute is only applied where the level difference extends for distances greater than approximately 50m.
Routes that cross at different levels are not split at the intersection; those that are in tunnels or on bridges less than 50m long are given the default LevelCode attribute of Surface Level.
The LevelCode value is used to indicate when a route is above or below normal ground level. The attribute is only applied where the level difference extends for distances greater than approximately 50m.
Routes that cross at different levels are not split at the intersection; those that are in tunnels or on bridges less than 50m long are given the default LevelCode attribute of Surface Level.
Above surface level on structure – example
Below surface level tunnel – example
Non Motorised Vehicular Route Network
Route usable by pedestrians, cyclists and ridden horses.
Surface Level
The route is at the same level as the surrounding terrain. This is the default value for RouteLink features.
Above Surface Level On Structure
The RouteLink is supported or suspended above ground level on a manmade structure that extends for more than 50m.
For example, a road, track or path may be on a bridge, footbridge or viaduct.
Below Surface Level Tunnel
The route passes through a specially built construction underneath the normal terrain surface primarily to avoid or reduce the effect of the terrain surface or to avoid an obstruction such as a river or mountain and extends for more than 50m.
Junction
The point where three or more RouteLink features intersect at the same physical level where a choice of route is available.
Pseudo
A node which represents a point where one or more attributes of the RouteLink features connected to it change their value.
Terminal
A Terminal node represents the start or end of a set of RouteLink features.
This attribute indicates whether a RouteLink in England and Wales falls within an area of Access Land as depicted on Ordnance Survey 1:25 000 Scale Colour Raster mapping. For ease of use in routing applications, all RouteLink features in Scotland have the value also set to ‘TRUE’, even though the concept of Access Land is not relevant to routes in Scotland.
Only links with the following descriptiveTerm are eligible to have the accessLand attribute set to ‘TRUE’:
Alley
Path
Private Road
Track
This includes Access Land of the following types where access has been agreed:
CRoW land
Forest Enterprise
National Trust
Other Access
Section 16
Woodland Trust
No information on the type of Access Land is provided
The Extent of Access land has been simplified to create a routable network
There are sections of RouteLink features within areas of Access Land that are disconnected from the wider network. This is due to the differing resolutions of the network data and the underlying Access Land data.
Work is ongoing to reduce the incidence in future releases. In Scotland, this attribute is always set to ‘TRUE’.
In England and Wales, RouteLink features with this attribute set to ‘TRUE’ can be used by pedestrians.
For Private Roads where the only right to use is because the road is in Access Land, there may not be a right to use the road itself.
Other users may only use the route if another attribute indicates this is permissible. For example, a Track in Access Land may also be a Bridleway or there may be no other usage rights.
This section describes the three features available in the OS Detailed Path Network product (Route, RouteLink and RouteNode). The attributes associated with these feature types are listed below along with a brief description of their data properties.
The name of the attribute and what it is describing.
The nature of the attribute, for example, a numeric value or a logical indicator.
Values are given here to indicate the maximum length that you will find in the data, to aid in developing applications. Length is not constrained in the GML (Geography Markup Language).
Describes how many times this element is expected to be populated in the data. An attribute may be optional or mandatory, and it may have multiple occurrences. For example:
‘1’ – there must be a value.
‘2’ – there must be two values.
‘n’ – there may be one or more values.
‘0’ – population is optional.
These values may be used in combination.
An association identifies the relationship between features. The relationships are by reference only and the value will be the identifier of the referenced feature.
XML schemas are used to define and validate the format and content of the Geography Markup Language (GML). The GML v3.2.1 specification provides a set of schemas that define the GML feature constructs and geometric types. These are designed to be used as a basis for building application-specific schemas, which define the data content.
The ‘OS Detailed Path Network’ schema document defines the Namespace; this is defined in the XSD available on the .
These schemas make use of XSDs (XML schema definitions) produced by the W3C; these .
The application schema uses the following XML namespaces, for which definitions are available in the table below:
GML is designed to support a wide variety of capabilities, ranging from simple contextual mapping, such as OS Open Map, to products that include complex geometric property types or even spatial and temporal topology.
defines a restricted subset of GML, allowing scope for greater interoperability.
This product conforms to Simple Features Profile – Level 1.
gml
Xsi
Built into XML, see http://www.w3.org/TR/xmlschema-1/
xlink
This attribute indicates that part or all of the RouteLink passes through an area that may pose an impediment to passage for users or a level of risk.
Only RouteLink features with the descriptiveTerm of ‘No Physical Manifestation’ or ‘Path’ are eligible to have the potentialHazard attribute populated. Values may be multiple if appropriate.
For all other navigableLink features, this value is null.
Classification of hazardous terrain that may pose a risk or impediment to passage.
Boulders
The route passes through an area of boulders.
Cliff
The route passes over an area of cliffs.
Quarry Or Pit
The route passes through an active or disused excavation, for example, a pit or quarry.
Foreshore *
The route passes through an area that is covered by the tide at normal High Tides in England and Wales and an area that is covered by the tide at normal Spring High Tides in Scotland.
Note that paths near the High Water Mark may also be covered when tides are higher than the marks that Ordnance Survey record – normal High Tides in England and Wales and Spring High Tides in Scotland.
Marsh
The route passes through an area of marsh.
Mud
The route passes through an area of mud.
Sand
The route passes through an area of sand.
Scree
The route passes through an area of scree.
Shingle
The route passes through an area of shingle.
Spoil
The route passes through an area of deposited material.
Rock
The route passes over an area of surface rock.
Tidal Water
The route passes through an area of permanent tidal water.
Inland Water
The route passes through an area of permanent non-tidal water.
*Foreshore is added to all links that are intertidal.
A feature at the end of one or more RouteLink features that indicates either:
The junction of three or more RouteLink features
A change in the attribution resulting in the creation of two RouteLink feature
The start or end of a RouteLink feature
A unique identifier for a RouteNode. The ID is in the form of a GUID.
Attribute Name: featureID (GML), feature_id (GeoPackage), feature_id (Vector tiles)
Type: CharacterString
Length: 36
Multiplicity: [1]
A number assigned to uniquely identify and manage change. The versionID is used to distinguish between different revisions of a feature; within the set of all revisions, the versionID is unique.
Attribute Name: versionID (GML), version_id (GeoPackage)
Type: Number
Length: 20
Multiplicity: [1]
The date on which the version was created.
Attribute Name: versionDate (GML), version_date (GeoPackage)
Type: Date
Multiplicity: [1]
The primary classification attribute of a feature. For OS Detailed Path Network features, this value is set to “Non Motorised Vehicular Route Network”.
Attribute Name: descriptiveGroup (GML), descriptive_group (GeoPackage), descriptive_group (Vector tiles)
Length: 50
Multiplicity: [1]
The reason that a RouteLink feature has started or ended.
Attribute Name: descriptiveTerm (GML), descriptive_term (GeoPackage), descriptive_term (Vector tiles)
Length: 10
Multiplicity: [1]
Point geometry recording, in three dimensions, the position of the node where RouteLink features join, start or end.
Attribute Name: geometry (GML)
Type: GM_Point
Multiplicity: [1]
The table below shows a selection of the attribute mapping for GeoPackage Route feature attributes.
featureID
feature_id
versionID
version_id
versionDate
version_date
descriptiveGroup
descriptive_group
descriptiveTerm
descriptive_term
OS Detailed Path Network is supplied as one GeoPackage file per National Park area. GeoPackage (*.gpkg) is an open, standards-based data format, as is defined by the Open Geospatial Consortium (OGC). It is designed to be a lightweight format that can contain large amounts of varied and complex data in a single, easy to distribute and ready to use file.
GeoPackage can be used in most GIS software in its native format without translation. GeoPackage attribute names are not limited in length. A GeoPackage file has no size limit, and it supports raster, vector and database formats, making it a highly versatile solution.
The naming of attributes between GeoPackage and the Geography Markup Language (GML) file is very similar as GeoPackage files are not limited in the number of characters for an attribute name. Therefore, the tables included in this section map the GML attribute name to the attribute name in the GeoPackage files.
The GML contains an attribute which describes the geometry of the feature; this is not applicable for a GeoPackage file as they are separated by their geometry.
Detailed classification of type of feature that the RouteLink represents which the non-vehicular traffic can travel along or alongside.
In these examples, public rights of way exist but there is no physical disturbance on the ground. These are indicated with a descriptiveTerm value of 'No Physical Manifestation'.
If a RouteLink feature is attributed with one of the following DescriptiveTerm values, it can be considered as being along or alongside a road depending on the user:
A Road Minor Road
B Road Local Road
For example, the actual route may be along a pavement (if present), a verge or the carriageway itself dependent upon the user. A cyclist may use the road carriageway, a pedestrian the pavement, and a horse rider and their horse may use the verge.
The OS DPN data does not currently include information on the presence or absence of a pavement and / or verge.
The descriptiveTerm attribute indicates the nature of the route. Any right to use the RouteLink feature needs to be identified from the following attributes:
RightOfWayValue
NationalCycleRoute
OtherCycleRoute
RecreationalRoute
AccessLand
The description of a RouteLink with a descriptiveTerm of Local Road or Private Road does not indicate that any right of use by motorised vehicles exists.
A Route is a feature representing a named entity that forms a recognised and signed route that the public can use.
The following sub-sections provide details about the attributes included with this feature, their data types in the different output formats, and other important metadata about them.
A unique identifier assigned to a Route. The ID is in the form of a GUID.
Attribute Name: featureID (GML), feature_id (GeoPackage), Not provided (Vector tiles)
Type: CharacterString
Length: 36
Multiplicity: [1]
A number assigned to uniquely identify and manage change. The versionID is used to distinguish between different revisions of a feature and within the set of all revisions, the versionID is unique.
Attribute Name: versionID (GML), version_id (GeoPackage), Not provided (Vector tiles)
Type: Number
Length: 20
Multiplicity: [1]
The date on which the feature was last edited.
Attribute Name: versionDate (GML), version_date (GeoPackage), Not provided (Vector tiles)
Type: Date
Multiplicity: [1]
The primary classification attribute of a feature. For OS Detailed Path Network features, this value will always be set to "Non Motorised Vehicular Route Network".
Attribute Name: descriptiveGroup (GML), descriptive_group (GeoPackage), Not provided (Vector tiles)
Type:
Length: 50
Multiplicity: [1]
The recognised classification of the type of Route. For example, National Cycle Network, National Trail and Core Path.
Attribute Name: descriptiveTerm (GML), descriptive_term (GeoPackage), Not provided (Vector tiles)
Type:
Length: 50
Multiplicity: [1]
A proper name assigned to identify to the Route. If the proper name is defined in multiple languages, then each name is provided with an associated language qualifier. If the proper name is only defined in one language, then no language qualifier will be provided.
Attribute Name: name (GML), name (GeoPackage), Not provided (Vector tiles)
Type: LocalisedCharacterString
Length: 50
Multiplicity: [1..2]
Ordered list of references to the RouteLink features that comprise the Route.
Attribute Name: adopts (GML), adopts (GeoPackage), Not provided (Vector tiles)
Multiplicity: 1..*
A Road
Route is along or alongside a road classified by the Department for Transport as an A Road.
Alley
Route is along or alongside a vehicular route that provides secondary access to land or properties.
B Road
Route is along or alongside a road classified by the Department for Transport as a B Road.
Cableway
Route uses a form of scheduled cableway service, for example, a Cabin Cable Car, Chair Lift or Ski Tow.
As a minimum, it can be assumed that the cableway will carry pedestrians; the carriage of other users is not recorded.
Ferry Crossing
Route uses a boat or ship that provides a scheduled service to cross a body of water. As a minimum, it can be assumed that the ferry will carry pedestrians; the carriage of other users is not recorded.
Local Road
Route is along or alongside a road providing access to land or houses and is not generally intended for through traffic.
No right of use for motorised vehicles should be inferred, see Usage – further information.
Marked Or Signed Route With No Physical Manifestation
A route that has sufficient signage or waymarking to make it easy to follow, but where there is not a visible continuous or near continuous path to follow on the ground.
Minor Road
Route is along a public road or alongside a public road without a Department for Transport (DfT) classification of Motorway, A or B. Where the road connects to B and higher classification roads.
No Physical Manifestation
A linear route that is not easily identifiable on the ground but where there are rights of use.
For example, a legal bridleway across a field where there is no evidence along the route such as a worn strip of ground or a constructed surface of gravel or similar.
Path
Route is along a surface built for pedestrians or cyclists or created by the passage of pedestrians or cyclists over a natural surface.
See SurfaceTypeValue for further information.
Private Road
Route is along or alongside a road not maintained by a Highway Authority. Note: For Private Roads where the only right to use is because the road is in Access Land, there may not be a right to use the road itself. No right of use for motorised vehicles should be inferred; see Usage – further information. The right of use by pedestrians, cyclists and horses being ridden may be restricted; see RightOfWayValue
Towpath
A towpath is a way alongside the bank of a river used for inland navigation, or canal whose original purpose was to provide access in support of inland navigation.
Not populated in current release; where present, will be described as Path.
Track
Route is along an unmade way created by the passage of vehicles although no right of use by vehicles is implied. The right of use by pedestrians, cyclists and horses being ridden may be restricted; see RightOfWayValue
The table below shows a selection of the attribute mapping for GeoPackage RouteLink feature attributes.
featureID
feature_id
versionID
version_id
versionDate
version_date
descriptiveGroup
descriptive_group
descriptiveTerm
descriptive_term
surfaceType
surface_type
physicalLevel
physical_level
roadNumber
road_number
name
name
alternativeName
alternative_name
rightofUse
right_of_use
adoptedByRecreationalRoute
adopted_by_recreational_route
adoptedByNationalCycleRoute
adopted_by_national_cycle_route
adoptedByOtherCycleRoute
adopted_by_other_cycle_route
withinAccessLand
within_access_land
crossesDangerArea
crosses_danger_area
potentialHazardCrossed
potential_hazard_crossed
verticalGain
vertical_gain_in_direction
verticalGain
vertical_gain_against_direction
planimetricLength
planimetric_length
surfaceLength
surface_length
startNode
start_node
endNode
end_node
The table below shows a selection of the attribute mapping for GeoPackage RouteNode feature attributes.
featureID
feature_id
versionID
version_id
versionDate
version_date
descriptiveGroup
descriptive_group
descriptiveTerm
descriptive_term
This page provides examples of the different GML structure for Full Supply orders and COU orders and the transactions within.
An example of the Full Supply GML including the opening and closing tags:
<os:FeatureCollection>
<os:FeatureMember>
<highway:RoadNode gml:id="osgb5000005193042483">
<gml:identifier codeSpace="http://inspire.jrc.ec.europa.eu/ids">http://data.os.uk/id/5000005193042483</gml:identifier>
<net:beginLifespanVersion>2017-01-13T00:00:00.000</net:beginLifespanVersion>
<net:inspireId>
<base:Identifier>
<base:localId>5000005193042483</base:localId>
<base:namespace>http://data.os.uk/</base:namespace>
</base:Identifier>
</net:inspireId>
<net:inNetwork xlink:href="#OSHighwayNetwork"/>
<net:geometry>
<gml:Point srsName="urn:ogc:def:crs:EPSG::27700" gml:id="LOCAL_ID_6">
<gml:pos>611319.332 231278.275</gml:pos>
</gml:Point>
</net:geometry>
<tn:validFrom nilReason="unknown" xsi:nil="true"/>
<tn-ro:formOfRoadNode xlink:title="junction" xlink:href="http://inspire.ec.europa.eu/codelist/FormOfRoadNodeValue/junction"/>
<highway:reasonForChange codeSpace="http://www.os.uk/xml/codelists/ChangeTypeValue.xml">New</highway:reasonForChange>
<highway:relatedRoadArea xlink:href="#osgb5000005193041468"/>
</highway:RoadNode>
</os:FeatureMember >
</os:FeatureCollection An example of the COU GML including opening and closing tags and the different types of transactions:
<os:Transaction>
<os:insert>
<highway:RoadNode gml:id="osgb5000005193042483">
<gml:identifier codeSpace="http://inspire.jrc.ec.europa.eu/ids">http://data.os.uk/id/5000005193042483</gml:identifier>
<net:beginLifespanVersion>2017-01-13T00:00:00.000</net:beginLifespanVersion>
<net:inspireId>
<base:Identifier>
<base:localId>5000005193042483</base:localId>
<base:namespace>http://data.os.uk/</base:namespace>
</base:Identifier>
</net:inspireId>
<net:inNetwork xlink:href="#OSHighwayNetwork"/>
<net:geometry>
<gml:Point srsName="urn:ogc:def:crs:EPSG::27700" gml:id="LOCAL_ID_6">
<gml:pos>611319.332 231278.275</gml:pos>
</gml:Point>
</net:geometry>
<tn:validFrom nilReason="unknown" xsi:nil="true"/>
<tn-ro:formOfRoadNode xlink:title="junction" xlink:href="http://inspire.ec.europa.eu/codelist/FormOfRoadNodeValue/junction"/>
<highway:reasonForChange codeSpace="http://www.os.uk/xml/codelists/ChangeTypeValue.xml">New</highway:reasonForChange>
<highway:relatedRoadArea xlink:href="#osgb5000005193041468"/>
</highway:RoadNode>
</os:insert>
<os:replace>
<highway:RoadNode gml:id="osgb4000000003855390">
<gml:identifier codeSpace="http://inspire.jrc.ec.europa.eu/ids">http://data.os.uk/id/4000000003855390</gml:identifier>
<net:beginLifespanVersion>2016-08-21T00:00:00.000</net:beginLifespanVersion>
<net:inspireId>
<base:Identifier>
<base:localId>4000000003855390</base:localId>
<base:namespace>http://data.os.uk/</base:namespace>
</base:Identifier>
</net:inspireId>
<net:inNetwork xlink:href="#OSHighwayNetwork"/>
<net:geometry>
<gml:Point srsName="urn:ogc:def:crs:EPSG::27700" gml:id="LOCAL_ID_2497055">
<gml:pos>398309.376 865124.714</gml:pos>
</gml:Point>
</net:geometry>
<tn:validFrom nilReason="unknown" xsi:nil="true"/>
<tn-ro:formOfRoadNode xlink:title="junction" xlink:href="http://inspire.ec.europa.eu/codelist/FormOfRoadNodeValue/junction"/>
<highway:reasonForChange codeSpace="http://www.os.uk/xml/codelists/ChangeTypeValue.xml">New</highway:reasonForChange>
<highway:relatedRoadArea xlink:href="#osgb1000002063990526"/>
</highway:RoadNode>
</os:replace>
<os:delete>
<highway:RoadNode gml:id="osgb4000000003334901">
<gml:identifier codeSpace="http://inspire.jrc.ec.europa.eu/ids">http://data.os.uk/id/4000000003334901</gml:identifier>
<net:beginLifespanVersion>2017-01-13T00:00:00.000</net:beginLifespanVersion>
<net:inspireId>
<base:Identifier>
<base:localId>4000000003334901</base:localId>
<base:namespace>http://data.os.uk/</base:namespace>
</base:Identifier>
</net:inspireId>
<net:endLifespanVersion>2017-01-13T00:00:00.000</net:endLifespanVersion>
<net:inNetwork xlink:href="#OSHighwayNetwork"/>
<net:geometry>
<gml:Point srsName="urn:ogc:def:crs:EPSG::27700" gml:id="LOCAL_ID_0">
<gml:pos>215328.243 943956.030</gml:pos>
</gml:Point>
</net:geometry>
<tn:validFrom nilReason="unknown" xsi:nil="true"/>
<tn-ro:formOfRoadNode xlink:title="road end" xlink:href="http://inspire.ec.europa.eu/codelist/FormOfRoadNodeValue/roadEnd"/>
<highway:reasonForChange codeSpace="http://www.os.uk/xml/codelists/ChangeTypeValue.xml">End Of Life</highway:reasonForChange>
<highway:relatedRoadArea xlink:href="#osgb9999"/>
</highway:RoadNode>
</os:delete>
<os:delete>
<highway:RoadNode gml:id="osgb4000000003336706">
<gml:identifier codeSpace="http://inspire.jrc.ec.europa.eu/ids">http://data.os.uk/id/4000000003336706</gml:identifier>
<net:beginLifespanVersion>2017-02-17T00:00:00.000</net:beginLifespanVersion>
<net:inspireId>
<base:Identifier>
<base:localId>4000000003336706</base:localId>
<base:namespace>http://data.os.uk/</base:namespace>
</base:Identifier>
</net:inspireId>
<net:endLifespanVersion>2017-02-17T00:00:00.000</net:endLifespanVersion>
<net:inNetwork xlink:href="#OSHighwayNetwork"/>
<net:geometry>
<gml:Point srsName="urn:ogc:def:crs:EPSG::27700" gml:id="LOCAL_ID_16">
<gml:pos>287295.241 935655.346</gml:pos>
</gml:Point>
</net:geometry>
<tn:validFrom nilReason="unknown" xsi:nil="true"/>
<tn-ro:formOfRoadNode xlink:title="junction" xlink:href="http://inspire.ec.europa.eu/codelist/FormOfRoadNodeValue/junction"/>
<highway:reasonForChange codeSpace="http://www.os.uk/xml/codelists/ChangeTypeValue.xml">Modified Geometry</highway:reasonForChange>
<highway:relatedRoadArea xlink:href="#osgb1000000288453345"/>
</highway:RoadNode>
</os:delete>
</os:Transaction>State of a surface in the context of the origin of the surface and resistance to environmental elements.
Made Sealed
A constructed surface, commonly mineral based, that consists of a solid material that is bonded (i.e. is not loose), such as asphalt or concrete.
Made Unknown
A constructed surface, commonly mineral based, that may be bonded or loose. This value is used where the revision method employed does not allow it to be differentiated into ‘Made Sealed’ or ‘Made Unsealed’.
Made Unsealed
A constructed surface, commonly mineral based, that consists of an un-bonded surface (i.e. the material is loose), such as gravel (including self- binding gravel), cinder or hoggin. Also used to describe surfaces that are bonded but which have been employed as a mesh / grid or similar form to allow vegetation to grow and water to drain through the surface.
Unmade
A surface that has not been constructed but has evolved through use by pedestrians, cyclists, horses being ridden, or motorised vehicles, and where the use has removed or minimised the natural vegetation and fully or partly exposed the underlying mineral surface and / or mud.
As a general note, it can be problematic to precisely differentiate between surface types. For example, the difference between an unsealed road and a track is open to interpretation. The following images illustrate typical examples of different surface types.
A RouteLink is a feature that represents all or part of a road, track, path or right of way that can be used by pedestrians, cyclists or horses being ridden.
A unique identifier for a RouteLink. The ID is in the form of a GUID.
Attribute Name: featureID (GML), feature_id (GeoPackage), feature_id (Vector tiles)
Type: CharacterString
Length: 36
Multiplicity: [1]
A number assigned to uniquely identify and manage change. The versionID is used to distinguish between different revisions of a feature and within the set of all revisions; the versionID is unique.
Attribute Name: versionID (GML), version_id (GeoPackage), Not provided (Vector tiles)
Type: Number
Length: 20
Multiplicity: [1]
The date on which the version was created.
Attribute Name: versionDate (GML), version_date (GeoPackage), Not provided (Vector tiles)
Type: Date
Multiplicity: [1]
The primary classification attribute of a feature. For OS Detailed Path Network features, this value is set to "Non Motorised Vehicular Route Network".
Attribute Name: descriptiveGroup (GML), descriptive_group (GeoPackage), descriptive_group (Vector tiles)
Type:
Length: 50
Multiplicity: [1]
Further classification indicating the type way that the RouteLink alignment is along or alongside. See RouteLinkDescriptiveTermValue for more information.
Attribute Name: descriptiveTerm (GML), descriptive_term (GeoPackage), descriptive_term (Vector tiles)
Type:
Length: 50
Multiplicity: [1]
Type of material used to protect the surface of the way.
Attribute Name: surfaceType (GML), surface_type (GeoPackage), surface_type (Vector tiles)
Type:
Length: 30
Multiplicity: [0..1]
Relative vertical position of the RouteLink in relation to the ground surface.
Attribute Name: physicalLevel (GML), physical_level (GeoPackage), physical_level (Vector tiles)
Type:
Length: 30
Multiplicity: [1]
Official number assigned to identify the road by the Department for Transport (DfT), for example, A64
Attribute Name: roadNumber (GML), road_number (GeoPackage), road_number (Vector tiles)
Type: CharacterString
Length: 5
Multiplicity: [0..1]
A proper name in common use that applies to the RouteLink, the same name may apply to more than one RouteLink. If the proper name is defined in multiple languages, then each name will be provided with an associated language qualifier. If the proper name is only defined in one language, then no language qualifier will be provided.
Attribute Name: name (GML), name (GeoPackage), name (Vector tiles)
Type: LocalisedCharacterString
Length: 40
Multiplicity: [0..2]
A second, different, proper name that applies to the RouteLink. If the alternative proper name is defined in multiple languages, then each name will be provided with an associated language qualifier. If the alternative proper name is only defined in one language, then no language qualifier will be provided.
Attribute Name: alternativeName (GML), alternative_name (GeoPackage), alternative_name (Vector tiles)
Type: LocalisedCharacterString
Length: 40
Multiplicity: [0..2]
The designated rights of access that apply to the RouteLink. These may be legally designated rights such as Public Rights of Way or may be public rights of access across private lands allowed by the Landowner (for example, Permissive Paths).
Attribute Name: rightOfUse (GML), right_of_use (GeoPackage), right_of_use (Vector tiles)
Type:
Length: 60
Multiplicity: [1]
Indicates whether the link is part of a recognised recreational route.
Attribute Name: adoptedByRecreationalRoute (GML), adopted_by_recreational_route (GeoPackage), adopted_by_recreational_route (Vector tiles)
Type: Boolean
Length: 5
Multiplicity: [1]
Indicates whether the link is part of the National Cycle Network.
Attribute Name: adoptedByNationalCycleRoute (GML), adopted_by_national_cycle_route (GeoPackage), adopted_by_national_cycle_route (Vector tiles)
Type: Boolean
Length: 5
Multiplicity: [1]
Indicates whether the link is part of a recognised cycle route that is not part of the National Cycle Network.
Attribute Name: adoptedByOtherCycleRoute (GML), adopted_by_other_cycle_route (GeoPackage), adopted_by_other_cycle_route (Vector tiles)
Type: Boolean
Length: 5
Multiplicity: [1]
Indicates whether the link falls within an area of Access Land as represented on Ordnance Survey Explorer mapping. See Access Land scope for more information.
Attribute Name: withinAccessLand (GML), within_access_land (GeoPackage), within_access_land (Vector tiles)
Type: Boolean
Length: 5
Multiplicity: [1]
Indicates whether the RouteLink intersects a Ministry of Defence firing range.
Attribute Name: crossesDangerArea (GML), crosses_danger_area (GeoPackage), crosses_danger_area (Vector tiles)
Type: Boolean
Length: 5
Multiplicity: [1]
Indication that the RouteLink passes through an area that may pose an impediment to passage or a level of risk. For example, the RouteLink is in close proximity to a cliff or the RouteLink passes through an area of scree or shingle which may be difficult or dangerous to traverse. See PotentialHazardValue for more information.
Attribute Name: potentialHazardCrossed (GML), potential_hazard_crossed (GeoPackage), potential_hazard_crossed (Vector tiles)
Type:
Length: 20
Multiplicity: [0..*]
Vertical gain is calculated from the three-dimensional geometry to define the total ascent experienced when passing along a routeLink feature. The value is expressed both with and against the direction of digitising.
Attribute Name: verticalGain (GML), vertical_gain_in_direction (GeoPackage), vertical_gain_in_direction (Vector tiles)
Type: VerticalGainType
Multiplicity: [1]
Measurement of the length of the RouteLink along a planar surface.
Attribute Name: planimetricLength (GML), planimetric_length (GeoPackage), planimetric_length (Vector tiles)
Type: Length
Multiplicity: [1]
Measurement of the length of the RouteLink along the three-dimensional surface used to create the three-dimensional geometry.
Attribute Name: surfaceLength (GML), surface_length (GeoPackage), surface_length (Vector tiles)
Type: Length
Multiplicity: [1]
References the node at the start of the RouteLink feature that is coincident with the first vertex.
Attribute Name: startNode (GML), start_node (GeoPackage), Not provided (Vector tiles)
Multiplicity: 1
References the node at the end of the RouteLink feature that is coincident with the last vertex.
Attribute Name: endNode (GML), end_node (GeoPackage), Not provided (Vector tiles)
Multiplicity: 1
The table below shows selection of attribute mapping for Vector Tiles RouteLink feature attributes.
As the product is created from existing OS data, the quality of the OS Detailed Path Network data depends on the quality of the compilation data.
Our focus has been to provide a connected network with the attribution required to facilitate routing.
The positional accuracy of OS Detailed Path Network has been designed to be usable with readily available GPS-enabled hardware that does not make use of real-time correction, such as mobile phones and personal navigation devices.
The typical device that the data will be used upon is positionally accurate to in plan.
The alignment of roads, tracks and paths has been sourced from Ordnance Survey large-scale data whose positional accuracy is typically between 2.4 and 8.9m (99% confidence level).
Sample data tracked using an ordinary mobile phone showed a correlation of 95% of GPS positions being within 10m of the RouteLink feature contained within the product.
Data only sourced from the 1:25 000 Scale Colour Raster will have a lower planimetric accuracy. This is because the processes of generalisation, exaggeration, selection and offsetting reduce the positional accuracy.
This applies to RouteLink features for rights of way and the extent of danger areas where there is not an Ordnance Survey large-scale data representation.
GPS devices may only provide coordinates using the WGS84 coordinate reference system (EPSG code 4979, although 4326 is often used also). The OS Detailed Path Network data is supplied using a combination of coordinates in the OSGB36 British National Grid system and heights relative to Ordnance Datum Newlyn (EPSG code 7405) for both the Geography Markup Language (GML) and GeoPackage formats. Note that the vector tiles format is supplied in Web Mercator (EPSG code 3857).
To allow the data to be used with positions from GPS devices, a transformation is required. The transformation can be applied to the OS Detailed Path Network data (to move it on to WGS84) or to the GPS coordinates (to provide positions in OSGB36 British National Grid). The choice may depend on the coordinate systems of any other datasets in use.
Given the difference that can ensue from using the incorrect coordinate reference system, care must be taken to use the appropriate transformation. A recommended transformation is the seven parameter one published in . This transformation is EPSG code 1314.
The positional accuracy of OS Detailed Path Network data has been designed to be usable with readily available GPS enabled hardware that does not make use of real-time correction, such as mobile phones and personal navigation devices. Typically, these devices are accurate to .
OS Detailed Path Network data has been heighted using the source data that was in turn used to create the OS Terrain 5 and OS Terrain 50 products – the accuracy of this data is expected to be +/- 6m.
The height data used to height the OS Detailed Path Network data was captured in a separate process to the network data. On occasion, there may be discrepancies where the height data has not captured the intricacies of the terrain. For example, along an embankment or locating the precise start and end of a tunnel. The result can be discrepancies in the height value of individual vertices.
These limitations should be considered when using the height values and related calculated attributes to create estimates of journey times and draw profiles.
The data includes all roads, tracks and paths contained within Ordnance Survey data and rights of way information contained on 1:25 000 Scale Colour Raster.
Changes to Roads are generally captured within six months of the change occurring.
Changes to Paths and Tracks are captured as part of a cyclic revision programme that completes every three to five years, using aerial photography as the main tool to identify change.
Changes to rights of way are updated when received from Local Highway Authorities or National Park Authorities, where they are responsible as legal custodians of the Definitive Map and Statement for Public Rights of Way.
Feature classifications are based upon Ordnance Survey datasets, including interpretation of aerial photography. This presents the following data capture limitations:
Surface descriptions may be limited to made and unmade surfaces.
Unmade paths in upland areas can be ambiguous and, consequently, are sometimes not captured.
Changes that have occurred in obscured areas, for example, under trees, can go unrecorded.
Values for proper names have been extracted from existing Ordnance Survey data. The coverage of language alternatives may not be as complete as it is in other datasets.
Length of lines is calculated and is not based on real-world measurement.
Three-dimensional capture is based on a terrain model that may not be entirely sympathetic with
OS Detailed Path Network data. For example, in the terrain model, disused railway cuttings will not have been explicitly modelled, and bridges and tunnels may not be entirely coincident with OS Detailed Path Network data; see .
The featureID, versionID and versionDate attributes have been included to support future developments of the product that would support change-only update (COU) and maintained identifiers. At present, the data is supplied as a complete replacement, and identifiers are not maintained between epochs of data supply.
featureID: This will be unique within each supply. The same feature in a future release will have a different value.
versionDate: This will be set to the date the product data was created.
Customer input on the desirability of COU and maintained identifiers in future releases is welcome.
Content
Attribute values are imposed by edit systems and tested using validation to comply with those in the schema.
Logical combinations of attributes are imposed by edit systems and tested using validation.
Basic topology is tested in the edit software and additional validation is applied to ensure the topology is correct.
The connectivity between features at the same and different levels is tested through validation and visual inspection.
verticalGain
vertical_gain_in_direction
verticalGain
vertical_gain_against_direction
planimetricLength
planimetric_length
surfaceLength
surface_length
startNode
*
endNode
*
Node
featureID
feature_id
versionID
*
versionDate
*
descriptiveGroup
descriptive_group
descriptiveTerm
descriptive_term
featureID
feature_id
versionID
*
versionDate
versionDate
descriptiveGroup
descriptive_group
descriptiveTerm
descriptive_term
surfaceType
surface_type
physicalLevel
physical_level
roadNumber
road_number
name
name
alternativeName
alternative_name
rightofUse
right_of_use
adoptedByRecreationalRoute
adopted_by_recreational_route
adoptedByNationalCycleRoute
adopted_by_national_cycle_route
adoptedByOtherCycleRoute
adopted_by_other_cycle_route
withinAccessLand
within_access_land
crossesDangerArea
crosses_danger_area
potentialHazardCrossed
potential_hazard_crossed
Rights of way information for England and Wales has been sourced from Ordnance Survey 1:25 000 Scale Colour Raster mapping and inferred from Ordnance Survey road network data.
The allowable uses for RightOfWayValue are summarised in the table below; this reflects the accepted legal rights for public rights of way. Further rights of use are also possible and are described in the Additional rights to use a RouteLink – England sub-section below.
In all circumstances, information from the Local Highway Authority takes precedence, and any local signage should always be observed. For example, temporary restrictions may exist that override rights of way or access rights in Access Land.
In Scotland, rights of way do exist, but they are not included within the OS Detailed Path Network product as for recreational purposes, they are superseded by rights under the Land Reform Act 2003 (see the Rights to use a RouteLink – Scotland sub-section below).
Classification of the designated rights of access and use assigned to the RouteLink.
Bridleway
A route where there is a right to travel on foot, on horseback, to lead a horse and to ride a bicycle
Pedestrians, horses, cyclists
Byway Open To All Traffic
A highway open to all traffic.
Pedestrians, horses, cyclists, motorised vehicles
Core Path
A route in Scotland identified as part of the Core Path network.
Not populated in release 1.
Not applicable
Footpath
A route where there is a right to travel on foot.
Pedestrians
None
A route where no permissive or conventional right of way has been identified. Use may be allowed if the route has been identified as a cycle route (see NationalCycleRoute, OtherCycleRoute), as part of a RecreationalRoute or as lying within an area of Access Land.
See NationalCycleRoute, OtherCycleRoute, part of a RecreationalRoute or as lying within an area of Access Land
Normal Permissible Uses
No known restrictions on pedestrians, cyclists or horses being ridden. Restrictions may apply to vehicles.
Pedestrians, horses, cyclists – used for public roads without a restriction
Other Route With Public Access
A route that is the responsibility of Local Highway Authorities and maintained at public expense. All Other Routes with Public Access (ORPAs) have rights for pedestrians. Beyond that, any particular ORPA may, or may not, have rights for cyclists and equestrians, and may or may not have rights for motor vehicles. OPRAs are sometimes known as unclassified unsurfaced roads (or unclassified country roads).
Pedestrians
Permissive Bridleway
A route where the landowner has permitted travel on foot, on horseback or leading a horse, and to ride a bicycle. This right may be withdrawn by the landowner.
Pedestrians, horses, cyclists
Permissive Path
A route where the landowner has permitted travel on foot. This right may be withdrawn by the landowner.
Pedestrians
Restricted Byway
A route open to all traffic except mechanically propelled vehicles. Formerly known as Road Used as Public Path (RUPP).
Pedestrians, horses, cyclists
Other rights may exist, but these will need to be determined from the Local Highway Authority.
Most RouteLink features with a descriptiveTerm of Local Road will have a RightOfUse value of ‘Normal Permissible Uses’. However, in some cases, a more restrictive value applies; when this is present, this more restrictive value should be used to determine who may use the route.
The preceding table summarises the type of user who may travel along a specific RouteLink in England and Wales where a right of way exists. The right to use a RouteLink may also be indicated by one or more of the following logical attributes in the table below being set to indicate:
adoptedByNationalCycleRoute
= TRUE
A link part of the National Cycle Network
Pedestrians, cyclists
adoptedByOtherCycleRoute =
TRUE
A link part of a Cycle Network that is not part of the National Cycle Network
Pedestrians, cyclists
adoptedByRecreationalRoute
= TRUE
A link part of a Recreational Route
Pedestrians
withinAccessLand = TRUE
A link within Access Land
Pedestrians. Note that for Private Roads where the only right to use is because the road is in Access Land, there may not be a right to use the road itself.
These values may co-exist, for example, a cycle route may pass through an area of Access Land and be coincident with a Restricted Byway.
For ease of use of the data in routing applications, all RouteLink features in Scotland have the value of the AccessLand attribute also set to ‘TRUE’ even though the concept of Access Land is not relevant to routes in Scotland.
In Scotland, the rights of access have been established by the Land Reform (Scotland) Act 2003; these are described in the Scottish Outdoor Access Code. The following is an extracted summary:
A summary of the access rights:
Everyone, whatever their age or ability, has access rights established by the Land Reform (Scotland) Act 2003. You only have access rights if you exercise them responsibly.
You can exercise these rights, provided you do so responsibly, over most land and inland water in Scotland, including mountains, moorland, woods and forests, grassland, margins of fields in which crops are growing, paths and tracks, rivers and lochs, the coast and most parks and open spaces. Access rights can be exercised at any time of the day or night.
You can exercise access rights for recreational purposes (such as pastimes, family and social activities, and more active pursuits like horse riding, cycling, wild camping and taking part in events), educational purposes (concerned with furthering a person’s understanding of the natural and cultural heritage), some commercial purposes (where the activities are the same as those done by the general public) and for crossing over land or water.
Existing rights, including public rights of way and navigation, and existing rights on the foreshore, continue.
The main places where access rights do not apply are:
Houses and gardens, and non-residential buildings and associated land
Land in which crops are growing
Land next to a school and used by the school
Sports or playing fields when these are in use and where the exercise of access rights would interfere with such use
Land developed and in use for recreation and where the exercise of access rights would interfere with such use
Golf courses (but you can cross a golf course provided you don’t interfere with any games of golf)
Places like airfields, railways, telecommunication sites, military bases and installations, working quarries and construction sites
Visitor attractions or other places which charge for entry
Local authorities can formally exempt land from access rights for short periods. Local authorities and some other public bodies can introduce byelaws.
Access rights do not extend to:
Being on or crossing land for the purpose of doing anything which is an offence, such as theft, breach of the peace, nuisance, poaching, allowing a dog to worry livestock, dropping litter, polluting water or disturbing certain wild birds, animals and plants
Hunting, shooting or fishing
Any form of motorised recreation or passage (except by people with a disability using a vehicle or vessel adapted for their use)
Anyone responsible for a dog which is not under proper control
Anyone taking away anything from the land for a commercial purpose
Statutory access rights do not extend to some places or to some activities that the public have enjoyed on a customary basis, often over a long period of time. Such access is not affected by the Land Reform (Scotland) Act 2003 and will continue.
Core Path
A route in Scotland identified as part of the Core Path network.
Not populated in current release.
European Long Distance Path
The European long-distance paths are a network of long-distance footpaths that traverse Europe. While most long-distance footpaths in Europe are located in just one country or region, each of these numbered European long-distance paths passes through many different countries.
The European long-distance paths were designated by the European Ramblers' Association.
Not populated in release 1.
National Cycle Network
A route which is part of the Sustrans National Cycle Network (NCN).
National Trail
An extensive route of national importance supported by Natural England, Natural Resources Wales or Scottish Natural Heritage.
Recreational Path
A named route that:
is at least 10km long;
is fully and distinctively waymarked;
is endorsed by all of the local authorities the route traverses
is supported by a Guidebook or Leaflet; and
has a responsible person who informs Ordnance Survey of future route amendments.
Scotland's Great Trail
Great Trails, formerly Long-distance routes, are named routes in Scotland established under the Countryside (Scotland) Act of 1967 and are nominated by Scottish Natural Heritage.
Not populated in release 1.
This section describes the structured data type which makes up the OS Detailed Path Network product.
The attributes associated with these data types are listed below along with a brief description of their data properties.
The name of the attribute and what it is describing.
The nature of the attribute, for example a numeric value or a code list value.
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.
OS Detailed Path Network is supplied as a national vector tiles set in a single MBTiles file. This is a lightweight set of tiles that are efficient and fast to render in your software, and which provide high- resolution data and give a seamless experience when zooming in and out. The data is supplied in Web Mercator projection (ESPG:3857).
The naming of attributes between vector tiles and the Geography Markup Language (GML) file is very similar as the vector tiles set within the MBTiles file is not limited in the number of characters for an attribute name. The tables included in this section map the GML attribute name to the attribute name in the vector tiles. Please note that the use of an asterisk symbol (*) in the following tables indicates that a particular attribute is not mapped to vector tiles.
The vector tiles schema is detailed in the following table. In the zoom levels columns within the table, the letter N indicates that the specified layer and attribute are not mapped within that zoom level, whereas the letter Y indicates that the specified later and attribute are mapped within that zoom level.
feature_id
N
Y
Y
Y
Y
Y
Y
Y
descriptive_group
N
Y
Y
Y
Y
Y
Y
Y
descriptive_term
N
Y
Y
Y
Y
Y
Y
Y
surface_type
N
Y
Y
Y
Y
Y
Y
Y
physical_level
N
Y
Y
Y
Y
Y
Y
Y
road_number
N
Y
Y
Y
Y
Y
Y
Y
name
N
Y
Y
Y
Y
Y
Y
Y
alternative_name
N
Y
Y
Y
Y
Y
Y
Y
right_of_use
N
Y
Y
Y
Y
Y
Y
Y
adopted_by_recreational_route
N
Y
Y
Y
Y
Y
Y
Y
adopted_by_national_cycle_route
N
Y
Y
Y
Y
Y
Y
Y
adopted_by_other_cycle_route
N
Y
Y
Y
Y
Y
Y
Y
within_access_land
N
Y
Y
Y
Y
Y
Y
Y
crosses_danger_area
N
Y
Y
Y
Y
Y
Y
Y
potential_hazard_crossed
N
Y
Y
Y
Y
Y
Y
Y
vertical_gain_in_direction
N
Y
Y
Y
Y
Y
Y
Y
vertical_gain_against_direction
N
Y
Y
Y
Y
Y
Y
Y
planimetric_length
N
Y
Y
Y
Y
Y
Y
Y
surface_length
N
Y
Y
Y
Y
Y
Y
Y
feature_id
N
Y
Y
Y
Y
Y
Y
Y
descriptive_group
N
Y
Y
Y
Y
Y
Y
Y
descriptive_term
N
Y
Y
Y
Y
Y
Y
Y
Describes the total ascent experienced when passing along a RouteLink feature in either direction.
Total increase in height experienced when passing along the link from the start to the end.
Type: Measure
Multiplicity: [1]
Total increase in height experienced when passing along the link from the end to the start.
Type: Measure
Multiplicity: [1]
See also Height and Planimetric Correlation in data quality.
The table below shows selection of attribute mapping for Vector Tiles Route feature attributes.
verticalGain
vertical_gain_in_direction
verticalGain
vertical_gain_against_direction
planimetricLength
planimetric_length
surfaceLength
surface_length
startNode
*
endNode
*
Node
featureID
feature_id
versionID
*
versionDate
*
descriptiveGroup
descriptive_group
descriptiveTerm
descriptive_term
The following code lists contain the permitted values for each attribute and an explanation where required:
