Hello,
What are the reasons for not displaying it as figures? I don't understand not displaying existing information, here the pressure.

Hello,
Thank you for Windy app! I enjoy it very much!

I found the following symptoms. And may I ask you kindly for improvements here?

Symptom 1:
Entered or pasted coordinates are not recognised if they contain special typographic characters such as typographic apostrophes.

Symptom 2:
Coordinates are not recognised if a required comma is missing or an additional comma is present.

Use cases

Use case 1.1:
Open the OSMAND app.
Select a location.
Copy the coordinates in DMS format within OSMAND.
Open the Windy app on an Android device.
Open the search function and paste the copied coordinates from the clipboard.

Use case 1.2:
Open the Windy web app in the Firefox browser on a notebook.
Open the search function and paste the copied coordinates containing typographic apostrophes.

Use Case 1 Expected Results:
The coordinates should be recognised correctly.

Use Case 1 Actual Results:
The coordinates are not recognised.

Use case 2.1:
Enter coordinates in DMS, DMM or DD format in the Windy app search function, omitting a required comma or inserting an additional comma.

Use case 2.2:
Enter coordinates in DMS, DMM, or DD format into the Windy web app search function in the Firefox browser on a laptop, omitting a required comma or inserting an additional comma.

Use Case 2 Expected Results:
The coordinates should be recognised correctly.

Use Case 2 Actual Results:
The coordinates are not recognised.

Root cause for symptom 1
I found out that the root cause for symptom 1 is probably the character encoding of the copied coordinates.
When I changed the copied coordinates to ASCII/ANSI then the coordniates will be recognized by Windy.

Summary:
The input and insertion of coordinates in the search function should be both character set-independent and comma-independent in order to enable the problem-free transfer of coordinates from other applications.

Versions used:

Windy app version 42.5.3 on Samsung Android
Windy web application version 43.0.0 in the Firefox browser version 130.0 on a notebook
OsmAnd+ app version 4.8.6

I have not checked it on other mobile devices.

@rittels Thank you very much! Issue is resolved!

@rittels I tried it. Unfortunately, the error still exists.

Name: windy-plugin-da
Autor: @rittels
Version: 0.3.37
Aktualisiert: 2026-05-20

Debug console shows:

