Hi,

Could you create a layer that shows the conditions for stargazing - i.e. taking into account light pollution and visibility. This would need to combine:

• sunrise/sunset
• moonrise/moonset/moon phase
• fixed light pollution from human sources (see https://www.lightpollutionmap.info )
• cloud cover
• fog
• aurora forecast (ideally it would be good to be able to see the layer with/without this included, as you may want to observe the aurora)

Algorithms for sun/moon are at: https://github.com/mourner/suncalc
Light pollution: https://www.lightpollutionmap.info/help.html
Space weather / Aurora: https://www.swpc.noaa.gov/

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:

1. Go to phone settings
2. Select Apps
3. Select Windy from the Apps list
4. Select Battery
5. Select Optimise Battery Usage
6. Change the filter at the top of the page to 'All Apps'
7. Scroll down to Windy and switch the optimisation off

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.

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:

1. Go to phone settings
2. Select Apps
3. Select Windy from the Apps list
4. Select Battery
5. Select Optimise Battery Usage
6. Change the filter at the top of the page to 'All Apps'
7. Scroll down to Windy and switch the optimisation off

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.

Can I suggest adding support / examples for developing a plugin in TypeScript .

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.

Correct.

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.