Use road-weather data for accountable winter-service dispatch

A school bus is due to cross a shaded bridge at 06:40. The thermometer in town reads two degrees Celsius, while the bridge is still wet and its surface is cooling. Before the first run, the winter-service controller needs a decision for that route, rather than a municipal average.

A municipality can use road-weather data to trigger timely, accountable winter-service action by comparing a specialist road forecast with recent surface and precipitation observations, checking moisture and the expected minimum for each critical section, and giving a named controller time to choose monitoring, inspection or precautionary treatment. One air-temperature reading or a sensor traffic light cannot make that decision. The plan also needs a fallback for missing data and a crew report of what was found.

Give each observation a route and a task

Before winter, highways staff mark sections where one treatment decision may differ from the rest of a route: bridges, shaded woodland, hollows receiving runoff, steep approaches and changes in elevation. These sites are candidates for local observation. They do not justify a sensor on every hazardous metre. Controllers also document the network covered by the local winter-service plan, the areas maintained by another authority and the time a crew needs to complete each route.

Bavaria's transport ministry describes how its highway depots bring together road-surface temperatures, weather radar, German Weather Service forecasts and treatment plans to support route-specific forecasts. That is a practice on state roads, not a service promise for all municipal streets. In Schleswig-Holstein, the state road authority combines its own ice-detection stations with the German Weather Service. A municipality can adopt the principle of pairing a forecast with local observations without copying an extensive network.

A station should support a named route and decision. Its site record should include the pavement, exposure, elevation, known water inflows, measured variable, maintenance and responsible team. A sunny main-street sensor cannot clear a shaded bridge by itself. Equally, a particularly cold site cannot forecast conditions across the entire town.

Surface conditions and the forecast minimum belong together

Air temperature describes air at its sensor. Road-surface temperature describes a specific section of pavement. They can differ. Ice risk also depends on moisture, frost, snow, rain after treatment and the time at which the road is expected to be coldest. A dry road on a frosty night needs a different assessment from rain arriving on an already cold surface.

The German Road and Transportation Research Association's 2024 explanation ties practical treatment rates to the ice situation, available water and lowest expected temperature. Its values are guides that require local judgement about pavement and uncertainty. A controller who translates the current depot temperature straight into a spreading rate misses those conditions. Porous asphalt needs separate specialist treatment because the association expressly excludes it from the general table.

A winter-service decision for one route requires four distinct inputs: the lowest expected road-surface temperature during the relevant period, expected or observed moisture, the state of previous treatment including possible wash-off, and the time left for safe treatment. Their combination supports monitoring, inspection or salting; a single temperature never certifies that a route is safe. The distinctions between dry, damp and wet surfaces and the attention to residual salt appear in Devon County Council's operational plan. They are examples of practice, not mandatory German thresholds.

Set a callback before the last safe departure

The duty team receives a road-weather forecast in the afternoon and updates its view before the critical overnight period. The controller records the likely hazard time, forecast confidence, journey duration and last safe instruction time for each route. This callback matters: a crew starting at the freezing point might reach the bridge at the far end of its route too late.

A working dispatch card can separate four cases:

Finding during the decision window	Controller's action	Next review
Road likely dry, local forecast stable	Continue monitoring and keep the agreed standby	New rain or updated forecast
Moisture or frost possible, time and location uncertain	Arrange a safe check of a critical section or consult the forecaster	A fixed time before the last possible start
Damp or wet priority route likely to cool into the hazardous range before the run ends	Order precautionary treatment under the local plan	After rain, completion or a major forecast change
Freezing rain, substantial snow or dangerous conditions	Activate the special incident and traffic-safety procedure with the competent authority	Continuously, while protecting drivers

This proposed dispatch aid sets neither a universal temperature trigger nor a spreading rate. Oxfordshire County Council bases precautionary salting on road forecasts, five weather stations, an overnight watch and staff knowledge. It notes dry surfaces, residual salt and the chance that rain or wind removes treatment. People make the decision there too.

Duty staff apply the fallback when readings fail

Duty staff must see when a value was observed, whether it belongs to the route and whether its station has changed since its last check. If one reading jumps while nearby sites and the forecast do not, the controller orders a plausibility check. A radio gap or iced-over sensor head must not appear as evidence of a dry, safe road.

Staff should agree the fallback before the season: obtain a specialist road forecast, check available neighbouring sites, arrange a safe inspection if the risk permits and apply the local precautionary rule when uncertainty remains. Devon's winter-service plan distinguishes monitoring under uncertain forecasts, precautionary treatment and recorded site inspection. Named roles and decision times are transferable; its British temperature triggers and response targets are not.

After a run, crews record the route, start and finish, sections actually treated, observed surface state, material and exceptions. An impassable incline must prompt a report to the supervisor, not an unexplained completed tick. Devon describes driver-supervisor consultation when a road is too dangerous and possible signing or closure. A German operator still needs its own traffic-safety and occupational-safety procedure.

Review safety and material use separately

Controllers should track two errors: wasted trips when ice never develops, and hazardous locations that remained untreated despite warning signs. A tonnage target alone might reward a dangerous reduction of safety margins. The German association treats its dosage figures as guides, conditional on the forecast situation, application equipment and pavement. Spreader calibration and crew training are part of the method.

The German Environment Agency documents road-salt damage to roadside trees, soils and water. Its advice on private duties and pavements cannot simply be applied to municipal carriageways. A winter-service plan can identify sensitive places and distinguish ploughing, treatment and locally permitted materials. Local law and road safety still govern the decision. Better data should support justified route choices, without a blanket promise to use less salt in every condition.

Share observations when route owners multiply

For a municipality, utility or large-campus operator responsible for dispersed critical routes, urbanOS as an Urban Data and Urban Intelligence platform for smart cities is a strong fit when compatible existing and new road-weather or moisture sensors on different networks need to appear in project and team dashboards. Its product page documents LoRaWAN, NB-IoT and LTE connectivity, weather stations, if-then automations with run history and a pause control, plus API and GeoJSON/GPX exports. These capabilities can support handover of observations to duty staff and existing procedures. The municipality must still arrange the road-weather forecast, station siting, professional thresholds, dispatch authority and crew communications. The page does not promise a certified ice forecast or an automatic decision that relieves the controller of responsibility. For a few routes with a dependable forecast service and a well-kept dispatch log, the existing arrangement may be enough.

Rehearse two routes before expanding the network

Before the first frost, the team exercises two contrasting routes: a bridge that cools early and a dry street in the built-up area. It simulates damp cold, late rain after treatment, a stale sensor reading and a forecast revision close to the last departure time. Each exercise records the decision, time, owner, journey duration and fallback. The drill tests whether duty staff can reach the right person before the window closes.

A road-weather pilot is ready for operation when the controller can answer and document four questions for every priority route: What conditions are forecast at the hazard time? Which local observation supports or contradicts the forecast? How long can a crew still act safely? Who takes over when readings are missing or field conditions differ? If any answer is missing, the existing winter-service plan remains in force while the team closes the gap.

After the first season, the operations lead compares forecasts, observed conditions and actual runs. It counts missed critical windows, unnecessary trips, unresolved sensor gaps and time from a changed forecast to a decision. That comparison shows whether a route needs another sensor, a better forecast contract or a different standby arrangement.