Hello,

I get the same issues with my applications.

Regards,
Basile

@korina
Hello, thanks for answering. I found the answer to my problem, I was using the wrong output key gust_surface instead of gust-surface...

Sorry for wasting your time.

@nesro Thanks a lot

@ss-nick said in No 'Access-Control-Allow-Origin' header is present on the requested resource:

Hi,

We are getting error No 'Access-Control-Allow-Origin' header is present on the requested resource.

Its coming from https://ims-s.windy.com/im/v3.0/forecast/gfs/minifest2.json?0051'

Also net::ERR_FAILED in the same file

Please help, Thanks

Hello,

I'm also getting this type of error tonight :

"Access to XMLHttpRequest at 'https://ims-s.windy.com/im/v3.0/forecast/gfs/minifest2.json?1931' from origin 'http://myapp' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource."

Can you tell me what it is ?

Best regards,
Basile

@Suty Yes indeed, it is now fixed and fully operationnal !
Thanks

Hello,

I noticed that we only have access to the first 10 days of GFS and first 5 days of ICON global on windy map api instead of the 15 days and 7 days range we have on windy website.

Is this normal ? I can't find it in the documentation of the API.
Is there a way to increase this limit ?

Regards,
Basile

@Suty Yes indeed, it is now fixed and fully operationnal !
Thanks

Hello,

Windy Map API seems to be broken.

I have this kind of plot on the map :

Can you fix the issue ?
Regards,

@nesro Thanks a lot

Hello,

I get the same issues with my applications.

Regards,
Basile

Hello everyone,

Is there a reason why GFS Wave (ww3?) model has missing values on some areas, and these areas are changing over timestep ?

Is this linked to Windy or coming from NOAA ?

Here is an example.

Hi @idefix37 and thanks for your quick answer !

Yes that's what I was thinking for the website, missing values means 0 m.

My question is then why the API is giving a different value for the same location and same timestamp ?

Here is my API call code :

And here is the result (I reduced it to get the last timestamp on the one we want 1681257600 (04-12 00:00 UTC) :

Hello,

We are experiencing some weird data with swell 1 values on gfsWave API.
We're getting higher swell 1 than the total wave height.
Ex :

• Timestamp : 1681257600 (04-12 00:00 UTC)
• Position : 29°N ; 89°30W
• Wave Height : 1.0397
• Wind Waves : 1.0397
• Swell 1 : 2.5998

We checked on windy and it seems there is missing data for swell 1 with gfs model (see picture)

Is there an explanation for that ? Why is the API giving some weird value instead of a NaN or something like that ?

Moreover, it seems that there is some difference between the API result and the windy picker for same timestamp and location.

Regards,
Basile

@b-rochut It seems to work well for other satellites but not this one...

Hi,
Satellite views are not updating well since yesterday.
I'm talking about the GOES-EAST.

For example right now, there is a display for everything except the last 30 minutes.

Thanks a lot
Basile