How to find businesses along a highway with a corridor search
A circle around a city misses most businesses along a highway. Search a chain of points spaced down the road instead, then sort the results by order along the route.
Part of the guide Location intelligence automation
To find businesses along a highway, do not draw one big circle: place a chain of points every few kilometres along the road, search a short distance around each point, merge the results and remove duplicates. The chain of small circles follows the road's shape, so you get the fuel stations, truck stops, motels and workshops beside it and not the suburbs that a single circle would sweep in.
This guide is for fleet and logistics managers, roadside assistance networks, fuel and charging operators, suppliers selling to roadside trades and anyone planning a service along a route. It covers why corridor searches beat circles, how to place the points, a made-up example on the road between Mexico City and Queretaro, an alternative using a drawn corridor, the mistakes, and an AI employee that keeps the list current.
Why a circle is the wrong shape
A highway is long and thin. A circle big enough to cover 200 km of road covers an area the size of a region, full of towns that are nowhere near the road. Searches also return the nearest places first and stop at a limit, so the result fills up with the dense town at the circle's middle while the quiet stretches of road, where a truck stop matters most, are left out.
A corridor of small circles fixes both problems: each search covers only a few kilometres of road and its sides, and every stretch gets its own share of the results.
Placing the points
- Trace the route on a map and write down a point every few kilometres. Closer points in built-up areas, further apart on open road.
- Add points at every junction and interchange, where services cluster.
- Give each point a name that says where it is on the route, such as km 45 northbound, so results can be put in order later.
- Save the points as a small table with name, latitude and longitude, and upload it to My data.
- Choose a search distance that covers the road and its service roads but not the towns behind: often 1 or 2 km.
Each point then acts like a site of your own. Nearby places, set to search around each incoming place, looks around every point for the types you pick and tags each place found with the point it was found near and its distance in metres. It can search around up to 100 points in one run.
A worked example in Mexico
This example is made up. A freight company runs trucks between Mexico City and Queretaro and wants a directory of fuel stations, truck stops, tyre shops and places to eat along the highway for its drivers.
- The planner places about forty points along the route, closer together at the edge of Mexico City and around the interchanges, wider apart on the open stretches.
- Nearby places searches within 1 km of each point for gas stations, truck stops, tire shops and restaurants.
- Remove duplicates keeps each business once where neighbouring circles overlap.
- A Filter keeps only places that are open and have a rating, and a Calculated field turns the point's name into a distance along the route.
- Sort and limit puts the directory in order from Mexico City northwards.
- The drivers get a sheet and a map: every service along the road, in the order they meet it, with phone numbers where they are listed.
The useful part of the result is often the gaps. The directory shows a long stretch with no truck stop at all, which is exactly where drivers need to plan their breaks.
The other way: a drawn corridor
If you would rather draw than list points, the Map business scan block can search inside your own boundary: draw a long, thin shape along the road, paste it as a GeoJSON polygon, and choose Cover the whole area so a grid of searches runs across it. Only places inside the shape are kept. This works well for one corridor checked now and then. For a corridor you check every week, the table of points is easier to adjust: move or add a point and the next run follows.
Mistakes to avoid
- Circles too wide. A 10 km radius around each point brings back whole towns. Keep it tight.
- Points too far apart. If the circles do not touch, stretches of road between them are not searched at all.
- Forgetting both directions. On divided highways, services sit on one side. Name the side in the point, and tell drivers which way each place serves.
- Not removing duplicates. Overlapping circles find the same station twice, and the directory looks longer than it is.
- Searching once. Roadside businesses open and close. Rerun the search every quarter at least.
How to do it with an AI employee
In xMap Flows an AI employee can refresh the corridor directory on its own. The blocks:
- Schedule: every quarter, or every month for a busy route.
- My data: the table of points along the road.
- Nearby places: around each incoming place, within 1 or 2 km, the types you need.
- Remove duplicates: each business once.
- Place classifier: tidy categories such as fuel, truck stop, tyres, food.
- Sort and limit: in order along the route.
- A sheet in Google Sheets for the drivers' directory, a map, and an Email to the fleet manager listing new and closed places.
What lands in the inbox is the updated directory and a short list of what changed along the road since the last run. The truck stops and rest areas on my corridor and truck stops and fuel along the haul corridor templates are close starting points that search the corridor's cities; swap the cities for your points table to follow the road itself. Towns on the highway short of fuel stations turns the gaps into an expansion list, and towing partners along the highways builds a roadside network. See the location intelligence guide and the logistics page for more.
Questions
Why not just search the cities along the route?
Cities cover the towns, not the road between them. The stretches where drivers most need services are often between towns, so points along the road catch them.
How far apart should the points be?
Close enough that the circles touch or overlap. With a 1 km search distance, points about 2 km apart cover the road; on open road you can space them more widely with a larger distance.
Can I draw the corridor instead of listing points?
Yes. Map business scan can search inside a drawn shape pasted as GeoJSON, covering it with a grid of searches.
Does it know which side of the road a business is on?
Not directly. Each place has its position, so you can tell the side from the map, and naming your points by direction helps.
How many points can one run search?
Nearby places searches around up to 100 incoming places a run, which covers a long corridor at sensible spacing.
Templates that do this
Read next
More on business and places data · Every article · Templates