Thanks for drawing my attention to info in the zoomed in view, Jeff.
".....It's not a number, but I see three places where the crosswind component can be easily guessed...."
Yeah, but as for "easily guessed" ..... That guessing is already exactly what we're all already doing (or trying to remember a rule-of-thumb such as "If the wind differs from the runway heading by 15 degrees, the crosswind component is one-quarter (25%) of the wind velocity. If the wind makes a 45-degree angle with the runway, the crosswind component is three-quarters (75%) of the overall wind speed").... Guessing that while lining up the runway, watching my glide path, announcing "on final", lowing flaps, etc. And the last thing I want to be doing at that moment is zooming in on the diagram to get graphically nothing more than the AWAS gave me by audio (wind direction and speed.)
I still say it would be ridiculously simple for the AWAS (and ATIS, AWOS, etc)to calculate and report by audio "Crosswind component is 15 knots from the left with gusts to 20 for runway 30." Technology to do that has been available for decades if not longer and virtually at no cost. Almost inexplicable that it hasn't been done."
Wouldn't you rather have the AWOS, etc. just give you the crosswind component as it does with with the traditional pressure altitude report? (That is, ATIS doesn't give you the real altitude, plus humidity, plus temperature and depend on you to estimate the pressure altitude for yourself while on final. ;-) It gives you the derived number you need. Why not do it for cross-wind component, as it's a trivial instant computation for the most primitive automated system at a trivial development cost. IMO odd and almost inexcusable it's not done.
And if iFly could extract and calculate that from the METAR data it gets and show it on our screen, that would be a start while waiting for the FAA to mandate it for 2050. ;-)
Alex