OS DPN attribution is designed to provide partners and developers with the detailed information required to enable the selection of a suitable route for specific users and their chosen method of travel. Depending on the type of user, the attribution also enables journey time estimation.

Detailed information on OS DPN attribution can be found in the OS Detailed Path Network Technical Specification document which is available on the OS DPN Product Support page of the OS website.

The following headings detail the types of information that OS DPN attribution provides.

Names

The names of sections of road, track or path are included, where known, to provide the partner or developer with the means to deliver additional information to the user. For example, walk along “High Street” and turn into “Canal Walk”.

Usability of a route

The physical usability of a route, for example, the type of route:

• Description of route – For example, an A or B road classification, a track or a path.

• Surface type – The nature of the material the route is made of, for example, sealed or unmade surfaces.

Access rights for a route

The access rights for a route reflect the permissions granted to travel along it. This is usually based upon the mode of travel, for example:

• Public rights of way (England and Wales only)

• Access land (England and Wales only)

Difficulty of a route

The difficulty of a route depends upon many factors; some of these factors have been included within the data. This attribution allows a developer or partner to select routes appropriate for specific users, dependent upon their level of fitness and expertise in outdoor navigation.

Attribution is provided to inform the user as to the potential difficulty of the route in the following way:

• Geometry – Provided as three-dimensional coordinates.

• Planimetric length – The two-dimensional length.

• Surface length – The three-dimensional length.

• Cumulative vertical gain – Total ‘climb’ when travelling along a RouteLink.

• Problematic terrain – An indication of when a route may pass through an area that could pose a risk or impediment to passage, for example, proximity to a cliff or a scree slope.

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.

Feature type Attribute information

Name and Definition

The name of the attribute and what it is describing.

Attribute Type

The nature of the attribute, for example, a numeric value or a logical indicator.

Length

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

Multiplicity

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.

Association

An association identifies the relationship between features. The relationships are by reference only and the value will be the identifier of the referenced feature.

OS Detailed Path Network is a fully-connected, heighted path network covering Britain’s National Parks. Create off-road navigation apps, build exciting navigation websites and apps that help your users find great routes and stay on the right track.

How to get this product

You can try out a sample of OS Detailed Path Network data for evaluation and testing through the Detailed Path Network product page. Alternatively, you can try out the full product by applying for a Data Exploration license.

The OS Detailed Path Network (DPN) product is a digital representation of the roads, tracks and paths in the National Parks of Great Britain that the public may use to travel on and enjoy the great outdoors.

Whilst the product is indicative of the right of access along roads, paths and tracks within Great Britain's National Parks, it is not the legally definitive source of access information, including public rights of way.

Key features

The product is designed to facilitate applications and services to provide routes for pedestrians, cyclists and horse riders, primarily for leisure purposes.

The key features of the OS DPN product are as follows:

• A connected link and node network that facilitates routing

• Heighted data

• A description of the type of route – road, track or path

• National and local cycle routes identified

• Named long distance routes

• Names of roads, tracks and paths

• Information on rights of way (England and Wales only)

• Routes within access land identified (England and Wales only)

Product applications

The OS DPN product has been created to allow partners and developers to design and provide bespoke applications to provide routes within Great Britain's National Parks for pedestrians, cyclists and horse riders, including:

• Advanced route planning

• Live route planning

• Turn-by-turn instructions

The data is not designed to be a definitive record of rights of way or other access rights.

The data can also be used by those responsible for assessing public access to areas as the product provides information on the levels of access available to different users.

Use of the product

This product is intended to be used only as a travel aid and must not be used for any purpose requiring precise measurement of direction, distance, location or topography. Ordnance Survey makes no warranty as to the accuracy or completeness of data in this product.

When using OS DPN for navigation and routing, carefully compare information displayed on the device to all available navigation sources, including warning signs for danger areas, road signs, road closures, road conditions, traffic congestion and weather conditions.

For safety, always resolve any discrepancies before continuing navigation, and defer to posted local signature and conditions. OS DPN is designed to provide route suggestions. It is not a replacement for user attentiveness and good judgement.

