I've just noticed a series of messages that the system doesn't recognise the word 'SNOCLO' - just a bit relevant at the moment!!!

Quite! You'll be pleased to hear that the next version of SkyDemon, due in January, does interpret SNOCLO.

Hi Tim,

I've noticed a few other METAR decoding snags.

In "METAR: LFQQ 042300Z 20009KT 9999 BKN040 00/M02 Q1013 08090095 NOSIG", SD doesn't understand the 08090095.



also

in "TAF: EBFN 041541Z 0419/0507 20012KT 8000 FEW010 BKN015 BKN030 TEMPO 0419/0504 4000 -SNRA/-RA SCT007 BKN010 TEMPO 0420/0502 2500 -SN/-SG SCT004 BKN007", SD can't decode the precipitation.



My "Home" airport is Antwerp so these airfields are not really obscure in any way.



I have another comment/suggestion.

I flew from Antwerp to Southampton a few weeks ago. When I printed out the Flight Plan, I noticed that the nearest ATIS from Antwerp was Ostende! I'm guessing this means you pick up these frequencies using a along the route" algorithm.



Might I suggest that, for ATIS at least, you do a radius search for one at the departure and one at the destination? This would ensure that I get an ATIS 25 miles away instead of 100 miles away.



Otherwise still over the moon with SkyDemon. Not so happy with the 7" Mio that its on though. Looking forward to the day I can start it up from an iPad :-)

Meaning I don't have one yet, but I'll buy one the very day you release the app for it.



Cheers,

Stuart

Thanks for the feedback. At present we don't decode runway surface state groups, but we may do in the future. The weather at EBFN is interesting; I've never seen slashes in weather groups before. Is that a local (national) extension/alteration to the standard TAF format? Is it documented somewhere?

No, I've never seen slashes before either but I can't imagine it's a local thing. Isn't it a worldwide standard? I'll see if I can get in touch with the airfield and see what they say.

I think it supposedly is, but there are all sorts of country-specific things that we end up having to cater for.