A wireless sensor deployment should not begin with a device choice. It should begin with the operational question the authority needs to answer: is a signal stage failing to call, are cyclists being missed, is rat-running increasing, or is a speed intervention needed at a particular location? Clear requirements determine the detection technology, mounting position, communications approach and data outputs needed to make a measurable difference.

For highways teams, the attraction is clear. Above-ground wireless sensors can provide vehicle detection and traffic data without cutting carriageways, installing inductive loops or extending road closures. That reduces disruption to road users while giving engineers greater flexibility to adjust, relocate or expand detection as network conditions change.

Start with the traffic outcome, not the sensor

Wireless sensors are often specified for junction control, traffic counting, vehicle classification, speed monitoring and active travel schemes. These applications can look similar on a plan, but they impose different demands on detection.

At a signalised junction, the priority may be reliable presence detection in a defined lane or accurate approach detection to support an extension request. On a rural route, the requirement may instead be speed and volume data over several weeks to establish whether a speed indication device or other intervention is justified. A cycle route crossing may require dependable detection of slower-moving cyclists, including at times of low traffic flow.

The specification should state what must be detected, where, and what action follows from the detection event. This includes vehicle types, lane coverage, direction of travel, speed range, queue conditions and whether pedestrians or cyclists must be identified. It should also define the performance needed in rain, darkness, headlight glare, stop-start traffic and congested approaches.

A sensor that produces useful volume data may not be the best option for signal actuation. Equally, a detector configured for a single stop line may not deliver the approach information needed for queue management. Matching the technology to the control objective prevents poor data and avoidable rework later in the programme.

Survey the site before finalising wireless sensor deployment

A desktop review is useful, but it cannot replace a proper site survey. The survey establishes whether the proposed field of view, detection zone and communications arrangement will work in the real road environment.

For radar-based detection, engineers should consider the mounting height, alignment, lane geometry, vehicle paths and nearby objects that could affect the detection area. Large signs, street furniture, safety barriers, parked vehicles and road curvature can all influence the practical placement of equipment. AI video detection requires the same discipline, with additional attention to lighting changes, shadows, occlusion and the angle needed to distinguish road users accurately.

The survey should also identify available power, cabinet space, existing controller interfaces and the route for communications. Wireless does not mean infrastructure-free. A detector may be wireless in its communication with a roadside gateway or controller, yet still need a suitable power source, secure enclosure and clear radio path.

On constrained urban sites, pole availability can be decisive. On rural sites, long distances and limited existing infrastructure may favour low-power sensor arrangements, but only after radio coverage and battery-life assumptions have been tested. Where temporary traffic management would be difficult or disruptive, non-intrusive installation is particularly valuable.

Check for future changes at the same time

Road layouts evolve. A temporary cycle lane may become permanent, a junction may be retimed, or a development may alter turning movements and demand profiles. During the survey, consider whether the mounting location and detection zones allow for these changes.

This is one of the advantages of above-ground technology: it can be reconfigured without reopening the road surface. However, relocation is only straightforward when brackets, power provision, communications and access arrangements have been planned with future adjustment in mind.

Select communications for the operating environment

The communications method should suit the purpose of the installation, rather than follow a default preference. Short-range wireless links can be effective where sensors and controllers are close together. Cellular communications may suit dispersed monitoring sites where data needs to reach a central platform without a local network connection. In other locations, an existing authority network may be the right route.

The key consideration is not simply whether data can be transmitted. It is whether it reaches the destination with the availability, latency and security appropriate to the application. Signal control functions require a different level of assurance from periodic traffic survey data. A missed data upload may be inconvenient for a count site; delayed detection at a junction can affect capacity, safety and user experience.

Define how devices will be commissioned, authenticated and monitored. Confirm who owns the connection, how firmware updates are managed and what happens if communications are interrupted. For traffic management applications, a clear fallback state is essential. The junction or monitoring location must continue to operate safely when a device, gateway or connection is unavailable.

Commission with real traffic, not assumptions

Installation is only the midpoint of a successful deployment. Commissioning should verify the physical installation, system interfaces and live detection performance under representative traffic conditions.

For a junction application, this means observing vehicles in each relevant lane, including cars, buses, motorcycles and lorries where applicable. Test turning movements, closely following vehicles, queuing traffic and vehicles approaching at lower speeds. If cycle detection is included, verify detection with real cyclists using the route as intended, not only a static test at the kerb.

Detection zones and classification settings often need refinement after initial observations. A correctly mounted sensor can still require adjustment to exclude an adjacent lane, avoid detecting traffic on a nearby side road or improve performance around an unusual lane merge. These changes should be recorded alongside the final configuration so the asset can be supported properly over its working life.

A useful commissioning record includes the installation location, device orientation, mounting height, configured detection areas, communications details, controller inputs and test results. Photographs showing the installed equipment and its view of the carriageway make later fault investigation substantially quicker.

Turn detected movements into useful decisions

The value of wireless detection lies in what the data enables. Traffic volumes, speeds, classifications, occupancy and directional movements can support practical decisions across the network.

At a local level, data can identify periods when a junction is operating inefficiently, assess whether a speed concern is evidenced by measured behaviour, or show how road users respond after a scheme has been introduced. Across a wider network, consistent data collection can help authorities compare sites, prioritise interventions and assess the effect of seasonal demand, roadworks or network changes.

Data quality matters as much as data quantity. A dashboard full of figures does not assist a transport team if the source, time period, vehicle classes and confidence of the measurement are unclear. Establish a reporting structure that reflects the original objective. For example, a safety scheme may require before-and-after speed distribution analysis, while a signal optimisation exercise may focus on demand by lane and time period.

There is also a trade-off between detailed classification and operational simplicity. More granular data can improve scheme design, but it may require more careful configuration, validation and interpretation. The right level of detail is the one that supports a decision without creating unnecessary maintenance or analytical burden.

Plan maintenance and support from day one

Non-intrusive sensors remove the need to cut into the carriageway, but they still require asset management. Periodic checks should confirm that equipment remains correctly aligned, brackets and housings are secure, power is stable and communications are active. Changes at the roadside matter too: new signage, vegetation growth and redevelopment can alter a detector’s effective view.

Remote monitoring can identify a failed connection, low battery condition or unexpected data pattern before it becomes a wider operational issue. This is especially useful for distributed sites where visits take time to arrange. Maintenance teams should have access to accurate asset records and a defined process for diagnosing whether an issue originates in the sensor, communications path, controller interface or configuration.

For authorities moving away from inductive loops, the wider benefit is resilience in maintenance planning. Detection changes can often be made from the roadside rather than through carriageway excavation, reducing exposure for crews and avoiding the disruption associated with lane closures.

Make deployment part of a wider detection strategy

Wireless sensor deployment is most effective when it forms part of a coherent approach to traffic detection. Radar may be the preferred choice for a particular vehicle detection task, while AI video may provide the road-user insight needed at a complex urban junction. Traffic counters and data platforms can extend the picture beyond an individual site.

The objective is not to replace every existing technology automatically. It is to use non-intrusive detection where it delivers safer installation, better operational data, quicker deployment or lower disruption over the asset life. A well-surveyed, properly commissioned sensor can turn a difficult-to-observe road location into evidence that supports better control, targeted investment and safer decisions for every road user.

C & T
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.