After you repaired the data sync problem it worked for some days. Maybe you can do this again.Unable to fly online with this:W189/94@FL300!There should be a little wind from north.Please repair this in the next to weeks. Or I have to cancel my slot at Cross the Pond. One of the biggest events at Vatsim.

All,The programming team has looked into this each time and except for that very first time when the secondary server was out of sync, nothing is wrong with the servers, the data, or ASE. I have even gone to online weather data sites and compared the winds aloft from data and what ASE is reporting and things match up.

All,The programming team has looked into this each time and except for that very first time when the secondary server was out of sync, nothing is wrong with the servers, the data, or ASE. I have even gone to online weather data sites and compared the winds aloft from data and what ASE is reporting and things match up.

Sorry, but if you really think, ETHT matches with real life data, you have not looked at my screens.All non-interpolated stations are very fine.

Hi,If #76 has graphics then you are correct, becuase I am at work and can't see graphics that are posted.

Hi,I had the same phenomen some days ago. Look at this post here in the forum.Within some miles wind direction changes totally for some stations. How should this work? And the bad information: This happened at the same time and place also in ASV 6.5 at the same station. I checked this for this route. So it looks like a data problem. I didn't have any logfiles, as I didn't save them at that time. But as this happens quite often, there must be a possibility to find this issue. And there is definitely an issue!RgdsReinhard

Hi Jim,I have to agree there is a problem with the interpolated winds. Here is the example from above with all the screens of the stations that the interpolation comes from:As you can see below, ETHT has all winds coming from the south. ETHT is an Interpolated station.Now the next four slides are the stations used for interpolation. As you can see, the upper winds are from the north in all four instances. None of these are interpolated sites but raw data sites.Here is the shot of the interpolation sites used. The farthest one is 104NM away.And for the record, these were off the primary server.I believe there is a problem with how the winds are calculated. I work in a field were sometimes wind direction is important...we also use points to average out wind direction and speed in the program we use.Below is basically how it is done in the program according to one of our program gurus:

"Assuming we have 3 readings of 359, 000, and 001 degrees, reasoning tells us this should average to 000 degrees, not (000+001+359)/3 = 120 by simply averaging the values.Let v be the wind velocity. If all you want is direction, assume a constant speed(v) of 1 and the v's go away. If you want to know the average direction where most of your speed comes from (the magnitude), you need to also measure the speed(v) for each direction recorded. This example sets v to a constant of 1 for simplicity. From trigonometry we get: Vector = (X,Y) where X = v * cos(Angle) and Y = v * sin(Angle) Vector 1(V1) = (v cos(359), v sin(359)) = (0.99985v, -0.01745v) Vector 2(V2) = (v cos(0), v sin(0)) = (1v, 0v) Vector 3(V3) = (v cos(1), v sin(1)) = (0.99985v, 0.01745v)Add the 3 vectors by adding their X components together and their Y components together and divide by the number of readings(3) to get the resulting "average" vector:(V1+V2+V3)/3 = ((0.99985+1+.99985)/3, (-0.01745+0+0.01745)/3) = (0.99990, 0)So our average Vector(X,Y) is (0.99990, 0)The angle here is obvious since Y is 0 and X is positive(0.99990), the vector is along the positive X axis which is defined as 0 degrees.But to make sure the math works for all average vectors you use this:tan(Angle) = Y/X which gives: Angle = inverse tan(Y/X) orOur average angle = inverse tan(0.99990) = 0 degrees as expectedIt is important to point out that the angles calculated using tan will always be from -90 to +90 degrees. You must keep up with which quadrant this vector is in to make sense of the angle. Quadrant 1: 0 - 90 degrees, Quadrant 2 90 - 180, Quadrant 3: 180 - 270, Quadrant 4 270 - 360(0) Q2 90 Q1180 + 0 Q3 270 Q4If we used 179, 180, 181 degrees we would have ended up with (-0.99990,0) Our angle would still be 0. This is why you must keep up with the quadrant of the resulting "average" vector. This vector(-0.99990,0) is along the X axis in the negative direction, so the angle is 180. For numbers where X or Y are 0, the angle is 0, 90, 180, or 270. For all other answers, simply plot the point in the proper quadrant 1, 2, 3, or 4 as shown above. Here is the corrected Average Angles for each of the 4 possible sign values of the resulting Average Vector( X,Y) in each quadrant:Quadrant 1: (+X, +Y) Angle is always positive. Average Angle = 0 + Angle.Quadrant 2: (-X, +Y) Angle is always negative. Average Angle = 180 - |Angle|Quadrant 3: (-X, -Y) Angle is always positive. Average Angle = 180 + AngleQuadrant 4: (+X, -Y) Angle is always negative. Average Angle = 360 - |Angle|Final Example: You calculate your "Average" vector and end up with (4, -3). This is in quadrant 4. Your angle using inverse tan(-3/4) is -36.8699 degrees. Your "Average" angle would be 360 - |-36.8699| = 360 - 36.8699 = 323.1301 degrees."

Now this is way over my head, but to me this is probably the underlying problem with the interpolated data. The raw data is fine...the result of the calculations are wrong.Not really being a programmer, I went to excel and plugged in this formula:

=ROUND(MOD(ATAN2(ROUND(AVERAGE(COS(range*PI()/180)),5),ROUND(AVERAGE(SIN(range*PI()/180)),5))*180/PI()+360,360),2)