Do not follow route suggestions if they propose an unsafe option or would place the user in a potentially dangerous situation.

When using the data in a portable electronic device, it is recommended that a suitable hard copy map be carried by the user in case of failure of the device.

Third-party data in the product

Public rights of way represented within the OS DPN product have been taken from Ordnance Survey 1:25 000 Scale Colour Raster that was created from local authority definitive maps and later amendments. Rights of way are liable to change and may not be clearly defined on the ground. Please check with the relevant local authority for the latest information.

Portrayal of access land on this map is intended as a guide to land which is normally available for access on foot, for example, access land created under the Countryside and Rights of Way Act 2000 and land managed by the National Trust, Forestry Commission, and Woodland Trust. Access for other activities may also exist. Some restrictions will apply, and some land may be excluded from open access rights. The depiction of rights of access does not imply or express any warranty as to its accuracy or completeness.

Identifying difficult routes

OS DPN is designed to facilitate off road routing in applications for consumers. After discussions with members of the outdoor community, it is strongly recommended that developers make use of all the attribution contained within the product to identify potentially difficult routes.

OS DPN has the functionality to highlight challenging or hazardous routes. It is for the developer to decide whether to advise the user that the created route is difficult or not to return the route at all.

Product attribution

The main product attribution that contains information on difficulty and hazards lies within the following attributes:

DescriptiveTerm

This attribute indicates the nature of the route on the ground or identification that there is not a clear route to follow (specific value ‘No Physical Manifestation’) but a legal right exists.

surfaceType

This attribute can indicate that a route is ‘Unmade’, meaning that the route may be more difficult to traverse than a made path. Examples are contained within the specification.

potentialHazard

This attribute indicates whether the route passes over specific types of terrain, for example, Rock or Scree.

Geometry

Using the three-dimensional geometry to establish steep routes or steep sections of a route.

crossesDangerArea

This attribute indicates links that pass through Ministry of Defence (MOD) firing ranges. Routes generated using these links should be flagged and should refer to external sources of information to identify access restrictions.

For example, a public right of way that is not evident on the ground and which crosses steep terrain could be represented by a RouteLink with the following attributes:

• routeLinkDescriptiveTerm value of No Physical Manifestation.

• surfaceType of null in this instance because the route is not evident on the ground.

• potentialHazard values of Rock and Scree.

• Three-dimensional geometry which indicates a steep gradient.

It is strongly recommended that any generated routes that include combinations of attributes indicating difficulty should either present the user with a warning or be excluded as a route option based upon the target user.

The OS Detailed Path Network product is available for the 15 National Park areas within Great Britain. The dataset is released in three formats: Geography Markup Language (GML), GeoPackage and vector tiles. All formats are compressed into a regular zip file (.ZIP).

Before loading the data, you will need to unzip it by using any of the regular zip programs available or via the facility within the Windows 10 operating system.

As the areas covered by the National Parks differ in size, the downloads in turn vary in size, from 11MB for the Lake District National Park to around 2MB for the Northumberland National Park.

The data is available as download only, and there are no plans for the data to be made available on hard media.

This getting started guide focuses solely on using the product in GML format. For guidance on using the product in GeoPackage or vector tiles formats, please see the following two getting started guides, which are available on the OS website:

• .

• .

Downloading the schema (GML format only)

To use the GML data format, some Geographic Information Systems (GIS) may need third-party data translation software to make the data usable within their GI application. To help with this, we provide a downloadable on the OS Detailed Path Network Product Support page on our website.

1. Go to the .

2. Find the Product schema (XML) link on the page (it is under the Getting started section which is located at the top of the page):

3. You can either:

   • Right-click on the link and Save link as to a location of your choice or

   • Click the link to open the schema online, then copy and save the content into a text editor

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.

The OS Detailed Path Network dataset was originally released in 2015. It is currently updated on an annual basis and coverage is restricted to the National Park areas of Great Britain. More information about the product, along with links to support documents, can be found on the .

Adherence to standards

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.

Loading GeoPackage data

