If you right click near the bottom of the map, the menu and soundings pop-ups are positioned off the bottom of the map.
If the location selected is in the bottom half of the screen the popup should open above the location rather than below it.
The soundings display is using Wind Barb notation for direction and speed which a) isn't understood by most people and b) is fixed on knots regardless of what units of measure you've selected in your settings.
Why not use the same number + arrow for wind speed and direction that you use in the rest of the app?
For me the widget not updating is due to Windy being on the list of apps that are "Optimsed" for battery usage. Google / Samsung have made this easy to switch on but awkward to switch off. Here is how I did it on a Samsung with Android Oreo:
If the devs can detect battery is optimised, perhaps suggest switching it off in the error message. Also, it would be a good idea to show the last updated date/time in the top right of the widget titlebar.
Normally on any web page, Ctrl - zooms the UI out, Ctrl = zooms in and Ctrl 0 resets the zoom to 100%.
On Windy, the last one still works, but the first two zoom the map the same way that pressing - or = without Ctrl does, rather than zooming the whole UI. You need to use the zoom buttons on the browser hamburger menu to zoom the whole UI to get larger fonts/buttons.
The event handlers for the - and = key presses should only trap events where Ctrl is not pressed, and allow the rest to pass through to the default handler.
Of those HIRLAM. However, how about offering the new FV3 variant of GFS ?
@idefix37 You miss my point - if the storm is travelling in a straight(ish) line its not a problem. But what if the storm is forecast to do a U turn in the next 24 hours. My point isn't that you can't see where the track is, bu that you wouldn't be able to tell if the stongest gust in the area it traverses twice is a gust from the past, or a gust from the future. This may lead people in that area to think the future wind was stronger than it is actually forecast to be.
Blue is predicted water level in the gauge, Red is actual measurement, and is called preliminary because they haven't confirmed the equipment isn't faulty yet. The datum sets where zero is on the scale - by default mean of the lowest of the 2 tides each day.
When using the tool to measure distances, it only reports the results in nautical miles, and kilometers. Could you add statute miles please.
There is not an issue with it failing to save them - it is the fact they are two different settings and one of them appears in two places that is confusing:
The units for rainfall can be toggled by clicking the scale on the rain layer, and your choice is also shown / can be changed in the settings panel.
The units for rain accumulation can be separately toggled by clicking the scale on the rain accumulation layer, but this setting is not shown in the settings panel
Either it should be consistent and show both choices in the settings panel, or (and i think this is the better option), have a single setting affect both the rain and rain accumulation layers. What use case is there for someone who wants to see rainfall in mm and rain accumulation in inches?
Yes they provide public data feeds of all tidal gauges: https://tidesandcurrents.noaa.gov/stations.html?type=Water+Levels
Click on one then on the web services button in the bottom right for API details.
Click Settings => Modify Layers Colours => Select Overlay = Rainfall Accumulation.
The value in the bottom row is 312 and I think it is supposed to be 31.2 as 312 just makes all rainfall over 19" the same shade of pink.
On the web version (don't know about the mobile apps) those settings are ignored by the rainfall accumulation layer and it always defaults to inches until you click on the scale in the bottom right. The rain settings only affects the rain/thunder layer.
The top colour band for accumulated rainfall defaults to 312 inches - I think this is supposed to be 31.2 inches. It certainly looks more informative if you look at North Carolina right now with this changed.
The icon to show more information about the selected layer is currently a clock, presumably because part of what it shows is timing information. However, I think the normal "information" icon of an inverted i in a solid circle would be more appropriate and better set users' expectations of what the button will do.
If you include the past data, there is no way to discern what has already happened from what is to come, particularly if the storm track loops.
Another bug: it doesn't use the current position in the timeline as the starting point for the 10 days - instead it uses the left edge of the timeline, which for me right now is 20 hours ago. Therefore, it includes winds that have occurred in the past.
E.g. right now as Typhoon Manghkut is making landfall in the Philippines and heading west, it is predicting100mph winds 400 miles to the east of there.