All Activity

There is ways to do that, but I guess the first question is whether you really need a map this big? Usually a distance of about 20 km from yours turbines/mast is more than enough and anything more will not have a significant effect on the flow modelling results, but will make the computations significantly slower.

I see a mail address in your profile and will use that for continued discussion.

Hi Morten, Thanks for picking this up. I have engaged with our IT team, and they arrived at the same conclusion as yourself. They have identified several IP's that have been blocked when making the access request, and have asked if you can confirm which of them relates to WAsP so that they can whitelist them. Are you able to pick this up in a private channel so that I'm not broadcasting IP addresses? Thanks

Hi Morten, Thanks for picking this up. I have engaged with our IT team, and they arrived at the same conclusion as yourself. They have identified several IP's that have been blocked when making the access request, and have asked if you can confirm which of them relates to WAsP so that they can whitelist them. Are you able to pick this up in a private channel so that I'm not broadcasting IP addresses? Thanks

Hello, I am currently trying to use the 'DTU Wind' tool for QGIS to create a roughness map for an area larger than 60 x 60 km, which is the area limit for the "Get WorldCover landcover polygons" tool. Is there a way to divide a larger area into sub-areas and merge the .map files?

When I load the roughness WAsP map, a popup window appears with the following information: "A "twin-line node" - with a pair of matching roughness lines - is encountered, at: (.....) It can readily be resolved by joining the two lines. It is recommended to resolve twin-nodes automatically. Do you accept auto twin-line node resolving by joining the matching roughness lines?" When I clicked “No,” it displayed the Cross points error. When I clicked “Yes,” I saw the same result as in your previous capture. Thank you for your clarification and suggestion on resolving this issue.

I tried to open your map, but I can see you have used 50 m resolution, so it takes hours to open in the map editor. I would recommend just using the default 100 m resolution, because it will be much faster to open and it will likely make very small differences only for WAsP, which is anyway simplifying the roughness map afterwards. I couldn't detect any errors in the map editor though, see below. Maybe make sure you use the latests version of the map editor and the QGIS plugin?

Hi Rogier, Please see map in this link: https://drive.google.com/drive/folders/19XUF6dFftUT-LeOY1R8szx7LWpnkqsIJ?usp=sharing Many thanks

Yes we recommend always checking with the map editor, but in principle there should be no errors. Could you share your map? Sometimes errors can be solved with "snap geometries to layer" in qgis.

Hi all, I am currently working with Wasp scripting in QGIS and utilizing the “Get Worldcover land cover process” tool, followed by “Polygons to roughness lines” and “Save WasP roughness lines.” Upon reviewing the exported roughness WAsP map file, I have encountered several cross points errors. It appears these errors occur at points where two polygons with the same z0 value intersect. I have a few questions regarding this issue: Should we validate the roughness WAsP map using the WAsP Map Editor for dead-ends, cross points, and LFR-errors, or is this validation only necessary when importing a Rough-ASC map (*.asc)? If validation is recommended and cross points errors are detected in the WME, what steps can we take in QGIS to resolve these errors before exporting? Best regards,

The error message suggests a problem connecting to our database. I am not sure why but you could try again another time, from another Network or from another PC. I made a small demo to illustrate the process, see https://panopto.dtu.dk/Panopto/Pages/Viewer.aspx?id=a8c6d653-53b5-4bee-8208-b21700925271. Note that I insert a turbine site before downloading the GWC to help WAsP finding the location of the process.

