thimu

thimu

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

thimu

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.

thimu

@Suty said in Report Issue cannot sent - Android App:

@thimu Could you please send all the details at support@windy.com, we prioritize this communication and it would be more effective to receive the report there.

Just sent to support@windy.com with the subject line:
Bug: Error message when tapping on "Sounding for this point"

@Suty , @MarkNagy

From my point of view, the status of the entire topic is as follows:

The original topic "Report Issue cannot sent - Android App" remains unresolved, as the submission via the app apparently did not go through or was not fully received.
The problem also exists on the Windy website - independent of the original post, as @javinpress noted; see:
https://community.windy.com/post/229760
This therefore constitutes a separate, additional issue.

In addition to fixing the problem, I suggest the following further improvements:

When submitting an error report via the app or website, the system should automatically include:

error messages from the error console (if any exist),
the Windy version number, and
relevant details regarding the device or operating system used (if necessary). As a user reporting an error, I want the process to require as little effort as possible.

The app or website should display not only a submission confirmation but also a receipt confirmation. Users take the trouble to report an error, and it should not happen that the report goes unnoticed while failing to actually reach Windy.

thimu

To: Windy team

This is an enhancement request to the original post (OP).

Composite synoptic chart

My favorite composite synoptic chart is the chart on the left on the webpage

https://www.wetter3.de/vertikal_en.html

This map - based on GFS data - combines multiple atmospheric layers and parameters into a single synoptic overview. It allows to identify large-scale weather patterns, fronts, air masses, precipitation types, and weather developments at a glance.

500 hPa Geopotential Height
Black contour lines. Show the height of the 500 hPa pressure surface. Used to identify troughs (cold, unstable) and ridges (warm, stable).

Surface Pressure (Isobars)
White contour lines. Shows low-pressure systems ("T") and high-pressure systems ("H").

850 hPa Temperature
Yellow contour lines. Show temperature at roughly 1.5 km altitude. Important for air-mass analysis, snow line estimation, and front detection.

700 hPa Relative Humidity
Gray shading. Indicates moisture in mid-level atmospheric layers. Highlights cloud fields, lifted air, and precipitation potential.

Precipitation Form
"0" -> Liquid. Rain or freezing rain. Typical of warm air masses, warm fronts, and stratiform rain.
"+" -> Solid. Snow or graupel. Typical of cold air masses, winter showers, or higher elevations.

Precipitation Intensity
Symbol size indicates intensity (starting around 0.03 mm/h). Large symbols -> heavy precipitation / convective cells.

Precipitation Type: Stratiform vs. Convective
Green -> Stratiform (large-scale). Fronts, widespread lifting. Long-lasting rain, widespread snowfall
Red -> Convective (showery/thundery). Vertical updrafts, instability. Showers, thunderstorms, localized heavy rain, graupel

