Excessive Temps Reported In As6.5

[Ray Proudfoot 8,960]

Hi,AS6.5 Build 552 has started reporting excessive temps. Here's the current report for FAJSFAJS 292200Z 3000/0106 02010KT CAVOK FM300600 34008KT CAVOK BECMG 3009/3011 30014KT SCT045 TEMPO 3014/3022 VRB15G25KT 5000 TSRA FEW040CB BECMG 3022/3024 04012KT SCT012 TEMPO 0101/0106 5000 BR BKN006 Am I correct in thinking BECMG 3022/3024 are the temps? Is this a server issue or something in the program? Or has something gone awray on my system?

[Damian Clark 1,262]

Hi Ray,That is a TAF report, not a METAR. The BECMG numbers indicate the date/time that the subsequent conditions are expected to prevail, but this is not a standard format (with the / and second date/time value).If you are getting this reported listed as a METAR in ASv6.5, it sounds like you are using TAF processing and the TAF is incorrectly being parsed into the METAR for dynamics, then that value is being read for temperature. This would be due to the invalid format. I would anticipate that the next TAF cycle will fix this, but if it does not please let us know and we will investigate potential solutions at the server end.Best,

[Ray Proudfoot 8,960]

Hi Damian,Thanks for your reply. The FAJS data was obtained just by entering the ICAO into the Fetch option but I first became aware of it via FS Flight Keeper's weather option. I was going to report it to Thomas Molitor until I checked AS6.5.I don't have TAF processing checked in my options. I'll continue to monitor this and will let you know how things go. Do you know when the cycle next changes?

[Ray Proudfoot 8,960]

Hi Ray,That is a TAF report, not a METAR. The BECMG numbers indicate the date/time that the subsequent conditions are expected to prevail, but this is not a standard format (with the / and second date/time value).If you are getting this reported listed as a METAR in ASv6.5, it sounds like you are using TAF processing and the TAF is incorrectly being parsed into the METAR for dynamics, then that value is being read for temperature. This would be due to the invalid format. I would anticipate that the next TAF cycle will fix this, but if it does not please let us know and we will investigate potential solutions at the server end.Best,

Hi Damian,I'm still getting these excessive temps being reported in the TAF report. Could you take a look please and see if there's anything you can do?Thanks.

[Andydigital 93]

Damian I would have a word with Thomas as I think he knows more about this subject as he has had to make some changes to FS Flight Keeper, but as far as I understand it they changed the format of the TAF's recently so this is probably why this issue has arisen.Actually I presume you already know about this as this thread was started at the end of November.

[JSkorna 137]

Hi Ray,Can you post an example TAF?Thanks,

[Ray Proudfoot 8,960]

Hi Ray,Can you post an example TAF?Thanks,

Hi Jim,I'm currently enroute FACT-EGLL and over central France. Here is the info from Fetch a report for EGLL...EGLL 280457Z 2806/2912 07013KT 9999 SCT018 TEMPO 2806/2810 9000 BKN014 PROB30 TEMPO 2821/2908 9000 BKN014Hope that helps.

[JSkorna 137]

Hi,No temperatures reported there.Thanks,

[Ray Proudfoot 8,960]

Hi,No temperatures reported there.Thanks,

Jim,The excessive temps are visible via FS Flight Keeper's weather info which it obtains from AS6.5. I can report this to Thomas if you prefer but as AS is gathering the weather data I suspect he'll just refer me back to you.Do you have FSFK? It's quite easy to see these erroneous reports.

[Andydigital 93]

Ray, Thomas already knows about this problem in FSFK and a fix is being implemented in a soon to be released beta, there may be a beta that fixes this already which can be obtained by visiting his forum.

[Ray Proudfoot 8,960]

Ray, Thomas already knows about this problem in FSFK and a fix is being implemented in a soon to be released beta, there may be a beta that fixes this already which can be obtained by visiting his forum.

Andy,Thanks. Indeed there is a fix that fixes this problem. I'd wrongly assumed it was a AS6.5 problem. My apologies Jim / Damien.Implemented TAF format changes (November 2008)