Neil Davis

This should be fixed now.

Hi Gyeongil, Thanks for the information about your error and the suggestion about improving the documentation. We are working to improve the documentation now ahead of an upcoming release. The issue that you are getting about the name, email, and institution is about the first time setup of Windkit. We ask for this information the first time that a user creates an xarray object, and store it in a configuration file. We are updating this process in the next version, but for now the easiest way to initialize this configuration is to run the following commands, which will then prompt you to enter the information. import windkit as wk wk.empty_bwc(wk.create_dataset([0, 1, 2], [3,4,5], 100, 4326))

We are replacing some critical hardware this afternoon (1700 CEST; April, 24, 2025). This will take both the licensing proxy and conda channel offline for the duration of the work. If everything goes to plan, it should be available again by 1900 CEST. We will be following up after the work is completed and will contact our IT department if we uncover any issues.

Unfortunately, this isn't possible in the browser, as we currently have it setup. If you are using a tool to work with the API link, that tool should provide a way to change the output file name. You could also make a small html page that would href to the API link, and then be able to right-click to save as. Some examples of tools would be the ones below. I am assuming you are windows user, if not it should be easy to get curl and wget for Linux or Mac. I haven't used the windows tools, so am not 100% sure they will work. Python wget or curl

Hi Michele, It depends a bit on the variable, but most of them are at "surface level", which would be the the terrain height of the location, which can be obtained from the Elevation variable. This is for sure the case for the Air Density.

Hi Michele, Thanks for letting us know. We have rolled out an update to the service, which has improved download speeds, but seems to have issues with larger requests. We are currently investigating the issue, but haven't found a solution yet. For now the best option is to download smaller subsets of data as you mention you are already doing. Sorry for the inconvenience.

Hi Pascal, We rolled out a new backend on a new server Monday evening (23.02.2025). We have noticed some instability, we have diagnosed it to be related to some memory issues on the new server. We hope to have a fix either today or tomorrow. Best, Neil

The Windows packages of PyWAsP 0.7 have been uploaded to our conda channel.

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.

Sure, everything is possible. I have reached out to via DM to see if this is something we could collaborate on.

Thank you for your suggestion, we have not seen academic torrents before. However, I am not sure that it would be a good set for the New European Wind Atlas dataset. Our dataset would almost double the amount of data available via that platform. It is also unclear to me how users would be able to subset the data so they could get what they are interested in and not the full dataset. We are almost finished repackaging the data into a format that should allow users to download around 10 years of data for a single point. We are doing performance testing to determine the new limits for this repackaged data. It should launch early next year.

Are you still having this issue? I am not able to replicate it. If I select say downloading 2005-01-01 for Wind Speed at a point near Copenhagen, I get the NetCDF file for that point.

We have released new versions of PyWAsP and Windkit. Windkit has a number of deprecations, please pay attention if you are using these. We aren't sure how long we should keep deprecations around, please let us know if you have thoughts on this. PyWAsP has a number of breaking changes, we are closing in on a more stable API, but still expect a few more breaking changes. The highlights of Windkit include a new Long Term Correct module, an improved WindTurbines class, better integration with GeoPanandas, Improvements to downloading of raster and vector maps, and a new function to implement cross prediction. Full release notes can be found at: https://docs.wasp.dk/windkit/release_notes.html#id1 For PyWAsP the main highlight is the new climate extrapolation functions. These functions allow the prediction of either binned or weibull wind climates without creating a generalized wind climate lookup table, reducing interpolation errors. The binned wind climate to binned wind climate approach was presented at the Wind Europe Technical Workshop for Resource Assessment. In addition, new BWC resampling functions have been added, we have included support for custom root CA certificates, and have been able to improve performance for a number of functions. Full release notes are found at: https://docs.wasp.dk/pywasp/release_notes.html#id1

The issue is that the time-series data is a raster in the projected space, but not in the lat/lon space. Therefore, the XLAT/XLON have to be two-dimensional, as the values at each point depends on both the x and y dimensions. The approach from David above will give you a non-raster dataset in the new projection. If you want to get a raster back in the new projection, you can use the Windkit tool we have developed, which will "warp" the data from one projection to another, keeping the grid spacing approximately the same. When warping, you will be performing an interpolation, nearest neighbor by default. import windkit as wk import xarray as xr ds = xr.open_dataset("mesotimeseries-Area 2.nc") ds ds_warped = wk.spatial.warp(ds, 3035) ds_warped

The timeseries data is defined on a lambert conformal grid. The WKT of the grid can be found in the crs_wkt attribute of the crs variable of the downloaded NetCDF file. It doesn't have an EPSG as it is a custom projection defined specifcally for the NEWA mesoscale simulations.