See also the legend in german language ( https://www.wetter3.de/hilfe_vertikal_dt.html ).

Feature request 1:

Recreate this chart in the Windy app.

Reason:

The map enables a full synoptic diagnosis and interpretation in a single chart.
There is nothing comparable in the Windy app.
(On the website https://www.wetter3.de/vertikal_en.html it is only available for Europe.)

Vertical cross-section diagnosis

On the right side of the webpage
https://www.wetter3.de/vertikal_en.html
the vertical cross-section for the latitude or longitude selected on the left is displayed.

Example: Select the "10E" box on the left (LON 10°E: Tunis -> Kassel -> Trondheim).

In the vertical cross-section on the right, the contours of the Alps are visible between 45°N and approx. 50°N.
This clearly illustrates, for instance, the impact of mountain ranges on weather parameters.

You can choose from five different sets of composite weather parameter combinations for the vertical cross-section.
These visualizations of composite weather parameter sets are excellent; they make it very easy to understand, for example, why specific weather parameters take on certain values at specific locations based on elevation and terrain profiles.

The Windy app also features vertical cross-sections. They are somewhat hidden under the "Distance & route plan" button.
Unfortunately, the Windy app currently only allows you to view forecasts for: Car/hike, Boat, VFR, IFR, and Airgram.

Feature request 2:

Please add one or more of these composite weather parameter sets to the Windy app alongside the existing tabs (Car/hike, Boat, VFR, IFR, Airgram) under the "Distance & route plan" button.

thimu

@Suty said in Report Issue cannot sent - Android App:

@thimu Could you please send all the details at support@windy.com, we prioritize this communication and it would be more effective to receive the report there.

Just sent to support@windy.com with the subject line:
Bug: Error message when tapping on "Sounding for this point"

@Suty , @MarkNagy

From my point of view, the status of the entire topic is as follows:

The original topic "Report Issue cannot sent - Android App" remains unresolved, as the submission via the app apparently did not go through or was not fully received.
The problem also exists on the Windy website - independent of the original post, as @javinpress noted; see:
https://community.windy.com/post/229760
This therefore constitutes a separate, additional issue.

In addition to fixing the problem, I suggest the following further improvements:

When submitting an error report via the app or website, the system should automatically include:

error messages from the error console (if any exist),
the Windy version number, and
relevant details regarding the device or operating system used (if necessary). As a user reporting an error, I want the process to require as little effort as possible.

The app or website should display not only a submission confirmation but also a receipt confirmation. Users take the trouble to report an error, and it should not happen that the report goes unnoticed while failing to actually reach Windy.

thimu

I sent the error report with success via the Android app. It seems the behaviour is different between app and website.

FYI: Just as a precaution: The content of the ERROR CONSOLE of the new error in the sent error report should be as follows:

{
"errorID": "uncaught-typeerror-r-is-not-a-function",
"overlay": "radar",
"runningPhase": "3_redrawFinished",
"timestamp": 1784045099949,
"runningMinutes": 0,
"type": "error",
"msg": "Uncaught TypeError: r(...) is not a function",
"url": "https://app-webview.windy.com/#?radar,49.615,8.643,9,p:cities",
"ver": "50.1.1",
"target": "mobile",
"platform": "android",
"device": "mobile",
"latestBcast": "bcast: rqstOpen sounding (2ms ago at 1784045099947)
picker: pickerClosed (1ms ago at 1784045099948)
bcast: pluginClosed picker-mobile (1ms ago at 1784045099948)",
"network": {
"downlink": 9.5,
"downlinkMax": null,
"effectiveType": "4g",
"rtt": 0,
"saveData": false,
"type": "wifi"
},
"script": "_shared-client.js",
"line": 20,
"col": 24497,
"stack": "TypeError: r(...) is not a function
at U (https://app-webview.windy.com/v/50.1.1.mob.4aea/plugins/_shared-location-buttons.js:1:3450)
at HTMLDivElement.onclick (https://app-webview.windy.com/v/50.1.1.mob.4aea/plugins/_shared-location-buttons.js:1:3148)
at HTMLDivElement. (https://app-webview.windy.com/v/50.1.1.mob.4aea/plugins/_shared-location-buttons.js:1:5012)
at HTMLDivElement.Qi (https://app-webview.windy.com/v/50.1.1.mob.4aea/plugins/_shared-client.js:20:24366)"
}

⚙️

@MarkNagy, @all Windy staff
Did you receive the error report which I sent?
The sent error report should contain the error console content automatically as shown above, my short step description and an attached mp4 screen recording video file of appr. 14 MB size

thimu

@MarkNagy
I just sent an error report with success. The issue here with sending the issue report is resolved using version 50.1.1
Thanks!

The error report which I just sent covers a new, other error.

thimu

@rittels Thank you very much! Issue is resolved!

thimu

@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)"
}

thimu

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.

thimu

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

thimu

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

thimu

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

I do not know any good and useful front line maps from the destination region,
it is time-consuming for me to search for them and then save them as shortcuts on my smartphone, and
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:

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.
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.
Travel-related adjustments
Frequent travelers can dynamically adjust links for different regions without modifying the entire set of predefined links.
Additions and specialization
Some users may want to add more regions or specialized maps (e.g., only North Atlantic, only Southern Hemisphere).
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.