Is it possible to get these values?

Thanks a lot in advance
Nicki

A slightly different usage that I'm more familiar with is to understand building energy consumption in relations to weather, for instance for electricity demand prediction and building energy simulation. Weather is such a big driver in this area that without historical weather data, it would be very difficult to plan and design critical infrastructures (buildings, electricity grid) that we all depend on.

Joseph

@surfwolf

In this case you could use the Observation vs Forecast feature. The forecast was displayed at same time with observed wind and temperature during several days. Unfortunately at the moment the past forecast is shown only for few hours. But this feature should be back in future.

https://community.windy.com/topic/9425/how-to-use-the-observation-vs-forecast-feature

Thank you very much—got it, works.

Btw, I didn't realize this was an old thread already but it was my first post here and someone else had pushed this topic to the top :)

In this case you could use the Observation vs Forecast feature. The forecast was displayed at same time with observed wind and temperature during several days. Unfortunately at the moment the past forecast is shown only for few hours. But this feature should be back in future.

https://community.windy.com/topic/9425/how-to-use-the-observation-vs-forecast-feature

aviation briefing: well Air traffic control organsations run weather briefing and flight planning services, like for instance Nav Canada - I guess in the UK it's https://www.nats.aero

By the way, with the aviation briefs, what's the "aviation briefing website"? Could you give me a link? Also, I just spent some time on working on my skewT platform tephigrams.org over the weekend, some vertical profiles, if it helps at all.

Thanks for the comments @mhaberler. You've hit on an important concept here. Is there such a thing as a "historical weather forecast"? You seems to be alluding to model data. The important question is this – could you have avoided a dangerous situation if you had looked at the forecast an hour before flying vs. 3 days before flying? Which model run is the one to reference?

that is the secondary goal

First, I would love our wonderful and super-expensive ATC corporations would provide their forecasts not just from today onwards, but a couple of days back. Just what they publish on their aviation briefing website. That would cover 90% of my learning needs. Could I have avoided that situation if I had read the aviation briefing more diligently? Note: no historical 'data', no fancy UI and yadayada - JUST their briefs. So wrong forum here.

the other 10% of my needs would be going back in time for a few days max and look for stuff which was NOT in the aviation briefs. For instance, the accident linked above was due to a cold are pressure wave within the inversion layer, and it was NOT in the aviation briefs.

Let me ask you this @mhaberler, what level of detail would you need to "see if you could have avoided a situation"? Highs and lows? Surface winds? Gusts? Winds at all levels? Precipitation? Visibility? As gridded data or just at airfields? I have some aviation forecasting experience, but we were very focused on just our own airfields, and the WAFC/LOLAN guys used to take care of the rest.

I know.. the aviation weather forecasts are of so-so for ballooning and of moderate value at best if you do long-distance/high altitude. Example: predicting northerly föhn a few days ahead - in reality you get hints for föhn-affected terminal areas like Innsbruck and not much beyond.

For a short-range check a few hours before a pedestrian flight I mostly do precipitation, visibility, clouds/fog, average wind, wind gusts, shears. An important value for us is winds/gusts in the planned landing area, and here forecasts outside of large airports scarce and unreliable - we replace that by webcam views (sometimes you can judge wind that way), private weather stations, and experience about typical valley wind systems.

for long-distance over mountains a lot more is involved - vertical profiles, soundings, wave prediction, sometimes even likelyhood of a hydraulic jump. For longer-term prediction Rossby waves in the FL180 Geopotential forecast help - black line cutting the Alps N/S is a good predictor a few days out. As the flight comes closer, you look at the more local phenomena - ground wind etc like for a pedestrian flight.

We've talked about creating more detailed surface analyses before. But with an investigation, for example, you would need to know what forecast data you had available at the time (and what's its lead time was). Not only that, but which model. Weather forecast models are an extremely fluid thing, and are just a tool. This is why, when stakes are high, companies shell out for private forecasting companies who employ real forecasters. And with a proper accident investigation, it's usually time to do that. I can't speak to other modelling centres, but I know the UK Met Office archive all their UM forecasts (which cost an obscene amount in storage), so that they can be referenced later.

But, if we're just taking about your own learning, it sounds like a surface analysis would do the job nicely. Surface analyses are traditionally just synoptic charts (isobars and fronts), but I think we can do better. I may just start working on something like that myself (though with one year left, I should probably make a stab at starting to write my PhD thesis).

Let me ask you this @mhaberler, what level of detail would you need to "see if you could have avoided a situation"? Highs and lows? Surface winds? Gusts? Winds at all levels? Precipitation? Visibility? As gridded data or just at airfields? I have some aviation forecasting experience, but we were very focused on just our own airfields, and the WAFC/LOLAN guys used to take care of the rest.

(1) assume I do a flight and some meteorological situation crops up which I did was not aware of/did not look at

(2) assume some flight accident happened. The press typically reports sensationalistic nonsense like so: https://www.austrianwings.info/2019/06/heissluftballon-in-kilb-abgestuerzt/ . And a proper accident investigation takes forever, und you might not hear of the results. The national ATC organisations arent much better - they typically delete forecasts right away - no going back.

In both cases I would like to go back in time, and see myself if I could have avoided the situation - basically for my learning, and to answer questions of concerned people.

Both use cases involve a time window of a few days max. Two days would already be great!

Personally I have no use for historical data going back further in time.

The new future is great! Thanks for the quick responses. I look forward to windy becoming better and better everyday.

Best Regards,

Hello. Yes climatology would be the correct term I am looking for. I would love for Windy to have "average highs and lows" data built in for airfields, especially under ICAO codes. Would be extremely helpful! Right now we take data off of Meteoblue. But I would like to have more accurate data taken from the history of METAR reports if it is possible.

I guess what I am looking for overall is a history of purely observational data to reference at certain airfields built into windy.

Thanks for your time.

some

I would love to have access to historical weather data for aviation purposes.

I work for a charter airline that operates to destinations all over the world. We would love to have this data regarding averages for a given month. This is crucial when trying to figure out our Take-Off and Landing performance for future operations.

Whats the average high for a given month or week for a specific time during the year? What are the average winds during a specific time of day? Do we need to add a stop somewhere because recent annual trends show its going to be too warm? Or can we make a specific nonstop route because its trending cooler?

Some websites try to provide this data...most seem inconsistent. However, we would love to see this information come from Windy.