Can't download data from api

[tronigp]

I have been trying to download micro and meso data from the API, but it hasn't been working since Thursday. Do you know what the issue might be?

[Joan]

Hi,

The GWA and NEWA servers are currently down due to a file system issue. Our team is working diligently to resolve this and restore service as soon as possible.

Unfortunately, we don’t have any updates at the moment. Please refer to our webpage for the latest information, as we are currently handling a high volume of inquiries.

Alternatively, you can download GIS data from the following sources: https://globalwindatlas.info/en/download/gis-files
https://data.dtu.dk/articles/dataset/Global_Wind_Atlas_v3/9420803

Thank you for your patience.

Best regards,

Joan

[Neil Davis]

The services should be back online now. Sorry for the long outage. We have put some new processes in place to prevent the same situation from occuring.

[Nour hamda]

Hello,

I'm trying to download data using the API, but it's not working , even tried to access the link manually,  it shows :"gateway timeout" ! is the server still down ? 

 

Thank you 

[Neil Davis]

This should be fixed now.

[Carl Lange]

Hi,

The API is not working for me, I am receiving Internal Server Errors after last week's Gateway timeout seemed to be fixed. Are you already aware of the outage?

Thanks!

[Neil Davis]

Hi Carl,

Are you still seeing Internal Server Errors? I didn't see many when taking a quick look at the logs. If you are getting them, could you dm or email me the request that is throwing it so we can investigate further?

 

[Richard]

Hi Neil,

We are also experiencing 502 gateway timeout errors. When we get such an error we retry and we are receiving a .nc file but with empty content.  This seems to be a persistent problem with latest examples from this morning. Happy to share the api call directly if that helps.

Thanks for you help,

Richard

 

[Neil Davis]

Hi Richard,

Yes, if you could share an API call with me directly that would be great. My go-to tests are working, but perhaps they are a happy path 🙂.

[Richard]

Hi Neil, I am having difficulties with the API again. Specifically, the 'get-data-point' API often gives 502 response code. At times it gives 200 response but without netcdf file content.  Below are example API calls along with the timestamps at a dummy site: 

2025-09-19 12:21:18.500 DEBUG:urllib3.connectionpool:https://wps.neweuropeanwindatlas.eu:443 "GET /api/microscale-atlas/v1/get-data-point?height=100&height=200&variable=wind_speed&latitude=52.866722&longitude=-1.282186 HTTP/2.0" 502 11

2025-09-19 12:53:55.259 DEBUG:urllib3.connectionpool:https://wps.neweuropeanwindatlas.eu:443 "GET /api/microscale-atlas/v1/get-data-point?height=100&height=200&variable=wind_speed&latitude=52.867595&longitude=-1.28203 HTTP/2.0" 502 11

 

Any support would be greatly appreciated.

[Neil Davis]

Hi Richard, Thanks for letting me know. I am wrapping up another project right now, but will take a look next week, when I have some time to investigate the problem.

[NADEEM]

Hello Neil,
We are having trouble with API. Specifically, the 'get-data-point' API often gives 502 response code. At times it gives 200 response but without netcdf file content.  Below are example API calls along with the timestamps at a dummy site. Kindly need your support.

2025-12-29 11:12:48.190 DEBUG:urllib3.connectionpool:https://wps.neweuropeanwindatlas.eu:443 "GET /api/microscale-atlas/v1/get-data-point?height=100&height=200&variable=wind_speed&latitude=55.960946&longitude=-4.385082 HTTP/2.0" 502 11

2025-12-29 11:12:48.190 DEBUG:urllib3.util.retry:Incremented Retry for (url='/api/microscale-atlas/v1/get-data-point?height=100&height=200&variable=wind_speed&latitude=55.960946&longitude=-4.385082'): Retry(total=2, connect=None, read=None, redirect=None, status=None)

2025-12-29 11:13:09.766 DEBUG:urllib3.connectionpool:https://wps.neweuropeanwindatlas.eu:443 "GET /api/microscale-atlas/v1/get-data-point?height=100&height=200&variable=wind_speed&latitude=55.960946&longitude=-4.385082 HTTP/2.0" 200 None
 

[Dr. Michael Cosacchi]

Hi,

