You really donīt understand anything Iīm saying. Concerning demand figures: I said, that connecting passengers already are worked into the system, otherwise Atlanta for example would have the demand of any other middle-sized city of the US.
So the numbers of your transit passengers would just add on top of already worked in numbers, leaving demand/traffic hugely oversized.And Iīm not talking just lowering the figures a bit, it needs a complete data overhaul. (City based demand)
Concerning hubs: With connecting passenger system you can build a hub out of any base airport you choose.If we use city-based demand itīs up to the players where they evolve their hub for connections. Real-world infrastructure data have evolved over ages with traffic/politics as given by history, but if we develop a new system of hubs, infrastructure would have to grow after our needs, turning airports like maybe Kansas City into a major american hub,leaving Atlanta a mediocre airport for example. Itīs going to be a completely new world for every game, not just re-playing history over and over.
In your example you just talk about one additional connection via hub. But whatīs about all other connections that are possible within 4 (why?) hours transit, each and every one forming a route you would have to establish, make prices for and check regularly.And itīs not just concerning you, but every player in game, the data to be handled would not just add up ,they would explode.
What about the time needed for every player, to harmonize all that additional demand/traffic? With big businesses, one additional flight from hub to a new destination might open up numerous of possible new connection routes, each and every one to be managed.How many staff you are going to hire in RL to help you manage that monster? How are the single passengers documented per aircraft, because on every single plane there will be direct passengers and passengers for/from up to hundreds of other destinations, not to mention the possibilities of connecting flights via more than one hub, connections to other alliance members, to other airlines, codesharing?
How should planning/documentation of flights/aircrafts look, when every flight is also used as a part of another one and every passenger has another final destination? How do you set prices, when splitting complete price evenly over used single legs canīt be the answer considering SH/LH connections? How do you work out single flight/aircraft results, if in worst case every passenger is paying a different fare for his single leg seat? What about combinations of different cabin classes?
You will have to think just one or two steps further to see all those additional problems to be solved besides your nice shiny new column.So itīs fully understandable why it is not implemented yet.