This getting started guide focuses solely on using the product in GML format. For guidance on using the product in GeoPackage format, please see the in the getting started documentation.

Loading VectorTiles data

This getting started guide focuses solely on using the product in GML format. For guidance on using the product in vector tiles format, please see the in the getting started documentation.

Support links

Throughout this document, we reference files or documents as part of your 'Getting Started' instructions. These include:

Available formats

The OS DPN product is available in the following formats:

• Data: Geography Markup Language (GML) v3.2 Simple Features, compressed using gzip

• Vector: GeoPackage file, zipped using gzip

• Vector: Vector tiles (MBTiles) file, zipped using gzip

Product supply mechanism

The OS DPN product is supplied as an online download only. You can download data in various formats from the .

File sizes

For GML and GeoPackage product formats, one file is supplied for each National Park (i.e. you will receive 15 files when ordering the product in one of these formats).

The vector tiles product format is supplied as a single file that contains all National Parks. Each file will contain up to three feature types.

Coordinates in the OS DPN product are provided in three dimensions.

The Geography Markup Language (GML) and GeoPackage product formats enable the use of the British National Grid (BNG) coordinate reference system for the planimetric element of the geometry. The BNG spatial reference system uses the OSGB36 geodetic datum and a single Transverse Mercator projection for the whole of Great Britain. Positions on this projection are described using easting and northing coordinates in units of metres. The BNG is a horizontal spatial reference system only; it does not include a vertical (height) reference system.

The height element is provided using the same datum (i.e. Ordnance Datum Newlyn) used for other Ordnance Survey products that contain height.

In the GML data, this combination of BNG and Ordnance Datum Newlyn is represented by reference to its entry in the EPSG registry, as

The vector tiles product format is in the Web Mercator (EPSG:3857) projection. This projection is a global coordinate reference system.

Using the data with GPS devices

GPS devices may only provide coordinates using the WGS84 coordinate reference system (EPSG code 4979, although 4326 is often used also). The OS DPN data is supplied using a combination of coordinates in the OSGB36 BNG system and heights relative to Ordnance Datum Newlyn (EPSG code 7405) for both the GML and GeoPackage formats.

To allow the data to be used with positions from GPS devices, a transformation is required. The transformation can be applied to the OS DPN data (to move it on to WGS84) or to the GPS coordinates (to provide positions in OSGB36 BNG). 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 (PDF download). This transformation is EPSG code 1314.

.

Data lineage

The OS DPN product has been created from a number of existing Ordnance Survey data sources:

• Roads, tracks and paths – The geometry and information about the physical nature of a route has been sourced from the Ordnance Survey large-scale data which is used to create the OS MasterMap Topography Layer and OS MasterMap Highways Network products.

• Rights of way, long distance paths, cycle routes, access land and danger areas – These have been extracted from .

• Hazardous terrain – Attribution relating to selected potential difficulties along a route (for example, scree / cliffs) has been interpolated by overlaying the network on the Ordnance Survey large-scale data used to create the OS MasterMap Topography Layer product.

• Height values – These have been interpolated from the source data used for the and products.

The raw data used to create the product has undergone extensive data re-engineering, manual editing and validation.

Coverage

The OS DPN product includes all roads (except motorways), tracks and paths that the public are allowed to use within the 15 National Parks of England, Scotland and Wales.

Full details as to the locations of Britain’s National Parks can be found on the . The 15 National Parks covered in the OS Detailed Park Network product (and hyperlinks to the official website of each National Park) are as follows:

Product update schedule

The product will be resupplied as a complete dataset; change-only updates (COUs) will not be available.

The product contains identifiers and feature versions; however, identifiers will not persist, and versions will not increment. They have been included for future, potential product enhancements.

Feature types included in the product

The data is supplied as a link and node model, similar to the OS MasterMap Highways Networks and

OS Open Roads products. Links represent the general alignment of roads, tracks, paths and rights of way; nodes are used to record the connectivity between links explicitly. Named routes are represented as collections of links.

The OS DPN product contains three feature types: Route, RouteLink and RouteNode. These feature types are defined below.

