@tomA27 again?? 😒

@rittels Thanks for the hint. I did wonder if this was happening and will now take another look as this will also have a bad effect in SoarCalc. For me, this has been masked by the worse problem that getLatLonInterpolator() fails (never resolves) some fraction of the time and I needed to add a timeout and fail gracefully. Right now I am struggling to work out why the "publish-plugin" action always fails with "Error: Process completed with exit code 22." This has happened before and I cannot for the life of me remember what I did to resolve it.

@tomA27 the map and the detail forecast progress bar should be in sync? devs can help here?

@idefix37 Thank you again.

@jancellor @vicb Thank you for your input. I'm sorry that I never discovered your thread before. The Sounding forecast already uses the surface temperature/dewpoint at the 1000hPa level. (or perhaps it uses the temperature and dewpoint from getPointForecastData which gives the same values). This is plain to see if you display the temperature, dewpoint and LCL separately in another add-in My understanding is that "surface" means the air in contact with the surface (normally at 2m). Indeed dewpoint-surface, rh-surface, wind-v-surface etc are clearly properties of the air close to the surface rather than the surface itself. I find it impossible to see any good reason not to use the surface temperature/dewpoint at the surface level (model elevation). Personally, I see this as quite an important bug in the official sounding forecast.

OK, worked it out by looking in fetch.d.ts... const latLonStep: LatLonStep = { lat:_loc.lat, lon:_loc.lon, step:1}; getMeteogramForecastData(_model, latLonStep).then((meteogramForecast) => { _meteogramForecast = meteogramForecast; updateSounding(); });

@rittels Thank you very much. I will take a look.

I have encountered errors when trying to run template plugins too! It often happens due to incorrect configurations or version mismatches. I usually check the plugin documentation, verify dependencies, and ensure everything is up-to-date. Anyone else experience this and found a smooth fix?