I second Nadeem's motion. I've got issues with the API, too. To make sure that my code isn't the problem, I entered my parameters into the Swagger UI:
Curl:
curl -X 'GET' \ 'https://wps.neweuropeanwindatlas.eu/api/mesoscale-ts/v1/get-data-point?latitude=51.39&longitude=11.28&height=%5B50.0%2C%2075.0%2C%20100.0%2C%20150.0%2C%20200.0%2C%20250.0%5D&variable=%5B%22TKE%22%2C%20%22WS%22%5D&dt_start=%222020-01-01T00%3A00%3A00%22&dt_stop=%222022-12-31T23%3A30%3A00%22' \ -H 'accept: application/x-netcdf'

Request URL:
https://wps.neweuropeanwindatlas.eu/api/mesoscale-ts/v1/get-data-point?latitude=51.39&longitude=11.28&height=[50.0%2C 75.0%2C 100.0%2C 150.0%2C 200.0%2C 250.0]&variable=["TKE"%2C "WS"]&dt_start="2020-01-01T00%3A00%3A00"&dt_stop="2022-12-31T23%3A30%3A00"

Error: response status is 502

Please advise.

Best,
Michael

[A Remirez]

I've got the same response status

[Neil Davis]

Sorry for the delay in getting back to this. It got lost in my post vacation to-do list. 

I have tried deploying a fix this morning. It seems like downloads are still very slow, I am not sure why, but the server should be more stable now and allow you to actually get the data eventually. I found in some cases that cancelling and restarting a download could improve performance.

[NADEEM]

There seems to be issue with the API again. It's taking a long time to respond and eventually resorts to 502. The swagger page https://wps.neweuropeanwindatlas.eu/api/microscale-atlas/v1/docs#/ also doesn't load. 

[Neil Davis]

Thanks for letting me know. I don't see any issues on the server. I have spun up some extra resources, hopefully that will help to make it more responsive.

[kiko]

Hi all,

I've been trying to get some information this morning and it seems only timeseries is working but other endpoints are showing an alert window with the message "Something went wrong".

Some of the links not working:
https://wps.neweuropeanwindatlas.eu/api/mesoscale-ts/v1/get-data-bbox?southBoundLatitude=56.450429&northBoundLatitude=56.774138&westBoundLongitude=-1.453857&eastBoundLongitude=-0.593262&variable=HGT

https://wps.neweuropeanwindatlas.eu/api/mesoscale-atlas/v1/get-data-bbox?southBoundLatitude=56.450429&northBoundLatitude=56.774138&westBoundLongitude=-1.453857&eastBoundLongitude=-0.593262&variable=elevation

An example of a link working:
https://wps.neweuropeanwindatlas.eu/api/mesoscale-ts/v1/get-data-point?latitude=57.18463&longitude=2.391358&height=100&height=150&variable=WS&variable=WD&dt_start=1989-01-01T00:00:00&dt_stop=1989-01-02T23:30:00

Kind regards

[Aidan]

On 14/01/2026 at 10:25 AM, NADEEM said:

There seems to be issue with the API again. It's taking a long time to respond and eventually resorts to 502. The swagger page https://wps.neweuropeanwindatlas.eu/api/microscale-atlas/v1/docs#/ also doesn't load. 

Hi, These issues seem to have come back again.

[PBH]

Hi, I can confirm the issue is still there download does not work via the API or the GUI 

[Dr. Michael Cosacchi]

Hi, same here...

[Vittorio]

Hi,
it was back again a few days ago but now it is off again.

[kiko]

Hi all,

I can't download mesoscale data today using a bounding box.

Also, elevation data is not available since a while. My previous post in this thread was from 2 months ago and during this period I have tried to get data several times with no luck. I have no idea if some endpoints have been removed.

KR,

[Neil Davis]

Hi Kiko,

The mesoscale time-series is not available for download by bounding box, only the atlas data. We hope to return this functionality soon, but it will come with registration and a limit on the amount that can be downloaded. We are currently testing this functionality and hope to roll it out within two months.

 

[kiko]

24 minutes ago, Neil Davis said:

Hi Kiko,

The mesoscale time-series is not available for download by bounding box, only the atlas data. We hope to return this functionality soon, but it will come with registration and a limit on the amount that can be downloaded. We are currently testing this functionality and hope to roll it out within two months.

 

Thanks, Neil, for the clarification. Well understood.