Route

A Route feature can include references to different types of RouteLink. For example, a Route feature may include sections of paths, tracks and public roads to create a continuous named trail.

RouteLink

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

RouteLink features are split in the following circumstances:

• Where the classification changes.

• Where the name changes (or ceases to apply).

• Where there is a junction at the same physical level.

RouteNode

A RouteNode is a feature at the end of one or more RouteLink features. 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.

The data is supplied as a link and node model similar to that used for the .

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.

Route

A Route is a feature representing a named entity that forms a recognised and signed route that the public can use. For example, a , such as the Pennine Way, or one of , 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 for more details.

RouteLink

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 for more details.

RouteNode

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.

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.

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.

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.

Adherence to standards

OS Detailed Path Network is a derived product that has been designed with consideration of the INSPIRE 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.

Index

This technical specification includes the following sections:

• OS Detailed Path Network structure

• Feature types

• Structured data types

• Code lists

• Data quality

• GML overview

• GeoPackage overview

• Vector tiles overview

• GML examples

Describes the total ascent experienced when passing along a RouteLink feature in either direction.

Data Type attributes

inDirection

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

• Type: Measure

• Multiplicity: [1]

againstDirection

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

This section provides basic steps on loading the OS Detailed Path Network data into some common GI applications.

General information about using GIS with OS data is available on the Using GIS software page on the OS website.

CodeList: RouteDescriptiveGroupValue

The following codelists documents contain the permitted values for each attribute and an explanation where required.

CodeList: RouteDescriptiveTermValue

CodeList: RouteLinkDescriptiveTermValue

Detailed classification of type of feature that the RouteLink represents which the non-vehicular traffic can travel along or alongside.

No physical manifestation – examples

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

Routes along roads – further information

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 Detailed Path Network data does not currently include information on the presence or absence of a pavement and / or verge.

Usage – further information

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.

CodeList:RightOfWayValue

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 () Further rights of use are also possible and are described in the Additional rights to use a RouteLink– England sub-section.

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 Rights to use a RouteLink – Scotland).

Classification of the designated rights of access and use assigned to the RouteLink.

Other rights may exist, but these will need to be determined from the Local Highway Authority.

Right of use on local roads

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.

Additional rights to use a RouteLink – England and Wales

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:

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.

Rights to use a RouteLink – Scotland

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.

A summary of the access rights:

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

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

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

4. Existing rights, including public rights of way and navigation, and existing rights on the foreshore, continue.

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

6. Local authorities can formally exempt land from access rights for short periods. Local authorities and some other public bodies can introduce byelaws.

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

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

CodeList:PotentialHazardValue

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.

Foreshore is added to all links that are intertidal.

CodeList:SurfaceTypeValue

State of a surface in the context of the origin of the surface and resistance to environmental elements.

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 images in the three following figures illustrate typical examples of different surface types.

Made sealed surface – examples

Made unsealed surface – examples

Unmade surface – examples

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.

RouteLink attributes

featureID

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]

versionID

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]

versionDate

The date on which the version was created.

• Attribute Name: versionDate (GML), version_date (GeoPackage), Not provided (Vector tiles)

• Type: Date

• Multiplicity: [1]

descriptiveGroup

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

• Length: 50

• Multiplicity: [1]

descriptiveTerm

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

• Length: 50

• Multiplicity: [1]

surfaceType

Type of material used to protect the surface of the way.

• Attribute Name: surfaceType (GML), surface_type (GeoPackage), surface_type (Vector tiles)

• Type: SurfaceTypeValue

• Length: 30

• Multiplicity: [0..1]

physicalLevel

Relative vertical position of the RouteLink in relation to the ground surface.

• Attribute Name: physicalLevel (GML), physical_level (GeoPackage), physical_level (Vector tiles)

• Type: LevelCodeValue

• Length: 30

• Multiplicity: [1]

roadNumber

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]

name

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]

alternativeName

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]

rightOfUse

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

• Length: 60

• Multiplicity: [1]

adoptedByRecreationalRoute

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]

