Am I missing something.

Hiya Windy team.
Appreciate the epic app and stoked to be a premium member with full functionality.
Just wondering if I'm missing something.
When looking at "Forecast for this Location" the elevation will change when the "weather Picker" cursor is moved to mirror background map positioning and elevation changes. Unfortunately, the weather forecast remains the same (most importantly temps) when moving to a spot close by with elevation changing significantly. This makes calculating temps (and rain / snow transition) at certain elevations impossible. This issue is displayed in the two photos attached: one at 1965m and the other at 900m elevations but both showing the same temperatures. So which one is correct and which one can be used to calculate lapse rates from? Or is there some background data accessible somehow that shows what elevation the forecast (specifically temps) are based on? From that I can use lapse rates to figure out temps at any elevation in the area.
Alternatively displaying the elevation used on the clicked "Forecast for this location" would help so I could figure out lapse rates to any elevation.
Cheers,
Hans

@Hanz2018 You are absolutely right, that is quite misleading. Model elevation (elevation that model considers to be surface) is unfortunately only displayed in the sounding, which can be accessed by right click or long tap like so:
There you can see that model elevation at place with real elevation 900m is around 1037m
and model elevation at Mount Noir peak (where real elevation is around 1930m) is even less  1023m. You can then read temperature at desired altitude directly from the sounding (see below) which gives 6C in the example

@Filip_K
Your workaround is useful and I use it. But when the real elevation is lower than the model elevation, how do you do with the sounding graph? Do you add the same lapse rate to the model temp as it cannot be read directly on the graph?
BTW could we imagine that Windy makes a ‘vertical interpolation’ of temperature to smooth the model orography which is discrete and coarse. 
@idefix37 Yes, pretty much, that's what I do. Models provide data in a grid that is, as you said, quite coarse. All model data are then bilineary interpolated to fill the "gaps" in the grid, including "model elevation" (orography). "Real elevation" data have much denser grid and are thus much more accurate but they are in no way incorporated in the values. "Real elevation" is only displayed in forecast detail and sounding

@Filip_K
Please think about include model altitude next to real altitude as proposed (years ago), here
https://community.windy.com/topic/7929/modelaltitude/3


Thanks Filip_K for the sounding method. Gkikas LGPZ including model elevation next to altitude would be the golden ticket. Let's hope it's possible.