Skip to content

50,000 free calls a month, card-free. Get an API key →

Every asset on your network, with the frame that proves it.

A positioned register of signs, markings, lighting columns and kerbs, each linked to the dated photographic frame it was read from, so an officer can answer 'what is on this street, and can you show me'.

A survey record, not a picture library.

Every extracted feature is positioned, map matched to the road network and tied to the dated frame it came from. Anything the pipeline could detect but not read is recorded as an honest unknown rather than filled in.

The MapMap Roadside capture viewer on the Brighton pass: the map beside the 360 frame a shopfront record was read from, with reading chips naming the REISS fascia at 97 per cent, bunting, a wall mounted sign and double yellow lines · © OpenStreetMap contributors © OpenMapTiles
Evidence

A dated evidence chain per feature

Each record names its source frame, capture date, position method and network reference. When a reading disagrees with the map you already hold, the record carries the frame that settles it. Imagery stays on our side, reached through per-feature links.

How a pass becomes a record
The MapMap Roadside capture viewer on the Brighton pass: the layers panel counting 4,146 located objects and 2,008 captured frames beside the map, where the located findings are drawn as coloured category dots along central Brighton streets · © OpenStreetMap contributors © OpenMapTiles
Registers

One GIS layer per asset class

Signs, road markings, street nameplates, lighting columns, street furniture, boundaries, trees and utility covers, delivered in British National Grid with a data dictionary and stable feature identifiers.

The MapMap Roadside capture viewer filtered to the kerbside classes, with parking, speed limit, crossing and cycle infrastructure ticked in the carriageway and signs group and their per-class counts beside them · © OpenStreetMap contributors © OpenMapTiles
Kerbside

The kerb, as it is actually used

Dropped kerbs, tactile paving, crossings, parking restrictions, loading and waiting, EV and cycle provision: the layers that decide schemes and get argued about at committee, each with its evidence link.

The road-facing camera's frame of the carriageway in the MapMap Roadside capture viewer: a cracked, patched stretch of asphalt at the carriageway edge, tagged with the source frame GX030008/p01696.jpg and a five reads chip, with two of those reads pinned on the kerbside edge where the pipeline found them
Carriageway

A second camera reads the road itself

A road-facing camera on the same vehicle captures the carriageway roughly every 4 metres: cracking, worn markings, patches, ironwork and the inspector's own painted marks, read back as graded observations. A visual grade for prioritising an inspection, never a measured depth. The same readings can steer routing: our router already uses them to pick smoother cycle routes.

Open the cycle routing demo
Change

Change arrives as a fresh dated pass

A pass is the unit of work. Commission a later pass over the same segment and the registers line up on stable identifiers, so what changed is a comparison you can defend rather than a guess.

High streets

Vacancy evidence with a date on it

Shopfront and unit condition with a dated photographic record per address, for vacancy registers and high street rental auction work where the date on the evidence is the point.

Known limit

Roadside is asset inventory and evidence, not a statutory carriageway condition survey, and we do not hold the accreditation that would let us present it as one. Coverage is what has been driven, and each pass says where it went.

Proof first

Judge the record, not the pitch.

Ask and we will show you a live demo on ground we have already surveyed, then send a desk proof to keep: one street, delivered exactly as you would receive it. Both are free. A drive proof on your own network is £2,500, credited in full against any package you go on to buy.