FlowsBook a callSign inCreate free accountSign up
Roads and traffic

How wet weather slows a delivery round, and how to measure it

Rain makes roads slower and rounds longer, but by how much on your own streets? How to record road speeds on wet and dry days and turn the gap into a buffer for each round.

Part of the guide Location intelligence automation

By the xMap team · · 5 min read

Wet weather slows a delivery round in two ways: the roads move more slowly, and each stop takes longer as drivers park, carry and wait in the rain. You can measure the first part for your own streets by recording live road speeds at the same points and hours every day, next to that day's rain, and comparing wet days with dry ones after a few weeks. The gap you find becomes a rain buffer: add it to planned times on days with heavy rain in the forecast, and warn customers before they wait.

This is for delivery managers, dispatchers and owners of courier, grocery, pharmacy and parcel rounds who plan on usual drive times and watch them fall apart whenever it pours. It covers what the data can and cannot show, how to build your own wet-and-dry record, a worked example, the traps, and the AI employees that do the recording and the warning.

What live traffic data can show, and what it cannot

Traffic Flow measures how traffic is moving on the roads around each place at the moment a flow runs: the current speed, the speed when the roads are free, the jam factor from 0 to 10, the congestion as a percentage and the level in words. It does not count cars, and it keeps no history of its own. Run it at 8 am and you learn how 8 am looks today.

That is exactly what you need, if you run it on a timetable. Every daily reading at the same points and hours becomes a row in your own record. Weather forecast adds the rain expected that day, and after a few weeks you can sort the rows into wet days and dry days.

Building your own wet-and-dry record

  1. Pick 6 to 12 points that every round passes: the depot gate, the main bridges, the busiest junctions, a school street, the road into each zone.
  2. Pick the hours that matter: when the vans leave, the middle of the round, and the evening return.
  3. Schedule a flow at each of those hours that reads Traffic Flow at every point and the day's rain from Weather forecast, and adds a row per point to a sheet in Google Sheets or a table in My data.
  4. After three or four weeks with some wet days among them, compare the average speed at each point and hour on days with heavy rain against dry days.
  5. Turn the gap into a percentage, and add that much time to rounds on days with heavy rain forecast.

A Data analyst block can do the comparison for you: ask it "for each point and hour, what is the average speed on days with more than 5 mm of rain and on dry days?" and it writes a small program over the rows, runs it, and answers with a table and a chart.

A worked example

Here is an invented example, to show the arithmetic. A grocery delivery team in Bogota records speeds at eight points, three times a day, for four weeks. Six of the weekdays had heavy rain in the morning.

TimeAverage speed, dry daysAverage speed, wet daysWet journey takes
07:3024 km/h17 km/habout 41% longer
12:0028 km/h23 km/habout 22% longer
17:3019 km/h14 km/habout 36% longer

Invented speeds, for illustration only. A journey at 17 km/h instead of 24 km/h takes 24 / 17 = 1.41 times as long.

So on this team's streets, a wet morning stretches the driving part of a round by around two fifths, a wet midday by a fifth. A round planned at three hours of driving needs about another hour on a wet morning, before counting the slower stops. The team now loads fewer stops on the first wave when heavy rain is forecast, starts that wave 30 minutes earlier, and sends customers a later window. These numbers are invented: yours will differ by city, road and hour, which is the reason to measure them.

Traps when measuring the rain effect

  • Too few wet days. Two rainy mornings prove nothing. Wait for several before trusting the gap, and keep adding days.
  • Rain at the wrong time. A day with rain at night and dry roads at 8 am is a dry morning. Use the hour-by-hour forecast if your mornings and afternoons differ.
  • Comparing different hours. A wet 7:30 against a dry noon measures rush hour, not rain. Compare each hour with itself.
  • Holidays and school breaks. A quiet holiday week makes everything fast. Mark those days and leave them out.
  • Closures that are not rain. Roadworks or an event can slow a point on a dry day. Traffic incidents shows closures, so you can explain an odd reading.
  • Reading the jam factor alone. It says how jammed the road is compared with free flow; the speed says how long the trip takes. Plan time on speed.

Two AI employees: one records, one warns

In xMap Flows, the work splits neatly into two AI employees.

The road diary

  1. Schedule: several times a day, at the hours you chose, on weekdays.
  2. My data: the table of measuring points.
  3. Traffic Flow, then Weather forecast for each point.
  4. Google Sheets: add a row per point with the time, speed, jam factor and rain.

The rain warning

  1. Schedule: every evening at 18:00.
  2. Weather forecast for the depot and each zone, for tomorrow.
  3. Filter on Rain (mm) above your threshold.
  4. xMap LLM, given your measured buffer, writes a short note: which waves to load lighter and how much earlier to start.
  5. Email or a WhatsApp message to the dispatch lead.

What lands in the inbox: on dry evenings, nothing; on evenings before heavy rain, a note naming the zones affected, the rain expected and the time to add, based on your own record rather than a guess. The diary keeps growing, so the buffer gets more reliable every month.

Questions

Does Traffic Flow show traffic on past rainy days?

No. It measures speeds at the moment the flow runs. To compare wet and dry days, run it on a schedule and keep the readings in a sheet or table.

Can I see how many cars are on the road when it rains?

Not with Traffic Flow, which gives speeds and the jam factor, never car counts. Hourly car counts since 2021 exist only for roads in the United Arab Emirates, through Regional data.

How many weeks of readings do I need?

Enough to include several wet days at each hour you care about. Three or four weeks is a start in a rainy season; longer is better.

Does Route planner allow for rain?

No. It plans on usual traffic and does not add time at stops. Add your measured rain buffer on top of its times.

Templates that do this

Read next

More on roads and traffic · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.