[verystealthy]

Well done. I can see this working well for aviation enthusiasts (i.e. X-Plane folks) who like to use real world data. However, METAR/TAF are not the friendliest of formats. Have you considered including a METAR/TAF decoder?

[steven777400]

The data that I get from the web service does include a breakdown of the specific conditions (not a human readable translation, but enough to generate one). So far I haven't implemented that since I can read METARs myself. I'd want to be careful not to consume too much screen real estate. Something to think about for sure.

[verystealthy]

For sure. If you're getting your weather data via METAR/TAF, you should be able to read it :). And one can always resort to this (even though it won't decode everything). http://heras-gilsanz.com/manuel/METAR-Decoder.html

[mr1976]

actually, it's really useful just as just a METAR. Prefer it. quick, simple, solves exactly 1 problem well.

[steven777400]

Addendum: I did put the "about x minutes/hours" old thing on the data because of all the parts, the Zulu time is the one I consistently do have trouble with. :)

[presumeaway]

Love it, thanks.

And: showing an "as of" time somewhere, expressed in Zulu, would be helpful.

[steven777400]

The as-of time is in the METAR. It's the block immediately following the station identifier, e.g. 172054Z means the 17th of the month at 20:54 Zulu. That's the time of observation.

You're right that the TAF doesn't indicate the time the forecast was published (although usually it's assumed to be the first hour of the forecast).

If you meant instead, as-of meaning "when the data was loaded", that's true... Not shown. I have the METAR ages turn red when they hit an hour (normally they are issued every hour) as a "clue" to the user to refresh. But certainly I could be more explicit.

[presumeaway]

> If you meant instead, as-of meaning "when the data was loaded", that's true... Not shown. I have the METAR ages turn red when they hit an hour (normally they are issued every hour) as a "clue" to the user to refresh. But certainly I could be more explicit.

Correct, that's what I'm talking about.

[leetrout]

It's in the METAR and the TAF.

  KPDK 172053Z

17th day 2053 Zulu

[presumeaway]

Right, per METAR/TAF, but not in terms of when the data was last pulled.

Unless it's all realtime.