Be fantastic to have a vertical view of temp/dew point running of the model from a chosen point. Ideally it'd be a popup or a section of the page, so that as you moved to future time steps the tephigram would update in sync.

Found the answer: Under More Layers, Display Isolines, and select Geopot. height.
Now the equivalent altitude will be displayed as isolines while keeping the pressure constant.

So yet again, Windy already had the facility I wanted. It's just too great!

@idefix37 0.1mm seems worth including, then I wonder whether you could have a smoothing algorithm that spreads the rain across the same duration and achieving the same total, just that some periods with less than 0.1mm wouldn't get a value and others would, which would appear as sporadic rain which is really what it's like in these situations anyway.

Having 1.5mm and 0.7mm makes a bit of a difference if you're in the outdoors. I'd always rather know the total expected and over what duration.

Fantastic thanks. Yet again, shows what a great product Windy is already!

For the same day and model ECMWF on the browser app:

For 3-hourly there's a total of 1.5mm rain expected throughout the daylight time

For 1-hourly there's a total of 0.7mm rain expected and just around lunchtime

Why are these so different?
Shouldn't they mostly agree except for rounding issues?
If it's an issue of resolution, could the hourly use 0.1mm levels?

Clicking on the map right beside the scroll bar is too easy and means you have to go back and select the location for which you want a forecast.

When I'm looking at a forecast for a location I often click through the scroll bar to see what's going on in the map at different times. The scroll bar is a very small target, and if I miss it and go slightly too high, a location in the middle of the sea is selected and I have to go back and select my city.

I suggest clicking on the map be disabled for a small distance above the scroll bar.

@idefix37 I'd be happy if the 1hr totals were close to the 3hr ones. At present they can be wildly different so I need to switch to the 3hr version so see the rainfall then switch back to the 1hr to get temp and wind by hour.

It's not an issue for me if the 3hr value was 0.2m and the 1hr equivalent was 0.1, 0, 0.1 or even if 0.1 isn't available then 0, 0.2, 0

In the above:
0401-0700, 3hr shows 0.4mm and the 1hr 0mm => be good if 1hr shows total of 0.4mm, such as 0.1, 0.1,0.2 or 0,0.2,0.2 or 0,0,0.4
0701-1000, 3hr shows 0.3mm and 1hr 0mm => be good if 1hr showed total of 0.3mm
1001-1300, 3hr shows 0,.6mm and 1hr 0.7mm => 0.1 difference doesn't matter
1301-1600, 3hr shows 0.2mm and 1hr 0mm => be good if 1hr shows total of 0.2mm

1hr values that are close as reasonable to the 3hr totals is what I've been talking about.

I agree that for the 22nd up to 1600 the amount of rain is very low and you certainly shouldn't aim for numbers that disagree. I still think having one or more values in the 1hr that total to the same as the 3hr would be helpful. Needing to scan the pictograph as well as the numbers prevents a quick scan to see if any non-trivial rain is likely.

Other than that I go back to the images on my first post. The two versions of the time show quite different amounts of rain and there's nothing on the 1hr version that indicates there could be some between 0400 and 1000

@idefix37 I'd be happy if the 1hr totals were close to the 3hr ones. At present they can be wildly different so I need to switch to the 3hr version so see the rainfall then switch back to the 1hr to get temp and wind by hour.

It's not an issue for me if the 3hr value was 0.2m and the 1hr equivalent was 0.1, 0, 0.1 or even if 0.1 isn't available then 0, 0.2, 0

In the above:
0401-0700, 3hr shows 0.4mm and the 1hr 0mm => be good if 1hr shows total of 0.4mm, such as 0.1, 0.1,0.2 or 0,0.2,0.2 or 0,0,0.4
0701-1000, 3hr shows 0.3mm and 1hr 0mm => be good if 1hr showed total of 0.3mm
1001-1300, 3hr shows 0,.6mm and 1hr 0.7mm => 0.1 difference doesn't matter
1301-1600, 3hr shows 0.2mm and 1hr 0mm => be good if 1hr shows total of 0.2mm

@idefix37 0.1mm seems worth including, then I wonder whether you could have a smoothing algorithm that spreads the rain across the same duration and achieving the same total, just that some periods with less than 0.1mm wouldn't get a value and others would, which would appear as sporadic rain which is really what it's like in these situations anyway.

Having 1.5mm and 0.7mm makes a bit of a difference if you're in the outdoors. I'd always rather know the total expected and over what duration.

For the same day and model ECMWF on the browser app:

For 3-hourly there's a total of 1.5mm rain expected throughout the daylight time

For 1-hourly there's a total of 0.7mm rain expected and just around lunchtime

Why are these so different?
Shouldn't they mostly agree except for rounding issues?
If it's an issue of resolution, could the hourly use 0.1mm levels?

When I restart the browser roads all the current tabs including Windy. If I have hourly forecast set before the restart, this is shown as still set when the page is loaded - but 3-hourly forecasts are shown.

• I change to 3-hourly and back to hourly: no change, just 3-hourly forecasts are shown.
• I leave the setting hourly and reload the page. Behaves as before with just 3-hourly shown no matter what the setting.
• I change the setting to 3-hourly and reload. Then I change to hourly and hourly forecasts are shown correctly.

Windows 11 browser (Vivaldi latest)

Clicking on the map right beside the scroll bar is too easy and means you have to go back and select the location for which you want a forecast.

When I'm looking at a forecast for a location I often click through the scroll bar to see what's going on in the map at different times. The scroll bar is a very small target, and if I miss it and go slightly too high, a location in the middle of the sea is selected and I have to go back and select my city.

I suggest clicking on the map be disabled for a small distance above the scroll bar.

Found the answer: Under More Layers, Display Isolines, and select Geopot. height.
Now the equivalent altitude will be displayed as isolines while keeping the pressure constant.

So yet again, Windy already had the facility I wanted. It's just too great!

With the wind display I can move the slider to show lower pressure levels, but the isolines stay with the surface pressure.

Suggestion: When move above surface pressure, isolines show the heights.
Alternative (and perhaps more intuitive/seamless coming from the surface): Change the slider to be height driven, with the isolines showing the pressure at the given height.

These would enable us to tell what's going on at high altitude.

Fantastic thanks. Yet again, shows what a great product Windy is already!

In your wind charts the highest colour in the scale is for 100km/h, 60mph etc. That's too low, especially when looking at high altitudes and the jet stream where it's important to see the difference between 100km/h and 200km/h or higher. Could the scale be extended always, or extended when showing an altitude above surface?