Routable OS Highways data for fleet, depot, last-mile and transport operators.
A depot on the wrong side of a banned turn is not a geocoding glitch — it is an OS Highways join you never bought. We license the MasterMap Highways Network, AddressBase, postcode polygons and points of interest for operators that route vehicles, place depots and promise delivery windows across Great Britain.
MasterMap Highways Network as the connected, attributed road graph
AddressBase for kerbside and depot locations, not postcode centroids
POI and Code-Point for catchment, drive-time and site selection
// WHO THIS IS FOR
Fleets, carriers and infrastructure operators.
Routing, depot strategy and passenger or freight operations each hang off a different OS join. The Highways Network is the common layer.
Fleet and last-mile
Carriers, 3PLs and home-delivery operations.
You need a legal, attributed road network and premise-level addresses. Consumer map APIs are fine for a driver view; they are a poor basis for a contracted SLA, a depot investment or a local-authority access restriction.
Highways Network for routing, restrictions and road classification
AddressBase for delivery points and non-postal sites
Code-Point polygons for density and round design
Regional or national coverage with a stated vehicle class
Transport infrastructure
Road, rail, ports and public-transport operators.
Infrastructure owners need the same Highways and AddressBase layers, plus topography and sometimes terrain around depots, stations and compounds. This is closer to an asset GIS than a routing engine.
MasterMap around stations, yards and highway depots
Highways Network for diversion and resilience planning
AddressBase Plus for non-postal operational sites
Imagery for compound and access validation
// USE CASES
Where logistics teams actually spend the licence fee.
If the decision is a route, a depot, a delivery promise or a banned movement, it belongs on licensed Highways and addressing data.
Route planning and restrictions
Weight, height, one-way and access attributes on the Highways Network, rather than a geometric shortest path that ignores a low bridge.
Depot and hub siting
Drive-time catchments from Code-Point and Highways, plus land and access context from MasterMap before you sign a lease.
Kerbside and failed-delivery analysis
UPRNs instead of postcode centroids so a flat above a shop is not treated as the loading bay next door.
Round design
Postcode polygons and address density for slicing rounds that match how a town is actually laid out.
Control-room location
A lawful gazetteer for incidents, delays and customer calls that has to match what the driver sees on the street.
Multi-modal context
POI and Highways together for first/last-mile around railheads, ports and consolidation centres.
// THE OS DATA UNDERNEATH
Datasets logistics and transport teams license.
Highways first, then addressing. POI and postcode polygons come in for strategy; MasterMap comes in when you are buying land or running a depot GIS.
A graph for the router. Files for the planning team.
1. Network files or API
Highways Network as a connected dataset or via an API your routing engine already understands. Attribution and vehicle-class rules stay in the licence.
Best for: routing, ETA and control-room products.
2. Address and polygon files
AddressBase and Code-Point into the data warehouse that designs rounds, prices postcodes and reports SLA by area.
Best for: network planning and commercial teams.
3. Depot GIS build
MasterMap, imagery and Highways clipped to candidate sites or an operating region, sometimes with a hosted viewer for property and operations.
Best for: estate, property and infrastructure teams.
// LICENSING, EXPLAINED
Routing products versus internal operations.
Internal fleet operations
A closed routing stack for your own vehicles is usually a regional or national file licence with a seat and environment count. Contractor depots need to be named if they hold the data.
Customer-facing tracking apps
If a shipper or consumer sees the map or a derived ETA map, that display has to sit inside the partner terms, including attribution. We scope that as a product surface, not an internal GIS seat.
// FAQ
Questions from logistics data and network-planning teams.
Why not just use a consumer routing API?
Fine for a driver navigating a single job. Weak for contracted ETAs, restriction-aware routing, depot investment and any product that redisplays a map. The Highways Network is the OS source those decisions should cite.
Does AddressBase include what3words or plus codes?
No. It is UPRN and PAF-aligned addressing. If you need non-postal sites — depots, compounds, lock-ups — that is AddressBase Plus, not a third-party geocoder bolted on.
Can we use this for live traffic?
The Highways Network is the geometry and attribution. Live congestion feeds are a separate product. We can join them; we do not pretend OS publishes live speeds here.
Do rail operators need the Highways Network?
Usually yes, for station access, rail-replacement routing, depot approach and first/last-mile. Track geometry itself is not this dataset.
Can you clip to a franchise or regional operating area?
Yes. Send a polygon or a list of highway authorities and we will quote a regional cut rather than a national file you will never load.
How current is the road network?
OS publishes on a regular national cycle. If a new spine road is business-critical, tell us — we will say whether it is already in the current release or needs a workaround.
// REQUEST A QUOTE
Tell us whether this is a router, a depot or a round-design problem.
Share the operating area, vehicle types, and whether the data has to land in a routing engine, a warehouse or a hosted map. Indicative pricing comes back under NDA within one UK working day.
