[question]use different rules to assign runway in use

[tgpetrica]

Hello,

I was thinking of implementing this at the local level, but it would be insufficient considering the complexity of the way in which the runways is chosen in the service.

For instance, in my local vACC we assign runway in use based on different rules:

1. wind: some runways could be used with a tailwind / crosswind component up to 6 knots, while other runways can accept up to 12 knots;
2. runway in use at other nearest airport: To elaborate here, we have the situation where, at one airport, a direction is used approximately parallel and sloghtly same direction to that from other airport: LROP 08 (means LRBS 07), LROP 26 ( means LRBS 25)
3. parallel operations: There would be more to talk about here, as there are many possible configurations

So, what would interest me is if there is the possibility of expanding the current application to be able to set the maximum tailwind per airport (no_factor_wind) or for several airports in the same group.

And it would also be the case that bases on the airport /airspace config can be set for some airports, even if that would also mean opposite directions for operating at low traffic flow. (For example, runway 11 used for departures, while runway 29 used for landings.)

[laxentis]

Sure thing. Sounds like good ideas. It should be pretty straight-forward to allow no_factor_wind to be configurable per-airport. Also selected runways affecting runway choices should also be doable.

[laxentis]

I've added per airport configurable no_factor_wind in 03f9fc0. Am thinking about extending it further down to runways. With the planned rewrite of runway assignment order (#3) it could simplify runway assignment logic.