Create new route providers and use them in the demo scheduler

[Random-Ranger]

Some thoughts for future development [from #247 ] :

Don't you think the routes should be loaded by the scheduler

Probably yes. In the next steps, we can make the scheduler pick selected routes out of all the routes available from one or more providers. The routes can be selected incrementally:

1. When the user starts a flight at an airport - load routes for the departure airport
2. When the user files a flight plan - load routes for the destination airport and for the en-route
3. When the user diverts to an alternative airport ...
4. etc

We should have providers for the different operations types

• Airlines (static or online based on user preference)
• Cargo ?
• GA (random based on supported aircraft ranges)

I think that every provider can provide multiple operation types. For example, if a provider implements integration with an online service that provides data for airlines, GA aircraft, and gliders, then such categorization wouldn't be helpful.

Instead, we can add an operation type parameter to the abstract query function. And according to the algorithm you describe below, at each step, we query every provider passing it the operation type that corresponds to the step.

Route providers should only provide routes for supported aircraft

I think you implemented this - you already limit the retrieval of the routes to B738?

• The scheduler could then work that way :

  • List for each operation type the gates available at the current airport

  • Load route providers for supported operations types

  • Then for each supported operation type and until there are no more routes or the load factor is reached:

    • pick a route
    • generate a flight plan/pilot/aircraft
    • choose a gates that matches the flight plan

I can file an issue if you think that's a good enough basis for discussion.

Yes, sure. Let's track it.

Originally posted by @felix-b in #247 (comment)