Train station penalty when train already inbound.

[Simie]

If there is more than one station with the same name, a train will decide one based on distance, circuits enabling/disabling, or signals.

My scenario: I have a fleet of trains to pick up ore from outposts. I don't want to manage lines individually, it would take too long. So, I would name all my outpost stations "Iron Ore Pickup" and have every train in the fleet move between "Iron Ore Pickup" and "Iron Ore Dropoff". An outpost would disable it's station via circuits when there isn't enough to fill up a train. Trains would only visit outposts with resources available and more unproductive outposts wouldn't keep a whole set of trains busy if they're not needed. It would auto-balance.

But, trains will always choose the closest outpost, and multiple trains will be dispatched to that outpost while the first train is en-route. If there could be a penalty applied to the sorting used by the train logic when there is a train already inbound it would prevent this by prioritising open stations with no train inbound.

[Engimage]

I have made a similar but a bit more extended suggestion before
viewtopic.php?f=6&t=47695

[ssilk]

If you don't want to have a train on a train stop, why don't you just close the stop?
You can automate that: For even game-minutes A is closed, for uneven minutes A' is closed. So by probability the trains drive to both stations...