> I've updated the --wind=DIR@SPEED option to allow a range for DIR or
> SPEED. For example, winds from 180 degrees at 10 knots gusting 15
> knots would be
>
> --wind=180@10:15
>
> I haven't had the chance to add variable wind direction to
> FGEnvironment yet, but the option will be accepted:
>
> --wind=180:220@5
There is a standard METAR way to write this, something like
18010G15KT
180V2205KT
I think you should parse that, and allow an optional "@".
You cannot omit the KT because it is over-riding the default windspeed units.
180@10G15KT
180V220@5KT
There is also the standard format for writing TAF and winds aloft,
but they are more cryptic and best restricted to an input file parser.
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
