Rogier

That probably means that somehow you have invalid geometries. You can find them by running Vector > Geometry tools > Check Validity. This will generate three layers with valid, invalid and errors. Running the script on the valid output instead of the original layer that you used as input should work. Usually invalid geometry result from cropping very small areas near the border. If that's the case you can safely proceed with the valid layer. If not, you may have to edit your layer and make sure it is valid. I would also download the latest version of the QGIS plugin as there have been some bug fixes and updates: https://data.dtu.dk/articles/software/Using_QGIS_to_create_WAsP_maps/20495178

Hi, I am not sure if I understand correctly but if you select you wind farm there is the option the export and import from excel: You will have to save it as a "old fashioned" .xls file for this script to work though (in excel I mean).

From what you describe it seems like what you are trying to should work. I personally would usually use the QGIS plugin for doing this. You can download the plugin here; https://data.dtu.dk/articles/software/Using_QGIS_to_create_WAsP_maps/20495178 The video for working with displacement you can find here: https://panopto.dtu.dk/Panopto/Pages/Viewer.aspx?id=fd8f16a9-9cee-4644-a71e-b09200ad6533 Other videos to get this point are listed here: https://panopto.dtu.dk/Panopto/Pages/Viewer.aspx?pid=027e510f-32e6-473d-b96c-b0d800dddc2e 1a/b : then pick "Edit > Change landcover" and assign a roughness and displacement height to a certain landcover. Hopefully you can save this a gml. 1c: I would just keep them seperate and add them as seperate "vector map data layers": 2: The spider grid analysis is the default model since WAsP 12.7 so you don't have to do anything extra for this. The landcover table is not something you have to generate yourself neither, as it just made by the map editor/QGIS when you save the file as GML. It is embedded in that file. 3/4: Also this is just done automatically since WAsP 12.7. It will add the displacement heights from the landcover map to the orographic map in the program itself. In the video I linked I think there is towards the end a part where you can see it in WAsP where the displacement height shows up in the ´site effects´ tab.

Hi, no everything 'old' should work as expected: you will just have to specify a correct position using a georeferenced map. What do you mean with the form not working?

No with the introduction of new features related to profile modelling and stability it is not possible to export as .lib file anymore.

A location is now required for your GWC file, perhaps it is related to that. The newer version of WAsP requires a location to retrieve relevant meteorological variables around the site of interest to calculate the air density and the atmospheric stability. If you want a more definite answer, you can share your workspace by attaching it here or by writing to support: https://www.wasp.dk/support

Ah ok, yes I see you are right about the default path being the current working directory. Yes, the error you have discovered can occur in more places in windkit. Whenever you find that error you can fix it by using positional arguments instead of named arguments for the first argument (e.g. `bwc` instead of `bwc=bwc`)

Hi Nils, The only thing I had to change in your code is: # Create binned wind cliamte from timeseries bwc = windkit.bwc_from_timeseries( DS ) # Create .tab file from binned wind climate windkit.binned_wind_climate.bwc_to_tabfile( bwc, "/home/rofl/test.tab" ) But I agree what you are doing should also work (the ts=DS part), so I have reported it as a bug. In the last function you have to specify the path. Cheers

Hm, then I am really not sure. Perhaps the URL is not accessible for you somehow. Can you access the URL "esa-worldcover.s3.eu-central-1.amazonaws.com" directly?

I looked at your polygon and the first problem is that it is in a geographic coordinate system. So you will have to reproject to for example a UTM projection. Another problem is that ideally your bounding box should be rectangular so we can crop the boundary lines. I recommend to use the newest plugin that I uploaded: https://data.dtu.dk/articles/software/Using_QGIS_to_create_WAsP_maps/20495178 There is a new script included where you can create a bounding box from lat/lon and a option to download worldcover data. I have also updated the instruction videos.

Yes, you can either attach it here or send it to the support: https://www.wasp.dk/support

Yes there is no height and roughness classes there, but I don't think this is what WindPRO is using. This code is in beta and has not left DTU as far as know. Regarding your other questions: the problem is that the observed wind climate is valid for a certain roughness and height, so if your output location is not for exactly that location you will need more information about what the wind climate is for other heights and roughnesses.

Could you sent me the polygon that you are using? Because I can't reproduce the error.

Hi David, these are some good questions. Since some of these decisions were already made when WAsP was developed for the first time (80s/90s) and I have been at DTU only since since 2010 I can only give you my best guesses. 1) The generalized wind climate can be considered as a lookup table for the wind climate conditions. Typically, the workflow would be that you have one mast that you convert to a generalized wind climate and apply it to many turbines positions or a many points (resource grid). Therefore it computationally it make sense to do the transformation to a generalized wind climate only once. For all turbine positions or points in a resource grid we then only have to do a lookup in the generalized wind climate and not reprocess the whole histogram. Technically, the input histogram is actually first converted to a geostrophic wind climate (using the geostrophic drag law) and the the down transformation is continued (see page 585 here: https://backend.orbit.dtu.dk/ws/portalfiles/portal/112135732/European_Wind_Atlas.pdf ). But you could also continue from the geostrophic wind climate straight to the output locations, thereby removing some of the small interpolations errors that are made when interpolating the generalized wind climate. There is some code for doing this that we may introduce in the future, but it is not available in the WAsP GUI, also because the interpolations errors are typically very small. It is also easier to compare wind conditions if you have some standard heights and roughness you can compare with (as is done in the original european wind atlas tables). So in other words, the generalized heights and roughness are not strictly required but just a model choice that were made at some point. 2) The generalized wind climate is already 'cleaned' for effects of stability so these will not have an impact. So if your input wind climate, height, location (comes in via the coriolis parameter which depends on latitude) and stability for the generalization is the same and the wind climate at z0=0.1 and h=10 m is the same, all other heights and roughnesses should also be the same. 3) The main rules of thumb related to the generalized wind climate are to set the height of your observations and prediction close the heights of the generalized wind climate. Like that there will be minimal interpolation errors related to heights. Typically the generalized roughness classes interpolation errors are harder to avoid, unless the roughness length at your site is the same for all wind directions. If there are differences in roughness, you can set them so that the roughness length classes span the mesoscale roughnesses that are observed in your observed wind climate and your predicted wind climate. 4) The only literature that described the generalized wind climate procedure (as far as I know) is the European wind atlas itself (mostly around page 585). Some details may be different in the code that is currently in WAsP though.

You don't have to add any URL anymore. The videos correspond to a slightly older version of the plugin. The only thing you have to do now is make a scratch layer with a single polygon and use that layer as an input "Clipping layer" to the script "Get WorldCover landcover polygons". The resolution is limited to 50 m because otherwise the maps get too large and become very slow in WAsP.