Just want to go over METAR speak. One good one is that TEMPO can apply to any variable. Right now EGLL has BKN011 and at the end there is TEMPO SCT011.
EGLL 140550Z AUTO 20005KT 9999 BKN011 10/08 Q1025 TEMPO SCT011
Here is another great remark in METAR: VIRGA. This is the coolest feature flight simulator has with the weather are those correct rainbands and virga.
The last and most important other remark in METAR is WS or WSHFT. The wind shear remark can then override the METAR wind creating layers of different wind directions.
Yes, we all know clouds are always reported as AGL from the weather station location. I think the location elevation of the Metroblue weather station location may be different from the METAR station.
Last, I will post this legend just for review. Basically, in almost every case a remark in the other section will override something from a normal METAR reading.
METAR/TAF Abbreviations (moratech.com)
EDIT. I found one more example. I think things like runway visibility are a little beyond what MSFS would want to accomplish but maybe not.
ESDF 140620Z 18003KT 0500 R01/0550V1000N R19/0600N -RA FG VV002 05/05 Q1017
This METAR has an N. You have to dive a little deeper to figure that one out. I found it means Night or North. MSFS can disregard those runway visibility remarks. Instead using the 0500 visibility and the VV002 statement to create a layer of fog to whatever height makes the vertical visibility 200 feet and visibility under this fog layer 500m. In the USA, they use SM for visibility, but they might not for the RVR, I’m not sure if its feet or meters.
Bottom line, so much extra detail. The VV, FG, -RA are all that’s needed. And this METAR is missing a cloud level statement because they can only see up in the sky 200 feet I guess.