In the attached file, there is a METAR and the decoding.While METAR states CAVOK, decoding gives clouds which are also depicted in the Map page and in FSX.How can this be? In the same region, the METAR for LGTT is interpolated (wrongly) as in the second attachment, while there are three major airports within 50nm. So, the other three airports report CAVOK but LGTT appears cloudy.

Same here. I have clear skies (some high cirrus... but blue skies almost all) in my area.. and I see cumulus scattered in the sim... And the metar says CAVOK.

Well, first of all, have you tried to reduce the CAVOK cloud generation slider in ASE to zero ? CAVOK itself does NOT mean CLR or NCD, it just says there is no ceiling (that is broken or overcast cloud layer) or CB below the MSA at the reporting airport... this means the sky can be covered up to 4 octas (= scattered) and tell you CAVOK ... Regards, Christoph

As a matter of fact CAVOC generation was at 10%. I will test again with slider down to 0% and check again. What about the interpolation report? Are interpolation details you get from Report screen really the ones used for the airport stated in ID box?

As mentioned (thanks Christoph) CAVOK does not mean clear and the CAVOK slider can give you clear if you want it, despite this not being accurate to real life (at least not in all areas, i.e. CAVOK is indeed used a little differently in the US vs. Europe). The slider helps you get the results you desire. The interpolation system must use the closest station in each of 4 directional quadrants. If there are some far away and some close, the close ones will very much "outweigh" the far ones, but we still need ONE station from EACH quadrant. By user request we are working to "hide" this information in the future to prevent confusion. In those shots the interpolation is not for the station METAR, so I cannot compare this. We have no reports of any problems in the interpolation system, and recent improved surface temperature and wind interpolation in sparse-data station areas (B651) which is available in BETA in a pinned topic on this forum. But6 I'd be happy to look into this if you provide matching screenshots (i.e. wx report screen in full along with the interpolation details for that station).

CAVOK issue resolved as you both suggested by pulling the slider to 0%. I was confusing the use of the slider as "quantity" rather than "probability" (which really is). Interpolation: pls see attached. As you can check on the map, there are close-be stations/airports to be used in all quadrants rather than the ones shown in interpolation details.Strange thing I noticed is that when I first opened ASE, I first checked LGTT; this time interpolation seemed quite normal (using close-by stations). I then checked LGMG (which is quite close to LGTT) and I got what you can see in the picture. The TAF reported is actually from a close-by airport (as it should) but interpolation details are out of place.When interpolation seems to work funny, the stations used seem to be almost the same or at least from the same area.

Tested some times more. Here what I find so far:1. Start ASE.2. The first interpolated station you check in "report" page appears fine (using close-by station) in "interpolation details".3. The next station(s) you will check in "report" page have in "interpolation" page the wrong stations (almost identical each time and surely from the same remote area - in my case somewhere in W. Africa). Nevertheless, the actual METAR data calculated by the interpolation seem to me to be correct (compared to METARs of the actual near-by stations). If anyone could cross check this last point, would be great.Can it be only a funny glitch/bug of the "interpolation details" screen and not the actual interpolation algorithm?

Hello, It appears the problem in this case is your usage of lower case letters in the station ID (LGmg). The Wx report screen can handle this, but the Interpolation detail reporting can't. Using LGMG for your station lookup will provide the interpolation details you are looking for. We've documented this "find" and will work to automatically correct casing errors in the ICAO field as applied to the interpolation details. The interpolation system appears to be working properly.

ok, thnx for quick reply. That was something that can drive you mad for ages