[bug] select ordering

[RudiZhang]

I just found a very strange bug, Wind is 270/2 but runway selected 24 even 06 is above than 24

"runways": [ {"id": "06", "true_heading": 61}, {"id": "24", "true_heading": 241} ]

No preferred_ was used. but "no_factor_wind": 6, <- It means below 6kt will be assumed as 0 speed and select from above to bottom?

[laxentis]

The logic behind no factor wind for now is to assume a wind of 270 then.
I will include a setting in the json file for the assumed wind direction as it may differ worldwide.

[RudiZhang]

@laxentis Ah I see, I thought it was top to bottom selection in the wind calm condition or ignoring the wind condition. Since the headings are different for each airport, maybe a priority sort can be added? Convenient single runway direction selection regardless of wind direction? :)

[laxentis]

I think the best course of action would be to treat the runway's priority in the order they are configured (preferred runways should be put first in the config file). That would simplify assignment logic and would allow for additional per-runway defined features ( #7).