A missed call at a signal approach can hold traffic on red, waste green time and undermine public confidence in junction operation. Equally, an over-sensitive detector can generate unnecessary calls and compromise coordination. Effective radar detector selection begins with this operational reality: the right unit is not simply the one with the longest quoted range, but the one that produces dependable, usable data for the decision the network must make.
For highways authorities, signal engineers and contractors, above-ground radar offers a practical alternative to road-embedded loops. It can be installed with less carriageway intervention, avoids cutting the road surface and can provide richer information than a simple presence input. However, radar performance is always linked to the site geometry, intended application, mounting position and controller or platform integration. These factors should drive the specification from the outset.
Start radar detector selection with the operating outcome
The first question is not which sensor to buy. It is what the detector needs to achieve at the location. A radar installed for vehicle actuation at a signalised junction has different requirements from one used for speed feedback, queue monitoring, cycle detection or traffic data collection.
For signal control, establish whether the detector must provide approaching vehicle detection, extend a green phase, register a stopped vehicle, identify queues, or maintain detection across several lanes. Define where the detection needs to begin and end, the required response time, and whether the output must distinguish direction of travel. At a busy urban junction, preserving reliable detection at low speeds may matter more than maximum detection distance. On a high-speed rural approach, early and consistent approach detection may be the critical factor.
For monitoring schemes, the useful outputs may include speed, volume, lane use, vehicle class, direction and headway. These are not interchangeable capabilities. A sensor that is entirely suitable for count and speed data may not offer the logic, zone control or output behaviour required for real-time signal actuation.
A clear operational brief also prevents an avoidable mistake: treating radar as a like-for-like replacement for an existing loop without reassessing the detection strategy. A non-intrusive sensor creates an opportunity to improve zone design, cover multiple lanes from one mounting point and capture data that supports wider network management.
Match detection performance to the site geometry
Radar detects movement and range using radio waves, but its practical performance depends on how the detection field interacts with real traffic. Carriageway width, lane layout, gradients, bends, street furniture, nearby structures and the available mounting height all affect what the sensor can see and how reliably it can separate road users.
A site survey should confirm the available pole or mast position, mounting height, lateral offset and viewing angle. The sensor must have a clear, stable view of the approach or crossing area. Signs, foliage, parked vehicles, bridge parapets and other roadside equipment can restrict the usable field of view. A poorly positioned detector may still produce data, but it may not produce data that can be trusted to operate the junction safely and efficiently.
Zone configuration matters just as much. Specify the number of detection zones needed, their shape and their separation. Distinct zones can support different signal functions, such as an upstream call, a nearer extension zone and a queue or presence zone. On multi-lane approaches, lane-specific detection may be needed to prevent vehicles in one lane influencing another movement. This is particularly relevant where turning traffic, bus lanes or short flare lanes are present.
Radar is highly effective for moving vehicles in many conditions, including poor light and adverse weather that can challenge some optical systems. Yet no detection technology should be selected on a generic claim of accuracy. Slow-moving traffic, stationary objects, tightly spaced queues and complex movements require careful assessment against the detector’s actual capabilities and configuration. Where the operational requirement includes detailed road-user recognition or challenging stationary detection, radar may be most effective as part of a combined solution with AI video detection.
Specify the data and classification that will be used
More data is only valuable when it informs an operational action. Before specifying classification, decide what the controller, traffic management team or analytics platform will do differently with it.
Vehicle length and class can support demand-responsive operation, freight monitoring and more meaningful traffic counts. Direction data can distinguish opposing flows at suitable locations. Speed data can trigger a speed information display, support enforcement-adjacent monitoring programmes or reveal approach-speed trends. For corridor management, reliable volume and occupancy indicators can help engineers identify developing congestion before it becomes visible through complaints or incident reports.
The classification required should be proportionate to the scheme. If the objective is simply to call a side-road phase, basic vehicle detection may be sufficient. If a local authority is evaluating active travel interventions or freight impacts, it may require consistent separation of vehicle types and complementary detection for cycles and pedestrians. Motorcycles, bicycles and pedestrians present different radar signatures from cars and lorries. Their detection should be verified in the actual deployment geometry rather than assumed from a general product description.
For cycle schemes in particular, consider the speed range, route alignment and likely group riding behaviour. A detector must reliably see a cyclist approaching slowly, moving obliquely or waiting in the intended detection area. The same discipline applies to shared-use crossings, where the detection objective may be a call for demand rather than detailed classification.
Check integration before the installation design is fixed
A technically capable detector can still fail to deliver value if its outputs do not fit the existing control architecture. Radar detector selection should therefore include the controller interface, communications method, power provision, cabinet capacity and cybersecurity requirements at an early stage.
For a signal-controlled site, confirm the required input and output arrangement, including volt-free contacts, digital inputs or appropriate communications interfaces. Establish how detector health, loss of communication and fault conditions will be presented to the controller or monitoring system. Engineers need to know whether a fault results in a safe fallback mode, how it is logged and who will be alerted.
For traffic monitoring, define the data format, reporting interval, time synchronisation and ownership of the collected data. Raw detections, aggregated counts and event notifications serve different purposes. A platform should make it straightforward to validate data quality, compare locations and export information for network analysis without creating an ongoing manual burden.
Wireless connectivity can reduce civil engineering and simplify deployment, particularly where power and communications routes are constrained. It also introduces its own planning questions around coverage, antenna placement, resilience and maintenance access. The best option depends on the site, not on a preference for wired or wireless technology.
Prioritise installation quality and whole-life operation
One of the strongest arguments for above-ground detection is reduced disruption. There is no need to cut slots into the carriageway, close lanes for loop installation or return repeatedly to repair failed road-embedded cable. That benefit is realised only when the mounting, alignment and commissioning process is treated as part of the system design.
Specify equipment that can be safely accessed for installation and future adjustment, with suitable brackets and cable protection. Confirm the environmental rating, operating temperature range and resistance to vibration. In exposed locations, mounting rigidity is important: a detector that moves slightly in high winds can change its field of view and affect repeatability.
Commissioning should include live tests across the full range of expected road users, lanes and movements. Test daytime and night-time operation where relevant, then record the agreed zone layout, settings and acceptance results. This baseline is valuable when the road layout changes, a signal plan is reviewed or an operator reports unexpected behaviour months later.
It is also worth agreeing who owns detector configuration after handover. A simple process for making controlled adjustments, documenting changes and reviewing performance protects the integrity of the detection strategy. C & T Technology’s approach to above-ground traffic detection is founded on this practical point: hardware, configuration and traffic engineering expertise must work together.
Build evidence into the procurement decision
The most dependable specification combines a defined use case with measurable acceptance criteria. Rather than asking for a detector described as accurate or multi-lane, set out the movements, zones, classifications, outputs and environmental conditions that must be demonstrated. Include the expected mounting arrangement and the integration endpoint.
A representative site trial can be particularly valuable where the layout is unusual, traffic is mixed or the proposed sensor will support a safety-critical operational decision. Trials should test the difficult conditions, not only free-flow traffic on a clear day. Queued vehicles, cyclists, large vehicles, turning movements and wet-weather operation may reveal configuration needs that a desk review cannot.
The strongest radar scheme is rarely the one with the longest feature list. It is the one whose detection is designed around a clear control or monitoring objective, verified at the kerbside and maintained as part of the wider network. When selection starts with the road user’s real movement and the operator’s required response, non-intrusive radar becomes a practical route to safer roads, reduced congestion and more sustainable traffic management.