adoptedByNationalCycleRoute

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]

adoptedByOtherCycleRoute

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]

withinAccessLand

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]

crossesDangerArea

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]

potentialHazardCrossed

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

• Length: 20

• Multiplicity: [0..*]

verticalGain

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]

planimetricLength

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]

surfaceLength

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]

startNode

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

endNode

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

A Route is a feature representing a named entity that forms a recognised and signed route that the public can use.

Route attributes

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.

featureID

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: Character String

• Length: 36

• Multiplicity: [1]

versionID

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]

versionDate

The date on which the feature was last edited.

• Attribute Name: versionDate (GML), version_date (GeoPackage), Not provided (Vector tiles)

• Type: Date

• Multiplicity: [1]

descriptiveGroup

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

• Length: 50

• Multiplicity: [1]

descriptiveTerm

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

• Length: 50

• Multiplicity: [1]

name

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]

adopts

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

RouteNode atttributes

featureID

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]

versionID

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]

versionDate

The date on which the version was created.

• Attribute Name: versionDate (GML), version_date (GeoPackage)

• Type: Date

• Multiplicity: [1]

descriptiveGroup

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

• Length: 50

• Multiplicity: [1]

descriptiveTerm

The reason that a RouteLink feature has started or ended.

• Attribute Name: descriptiveTerm (GML), descriptive_term (GeoPackage), descriptive_term (Vector tiles)

• Type: RouteNodeDescriptiveTermValue

• Length: 10

• Multiplicity: [1]

geometry

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]

CodeList:LevelCodeValue

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

Schema overview and location

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:

The XML namespaces used by the application schema and their definitions.

Simple Features Profile – Level 1

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.

Data quality

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.

Positional accuracy

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.

Planimetric accuracy – physical routes

The typical device that the data will be used upon is positionally accurate to approximately 10m 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.

Planimetric accuracy – non-physical routes

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.

Using the data with GPS devices

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 A Guide to Coordinate Systems in Great Britain, which is available on the OS website. This transformation is EPSG code 1314.

Further information on coordinate systems and transformations is available on our website.

Height accuracy

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 approximately 10 to 20m in height.

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.

Height and planimetric correlation

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.

Completeness

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.

Attribute accuracy

Feature representation

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.

Feature level attributes

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 Height and Planimetric Correlation.

Feature level metadata

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.

versionID

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

Logical consistency

Content

Attribute values are imposed by edit systems and tested using validation to comply with those in the schema.

Context

Logical combinations of attributes are imposed by edit systems and tested using validation.

Correlation

Basic topology is tested in the edit software and additional validation is applied to ensure the topology is correct.

Connectivity

The connectivity between features at the same and different levels is tested through validation and visual inspection.

This annex provides examples of the different GML structure for Full Supply orders and COU orders and the transactions within.

Full Supply

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 

Change Only Update

An example of the Change Only Update 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>

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.

Attribute naming differences between GML and GeoPackage formats

The naming of attributes between GeoPackage and the Geography Markup Language (GML) file is very similar as GeoPackage files are not limited in the number of characters for an attribute name. 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.

XML schema

The OS Detailed Path Network XML schema is available to download from the product page here.

Stylesheets

Predefined stylesheets for OS MasterMap Highways Network are available for download from the Ordnance Survey OS-MasterMap-Highways-Network-stylesheets GitHub repository here.

• To download a ZIP containing all stylesheets, navigate to Code > Download ZIP.

CodeList: RouteNodeDescriptiveTermValue

Within access land

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.

The table below shows a selection of the attribute mapping for GeoPackage Route feature attributes.

The table below shows a selection of the attribute mapping for GeoPackage RouteLink feature attributes.

The table below shows a selection of the attribute mapping for GeoPackage RouteNode feature attributes.

The table below shows selection of attribute mapping for Vector Tiles Route feature attributes.

Vector tiles overview

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

Attribute naming differences between GML and vector tiles formats

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.

Vector Tiles schema

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.

The table below shows selection of attribute mapping for Vector Tiles RouteLink feature attributes.