Neil Davis

We have released PyWAsP 1.0.1 with a bug fix for the `root_ca_filepath` option of the user config.

PyWAsP 1.0.0 and Windkit 1.0.2 released We have released new versions of PyWAsP and Windkit. These are major updates with a number of breaking changes. Please read the windkit and pywasp release notes carefully for a full list of changes. We recommend pinning to the previous version of (windkit 0.8 and pywasp 0.7) until you are ready to migrate your code to these new versions. The main highlights of the releases are: WindKit: - Simplified and Consistent API: The API has been significantly cleaned up. Functions have been renamed and reorganized for better clarity and consistency, making the library more intuitive to use. - Revamped Map Reading and Writing: Generic map functions have been replaced with specific, format-aware functions for elevation, roughness, and landcover maps, which automatically infer the file format. - Polygon Representation for Maps: Landcover (roughness) maps now default to using polygon-based geopandas.GeoDataFrame objects, providing a more standard and powerful way to work with GIS data. - Unified Wind Climate Statistics API: A new set of generic functions allows for calculating statistics like mean wind speed and power density on any type of wind climate object, simplifying analysis. - New Loss and Uncertainty Modeling: The release introduces tools for creating, validating, and summarizing standardized loss and uncertainty tables, which are designed to integrate with PyWAsP for AEP calculations. PyWAsP: - Major API Cleanup and Restructuring: The API has been significantly cleaned up with many functions and arguments renamed for better consistency and clarity, alongside the removal of several outdated functions. - New Pydantic-based Configuration: The user configuration has been modernized, migrating from pywasp.cfg to a more flexible pydantic-based system using pywasp_config.toml or environment variables. - Enhanced Energy Yield Calculation: New functions have been added for advanced energy yield analysis, such as net_aep to calculate AEP with losses, px_aep for uncertain AEP. - Improved Landcover and I/O: The release introduces new functions for landcover processing like convert_to_classes and a much faster polygons_to_lines function. TopographyMap now also accepts GeoDataFrames with Polygons. - Updated Dependencies: PyWAsP 1.0.0 now supports Python 3.11-3.13, NumPy up to version 2.2, PyWake 2.6, and windkit 1.0. NB! docs for windkit 0.8 and pywasp 0.7 are still available via: - https://docs.wasp.dk/windkit/v0.8.0 - https://docs.wasp.dk/pywasp/v0.7.0

We have been having server stability issues for a while now, and I think I have tracked it down to issues with the get-data-bbox endpoint for mesoscale time-series data. I have disabled that end point for now, while we work on an improved solution. Unfortunately it is currently summer holiday in Denmark, so a solution will probably not be available until the end of August. If this is part of your workflow, please write to me here or in DM. That way it can help to guide our solution, and perhaps we can help find a workaround for the time being. Thanks for your understanding on this issue.

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 🙂.

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?

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.