{
  "msg": "mounted",
  "stack": "Error: mounted
		    at https://windy-plugins.com/214517/windy-plugin-da/0.3.37/plugin.min.js:1:54248
		    at T (https://windy-plugins.com/214517/windy-plugin-da/0.3.37/plugin.min.js:1:881)
		    at Array.map ()
		    at https://windy-plugins.com/214517/windy-plugin-da/0.3.37/plugin.min.js:1:3114
		    at re (https://windy-plugins.com/214517/windy-plugin-da/0.3.37/plugin.min.js:1:2655)
		    at ge (https://windy-plugins.com/214517/windy-plugin-da/0.3.37/plugin.min.js:1:4355)
		    at new In (https://windy-plugins.com/214517/windy-plugin-da/0.3.37/plugin.min.js:1:57476)
		    at eg.mount (https://app-webview.windy.com/v/50.0.2.mob.ed6d/mobile.js:7:33458)
		    at r (https://app-webview.windy.com/v/50.0.2.mob.ed6d/mobile.js:7:29342)"
}

Hi,
The Multipicker plugin generates error in Android app

Steps:

• install Multipicker plugin
• Click on Multipicker button in app

Result

• Go to Debug console

The debug console contains:

{
  "msg": "mounted",
  "stack": "Error: mounted
		    at https://windy-plugins.com/214517/windy-plugin-da/0.3.36/plugin.min.js:1:54183
		    at T (https://windy-plugins.com/214517/windy-plugin-da/0.3.36/plugin.min.js:1:881)
		    at Array.map ()
		    at https://windy-plugins.com/214517/windy-plugin-da/0.3.36/plugin.min.js:1:3114
		    at re (https://windy-plugins.com/214517/windy-plugin-da/0.3.36/plugin.min.js:1:2655)
		    at ge (https://windy-plugins.com/214517/windy-plugin-da/0.3.36/plugin.min.js:1:4355)
		    at new In (https://windy-plugins.com/214517/windy-plugin-da/0.3.36/plugin.min.js:1:57411)
		    at eg.mount (https://app-webview.windy.com/v/50.0.2.mob.ed6d/mobile.js:7:33458)
		    at r (https://app-webview.windy.com/v/50.0.2.mob.ed6d/mobile.js:7:29342)"
}

Android app

version: 50.0.2 (723ed6d)
built: 2026-05-12T08:03:45.608Z

Additional Note:

If you enable more than 3 features on the right side within the Multipicker settings, the picker displays no enabled features at all.

@MarkNagy Hi, The issue still exists in
Android app
version: 50.0.2 (723ed6d)
built: 2026-05-12T08:03:45.6087

The yellow button is disabled.

Expected: Button is enabled

Android Version: 16 API , SDK 36 , One UI Version: 8.0
Device: samsung/r9qxeea/r9q : 16 (Samsung Galaxy S21 FE 5G), Model SM-G990B, Locale: de-DE

A few days ago, the question came up again whether front line maps could be provided (see Display traditional fronts). This question has appeared regularly for years. The Windy team's answer is always essentially the same, summarized as: they cannot be provided, with the explanation that Windy is not able to create such front line maps.
I fully understand and accept this completly!

Nevertheless, there is a need for front line maps, including for myself.

My workaround is that I have searched for websites that display exactly these maps for a specific large region and saved their direct links as shortcuts on my Android smartphone.

This workaround works for the region where I live (Central Europe).
However, it is impractical when I travel, e.g., to the USA, South America, etc., because

1. I do not know any good and useful front line maps from the destination region,
2. it is time-consuming for me to search for them and then save them as shortcuts on my smartphone, and
3. having many shortcuts on the smartphone is, of course, not very desirable.

Therefore, I propose the following basic idea:

Basic idea

Windy would include a small collection of 10 URLs that directly link to front line maps. The list is grouped by large regions, and for each region there is one link. Together, these regions cover the entire world.
When a link is opened, it is opened in the smartphone’s default browser.
The links are accessed through the picker.

Some relevant aspects of the idea

1. Who maintains the URLs?

The 10 URLs are entered once by the Windy team.

2. Is there a copyright issue?

From my point of view, no. Windy only has pure links. No external websites are embedded. No caching of external websites.
I assume that the external providers of front line maps would welcome additional traffic.
As a courtesy, one could ask them whether they agree with this.

3. How could the links be accessed in Windy?

Through the picker. Based on the picker location, the corresponding regional link to the front line map is selected from the list.

4. Is there a language problem regarding the external front line map website?

In my view, no. The symbols on such maps are standardized worldwide by the WMO (World Meteorological Organization), meaning anyone can understand front line maps.

Sometimes, the websites also contain verbal descriptions of the synoptic situation. Many browsers now have built-in translation functions, so language plays only a minor role.

And the purpose here is solely to display a front line map website; additional verbal descriptions are only a nice-to-have in this context.

My idea in more detail

Additional submenu in the Settings

• In the Windy app → Settings, an additional submenu “External Front Line Maps” is added.
• This submenu contains a two-column table.
• The list of URLs can be viewed here.

Region (Broad area)	URL
Europe	https://14-tage-wettervorhersage.de/wetter/grosswetterlage/
…

BTW: Here are some different links for Europe
https://www.wetter.net/grosswetterlagenkarte
https://www.meteoschweiz.admin.ch/#tab=forecast-map

Possible list of regions (Broad areas)

• North America (Continent)
• North Atlantic (including parts of Europe)
• Europe (including northeastern Atlantic section)
• North Pacific (extratropical)
• Tropical Atlantic / Caribbean / Eastern Pacific
• Canada / Northern Hemisphere (northern sectors)
• East Asia / Western Pacific
• Australia / South Pacific / Indian Ocean (Southern Hemisphere)
• South Asia / Indian Subcontinent
• South America

This covers the entire world.

Perhaps this division is still too coarse. It could be made more granular if needed.

Opening the external front line map using the picker

When using the picker in the Windy app, the menu bar appears at the top.
To the right of the existing button “Forecast for this point”, there would be another button: “External Front line map”.

When clicking on the “External Front line map” button, the default browser opens the link corresponding to the region in which the picker is located.

Extended idea - make the table editable

Advantages:

It makes sense for the table to be editable because:

1. Flexible choice of sources
   Providers of front line maps vary greatly by region. Users can add the sources they consider best, most accurate, or most convenient.

2. Reliability
   If an external URL stops working, users can replace it themselves without having to wait for an update of the list by the Windy team.

3. Travel-related adjustments
   Frequent travelers can dynamically adjust links for different regions without modifying the entire set of predefined links.

4. Additions and specialization
   Some users may want to add more regions or specialized maps (e.g., only North Atlantic, only Southern Hemisphere).

5. Different languages and preferences
   Users can enter sources in their preferred language or with their preferred map style.

In short: An editable table makes the feature future-proof, flexible, and individually customizable—without requiring Windy to maintain all possible links worldwide.

Extended idea 1 – Only URLs editable

The advantages 1 to 3 and 5 are covered.

The two-column table (Region / URL) is only editable in the URL column.

Rows cannot be deleted.

There is also a button “Load default URL list”.

Extended idea 2 – Fully editable

The advantage 4 is covered.

The two-column table (Region / URL) is fully editable.

When clicking on the region name, a map section selector opens (similar to “Select area” in Google Maps for Offline maps or Overpass Turbo OSM {{bbox}}).

New rows can also be added.

There is also a button “Load default URL list”.

My use case

My personal use case is using the Windy app while traveling.
Therefore, I would like to see such functionality integrated into the app. Plugins are not available in the Windy app.

I would be pleased if parts of my suggestion were taken into consideration.

Dear Windy team,

Thank you for Windy! I have been using the app for years as a premium user.

I suggest the following addition to the alarms:

Addition of an alarm in the Windy app (Android) for the UV Index (UVI) with

• a configurable warning threshold for the UV index and
• a default value for the warning threshold of >= 3

The UV Index is used to assess the risk of UV-related skin and eye damage.
The World Health Organisation (WHO) recommends taking preventive protective measures from UVI ≥ 3.
A UVI = 3 is considered the lower threshold value for UV-related health damage.
Therefore, a notification should be activated as standard (default) from UV index 3. However, it should be possible to change the value.
When configuring the warning threshold yourself, it should also be possible to enter decimal values with 1 decimal place, e.g. 3.5

I currently use the following extra app to be notified of the UV index:
SunSmart Global UV app ( https://play.google.com/store/search?q=sun%20smart&c=apps ).

If I could be notified of the UV index via an alarm in Windy, then I would no longer need the extra SunSmart Global UV app.

The same happens if coordinates are copied from Organic Maps (2024.08.16-5-FDroid)

Hello,
Thank you for Windy app! I enjoy it very much!

I found the following symptoms. And may I ask you kindly for improvements here?

Symptom 1:
Entered or pasted coordinates are not recognised if they contain special typographic characters such as typographic apostrophes.

Symptom 2:
Coordinates are not recognised if a required comma is missing or an additional comma is present.

Use cases

Use case 1.1:
Open the OSMAND app.
Select a location.
Copy the coordinates in DMS format within OSMAND.
Open the Windy app on an Android device.
Open the search function and paste the copied coordinates from the clipboard.

Use case 1.2:
Open the Windy web app in the Firefox browser on a notebook.
Open the search function and paste the copied coordinates containing typographic apostrophes.

Use Case 1 Expected Results:
The coordinates should be recognised correctly.

Use Case 1 Actual Results:
The coordinates are not recognised.

Use case 2.1:
Enter coordinates in DMS, DMM or DD format in the Windy app search function, omitting a required comma or inserting an additional comma.

Use case 2.2:
Enter coordinates in DMS, DMM, or DD format into the Windy web app search function in the Firefox browser on a laptop, omitting a required comma or inserting an additional comma.

Use Case 2 Expected Results:
The coordinates should be recognised correctly.

Use Case 2 Actual Results:
The coordinates are not recognised.

Root cause for symptom 1
I found out that the root cause for symptom 1 is probably the character encoding of the copied coordinates.
When I changed the copied coordinates to ASCII/ANSI then the coordniates will be recognized by Windy.

Summary:
The input and insertion of coordinates in the search function should be both character set-independent and comma-independent in order to enable the problem-free transfer of coordinates from other applications.

Versions used:

Windy app version 42.5.3 on Samsung Android
Windy web application version 43.0.0 in the Firefox browser version 130.0 on a notebook
OsmAnd+ app version 4.8.6

I have not checked it on other mobile devices.

@Filip_K
Thanks Filip_K for your explanation! I understood your explanation, i.e. the phenomenon only occurs at certain times of the day. For example now that I am replying here the vertical alignment is correct as I just checked. For easy reading and understanding of the prediction comparison, a vertical orientation would be IMHO helpful. Would it be possible to get the vertical alignment right and not show anything where an older value is missing?