That's 100% correct: This is a long-standing bane-of-my-existence issue.
We have a national rail provider, and we can debate until tomorrow, next year and the next century about whether or not it's properly subsidized. The reality is that it exists today, it moves people and it has a clientele, and that clientele can be leveraged both ways. This issue is not only for Via; it is also for Metrolinx and the GO regional network in the greater Toronto and Hamilton areas. It's increasingly an issue for anywhere regional rail is starting to deploy.
The issue is twofold. One, the clientele—the passengers on Via Rail or Metrolinx—get off at stations. Those stations are not served by Via or by Metrolinx per se. They are served by local transit agencies or, in the case of rural communities, sometimes private rural service providers or sometimes nobody and Uber.
The world would be flipped on its head to the benefit of Canadians with a simple data share of clientele arriving—when they arrive and where they need to get to—for local transit systems and rural providers. The reverse holds as well. Enabling those private and public providers to share their data backward to identify to the rail provider or, in the case of coach, if we take it even further, to the coach bus stations that do exist, with FlixBus and Red Arrow.... When those people are arriving at their nearest local transit stop, they are necessary clientele who can be leveraged for the rail network or the coach network going in the other direction.
If I may give you one example, a long-standing issue has been across the Metrolinx line. It holds for Via as well. You will have a number of public transit agencies on the backbone of Metrolinx through the greater Toronto and Hamilton areas. What you have is a one-way flow of information, typically, from transit into Metrolinx. You don't have it the other way, so a lot of our members of the public transit agencies on that backbone don't have real-time data telling them when the train arrives and when their bus should be there.
It is very simple. It's an operational choice. There has been a lack of political will, shall I say, at the regional, provincial and federal levels to recognize that this is causing damage to the mobility of Canadians. It is a data solution, an operational integration solution, and what has hindered it, of course, is that for municipal transit it's municipal, for rural transit it's often the private provider and for rail it's regional or federal. All of these bodies are not talking together in a data-sharing arrangement for ridership optimization.
Your point is correct: There are clients going both ways, and we are not leveraging them properly.