Hi all, when attempting to import a GWC or vector map from the Global Wind Atlas using the "insert From Global Wind Atlas" function in the right-click menu, I am met with the following error: Exception report produced at 2024-10-22 11:44:08 The request was aborted: Could not create SSL/TLS secure channel. raised at: 2024-10-22 11:41:56 2024-10-22 11:41:56: Exception raised in: System:Net:HttpWebRequest:GetResponse 2024-10-22 11:41:56: Message added: Could not establish secure channel for SSL/TLS with authority 'dtu-pferdemund-01.eu' 2024-10-22 11:41:56: Exception raised in: Server stack trace: 2024-10-22 11:41:56: Message added: Could not create a data source 2024-10-22 11:41:56: Exception raised in: Rvea0364:Implementation:cTerrainDataSource:Constructor 2024-10-22 11:41:56: Message added: Cannot create a data retrieval session 2024-10-22 11:41:56: Exception raised in: Rvea0364:Rvea0364Classes:Rvea0364:IRvea0364Classes:CreateTerrainDataRetrievalSession 2024-10-22 11:41:56: Message added: Could not get a map from GWA3 servers 2024-10-22 11:41:56: Exception raised in: WAsP:cGwaMapRetriever.GetVectorMap 2024-10-22 11:41:56: Message added: Could not insert a new hierarchy member by reference 2024-10-22 11:41:56: Exception raised in: WAsP: cWorkspaceInsertionExpert:ExecuteMemberInsertionCustomVectorMap 2024-10-22 11:41:56: Message added: There was a problem with the insertion 2024-10-22 11:41:56: Exception raised in: WAsP:cWorkspaceInsertionExpert:ExecuteHierarchyInsertion 2024-10-22 11:41:56: Message added: Insertion failed 2024-10-22 11:41:56: Exception raised in: WAsP:cWorkspaceController:ExecuteHierarchyInsertion 2024-10-22 11:41:56: Message added: The insertion was not successfully completed 2024-10-22 11:41:56: Exception raised in: WAsP:cMemberPopupMenuMediator:ProcessInsertionFromMenu 2024-10-22 11:42:03: Message added: Could not get a map from GWA3 servers 2024-10-22 11:42:03: Exception raised in: WAsP:cGwaMapRetriever.GetVectorMap 2024-10-22 11:42:03: Message added: Could not insert a new hierarchy member by reference 2024-10-22 11:42:03: Exception raised in: WAsP: cWorkspaceInsertionExpert:ExecuteMemberInsertionCustomVectorMap 2024-10-22 11:42:03: Message added: There was a problem with the insertion 2024-10-22 11:42:03: Exception raised in: WAsP:cWorkspaceInsertionExpert:ExecuteHierarchyInsertion 2024-10-22 11:42:03: Message added: Insertion failed 2024-10-22 11:42:03: Exception raised in: WAsP:cWorkspaceController:ExecuteHierarchyInsertion 2024-10-22 11:42:03: Message added: The insertion was not successfully completed 2024-10-22 11:42:03: Exception raised in: WAsP:cMemberPopupMenuMediator:ProcessInsertionFromMenu Latest thread started in: WAsP:fProgressMonitor:Form_Load Apologies if the solution is obvious, I am new to the software. Thanks for any help in advance.

Thanks very much Rogier, I will try those and see if they help.

I see, this is a simple bug that I fixed now. The new version will be available soon. This can be when you use the polygonize script in QGIS or other tools. Those scripts don't insert extra nodes where several polygons meet. You can insert those by searching for the script "Snap geometries to layer" and running that. You can also install windkit and use the script poly2lines: https://docs.wasp.dk/windkit/io/topo_autogen/windkit.map_conversion.poly2lines.html

Hi, I've recently been working on a project which required input from several data sources to generate a WAsP roughness map, including raster forestry information, project specific vector roughness layers and Corine landcover. I combined forestry heights and downsampled the raster by running filters, converted to vector and after various other data cleaning steps, was able to combine the three information sources. For the WAsP polygons to roughness lines tool it wasn't clear from the documentation that even if you're not using displacement height that a "d" column is required within the roughness shapefile layer (with all zero values), in addition to the z0 column. Once I added that the conversion worked. It might be helpful to add a note to the instructions for the polygons to roughness lines tool. To check the file I saved as a .map and loaded into WAsP Map Editor (WME), which identified numerous dead ends and cross points as a result of the varied sources of data and operations I'd carried out. A lot of them occurred at points where 3 polygons were connected so I'm not sure if that may be an issue with the polygons to lines converter or just to do with the complexity of all the processing. I fixed them in WME, but wouldn't have been able to identify or fix them as easily in QGIS. Is there any plan to add a feature to identify cross points, dead ends and LFR errors in the QGIS WAsP toolkit? This would be very helpful for when WME support is withdrawn.

Hello, I can not download data series from New European Wind Atlas When I try to download data (mesodownload/time series, then I make a selection and press download button), I am getting a file of HTML format ( mesoscale-ts) that takes me here: DataPoint API reference - Met Office This is the same if I go to this link, NEWA Mesoscale Time-series API - Swagger UI (neweuropeanwindatlas.eu), I complete the fields, execute and then try to download. Please can you help me with this? Thanks https://map.neweuropeanwindatlas.eu/

Hi Rogier, thanks very much for your response. I am interested in learning more about how the most significant cells are chosen, in order to inform my roughness map creation process. Is this selection process described in more detail anywhere?

