Neil Davis

We have released windkit 0.6.2 which includes a few new functions for reading time-series data and cfdres files into Windkit. We also fixed an issue with writing RSF and WRG files from PyWAsP downscale output. Full release notes can be found at: https://docs.wasp.dk/windkit/release_notes.html#id1

Sorry for the long delay. We have fixed the issue in an updated release of Windkit 0.6.2. You should be able to install it from both pip and mamba now.

Hi, Sorry for this error. The issue is that by default elevation is not included in the result from `get_wasp_down`, but is required for creating the RSF. The easiest fix would be to set the argument `return_site_factors` to `True` in the call to `get_wasp_down`, this will include all of the site effects in the `pwc_rsf` variable. Alternatively, you could just copy the elevation like `pwc_rsf["elevation"] = site_effects["elevation"]`

We are happy to announce the release of Windkit 0.6.1 and PyWAsP 0.5.1. These have fixed a few issues reported to us. The main highlight is that we have fixed an issue with PyWAsP's licensing check that prevented it always working correctly in Docker containers. Full release notes can be found in documentation for each project: WindKit 0.6.1 PyWAsP 0.5.1

Hmm good to know about Jupyter lab, will take a look at that as well to see if it is the same issue as the REPL. We haven't advanced past the notebook interface yet 🙂 Glad to hear that the package is so helpful. We have already started discussing an interface for helping convert pandas based timeseries to our xarray time-series format, so hopefully this workflow will be easier in the future.

I can take this one. There is a challenge here when you are using the Python REPL. If you use ipython, a jupyter notebook, or call it as a script the code will work. I have an issue pending about giving a better error message here.

Great, thanks. Hope the XArray to BWC works for you.

Hi Andrea, We don't have a pandas to bwc, but we have an XArray Time-series dataset to bwc converter. You can find the docs for that at: https://docs-wasp.ramtt.xyz/windkit/io/wc_autogen/windkit.binned_wind_climate.bwc_from_timeseries.html#windkit.binned_wind_climate.bwc_from_timeseries It would be interesting to know the structure of the pandas data that you have, as we are looking to add more functionality to the time-series handling this year, and creating an XArray tswc from pandas is probably something that would be good for us to support.

Hi We are aware of some performance issues. We are currently focusing on processing the remaining 20 years of NEWA data, and then will revisit performance. For now, it seems that best performance is found when downloading data in 6-month intervals, as this matches best with the resources on the server. You have the correct URL. I am not sure why data would be provided with some data missing, as it should either succeed or fail. Could you provide a list of the variables that you are using so that I can do some testing? I will be on holiday starting Wed, so won't get a chance to look until the new year unfortunately.

Hi Gyeongil, We are currently gearing up for a release of PyWAsP in Q1 next year. It will be a separate product from WAsP and will therefore require an additional license. We will announce more information when we are closer to release.

We don't have this option available at present. The points are approximately 3 km apart, which may help you in identifying how far apart you should query each point. We are working on a new API infrastructure, which should allow users to download all lib files in a bounding box. The goal is to have this available before the end of the year.

Thanks for the bug report. I have forwarded it to our team, and hopefully we will have a fix out before too long.

Hi Shehan, Thanks for sharing this with us. This is due to a typo, the name of the package is wind_validation, with an underscore. We will be updating our documentation to fix the issue.

Hi Gururaj, We have had a lot of success with Q-GIS, which is an open source GIS software.

We have made a change to the website so that now bounding boxes should always be sent to the Energy Yield Calculator, which should have solved this problem.

We have recently have a number of questions about empty GeoTiff files from the energy yield calculation. In most of those cases it has related to using a polygon for the area being calculated rather than a rectangle. We are discussing ways to fix this internally, but for now if you make your request a rectangle you should be able to get results for your region.

We have an API that converts a GeoJSON polygon bounding box to the indices used in the OpenDAP queries used to download of the mesoscale time-series. The query will return an XML file that has a complex data element, which contains the indices for the west_east and south_north dimensions. This can then be substituted into the download. https://wps.neweuropeanwindatlas.eu/cgi-bin/?SERVICE=WPS&VERSION=1.0.0&REQUEST=Execute&IDENTIFIER=opendap_helper&DataInputs=location={"type":"Polygon","coordinates":[[[14,52],[16,52],[16,54],[14,54],[14,52]]]} Additionally, several users have asked about using the OpenDAP service with Python. We have used XArray for this purpose, using a command like below: ds = xr.open_dataset("http://opendap.neweuropeanwindatlas.eu/opendap/newa/NEWA_MESOSCALE_ATLAS/2015/NEWA-2015-12-30.nc?WS[0:1:47][2:2][674:1:674][628:1:628],WD[0:1:47][2:2][674:1:674][628:1:628],time[0:1:47],height[2:2],west_east[628:1:628],south_north[674:1:674],XLON[674:1:674][628:1:628],XLAT[674:1:674][628:1:628],Times[0:1:47],crs")

The temporal plots on the GWA, have a variable called the Wind Speed Index, this value is the mean wind speed for that temporal period divided by the 10-year mean wind speed at that point. The temporal plots are not downscaled to the 250m resolution, but come from the mesoscale simulations with 3km resolution. Therefore, by presenting the temporal data as an index, you can adjust it for your region of interest, or even local points. Of course, this also means that features not resolved by the mesoscale model that affect the timing of the wind are not represented.