• Wind Speed and Directions are always comes as wrong: please compare with real-time observations; Windy just plots on maps model forecasts provided by weather centers, it doesn't compute any forecast. Moreover, model forecasts computed on grids with 25 km / pixel resolution cannot be too precise over mountain/valley areas, where wind forecast values are particularly hard to predict.
• How we can understand 3 to 4 hrs ago that a specific cloud will come to a specific place?: just watch the forecast for next 3-4 hours (use the time bar).
• What is meant by >240 in this map: which data layer did you selected on that screenshot?
• No one replying: please, next time you post a question on such a community site, wait a bit more than 6 minutes for an answer...

@bobluck said in Option to set default view.:

Can’t I just set a preferred view and have it saved?

Yep, I think such a new feature, i.e. kind of option "keep currently enabled data overlays on next user sessions" (and why not current map coverage, too?), would be welcome for many use cases. At least for users who often use same data layers and/or map coverage...

WMO observing network contains both ships (voluntary observing ships or part of GTS network) and buoy stations.
Some met offices even use drones, turtles, whales, etc. as support for ocean weather sensors...
Buoys are generally static, ships are generally moving; both of them should have a series of standard weather sensors defined by WMO and provide messages of type SHIP or BUOY (which are extensions to the more generic SYNOP mesages). Ogimet web site (for example) provides part of them here (screenshot below).
WMO/GTS naming rules of all ocean observing stations are defined here.

Even more useful would be to get isolines rendering option to all pertinent data layers (not only pressure), and also to be also able to configure isolines interval value (like for color shading palettes), for each parameter.

This discussion (as well as many other community discussions, e.g. this one), makes me thinking that adding a collection of 3rd party, pertinent URLs to Windy UI would be really helpful to many users (and to Windy, too).

Of course such a 3rd party web sites are not intended to replace, nor to compete with Windy.com.
A good sample is the link provided in comment just above, which is for a web site specialized in dust forecast, provided by a research laboratory.
Windy.com has not the required resources to (and should not) compete with big research laboratories (e.g. official WMO product providers), but could advantageously provide such a pertinent list to its users; I guess everybody would win...

Such a pertinent URLs list may be pretty long, thus items may be grouped by category (e.g. "Weather Alerts", "LRF Models", "NWP Models Data Providers", "Local Forecasts Europe/NA/Asia/country/Etc)", "Satellite Imagery", etc.).
Its appearance may be also as discrete as needed (e.g. placed in the main Menu, just after Windy Plugins), in order to not change current look and feel of Windy UI.
Of course each URL link could and should have a full description (e.g. as OnMouseOver tooltip).

Btw., such a link to OSM Community web site could save a lot of time to both users and administrators and avoid all these long and boring posts about missing roads or wrong country names on Windy maps...

Moreover, as Windy has many occasional or permanent users and part of them are meteorologists, forecasters, pilots, I guess many of them would be happy to propose and share pertinent URLs which would be really helpful to users with less knowledge in these domains.
Btw., the community discussions already contain a pretty big collection of links to pertinent 3rd party web sites...

Only automatic weather stations refresh at such a frequency.
You can also use observations for closest METAR weather stations (every 30m).
For clouds you can use images from METEOSAT satellite, refreshed every 15m. Radar data is also available in your area, but it doesn't provide clouds or wind observations.
Forecast models available on Windy only refresh every hour (in best cases).

Both bearing and distance implies two points/positions; pointing to a map location is only one point, which displays its coordinates.
Distance is available on "Distance and Planning" feature.
Or well did I missed something?

As said in my previous post above, if forecasts and satellite image layers are displayed together on map, there would be a bug: they cannot be contemporary (excepted at full hours, maybe).

Satellite images are provided every 10 or 15 minutes; Windy should obtain that worldwide mosaic by merging images from differrent satellites, taken at small time difference (a couple of minutes or so, but surely not hours).

When combining satellite and atmospheric pressure layers together on map, then playing the animation over the whole available period on timebar (i.e. last 2, 6 or 12 hours), one can see that the pressure layer remains static over the whole period, while satellite images layer change at each time step...

Thus the pressure isobars layer doesn't follow current value on timebar as expected, which is wrong from my pov.

Having a static pressure isobars layer combined with animated satellite images would be useful for some specific deep analysis, but in such a case the validity time of the static layer should be clearly displayed on UI (I was not able to find it).

Providing Long Range Forecast (LRF) for weather should remain out of the scope of honest, public weather sites like Windy, as it would require huge scientific and computational effort.

