Difference in wind colour shading
-
Hello there
Can you please explain why the colour shading for wind differs between the wind only option and the basic option?
For example on ECMWF a 31 kts gust is shaded in red on the basic summary, but its shaded in green on the wind data summary.
Can send screenshots if useful
Many thanks
Steve (premium user)
-
@Selkie365 Hello, can you send these screenshots?
-
@Suty Sure and thanks for the reply. Will try copy them now. It happens on at least ECMWF and UKV.
Cheers Steve -
-
@Suty Hope you can access the link before - the system keeps marking it as spam.... If not I can email them to you. Steve
-
@Selkie365
To post a screenshot on the forum:
-
-
@Selkie365 Hello @idefix37 Do you see the difference in values? I would say it is same for same timestamps, but It is possible that I am missing something.
-
@Suty @selkie365
In the “Wind” panel, the same color shading is applied for both the wind speed and gusts. These shades are determined by the wind speed values.
In the “Basic” panel, the color shading is applied independently for the wind speed and gusts.
May be this is to reduce the space required for each row? -
@Suty Hi. So as said below (thanks 👍) the issue is that on the basic forecast you shade average wind and gusts independently, with different colours. But on the comparative wind summary, where you'd expect things to be clearer, you shade average and gust wind speed both in the same colour even if they are very different (eg very strong gusts). It looks like you apply the average speed colour to both average and gust.
To me this is unhelpful as using colours to readily highlight gust speeds (especially those over Beaufort 6) is so helpful for leisure water users.
It doesn't look like shading the gust speed independently would take up any more space in the wind comparison option, and be a big improvement.
Does that explain the issue and, if so, what do you and the Team think about a fix please?
Best wishes
Steve
-
@idefix37 Exactly - thank you 😊🥇
-
@Selkie365 @idefix37 Okay, thank you for further explanation, I can discuss this with colleagues to consider the change in our upcoming update.
