- Home
-
Public Sector
Public Sector
Quick links to popular content
- Business
-
Leisure
Leisure
OS getamap – print your route
Have your map custom made
Visit our shop
Read our magazine
-
Education & Research
Education & Research
Schools
Further & Higher Education
Research
General interest
-
About us
About us
Quick links
- Support
Feature types and attribution in the Urban Paths Network theme
Go to: Path | PathLink | PathNode | ConnectingLink | ConnectingNode | FerryLink | FerryNode | FerryTerminal
In OS MasterMap® Integrated Transport Network™ Layer (ITN), features are classified using feature type and feature description attributes. This page describes the feature types in the Urban Paths Network theme, illustrates their permitted attribution and shows the expected occurrence of the attributes for each feature type in the data. These occurrences are shown in UML notation; 0 for optional, 1 for a single, * for multiple, and ‘or’ being represented by double dots (..).
Path
A Path is a feature that represents a path with a name. This information is captured from the large-scale database that has been captured by surveyors on the ground. The feature consists of a set of references to PathLink features that provide the network topology of the path. Named extents like Hyde Park are not named via the Path feature. Unnamed paths are included as PathLink features, but are not referenced by a Path feature.
|
Feature type: Path |
||||
|
Attribute |
Cardinality |
Type |
Mandatory |
Notes |
|
TOID |
1 |
Identifier |
Yes |
|
|
version |
1 |
Integer |
Yes |
|
|
versionDate |
1 |
Date |
Yes |
|
|
theme |
1 |
Fixed String |
Yes |
‘Path Network’. |
|
descriptiveGroup |
1 |
Fixed String |
Yes |
‘Named Path’ |
|
changeHistory |
0..* |
Complex |
No |
|
|
boundedBy |
1 |
Rectangle |
Yes |
|
|
pathName |
1..* |
String |
No |
The ‘local’ name of the path (where Ordnance Survey has names in more than one language, such as Welsh or Gaelic). |
|
pathname sub-attribute |
||||
|
language |
0..1 |
String |
No |
The language that this name is in. |
|
Association |
Cardinality |
Type |
Mandatory |
|
|
networkMember |
1..* |
TOID of PathLink |
Yes |
List of TOIDs relating to the PathLink network. |
PathLink
A PathLink is a linear feature that represents the general alignment of the path area, where the only option for a person is to travel along the link or leave the path network, for example into a building or onto private land. This feature is captured from the Topography Layer and holds the general description of a path network. The current description from the TOPO 96 capture specification for a man-made path is:
‘The made surface of a communication Path which is not aligned to a road. The path might be described "Path" or have a distinctive name with "Path" in the name and the surface must be able to be interpreted as artificial, for example, gravel, paving slabs, tarmac.'
These features form the basis of the Urban Path Network. Production staff then use their expertise to include:
- Routes that cannot be inferred from the road network
- Connectivity between road networks
- Canal paths or towpaths
- Paths over footbridges
- Paths under subways
Paths are removed for the following reasons:
- They fall within the boundaries of schools or cemeteries.
- They are connected to motorways.
A PathLink will always connect to two PathNode features.
PathLink features use the life cycle rules of RoadLink features, with the additional clarification that if a path link is split into two parts of identical length, the link associated with the start node of the original path link will retain the original TOID.
PathLink feature attribute theme is set to ‘Path Network’ and descriptiveGroup is set to ‘Path Topology’.
|
Feature type: PathLink |
||||
|
Attribute |
Cardinality |
Type |
Mandatory |
Notes |
|
TOID |
1 |
Identifier |
Yes |
|
|
version |
1 |
Integer |
Yes |
|
|
versionDate |
1 |
Date |
Yes |
|
|
theme |
1 |
Fixed String |
Yes |
‘Path Network’ |
|
descriptiveGroup |
1 |
Fixed String |
Yes |
‘Path Topology’ |
|
changeHistory |
0..* |
Complex |
No |
|
|
descriptiveTerm |
1 |
Controlled String |
Yes |
‘Footpath’ or ‘Bridleway’ or ‘Canal Path’ or ‘Cycle Path’ or 'Shared Use’. All applicable terms must be present. |
|
make |
0..1 |
Controlled String |
No |
|
|
length |
1 |
Real |
Yes |
|
|
polyline |
1 |
LineString |
Yes |
|
|
Association |
Cardinality |
Type |
Mandatory |
Notes |
|
referenceToTopographicArea |
1..* |
TOID reference to topographic feature |
Yes |
Reference to the topographic area that the PathLink sits on. This is a place holder for future population. Currently set to default value of 'osgb9999’. |
|
directedNode |
2 |
TOID reference to PathNode |
Yes |
Has a reference to the PathNode at the start and end of this feature. |
|
Attribute of directedNode association |
||||
|
orientation |
1 |
Sign |
Yes |
|
|
gradeSeparation |
1 |
Integer |
No |
|
PathNode
A PathNode is a point having a connection with at least one PathLink, FerryLink or ConnectingLink. A PathNode represents:
- The intersection or crossing of multiple paths
- The point where a path name changes
- The point where a path name ceases to apply
- The point where a path description ceases to apply
- The start/end of a carriageway
A PathNode can have one or more PathLink features referenced to it.
|
Feature type: PathNode |
||||
|
Attribute |
Cardinality |
Type |
Mandatory |
Notes |
|
TOID |
1 |
Identifier |
Yes |
|
|
version |
1 |
Integer |
Yes |
|
|
versionDate |
1 |
Date |
Yes |
|
|
theme |
1 |
Fixed String |
Yes |
’Path Network’ |
|
descriptiveGroup |
1 |
Fixed String |
Yes |
’Path Topology’ |
|
changeHistory |
0..* |
Complex |
No |
|
|
point |
1 |
Point (coordinates) |
Yes |
|
|
Association |
Cardinality |
Type |
Mandatory |
|
|
referenceToTopographicArea |
1 |
TOID reference to topographic feature |
Yes |
Reference to the topographic area that this PathNode sits on. This is a place holder for future population. Currently set to default value of ‘osgb9999’. |
ConnectingLink
A ConnectingLink is a feature that represents a connection between the Urban Paths and the Road networks. This feature does not exist in real-world terms and only defines a logical connection. This is a new feature type introduced for the first time within Urban Paths Network.
|
Feature type: ConnectingLink |
||||
|
Attribute |
Cardinality |
Type |
Mandatory |
Notes |
|
TOID |
1 |
Identifier |
Yes |
|
|
version |
1 |
Integer |
Yes |
|
|
versionDate |
1 |
Date |
Yes |
|
|
theme |
1 |
Fixed String |
Yes |
‘Path Network’ |
|
descriptiveGroup |
1 |
Fixed String |
Yes |
‘Path Topology’ |
|
changeHistory |
0..* |
Complex |
No |
|
|
point |
1 |
Point (coordinates) |
Yes |
|
|
Association |
Cardinality |
Type |
Mandatory |
|
|
directedNode |
2 |
Reference to PathNode |
Yes |
References the nodes at the start and end of this feature – one PathNode and one ConnectingNode. |
|
Attribute of directedNode association |
|
|||
|
orientation |
1 |
Sign |
Yes |
-ve for the start directed node and +ve for the end |
ConnectingNode
A ConnectingNode is a notional feature that connects the Urban Paths Network to the Road Network. This feature can also be used to connect pedestrian features to the Road Network where they are not attached to a path, for example, a standalone pedestrian crossing. A ConnectingNode references the RoadLink it is assigned to and the ConnectingLink then references the ConnectingNode as either its start or end node.
|
Feature type: ConnectingNode |
||||
|
Attribute |
Cardinality |
Type |
Mandatory |
Notes |
|
TOID |
1 |
Identifier |
Yes |
|
|
version |
1 |
Integer |
Yes |
|
|
versionDate |
1 |
Date |
Yes |
|
|
theme |
1 |
Fixed String |
Yes |
’Path Network’. |
|
descriptiveGroup |
1 |
Fixed String |
Yes |
’Path Topology’. |
|
changeHistory |
0..* |
Complex |
No |
|
|
point |
1 |
Point (coordinates) |
Yes |
|
|
Association |
Cardinality |
Type |
Mandatory |
|
|
referenceToITN |
1 |
TOID of ITN Road Network items |
Yes |
A list of the TOIDs that reference the ITN Road Network. |
FerryLink
A FerryLink is a logical connection between two FerryNode features and represents a pedestrian ferry route between two ferry terminals. This feature does not indicate the actual route a ferry will take, only that a route is possible. Pedestrian ferry links use the ITN Road FerryLink specification.
The FerryLink within the Urban Paths Network theme is slightly different than the FerryLink within the Road Network theme as it now includes a descriptiveTerm of 'Pedestrian' to indicate the FerryLink can only be used by foot passengers. In the Road Network theme, it is assumed that the link can be used by pedestrians and vehicles.
In future, all road based ferries will have a descriptiveTerm value of 'road' and another attribute will be introduced to record ‘shared use’ for multiple use ferries (Phase 3).
|
Feature type: FerryLink |
||||
|
Attribute |
Cardinality |
Type |
Mandatory |
Notes |
|
TOID |
1 |
Identifier |
Yes |
|
|
version |
1 |
Integer |
Yes |
|
|
versionDate |
1 |
Date |
Yes |
|
|
theme |
1 |
Fixed String |
Yes |
’Path Network’ |
|
descriptiveGroup |
1 |
Fixed String |
Yes |
’Ferry Connection’ |
|
changeHistory |
0..* |
Complex |
No |
|
|
descriptiveTerm |
1 |
Controlled String |
Yes |
'Pedestrian' |
|
Association |
Cardinality |
Type |
Mandatory |
|
|
directedNode |
2 |
Link to Directed Node |
Yes |
|
|
Attribute of directedNode association |
|
|||
|
orientation |
1 |
Sign |
Yes |
-ve for the start directed node and +ve for the end |
FerryNode
A FerryNode equates, in logical terms, to a ferry port or harbour. A FerryNode connects to at least one FerryLink.
This point sits within the harbour or port but does not directly equate to any particular real-world feature, except the port as a whole. The point reuses the existing FerryNode feature from the Road Network data mode – the specification is unaltered and it uses the same life cycle rules.
|
Feature type: FerryNode |
||||
|
Attribute |
Cardinality |
Type |
Mandatory |
Notes |
|
TOID |
1 |
Identifier |
Yes |
|
|
version |
1 |
Integer |
Yes |
|
|
versionDate |
1 |
Date |
Yes |
|
|
theme |
1 |
Fixed String |
Yes |
’Path Network’ |
|
descriptiveGroup |
1 |
Fixed String |
Yes |
’Ferry Connection’ |
|
changeHistory |
0..* |
Complex |
No |
|
|
point |
1 |
Point (coordinates) |
Yes |
|
FerryTerminal
A FerryTerminal is a logical connection between a PathNode, or a RoadNode, and a FerryNode.
A FerryTerminal adapts the specification for ferry terminals used in the Road Network by introducing the descriptiveTerm ‘Pedestrian’. The descriptiveTerm should always be 'Pedestrian' followed by 'Ferry'.
|
Feature type: FerryTerminal |
||||
|
Attribute |
Cardinality |
Type |
Mandatory |
Notes |
|
TOID |
1 |
Identifier |
Yes |
|
|
version |
1 |
Integer |
Yes |
|
|
versionDate |
1 |
Date |
Yes |
|
|
theme |
1 |
Fixed String |
Yes |
’Path Network’ |
|
descriptiveGroup |
1 |
Fixed String |
Yes |
’Network Connection' |
|
changeHistory |
0..* |
Complex |
No |
|
|
descriptiveTerm |
2 |
Controlled string |
Yes |
The name of each connected network. Values are 'Pedestrian', then 'Ferry'. |
|
Association |
Cardinality |
Type |
Mandatory |
Notes |
|
referenceToNetwork |
2 |
TOID |
Yes |
References to the PathNode and FerryNode features. |
In this section:
ITN Technical specification – home
ITN Road Routing Information (RRI) theme
ITN Path Routing Information (PRI) theme
Feature types and attribution in the Road Network theme
Feature types and attribution in the Road Routing Information theme
Feature types and attribution in the Urban Paths Network theme
Feature types and attribution in the Path Routing Information theme
Descriptions of ITN Layer attributes
Attribution checklists for the Road Network and Urban Paths Network themes
ITN attribute definitions and values
This web page is part of the technical specification for OS MasterMap® Integrated Transport Network™ Layer. For the terms that apply to use of this specification, refer to Purpose of this specification.