Does a busy road help a site? Traffic, visibility and access explained

A busy road helps a site when the business lives on being seen and on quick, unplanned stops: fuel, drive-throughs, coffee to go, convenience shops, billboards. It hurts when the traffic is so fast that drivers cannot react, or so jammed that nobody can turn in, and it matters little for places people plan to visit anyway, such as a dentist or a furniture showroom. The useful questions are how fast the road moves, how often it clogs, and how easily a driver can get in and out.

This article is for expansion, property and operations teams weighing a site on or near a main road. It explains what a road gives and takes from a business, how to read live speed and congestion figures, where those figures stop being useful, and how to check every candidate the same way without standing at the kerb with a clicker.

What a road gives a site, and what it takes

A road brings three things. Visibility: every passing driver and passenger is a chance to notice the sign. Pass-by trade: some of them stop on impulse, which is the whole business model of a fuel station. Access: customers who planned the trip can reach the door easily. It can also take things away: a fast dual carriageway with a central barrier lets drivers see a shop they cannot reach, heavy traffic makes the car park hard to leave, and noise and fumes put off people sitting outside a cafe.

• Gains most from passing traffic: fuel and charging, drive-through food, coffee kiosks, car washes, tyre and repair shops, roadside billboards, convenience stores at junctions.
• Gains a little: pharmacies, bakeries and supermarkets, which mix planned and impulse visits.
• Gains least: destination visits such as clinics, schools, offices, specialist retail and hotels booked in advance. For these, access and parking count far more than how many cars pass.

Speed and congestion are different signals

Live road data describes how traffic is moving, not how much of it there is. The Traffic Flow block measures the roads around each place at the moment a flow runs and adds these fields to it:

• speed_kmh: how fast traffic is moving now, averaged over the nearby road stretches.
• free_flow_kmh: how fast the same roads move when they are empty.
• jam_factor: from 0 (free) to 10 (standstill or closed).
• congestion_pct: how much slower than free flow the traffic is, as a percentage.
• traffic_level: the jam factor in words, from Free flowing to Standstill, plus how many road stretches were measured, how many are closed, and the busiest road.

Congestion is worked out as one minus the current speed divided by the free-flow speed. A made-up example: a candidate on a boulevard in Bogota measures 18 km/h where the road runs at 50 km/h when free, so congestion is 1 minus 18/50, or 64%. Another candidate on a ring road in Johannesburg measures 72 km/h against 80 km/h free, a congestion of 10%.

Illustrative figures only, to show how the fields read together.

Slow traffic is not automatically bad. A billboard on a road that crawls at the evening rush is read; the same board on a fast road is a blur. But a drive-through on a road that sits at a jam factor of 8 every evening loses the drivers who cannot cross two lanes to reach it. Read speed and congestion together with the layout of the site: which side of the road it is on, whether there is a turn lane, and where the entrance sits.

What the data can and cannot tell you

Live speeds answer how a road behaves at a given moment. They do not count cars, they have no split by direction and no built-in rush hour. A road can be free flowing because it is empty or because it is wide; it can be jammed because it is busy or because of one set of lights. To see a pattern, measure at the hours your trade depends on: a coffee kiosk cares about 7 to 9 in the morning, a takeaway about 6 to 8 in the evening.

The Roads setting decides how far around the place to look: the adjacent roads (about 150 m), everything within 500 m, or everything within 1 km. For judging a shopfront, use the adjacent roads; the wider settings average in streets that may have nothing to do with the entrance. Places within 300 m of each other share one measurement, so two candidates on the same block will read the same.

Mistakes to avoid

• Judging on one reading. A single Tuesday at 11:00 tells you about Tuesday at 11:00. Schedule the same check across a week before drawing a conclusion.
• Treating speed as volume. A slow road is not proof of many cars. Pair speeds with what is around the site, such as offices, schools and other shops, to judge how many people actually pass.
• Ignoring closures. A road reading slow because of roadworks will not stay that way. The roads_closed field and the Traffic incidents block show when a reading is temporary.
• Forgetting the exit. Visibility without an easy way back onto the road puts off repeat visits. Check the turns on a map before you trust a high-traffic reading.

Checking every candidate with an AI employee

Instead of reading one road at a time, let a flow measure your whole shortlist at the hours that matter and keep the readings in a sheet, so each site builds its own record over the weeks.

1. Upload your candidate sites to My data as a table with an address or a position for each.
2. Add a Schedule for the hours you care about, for example weekdays at 08:00 and 17:30.
3. Add Traffic Flow with Roads set to the adjacent roads.
4. Add Nearby places set to count the shops, offices or schools within 500 m of each site, so the reading has context.
5. Add an xMap LLM block to score each site as a roadside location for your kind of business, from the speed, the jam factor and the places around it.
6. Send each reading to a Google Sheets row or an email to the expansion team.

After two weeks the sheet holds each candidate's morning and evening speeds side by side, scored and explained, ready for the site visit where you check the turns, the signage and the parking in person.