- 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...
Meeeeeeeee! Meeeeeeeee! Meeeeeeeee!
Best posts made by vsinceac
RE: A Complaint & some Questions about Map.
RE: 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.
RE: Visibility layer is not accurate
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...
RE: Results from pointing to a map location
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?
RE: El cambio climático y Windy
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...
RE: How to tell what time of day it is?
Servers are usually synchronized with time servers (e.g. https://www.meinbergglobal.com/english/productinfo/time-server.htm).
RE: Can isobars switch be a setting?
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.
Latest posts made by vsinceac
This is debatable... there are many pros (mainly about administrative areas) and cons (mainly for distances accuracy) about this map projection.
Anyway, plotting worldwide maps and data in "the best" map projection is a never-ending story; this is the reason Google created his own projection EPSG:900913 (900913 is the digit form of google string), which become standard for web mapping.
For worldwide maps, the best compromise would be to draw everything on a 3D sphere (which requires much more computing effort and resources); this is the reason Google finally ended by implementing it after many complaints from users. Afaik. Windy also plans to implement maps on 3D sphere (which was already available a couple of years ago), see this post.
RE: Map Scale
See also this related post.
Afaik. Windy uses Google projection, aka. Web Mercator, Google Web Mercator, Spherical Mercator, EPSG:900913 or WGS84 Web Mercator. It is a variant of Mercator projection, used as standard in Web mapping. As one can see on screenshot below Google Maps itself provides well a map scale on UI, which could always help:
Of course, displaying also on UI the current cursor position on map (lon/lat) would be a plus; Leaflet, as well as all other GIS frameworks provide UI controls for both map scale and cursor position.
RE: US - NAM data outage
From: NCEP.list.NOMADS-ftpprd on behalf of NOMADS-FTPPRD list Sent: Monday, October 26, 2020 22:04 To: _NCEP.List.nomads-ftpprd Subject: Re: [NCEP.list.NOMADS-ftpprd] Update on NOMADS Grib Filter and OpenDap Restoration Evening NOMADS Users, At this time we have restored all services and all data sets to NOMADS. The GEFS and NAM data were turned back on at 2150 UTC, and the ensemble data is running for the 18Z cycle right now. We will be unable to backfill any missing data. If users experience any other issues please report them to us so we can investigate. We thank you for your patience during this very impactful outage. Carissa Klemmer NCEP Central Operations IDSB Branch Chief 301-683-3835
RE: Forecast Timestamp
It is Unix Timestamp, provided with 4 extra digits after the second unit digit (i.e. values are in hundreds of microseconds, instead seconds as expected).
Try 1601629220 instead 16016292200000 in any timestamp to date converter (e.g. here): you should get "Friday 2 October 2020 09:00:20"
RE: What is the frequency of update of the weather models?
Anyway, "Pro" or "Regular" users could get update rate of each model via corresponding "clock" UI control: