> For the complete documentation index, see [llms.txt](https://docs.os.uk/os-downloads/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.os.uk/os-downloads/products/transport-network-portfolio/os-mastermap-highways-network-roads/os-mastermap-highways-network-roads-technical-specification/feature-types/roadnode.md). # RoadNode A point spatial object that is used to break up the road network for connectivity. The road network splits for the following circumstances: * The location where an attribute recorded on the road link changes for example its name or form. * The intersection or crossing of Roads (including bridges, flyovers and tunnels where there is no connectivity). * The start / end of a Road. * Where a One-Way Routing feature starts or ends. * Where a tunnel starts or ends. * Where there is a connection to the Path Network. The context diagram below shows how the RoadNode has been inherited from INSPIRE and the attribution held on the RoadNode.
Context Diagram for RoadNode.

Context diagram: RoadNode

## RoadNode Attributes A point representing either the start/end of a road, the connectivity between two or more roads or where one of the recorded attributes changes along a road. * **Constraints:** formOfRoadNode shall never be voidable ### id Unique identifier, for RoadNode this is a TOID * **Attribute name:** gml\_id (GML), toid (GeoPackage), toid (VectorTiles) * **Type:** CharacterString * **Size:** 20 * **Multiplicity:** \[1] ### identifier Uniform Resource Identifier * **Attribute name:** identifier (GML), identifier (GeoPackage), Not provided (VectorTiles) * **Type:** CharacterString * **Size:** 37 * **Multiplicity:** \[1] ### inspireId INSPIRE External object identifier of the spatial object. * **Attribute name:** inspireId * **Type:** Identifier * **Multiplicity:** \[0..1] ### beginLifespanVersion «lifeCycleInfo» «voidable» INSPIRE Date and time at which this version of the spatial object was inserted or changed in the spatial data set. Note: The time part is always set to zero. * **Attribute name:** beginLifespanVersion * **Type:** DateTime * **Multiplicity:** \[1] ### validFrom «voidable» INSPIRE The time when the transport node started to exist in the real world. Note: The time part is always set to zero. * **Attribute name:** validFrom * **Type:** DateTime * **Multiplicity:** \[1] ### geometry INSPIRE The three-dimensional location of the node. For nodes representing grade separated intersections the elevation is of the lower road * **Attribute name:** geometry * **Type:** GM\_Point * **Multiplicity:** \[1] ### formOfRoadNode «voidable» INSPIRE Description of the function of a road node in the road transport network. * **Attribute name:** formOfRoadNode (GML), form\_of\_road\_node (GeoPackage), form\_of\_road\_node (VectorTiles) * **Type:** [FormOfRoadNodeValue](/os-downloads/products/transport-network-portfolio/os-mastermap-highways-network-fundamentals/os-mastermap-highways-network-code-lists/formofroadnodevalue.md) * **Size:** 21 * **Multiplicity:** \[1] ### classification Further specialisation of the form of road node. * **Attribute name:** classification (GML), classification (GeoPackage), Not provided (VectorTiles) * **Type:**[ RoadNodeClassificationValue](/os-downloads/products/transport-network-portfolio/os-mastermap-highways-network-fundamentals/os-mastermap-highways-network-code-lists/roadnodeclassificationvalue.md) * **Size:** 19 * **Multiplicity:** \[0..1] ### access Point where vehicles can either exit or enter a controlled-access highway. Note: Values not populated in the initial release. * **Attribute name:** access * **Type:** [AccessPointValue](/os-downloads/products/transport-network-portfolio/os-mastermap-highways-network-fundamentals/os-mastermap-highways-network-code-lists/accesspointvalue.md) * **Size:** 5 * **Multiplicity:** \[0..1] ### junctionName The name of any junction that the node represents part of. Note: Where a feature has more than one name, the language of each name is provided as a 3-digit ISO 639-2 code (‘eng’, ‘cym’, ‘gla’). * **Attribute name:** junctionName (GML), junction\_name (GeoPackage), junction\_name (VectorTiles) * **Type:** LocalisedCharacterString * **Size:** 120 * **Multiplicity:** \[0..2] ### junctionNumber The number of any motorway junction that the node represents part of, for example M3 J12. * **Attribute name:** junctionNumber (GML), junction\_number (GeoPackage), junction\_number (VectorTiles) * **Type:** CharacterString * **Size:** 30 * **Multiplicity:** \[0..2] ### reasonForChange The reason for a change made to a feature. * **Attribute name:** reasonForChange (GML), reason\_for\_change (GeoPackage), Not provided (VectorTiles) * **Type:** [ChangeValue](/os-downloads/products/transport-network-portfolio/os-mastermap-highways-network-fundamentals/os-mastermap-highways-network-code-lists/changevalue.md) * **Size:** 32 * **Multiplicity:** \[1] ### relatedRoadArea Reference to the topographic representation(s) of the same part of the road. * **Attribute name:** reasonForChange (GML), reason\_for\_change (GeoPackage), Not provided (VectorTiles) * **Size:** 20 * **Multiplicity:** \[1..\*] --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.os.uk/os-downloads/products/transport-network-portfolio/os-mastermap-highways-network-roads/os-mastermap-highways-network-roads-technical-specification/feature-types/roadnode.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.