TAF translation for a newbie....
Thread Starter
Join Date: Jan 2008
Location: Yorkshire
Age: 41
Posts: 691
Likes: 0
Received 0 Likes
on
0 Posts
TAF translation for a newbie....
for Leeds Bradford (EGNM) today
LEEDS BRADFORD
EGNM 061516Z 061601 15010KT 9999 SCT020 TEMPO 1620 7000 SHRA BKN010TCU PROB30 TEMPO 1620 4000 +SHRA +TSRA BKN008CB BECMG 1720 24006KT BECMG 2023 7000 BKN008 TEMPO 2301 3000 BR BKN003
Can someone explain it please. It has been explained once before to me but not in writing so I can refer back to it and get used to reading them. I understand bits but not other parts.
Thanks in advance
Liam.
Join Date: Nov 2001
Location: UK
Posts: 939
Likes: 0
Received 0 Likes
on
0 Posts
If you register free at Met Office: Weather and climate change then log on and go to Met Office: Online services - customer login you will find the answer
Join Date: Dec 2003
Location: Massachusetts Bay Colony
Age: 57
Posts: 476
Likes: 0
Received 0 Likes
on
0 Posts
In short, it means you ain't goin' anywhere! 
Greatest TAF decode I've heard so far:
If the TAF is:
1 line - you can pretty well go
2 lines - Only people with IMC ratings are going anywhere
3 lines - no one's goin' anywhere
As crude as it sounds, it's not often that far off!
Greatest TAF decode I've heard so far:
If the TAF is:
1 line - you can pretty well go
2 lines - Only people with IMC ratings are going anywhere
3 lines - no one's goin' anywhere
As crude as it sounds, it's not often that far off!
Join Date: Feb 2007
Location: Amsterdam
Posts: 4,598
Likes: 0
Received 0 Likes
on
0 Posts
Well done G-EMMA. Just one minor addition. Every "BECMG" and "TEMPO" group supersedes the previous, and in most cases the PROB groups will be aligned with the timing of the BECMG and TEMPO groups so they also supersede the previous.
So if you want to break it down into multiple paragraphs, here's how to do that:
EGNM 061516Z 061601 15010KT 9999 SCT020 <- The general overall picture at the start of the period, so at 16Z. Anything in here that's not superseded later on will remain valid throughout the period.
TEMPO 1620 7000 SHRA BKN010TCU <- Temporary condition between 16Z and 20Z, after which, if nothing else mentioned, it reverts back to 15010KT 9999 SCT020
PROB30 TEMPO 1620 4000 +SHRA +TSRA BKN008CB <- But within this same period it might get worse.
BECMG 1720 24006KT <- Ah, between 17Z and 20Z the wind will become 240/6. But for the rest the previous still applies. So theoretically, if the forecast holds true, at 20Z the conditions are 24006KT 9999 SCT020
BECMG 2023 7000 BKN008 <- And this is what's going to get established from 20Z to 23Z. So at 23Z the conditions should be 24006KT 7000 BKN008.
TEMPO 2301 3000 BR BKN003 <- And from 23Z onwards it will worsen once again.
Oh, and all times are UTC, not local.
So if you want to break it down into multiple paragraphs, here's how to do that:
EGNM 061516Z 061601 15010KT 9999 SCT020 <- The general overall picture at the start of the period, so at 16Z. Anything in here that's not superseded later on will remain valid throughout the period.
TEMPO 1620 7000 SHRA BKN010TCU <- Temporary condition between 16Z and 20Z, after which, if nothing else mentioned, it reverts back to 15010KT 9999 SCT020
PROB30 TEMPO 1620 4000 +SHRA +TSRA BKN008CB <- But within this same period it might get worse.
BECMG 1720 24006KT <- Ah, between 17Z and 20Z the wind will become 240/6. But for the rest the previous still applies. So theoretically, if the forecast holds true, at 20Z the conditions are 24006KT 9999 SCT020
BECMG 2023 7000 BKN008 <- And this is what's going to get established from 20Z to 23Z. So at 23Z the conditions should be 24006KT 7000 BKN008.
TEMPO 2301 3000 BR BKN003 <- And from 23Z onwards it will worsen once again.
Oh, and all times are UTC, not local.
Join Date: Feb 2007
Location: Amsterdam
Posts: 4,598
Likes: 0
Received 0 Likes
on
0 Posts
Pretty cool
Text: EGNM 061810Z 061904 24006KT 9999 SCT020
Forecast period: 1900 to 2000 UTC 06 July 2008
Where does the 2000 UTC comes from? This bit applies to 0400 UTC, doesn't it? Oh no, later on, you'll find
BECMG 2023 7000 BKN008
So that's where the 2000 UTC comes from.
So... Pretty smart analysis algorithm, lousy presentation of the results.
This is the site I like better:
MET'MAP - ORBIFLY FLIGHT SCHOOL - IFR ET CPL AMERICAIN EN EUROPE - FAA IFR AND CPL IN EUROPE
Mouse over a site to see the METAR and its interpretation. Click on a site to make it your personal center of the universe, then bookmark whatever URL is listed for next time. They don't interpret TAFs though, only METARS. But they do give access to both the short and long term TAFs and I also like the color coding to get a glance of flight conditions. Especially if you combine that with rainfall radar or something like that.
Join Date: Dec 2007
Location: France
Posts: 481
Likes: 0
Received 0 Likes
on
0 Posts
Well, I just got proper training so that I could read and understand them the same way I read and understand a book. Oh, and proper training in meteorology, climatology, forecasting, modelling, and so forth too.
How little I knew, eh?
How little I knew, eh?
Join Date: Feb 2002
Location: Popham
Posts: 313
Likes: 0
Received 0 Likes
on
0 Posts
If the TAF is:
1 line - you can pretty well go
2 lines - Only people with IMC ratings are going anywhere
3 lines - no one's goin' anywhere
1 line - you can pretty well go
2 lines - Only people with IMC ratings are going anywhere
3 lines - no one's goin' anywhere
Join Date: Feb 2007
Location: Amsterdam
Posts: 4,598
Likes: 0
Received 0 Likes
on
0 Posts
Been looking at that ADDS thing a bit more. There's something seriously wrong with that algorithm. The interpretation is done correctly, as is the presentation. But then the wrong bits of TAF are associated with the presentation bits. Everything is well (excellent, actually) up to the PROB30 bit.
Then comes the following line:
Text: PROB30
And some text suggesting it interprets that line. But what that piece of text actually interprets is
Text: PROB30 TEMPO 1920 4000 +SHRA +TSRA BKN008CB
which is correct, as this is one "block".
The next "block" then seems to interpret the line
Text: BECMG 2023 7000 BKN008
But this line is listed after the block it interprets. Because the line preceding it is the "TEMPO 1920 ..." line which should have been on the PROB30 line.
So past the PROB30 bit, all the content of the "Text:" lines need to be shifted up one block to make things fit. And even then the interpretation block doesn't neatly interprets what's on the "Text:" line, since the interpretation also looks through the rest of the TAF for anything that precedes or supersedes this bit of "Text:" line.
Just guessing what happened: A smart programmer wrote an algorithm to make a linear interpretation of a TAF, from hour to hour, and present it in text form. Which worked flawlessly. And this is no mean feat, because to interpret what the weather is going to be at the end of the period may mean going backwards in the TAF a few "blocks", and to interpret how long the initial weather is going to last may mean going forward in the TAF.
Then a customer request comes along to have the actual TAF text inbetween the interpretation. Which isn't possible in this case since a TAF isn't necessary linear, but the algorithm linearizes the results. So the smart programmer refuses, tries to explain this to his non-understanding management or non-understanding customers, and moves on.
Anyway, request persists, so a less intelligent programmer comes along, willing to take the job (after all, a TAF is in ALL CAPS so it can't be difficult), finds he doesn't understand the code programmer #1 has written so he writes his own algoritm that breaks the TAF into blocks. And then injects these blocks into the blocks that the original algorithm spews out. A quick test by management finds no flaws with this so the thing goes into production.
And the worst thing is that that second programmer probably made a lot of money. First for taking on a job that everybody said was impossible, and secondly for getting it through acceptance testing. In less time than expected.
(Is it true you turn into a cynic after working in the same field for 10 years?
)
Then comes the following line:
Text: PROB30
And some text suggesting it interprets that line. But what that piece of text actually interprets is
Text: PROB30 TEMPO 1920 4000 +SHRA +TSRA BKN008CB
which is correct, as this is one "block".
The next "block" then seems to interpret the line
Text: BECMG 2023 7000 BKN008
But this line is listed after the block it interprets. Because the line preceding it is the "TEMPO 1920 ..." line which should have been on the PROB30 line.
So past the PROB30 bit, all the content of the "Text:" lines need to be shifted up one block to make things fit. And even then the interpretation block doesn't neatly interprets what's on the "Text:" line, since the interpretation also looks through the rest of the TAF for anything that precedes or supersedes this bit of "Text:" line.
Just guessing what happened: A smart programmer wrote an algorithm to make a linear interpretation of a TAF, from hour to hour, and present it in text form. Which worked flawlessly. And this is no mean feat, because to interpret what the weather is going to be at the end of the period may mean going backwards in the TAF a few "blocks", and to interpret how long the initial weather is going to last may mean going forward in the TAF.
Then a customer request comes along to have the actual TAF text inbetween the interpretation. Which isn't possible in this case since a TAF isn't necessary linear, but the algorithm linearizes the results. So the smart programmer refuses, tries to explain this to his non-understanding management or non-understanding customers, and moves on.
Anyway, request persists, so a less intelligent programmer comes along, willing to take the job (after all, a TAF is in ALL CAPS so it can't be difficult), finds he doesn't understand the code programmer #1 has written so he writes his own algoritm that breaks the TAF into blocks. And then injects these blocks into the blocks that the original algorithm spews out. A quick test by management finds no flaws with this so the thing goes into production.
And the worst thing is that that second programmer probably made a lot of money. First for taking on a job that everybody said was impossible, and secondly for getting it through acceptance testing. In less time than expected.
(Is it true you turn into a cynic after working in the same field for 10 years?
)
Join Date: Jan 2001
Location: The Burrow, N53:48:02 W1:48:57, The Tin Tent - EGBS, EGBO
Posts: 2,297
Likes: 0
Received 0 Likes
on
0 Posts
30% chance that temporarily between 4 in the afternoon and 8 in the evening it will deteriate to visibility of 4000m in heavy showers of rains and heavy thunderstorms and rain, cloud lowering to broken at 800ft cumulonimbus
I was with friends at Hebden all day and at 17:00hrs we had all of that - TS, heavy rain, low cloud etc. Driving home with the temperature at 11.5C we had radiation fog forming 
it looked quite pretty floating gently about 6" above the fields and between the trees. It also poured down whilst we spent a couple of hours at Brimham Rocks.For anyone who may not be too familiar with the geography of the UK, Hebden and Brimham Rocks are places in the Yorkshire Dales National Park.
Been looking at that ADDS thing a bit more. There's something seriously wrong with that algorithm. The interpretation is done correctly, as is the presentation. But then the wrong bits of TAF are associated with the presentation bits. Everything is well (excellent, actually) up to the PROB30 bit.
avbrief=# select count(*) from taf where icao ~~ 'K%' and text ~ 'PROB30';
count
-------
349
(1 row)
avbrief=# select count(*) from taf where icao ~~ 'K%' and text ~ 'PROB30 TEMPO';
count
-------
0
(1 row)
avbrief=# select count(*) from taf where icao ~~ 'EG%' and text ~ 'PROB30';
count
-------
205
(1 row)
avbrief=# select count(*) from taf where icao ~~ 'EG%' and text ~ 'PROB30 TEMPO';
count
-------
200
(1 row)
count
-------
349
(1 row)
avbrief=# select count(*) from taf where icao ~~ 'K%' and text ~ 'PROB30 TEMPO';
count
-------
0
(1 row)
avbrief=# select count(*) from taf where icao ~~ 'EG%' and text ~ 'PROB30';
count
-------
205
(1 row)
avbrief=# select count(*) from taf where icao ~~ 'EG%' and text ~ 'PROB30 TEMPO';
count
-------
200
(1 row)
Looking at some of the examples, TEMPO seems to be implied by PROB30 in some cases.
Thus my guess is that the algorithm was not tested on cases where two change words like "PROB30 TEMPO" appear consecutively.
Come to think of it, I like the US system better. I mean PROB30 would imply a TEMPO condition, wouldn't it?
In the first case, the airport might well be fogged out for the entire period. In the second case, there should be an opportunity to make an approach at some stage. Don't bet your life on it though.