My result for FL300 in the example above using that algorithm is 003 degrees (northerly) using the raw data of 006, 007, 001 and 358 from EPZG, EPWR, EDDC, and EDDB at FL300 for the "range". So the FL300 winds at ETHT should be near at least 003 degrees with a wind speed in the 23-32knot range (lowest knot value is 23 highest is 32). Instead it is 189 degrees with a 94 knot wind! :Shocked:So to sum up:1) All winds from 12K and up are northerly in the raw data. The interpolated winds are all southerly.2) The farthest raw data station is 104NM away.3) The data was from the primary server.4) Its my belief that this only happens when the four wind point being used crosses the 360 degree mark, meaning that some data is from the NE quadrant and some data is from the NW quadrant. Sorry for the long post, but I had to put in my two cents!! :( Cheers!Devin

Hi,Winds aloft data in ASE comes from data from the real world. It doesn't matter if the station is actual, interpolated, offline, closed, or not reporting.There are no calculations done by ASE when determining winds aloft, it is actual, live, unedited data. We have multiple upper wind data sources and there are also public sites that show the data.The winds in Germany were not the same as the winds in Poland.If anyone is going to check this data remember that it was this morning's 10Z data that was being used, not any data from the present.The only calculated wind is the surface wind and it is spot on, 100% correct.Please respectfully let your program gurus know that there are no calculations being done and none of the surface wind calculations are incorrect!

Hi,Winds aloft data in ASE comes from data from the real world. It doesn't matter if the station is actual, interpolated, offline, closed, or not reporting.There are no calculations done by ASE when determining winds aloft, it is actual, live, unedited data. We have multiple upper wind data sources and there are also public sites that show the data.The winds in Germany were not the same as the winds in Poland.If anyone is going to check this data remember that it was this morning's 10Z data that was being used, not any data from the present.The only calculated wind is the surface wind and it is spot on, 100% correct.Please respectfully let your program gurus know that there are no calculations being done and none of there surface wind calculations are incorrect!

OK Jim, no insult intended re the program gurus...I just inquired on how we do it in our program we use in the field!Now re you answer...Fine, I believe you that the surface winds are fine...but why are the upper winds way out of wack at that one point in the middle of the quadrant reporting north winds in each? You mention that ASE does not interpolate upper wind data, so where are the southerlys coming from then? I looked at ETHT and it is within the quadrant of EPZG, EPWR, EDDC, and EDDB. So where did the 189/96 FL300 at ETHT come from when non-interpolated stations within 100NM reports winds from 358 to 007 degrees with winds from 23 to 32 knots? I don't understand how the is such a huge discrepency in direction and speed. And it isn't Poland/Germany...I've seen this flying over Canada too!And if its "actual, live, unedited data", right now at this minute using the Force to Real Time option, the FL300 winds are:EPZG - 338/008EPWR - 019/016EDDC - 307/001EDDB - 242/006My winds at ETHT at FL300 is still 189/97.

So where did the 189/96 FL300 at ETHT come from when non-interpolated stations within 100NM reports winds from 358 to 007 degrees with winds from 23 to 32 knots? I don't understand how the is such a huge discrepency in direction and speed. And it isn't Poland/Germany...I've seen this flying over Canada too!

Thanks Devin, that is my question too. And why does that problem only (or in most cases) appear, if the wind is coming from the north.

Devin,The southern winds are coming from the actual data. You can't look at the other station data as a comparison. You need to take each station individually, on it's own.

Devin,The southern winds are coming from the actual data. You can't look at the other station data as a comparison. You need to take each station individually, on it's own.

Then you really have to check your sources.Btw there are so many stations in Germany, that I cannot believe that they can all provide actual data for winds aloft.

Is it possible that there is a problem with ETHT because the ICAO Code is outdated?EDCD is the correct one!

Hi,No, winds aloft data stations are not like ground weather stations, they are much fewer in number.For all of Europe there are about 75 winds stations, Africa way less.You can see the stations here:http://weather.uwyo.edu/upperair/sounding.html

Jim,It would appear that there is indeed a problem with the upper wind data for ETHT, Cottbus, Germany. As I write this, it is March 13 (GMT) at 03:40 (GMT). I just downloaded the latest WX from the server, and the upper winds for ETHT are exactly the same as what was being shown on the screen captures by Creppel and Netshadoe 5 days ago on March 8th. There are very minor variations in direction, velocity and temperature (no more than a couple of knots and degrees), but for all intents and purposes, the data is the same. Looking back at some historical downloads I made in ASE 2 weeks ago, I see that the ETHT upper winds were the same back then too.Other current winds aloft reports for nearby stations are very different, and looking at the real-time winds aloft charts for this hour and date for Europe, the other nearby stations are quite accurate, while ETHT bears no resemblence to actual conditions.The surface METAR for ETHT on the other hand, IS correct, and very different today (13 March) than what was shown in the previous screen caps for 08 March.I realize that this may not be something which HiFi has any real control over - just be advised that the data provider from whom you receive predicted upper winds for this part of Europe appears to be feeding you information for ETHT which is continuously "stuck" at some time in the past. Since FD data is not time/date stamped like METARS are, it would not be immediately obvious that the data is in error, unless you examine a series of reports for the same location over a period of several days - then it becomes clear that there is a problem for this particular location. Perhaps there are other stations in Europe (or elsewhere in the world) which also suffer from winds aloft data "stuck" on the same readings for days at a time, but ETHT is the only one I am sure about. Jim Barrett

Hi,OK, thanks for that, but remember that WA data covers large areas which would mean the whole area around that station would be stuck, not just at this station. It is something we can all keep our eye on this.