Smart traffic counting system for vehicles, bicycles, and pedestrians. Real-time traffic classification by type, lane, and direction, with speed measurement, no camera, no civil works, and traffic data integration via CSV, REST API, MODBUS, or uRAD Cloud.
Deployed by the Pamplona City Council — 8 radars and 2.7M annual passages monitored.
Quickly understand whether it fits your use case. A non-intrusive traffic counter for urban and interurban infrastructure — not a speed enforcement system and not video analytics.
Inductive loops and pneumatic tubes require civil works, road closures and maintenance.
Cameras depend on lighting, weather and privacy requirements — performance may degrade in rain, fog or low-light conditions.
uRAD is a non-intrusive radar-based traffic counter : 24/7 monitoring, no civil works and structured data ready for integration.
| Criterion | uRAD Smart Traffic | Cameras with AI | Inductive loops | Pneumatic tubes | Bluetooth / WiFi sensors | Manual counts |
|---|---|---|---|---|---|---|
| No civil works | Yes | Yes | Road cutting required | On-road installation | Yes | Yes |
| Continuous 24/7 monitoring | Yes | Depends on lighting | Yes | Temporary | Yes | No |
| Privacy · no image capture | Yes | Captures images | Yes | Yes | Anonymized MAC | Yes |
| Lane-by-lane counts | Up to 4 lanes | Yes | 1 loop per lane | 1–2 lanes | No | Operator-based |
| Vehicle classification | 5 classes | With ML | Limited | Axle-based only | No | Visual |
| Speed per vehicle | ±1 km/h | Estimated | By sensor pair | Yes | Section-based | No |
| Maintenance cost | Low | Medium | High · civil works | Replacement / reinstatement | Low | Manual labor |
| Integración API REST | Native | Variable | Requires PLC | No API | Variable | Excel sheet |
| Permanent deployments | Ideal | Yes | Yes | No | Yes | No |
| Temporary traffic studies | Yes | Yes | No | Ideal | Yes | Yes |
uRAD Smart Traffic is designed for projects that require continuous traffic data, technical integration and low-impact installation — not just a short-term counting campaign.
Each use case answers a project decision: where to install, which model to choose, what data to collect and how to integrate it.
Pamplona
Municipalities · Urban mobility
Continuous lane-by-lane traffic counts, heavy vehicle distribution and real-world speeds on main streets and avenues.
Decision supported: identify which streets require traffic calming or lane redesign.
Transport engineering firms
Fast deployment without civil works for traffic studies, before/after analysis and technical assessments.
Decision supported: measure the real impact of a traffic intervention.
ITS integrators · Traffic platforms
Data delivered through API or MODBUS to control centers, ITS systems and mobility platforms.
Decision supported: add radar-based counting without rebuilding the client’s backend.
Provincial councils · Roads
Counting and speed measurement on secondary and regional roads, up to 180 km/h, with data by direction.
Decision supported: prioritize maintenance, resurfacing or signage improvements.
Smart Cities
IoT sensor with documented REST API and uRAD Cloud, ready for integrated urban platforms and public tenders.
Decision supported: standardize traffic data within the municipal technical framework.
Pamplona
Sustainable mobility
Specific classification of bicycles and pedestrians to assess bike lane usage and pedestrian areas.
Decision supported: size sustainable mobility investments using real data.
Eight uRAD Smart Traffic radars monitor the city’s cycling network — without civil works, without cameras and with data integrated into the municipal platform.
The counters enable non-intrusive monitoring with very high accuracy and can even identify cyclists travelling in the wrong direction — 20,5% at Pío XII.
Also validated beyond road traffic: Inventeers in the Netherlands uses uRAD to count boats on inland waterways — Grip op Water project.
View project ↗We validate the setup before deployment to ensure accurate results on your road.
In correctly oriented installations, the system achieves more than 95% counting and classification accuracy. Performance is stable for 24/7 monitoring and does not depend on lighting conditions.
Real-world accuracy depends on mounting height, angle, lane width, road geometry and occlusions. Our team reviews each use case and recommends the configuration before deployment.
Where cameras lose accuracy in low light, rain or fog, radar maintains counting accuracy day and night.
A single installation covers traffic capture, classification, and data integration. Data is delivered via REST API or MODBUS — either to the uRAD Cloud platform or directly to your own system.
If you do not want to build your own dashboard, connect the radars to uRAD Cloud and get real-time statistics, report downloads and multi-sensor monitoring from your browser.
Same 60–64 GHz radar core, available in two versions. Choose the best fit for your deployment’s connectivity and integration needs.
A closed and compact sensor with native MODBUS RS-485 and with optional connectivity as required: WiFi, LTE/4G, or LoRaWAN connectivity options. Connect to uRAD Cloud or to your own system via REST API.
Processing processing with high-capacity internal storage: saves the full traffic history directly on the device, without relying on a continuous connection. Code access so the developer can integrate detection and send the data to their own platform in whichever way they prefer.
Send us the installation point and your measurement goal — we will recommend the right model, configuration and integration options.
| Feature | Compact | RPi model |
|---|---|---|
| Processor | Xtensa dual-core · 240 MHz | Raspberry Pi · ARM Cortex-A72 · 2 GB |
| Power supply | 8–42 V DC | 8–40 V DC |
| Power consumption | 2,5 W | 4,5 W |
| Communication | MODBUS RS-485 · WiFi / 4G / LoRaWAN opc. | WiFi · 4G nativo · API REST |
| Local storage | Basic internal buffer | Full onboard history · expanded capacity |
| Customizable code | Closed firmware | Code access · custom integration |
| External battery | Optional · purchase or rental | Optional · purchase or rental |
| Dimensions | 115 × 90 × 65 mm | 171 × 121 × 80 mm |
| Weight | 560 g | 1,1 kg |
| Data delivery | uRAD Cloud platform (AWS) · or · your platform via REST API / MODBUS | |
We review your road layout and provide a specific technical recommendation — so you know what to request, why it fits and what risks to consider.
We assess lanes, traffic direction, available mounting height, power supply, communications and measurement goals. If something does not fit, we tell you before quoting.
We tell you whether Compact o RPi según conectividad, integración, alimentación y entorno — no al revés.
We define whether you need CSV, API REST, MODBUS, uRAD Cloud or integration with your existing municipal or ITS platform.
You receive a proposal based on number of points, accessories, installation and integration, with estimated manufacturing and delivery times.
You do not need to know which model to choose: send us the approximate location and measurement goal — we recommend the configuration.
Request a technical recommendation →Freely access datasheets and user manuals for each model to review specifications, installation, configuration and integration before requesting a technical recommendation.
Compact model for counting, classification and speed measurement in installations that require a simple, non-intrusive solution.
Raspberry Pi-based model for projects that require local processing, connectivity and integration with external platforms.
Need a technical specification, tender support or integration examples for your project? We prepare it together with the technical recommendation.
Request a technical recommendation →The price depends on the model, number of measurement points, connectivity, power supply, accessories, installation and integration. We do not publish a fixed price because each deployment is different. Send us your road details and we will provide a quote within 24–48 h.
Number of lanes, traffic direction, possible mounting location, available height, power supply, communications and measurement objective. With that information, we can confirm whether the site fits before quoting.
Yes. Up to 4 lanes with one radar , depending on configuration and installation. The exact coverage depends on mounting height and road geometry.
Yes. Classification can include regular vehicles, medium vehicles, long vehicles, bicycles and pedestrians. Classification granularity and accuracy depend on configuration and site conditions.
Yes. In addition to counting and classification, it measures vehicle speed from 0 to 180 km/h with ±1 km/h resolution.
Yes. It is radar-based, not camera-based. It does not capture identifiable images of people or license plates, making it easier to deploy in privacy-sensitive environments.
Yes. Data can be delivered through API REST, MODBUS RS-485, CSV or direct connection to the uRAD Cloud platform. It is compatible with municipal platforms and existing control centers.
Yes. We can provide technical documentation to support public procurement, technical specifications and solution comparisons.: including datasheets, installation requirements, integration options and real-world use cases such as Pamplona
More than 95% counting and classification accuracy in correctly installed configurations. Real-world performance depends on mounting height, angle, lane width, traffic flow and occlusions, which is why we validate each point before final deployment.
Yes. The system is non-intrusive: can be mounted on an existing pole, gantry, streetlight column or roadside infrastructure. It avoids civil works such as inductive loop installation and pavement reinstatement.
Both. Compact and RPi are designed for permanent deployment, and they also fit temporary campaigns on existing infrastructure such as streetlight poles, posts, or gantries. If there is no power supply at the location, we offer an optional external battery — available for purchase or rental — compatible with both models for short-term studies.
Yes, with the RPi modelSince it is an open Linux system based on Raspberry Pi, the client’s development team can access the code and customize how detection is processed, where the data is sent, and in what format — sending it to your own platform, transforming it, filtering events, and so on. The Compact uses closed firmware and is designed for OEM integration via MODBUS or REST API without modifying the device.
Yes. As a radar-based sensor, it does not depend on lighting conditions. It is designed for 24/7 outdoor operation, with an IP66 enclosure and an operating range from -20 ºC to +80 ºC.
For each detection, the system can deliver timestamp, lane, direction, class and speed.. Available as event-by-event CSV, REST API in JSON, MODBUS RS-485, and aggregated data in the uRAD Cloud platform.
Not with the RPi model. It stores the full traffic history in its internal storage, so data is preserved even if the 4G or WiFi connection goes down for hours or days. Once the connection is restored. The Compact has a basic internal buffer — for locations with intermittent connectivity, we recommend the RPi model directly.
That is common. Send us the installation point and measurement objective - and we will recommend the right model, configuration and integration options before quoting.
We help you choose the right traffic counting radar based on road layout, number of lanes, connectivity, power supply and data integration requirements.