Hi Doha, the papers you mention are indeed the right references. This paragraph in the paper 1 you mention probably explains it best: The original zooming grid is just a grid where the grid cells increase in size further away from the site: The roughness lengths in these cells are then multiplied with a exponentially weighted distance. From those transformed cell values the most significant ones are found with a simple algorithm where you just loop over all roughness changes until you have explained enough of the initial variance in all transformed roughness changes in a certain sector.

Hi all, I have been investigating how large roughness maps are processed on WAsP, and have found the following two paper which describe some aspects of how the roughness rose is generated: https://wes.copernicus.org/articles/6/1379/2021/wes-6-1379-2021.html https://wes.copernicus.org/articles/3/353/2018/wes-3-353-2018.pdf I now understand that WAsP simplifies large roughness maps with many roughness changes into a roughness rose, and that each sector of this rose has a maximum of 10 roughness changes by default. I have also observed that a great amount of simplification is involved, as I have personally tested large roughness maps with more than 10 roughness changes in a given sector and seen resulting roughness roses with at most 5 changes in any sector. I have not found a detailed description of how the roughness changes used on the roughness rose are chosen or how WAsP simplifies or averages several roughness changes on the original roughness map into one roughness value on the corresponding section of the roughness rose. Does such a description exist anywhere?

Thank your support ! Best regards, Trantduc

We updated the wind climate models and the new model parameters are not supported by the old LIB file format. If you need a LIB file for a special purpose, you must recalculate the GWC without the new model options before you can export it to file. Follow this procedure: Right-click the GWC and select Show GWC from the popup menu. Open the Stability panel and select the old EWA profile model from the drop-down menu. Open the Geostrophic shear panel and hit the Turn off button Close the GWC and recalculate it Right-click the GWC and select the Export GWC to legacy format option from the popup menu. For WAsP calculations, we definitely recommend GWC calculations by the updated model and export to the new GWC file format. Maybe you can seek advice from the WindPro developers about the best workflow for their program. Best regards, Morten

Hello WAsP Team, I am encountering an issue with data usage. Previously, I would import a .tab file, map vectors in WAsP, perform calculations, and obtain a .lib file. In Winpro, I utilized this .lib file as wind statistics in Site data. However, in the latest version of WAsP, the .lib file has been replaced by a .gwc file. Unfortunately, the wind statistics in Site Data currently only accepts .lib files. Could you please assist me in using the .gwc file appropriately so that I can use it for park calculations? Thank you for your support. Best regards, Trantduc

The WAsP week 2024 is a three-days WAsP course followed by two days of workshops. You can learn about our ideas for workshop topics at WAsP Week 2024 open for registration, but we are open for your suggestions too. Do you have a topic, which you would like us to discuss in depth?

Hi Pablo, The Terrain analysis (CFD) window can optimize this mosaic to cover all turbines and met stations by a minimum number of 2x2 km tiles. As you say, this will normally not result in an area of a rectangular shape. WAsP allows you to generate one or several resource grids, and they may include areas with no CFD data. To see how this work, we can open the ParqueFicticio workspace, which is part of the WAsP sample data normally stored in ..\Documents\WAsP samples\WAsP 12\Wasp, import the associated CFD data and create a resource grid, which is larger than the area covered by CFD calculations as in the first screen dump below. If we export this to a WRG file, that file will include the grid nodes without CFD data and report zero in all result columns, see second screen dump. I do not know how Windfarmer will react to a WRG file containing lots of zeros. To learn about best practice for CFD results in Windfarmer, I suggest that you consult the Windfarmer documentation or ask for their guidance. Good luck with your project!

Hi Heather, The wind speedup and deflection script in WAsP Engineering provides a simple lookup table, which you can use to correct an observed time series observed at a reference point to the conditions at a turbine site and maybe another height above ground ground level. We made this script a long time ago supporting people who wanted to work with alternatives to the annual-maximum method, which in those days was the only extreme-wind estimation method in WEng. In principle, you could correct your time series by the lookup table of the WEng speedup and deflection script and use it for other purposes, but be aware that the WEng flow models focus on extreme wind conditions and does not include stability corrections. The built-in standard model of WAsP (IBZ) and WAsP-CFD are more suited for prediction of energy production. When correcting a time series by these models, you must consider possible differences in upwind flow profiles and apply the geostrophic drag law. As mentioned above by Rogier.