Park and ride catchment drive time: counting who can reach a station car park
How to draw the area drivers can reach a station car park from in 10 or 15 minutes, count the residents inside it where population data exists, and check the approach roads.
Part of the guide Location intelligence automation
A park and ride catchment drive time study answers one question: how many people could reach this station car park by car in a few minutes, following the real roads? You draw the area reachable in 10 or 15 minutes around the car park, count the residents inside it, take away the part another station already serves, and check how the approach roads move at the hour commuters arrive. A circle on a map cannot do this, because a river, a motorway with one junction or a one-way system changes who can get there.
This is for transport planners, rail and bus operators, councils and the consultants who advise them. It covers how to choose the drive time, what you can and cannot count inside the area, a made-up example with three candidate sites, the mistakes that inflate a catchment, and an AI employee that keeps the figures up to date.
Which drive time to draw
People who drive to a station want the car leg to be the short one. Most studies therefore draw two areas: a core one of about 10 minutes, where the car park is an easy choice, and an outer one of 15 minutes, where it competes with driving all the way. The Travel area block draws both, by car, along the roads, up to 15 minutes or 10 km by road for now. Its travel times are for usual traffic, not the traffic at the moment of the run, so treat the edge of the area as a fair average and not as the 07:45 queue.
Draw the area around the entrance drivers will use, not the middle of the platform. On a large site the two can be several minutes apart, and a car park whose only entrance is on the far side of a level crossing has a very different shape from one beside a main road.
What you can count inside the area
Once the area exists, other blocks search inside it. Three are useful here.
- Residents. Demographics counts the people who live inside each area, with men, women and nine age groups, from xMap's population grid. It counts residents, not homes, cars or commuters, and it has figures only in some countries (among them France, Canada, India, Thailand, Egypt and Australia). There are none for the United Kingdom or the United States, so in those countries the block is not the tool and you will need your own census table.
- Other stations and car parks. Nearby places lists the railway stations, bus stations and public car parks inside the area from xMap's places database, so you can see what the new site would compete with and what it would feed.
- Road speeds on the approach. Traffic Flow gives the current speed, the free-flow speed and a jam factor from 0 to 10 on the roads around a point at the moment it runs. It gives no car counts, so it tells you how slow the approach is, not how many vehicles use it.
A made-up example: three sites outside Lyon
The numbers below are invented to show the method. A transport authority is choosing between three sites for a 600-space car park on a tram extension east of Lyon. It draws a 10-minute drive area around each proposed entrance and counts the residents inside.
| Site (illustrative) | Residents within 10 minutes | Also within 10 minutes of an existing station car park | Left for the new site | Jam factor on the approach at 07:45 |
|---|---|---|---|---|
| A, beside the ring road junction | 63,000 | 38,000 | 25,000 | 7.2 |
| B, at the end of the line | 41,000 | 6,000 | 35,000 | 3.1 |
| C, by the retail park | 58,000 | 29,000 | 29,000 | 5.4 |
Invented figures for illustration only.
Site A has the largest catchment on paper, but more than half of it can already reach an existing car park just as fast, and its approach is the slowest in the morning. Site B has the fewest residents and the most that nobody else serves, on a road that is still moving at peak. The authority takes B forward and keeps C as the alternative if land at B cannot be bought.
The subtraction in the third column is the step most studies skip. To do it, draw the same drive time around each existing station car park and compare the two totals for the places where the areas overlap.
Mistakes that inflate a catchment
- Counting people who live closer to the city than the car park. Few drivers go away from their destination to park. Look at the map of the area and discount the half that lies on the city side.
- Reading residents as users. A resident count is the ceiling. It includes children, people who do not commute and people who already walk to a station.
- One drive time for every site. A site by a motorway junction and a site in a suburb need the same minutes to be compared fairly. Change the minutes for all of them or for none.
- Forgetting the peak. The area is drawn for usual traffic. Check the approach roads separately on weekday mornings.
- A circle as a shortcut. When the routing service cannot draw an area, Travel area falls back to a circle at a typical speed and says so in the step and in every email. Do not present an estimate as a road catchment.
How an AI employee keeps it current
A catchment is not drawn once. New housing fills in, a rival car park opens, a junction is rebuilt. In xMap Flows two small AI employees cover it, and both fit the wider idea of location intelligence automation. The first redraws the catchment each month:
- Schedule: the first working day of the month.
- My data: a table of your candidate and existing car park entrances.
- Travel area: 10 minutes by car around each incoming place.
- Demographics: totals for each area, where population data exists.
- Email to the planning team, with a map of the areas.
The second watches the approach roads: Schedule on weekday mornings at 07:45, My data with the same entrances, Traffic Flow with Roads set to Within 500 m, and an email. After a few weeks you have the morning speed and jam factor for every entrance on every working day, in a table you can average.
What lands in the inbox each month is one line per car park: its area, the residents inside and the age groups. If you would rather start from a ready flow, park and ride sites at the edge of the city looks for candidate sites, and stations with no bike share or parking nearby finds the stations where the first mile is the weak point.
Questions
What drive time should a park and ride catchment use?
Most studies draw 10 minutes as the core area and 15 minutes as the outer one. Use the same minutes for every site you compare.
Can I count the homes inside the drive time area?
The Demographics block counts residents, with age groups, not homes or cars. It has figures in some countries only, and none for the United Kingdom or the United States.
Does the drive time area reflect rush hour?
No. Travel area draws for usual traffic. Check the approach roads at peak with Traffic Flow, which gives live speeds and a jam factor but no car counts.
How do I allow for a station that already has a car park?
Draw the same drive time around the existing car park and take away the residents who fall in both areas. What is left is the catchment only the new site serves.