There are many so-called "Almanacs" that boast of providing weather forecasts over months or even years: none of them are trustworthy.
A good sample for such an Almanac is here (ouch! they even use Windy widgets :o))); as one can see, it is rather kinda horoscope...

Best would be to use directly WMO's LRF centers when required; they generally provide public data with pertinent documentation.
The full list is here, a good sample (DWD) is here.

Only automatic weather stations refresh at such a frequency.
You can also use observations for closest METAR weather stations (every 30m).
For clouds you can use images from METEOSAT satellite, refreshed every 15m. Radar data is also available in your area, but it doesn't provide clouds or wind observations.
Forecast models available on Windy only refresh every hour (in best cases).

I'm not sure that interpolating computed forecast values would be a good idea, as generally weather evolution is never linear. Such an artificial interpolation would get of course a more "beautiful" animation on screen, but I don't think Windy would assume the wrong interpolated values...

@hammo01 Maybe this site could help

This plugin should be able to cope with that (even for HAMPSHIRE PEOPLE I guess).

1st April joke?

I guess raised issue is about different temperatures and clouds coverage icons highlighted below.

... and grib2 files are also much bigger now: about 550 MB by file (i.e. for each forecast), compared to 300 MB before). This is up to 0.4 TB of grib files every day (4 runtimes of 174 forecasts each)

Starting from RUNTIME 2021-03-22 12:00 UTC, NCEP/NOAA upgraded GFSv16 weather forecast model (much more parameters/levels), see details here

Release Notes Model Global Data Assimilation System (GDAS) and Global Forecast System (GFS) Version 16.0.7 Implementation date/time March 22, 2021; 1200Z. Purpose The GDAS is the data assimilation backbone of the GFS. The GFS produces 16-day global forecasts 4 times per day. The system also includes a global ocean wave prediction model forced by the atmosphere. Changes being made for this release:
❏ Increase the number of model vertical layers from 64 to 127 and extend the model top from the upper stratosphere (~55 km height) to the mesopause (~80 km height).
❏ Employ a new scheme to parameterize both stationary and non-stationary gravity waves that are not explicitly resolved by the model.
❏ Usea new scale-aware turbulent kinetic energy based moist eddy-diffusivity mass-flux vertical turbulence mixing scheme to better represent the planetary boundary layer processes.
❏ Update the RRTMG radiation package to improve solar radiation absorption by water clouds and the cloud overlapping algorithm.
❏ Merge the operational standalone global deterministic WAVEWATCH III based wave model Multi_1 (wave_multi_1.v3.3) into the GFS system. New features include a grid redesign, wave-current interaction and improved physics optimized to more frequent atmospheric forcing
❏ Run Global Land Data Assimilation System as part of the Global Data Assimilation System.
❏ Replace the Ensemble Square Root Filter with the Local Ensemble Kalman Filter (LETKF).
❏ Implement 4-Dimensional Incremental Analysis Update (4D-IAU) technique.
❏ Turn on stochastic kinetic energy backscattering (SKEB) perturbations in ensemble forecast used in constructing background error covariances.
❏ Update variational quality control.
❏ Apply Hilbert curve to aircraft data.
❏ Use correlated observation error for Cross-track Infrared Sounder (CrIS) over sea surfaces and Infrared Atmospheric Sounding Interferometer (IASI) over sea and land.
❏ Change the format of forecast output history files from NEMSIO (binary) to compressed netCDF.
❏ Add products on seven new pressure levels (0.01, 0.02, 0.04, 0.07, 0.1, 0.2, 0.7 hPas). Made a number of other product changes.

Developed by NWS-NCEP-EMC in collaboration with NOAA-OAR and several other partners in the community. For more information on this model, please contact ncep.pmb.dataflow@noaa.gov. Runs on The National Weather Service (NWS) Weather and Climate Operational Supercomputing System (WCOSS) Community software Earth System Modeling Framework (ESMF); Cloud Radiative Transfer Model (CRTM 2.3.0); Unified Post Processing (UPP); Gridpoint Statistical Interpolation (GSI). Input GFS/GDAS uses the full set of global conventional and satellite observations. The GFS/GDAS also ingests snow coverage data and sea ice concentration data from other models in the NCEP production suite. The Wave component uses RTOFS ocean currents as forcing. Output and where to find it: https://nomads.ncep.noaa.gov, https://mag.ncep.noaa.gov, https://www.nco.ncep.noaa.gov/pmb/products/

Primary users NWS National Centers, Weather Forecast Offices, US Army, private sectors, and the global community In the future A fully coupled atmosphere-land-ocean-ice-wave system is under development. The system is scheduled to be implemented for operations in 2024 to replace the GFS.