#1 Re: Map Editor » SRTM Import Error » 2019-01-23 13:48:48

Hi Gaoithe, apparently a wrong SRTM URL-address was used. Glad the problem is solved.

Ole Rathmann

#2 Re: Map Editor » .jpg file » 2018-01-03 17:20:00

Hi, when you start from scratch you must - in addition to adding fixpoints for your background map (in your case: a *.jpg picture), also define the boundaries the map domain. You do that by the menu-option "File | Load Empty Map"  or "Edit | Adjust Map Domain Size". Then you will be able to perform digitzing within the specified domain boundaries.

#3 Re: Map Editor » Georeference/projection of .map file format (GDAL/OGR) » 2018-01-02 11:23:50

Dear Alex,
I can give you an answer re. the Geo-referencing format used by the WAsP applications: WAsP Map Editor and WAsP itself. Your examples File2.map ..  File5.map have apparently not been produced by these applications.

When saved by the Map Editor the header-line looks like this:
+Waspdale10 - webs-test | UTM-N Z31 WGS-8|WME ver.
So here "block2", between the first and the second bar-character, contains the projection specification: the projection type, the zone specification (if a zone is needed) and the datum-specifcation; here WGS-8 is the code for "WGS 84".
Block 3 has nothing to do with the geo-reference: it specifies the version of the Map Editor that produced the map file.   

When exported by WAsP itself the header-line looks like this (one long line):
+ 'Canela' (WAsP export) <OriginalLabel>'Canela Terrain'</OriginalLabel> | UTM-S Zone 19 (WGS 1984 datum)

Again, block 2 specifies the projection; the datum is here specified in parenthesis after the zone specification.

Hope this explanation is helpful.

#4 Re: WAsP » Digitizing Maps » 2017-09-18 13:52:47

Hi - combining two digital maps in the Map Editor is quite easy: You load the first map using the File|Open menu-option, and after that you load the second digital map using the "File | Add"  or "File | Add-and-Replace" option, the latter if the second map overlaps the first map and is ment to replace it in the overlapping area. Once the combination of the two maps has been performed you may simply save the combined map.
For this operation no WAsP licence is needed - the Map Editor is freeware.
/Ole Rathmann

#5 Re: Map Editor » import .shp files to WME » 2017-01-03 11:24:23

Hi (whoever you are)  - I agree importing shape-files into the Map Editor for roughness lengths by polygons is problematic. I guess the bottleneck is really the cross-point errors, which is caused by overlapping line-segments of neighbouring polygons. The Map Editor is not sufficiently smart to see that these lines segments only touch but do not cross. How to work around? Well, do you have any possibility to change the polygons so that a a tiny space (a fraction of a meter) is left between them? Then it would be possible  - although tedious - to add the necessary external roughnesses ...
Another solution requires a bit of patience. We are just now finishng a new Map Editor version which is able to accept "unknown roughness" specification for e.g. external roughness of a polygon. The new Map Editor is - in the process just after reading - able to infer the missing roughness lengths from neighboring or surrounding roughness-change lines. But it would still require you to adjust the polygons to avoid overlapping. Another new feature is grid-file importing. So if you could convert the shape-file to a grid file (Surfer ASCII .grd format) the new map editor version would be able to read that right away - and convert it to a standard WAsP .map file.
/Ole Rathmann

#6 Re: WAsP » Syncronize view with virtual globe button is grayed » 2016-09-30 15:58:17

Hi Javo Cord - correct! WAsP10.2 does not any longer support use of displaying stuff in Google Earth. - since Google has stopped supporting the interface WAsP 10 was created for.

However, WAsP 11 supports the new way of programmatic communication with Google Earth!! So all your WAsP-GoogleEarth troubles will be goen if you upgrade to latest version of WAsP11 ..
/Ole Rathmann

#7 Re: WAsP » Anemometer installed whitin an existing Wind farm » 2016-03-16 14:44:35

Hi Marco - you are posing a tricky question!
It is in fact  possible to use WAsP to get an estimate of the speed-reduction due to the wake from the wind farm in dependence of wind direction, but it is a somewhat cumbersome.
You would need, in a special WAsP-project, to set up the wind farm, using the actual power curve of the turbines; and then add an additional "virtual" turbine to represent the met-mast, i.e. with the location of the met-mast and the hub-height=met-mast measuring height. However, this virtual turbine should have its own, very special power-curve object (WTG): the Ct-should be = 0 for all wind speeds, and the power curve should be a "fake" one: it should be completely linear over a large speed-span, e.g. (0 for 0 m/s), (50 for 50 m/s). You could use any OWC to define the generalized wind climate of the "special" WAsP project, as long as it is well-behaved in all sectors: having a non-zero frequency and a histogram with a decent mean wind speed, e.g. 8 m/s.
The resulting wake effect for the virtual turbine, in dependence of wind direction, would then give the average speed-reduction due to the wake effect from the true turbines. I have written "average" since the wake effect will in fact be speed dependent since the Ct-coefficient for the true turbines depends on the speed.
This way you should have numbers for the speed reduction at your met-mast site.

Now, in your true Wasp project, you should then apply these speed reductions as negative user corrections for the met-mast: if in sector 1 the speed reduction (due to wakes) was found to be 5% you should then specify a user-correction of -5 for sector 1. Same thing for the remaining directions.

Good luck!

Ole Rathmann.

#8 Re: Map Editor » ASTER Data and WindFarmer Import » 2016-01-19 11:37:33

Hi, "ichadtanguilig" (what ever that means?) - unfortunately the WAsP suite does not support all digital map formats, in this case the Aster GDEM. But - as an alternative - the Map Editor may import SRTM maps (version2, 3-arc-sec resolution; up to 60 deg. North).
For Aster GDEM We could suggest to use a) Global Mapper to convert to WAsP .map, or b) Surfer: here should google for "Aster GDEM to Surfer" to find a solution to make Surfer read Aster GDEM, since Surfer cannot do it directly; afterwards have Surfer export the map-contours as a DXF-file, which the Map Editor may then read - and then save as .map. Both Global Mapper and Surfer are commercial products. Finally we could suggest to try the free-wares c) SAGA GIS and d) QGIS: they may be able to read GDEM and convert directly to .map or another vector format which may be imported by the Map Editor, and then saved as .map.
Regarding .map and Wind Farmer: you will have to contact the Wind Farmer people directly. The .map format is well described in the WAsP Map Editor - so it should be straight-forward to check whether  Windfarmer can accept that.
Ole Rathmann

#9 Re: Map Editor » Map Format for WAsP » 2015-11-03 11:37:24

Hi "kedx3mmn" - I have a feeling that I have already answered you - but anyhow!
You don't need to use BOTH WindPro and WAsP to run energy simulations, WAsP alone can do the job.

About the allowable size of maps: WAsP itself has no limitations regarding how large (comprehensive) a terrain map you use for the terrain around your wind farm. Normally we recommend 5km, or 10 km to be sure, in any direction from any of the turbines or the met-mast. If the met mast is located a long distance (say 20 km) from the wind farm, the met mast could have its own map, say 10x10 km, or better: 20x20 km with the met-mast location in the centre.
The Map Editor allows you to get a DEM-map from SRTM-data at a size required by the WAsP project - the Map Editor itself will not restrict the size of the DEM-map.
/Ole Rathmann

#10 Re: WAsP » Error message » 2015-10-19 10:31:28

Hi Stefano, re. the error message when AveragingTime<>RecordingInterval : I will report the error to the proper programmer. But you should not bother, just use, as you have already tried - AveragingTime=RecordingInterval: it has - for the moment - not effect on average and extreme wind climates.

"Unsuccessful Analysis" when calculating an OEWC-POT means that your observed extreme winds (ranked) are not distributed like expected. Could happen if you use too short time series. You may still be able to use it, however, but with increased uncertainty.

Using two maps:
When calculating the average wind climate at site B from the measured data at site A: Associate the map around site A directly with the met-station (at site A) or with the generalized wind climate object - and the map around site B with the project object.

When calculating the extreme wind climate at site B from the measured data at site A (using WAsP Engineering): If you are not able to combine Maps A and B you will have to perform the calculation I two steps: Step 1: Calculate the generalized extreme wind climate from the observed extreme wind climate at A - using map A; and save the generalized extreme wind climate. Step 2: In a new WAsP Engineering project, with Map B, include the aforementioned generalized extreme wind climate, and then calculate the extreme wind climate at site B.   

#11 Re: WAsP » WAsP Vs WAsP-WindPro » 2015-10-16 10:12:14

Hi - first: You can certainly make 1st class wind energy simulations using WAsP alone. Windpro is a different piece of Wind Resource software - but it uses the WAsP flow model as its modeling engine. Both softwares have automated facilities to get topographical maps from SRTM. The difference may be regarding the latest, high-resolution versions of the SRTM maps: in WAsP we have not yet upgraded the automated SRTM import facility to also include the latest high-resolution versions of SRTM-maps - but we will in the near future.

#12 Re: WAsP » Copying Wind Farm Power Curve to Excel or Similar Programs » 2015-10-14 11:05:13

Sorry Neil - I thought you were talking about WAsP 11.2.

However, I have just checked the latest WAsP10.2 (10.02.0017) - and the CTRL+C copying option works in relation with the Wind Farm Power curve: Point into the wind farm power curve window, type CTRL+C and you should see a small yellowish notifier-label saying the content has been copied to the clip-board.
Ole Rathmann

#13 Re: WAsP » Copying Wind Farm Power Curve to Excel or Similar Programs » 2015-10-14 10:57:02

Hi Neil - it seems that the copy-option somehow dropped out in version 10.2.  However, it works fine in the latest version, 10.4 - so just update your WAsP installation.
Ole Rathmann

#14 Re: WAsP » Power curve for wind farm greater than single turbine » 2015-10-14 10:25:00

Hi "vob" - agree that this looks mysterious. First, please make sure that the  reference mast is located at the same position as the turbine and has the same height as the hub-height of the turbine - otherwise you cannot make that comparison.

If nothing is wrong there we need to have your workspace to solve the case. So in that case I invite you to send the case and the workspace to us on WASPSUPPORT@dtu.dk, full confidentiality of course - and we will find out what is the matter.
Ole Rathmann

#15 Re: Map Editor » Map Format for WAsP » 2015-06-17 13:54:41

Apparently, when you got the Malaysia map it may have contained some roughness consistency errors. What I can see is that the "Nodes" consistency check was disabled, meaning that the Map Editor did not make any consistency check at all!
So, if you reopen the Malaysia map you should make sure that all consistency items are enabled (look in the menu point at the main window "Tools | Roughness  consistency" and enable (check) All consistency items. Then you should see whether there are any consistency errors - and you should of course fix them if there are any. If/when there are no consistency errors, you should not get any warnings when you save the file. OK?

Ole Rathmann

#16 Re: Map Editor » Map Format for WAsP » 2015-06-10 13:31:35

Hi, Please describe your problem to waspsupport@dtu.dk, and attach the problematic KML-file, please. Also state the Google-Earth version from which you got the KML-file.
/WAsP Team /Ole Rathmann

#17 Re: WAsP » Wake effect of neighbouring farms? » 2015-02-06 14:55:42

Hi "vob",  you are right - wake effects from one wind farm object (A) are not felt at all by turbines in another wind farm object (B) - they are treated completely separately. If you want to model the mutual wake effect the trick is to make a "super"-wind farm, having your two existing wind farms as sub-turbine groups. In fact it is very easily done:
a) create a new (empty) wind farm object;
b) drag wind farm A to the super wind farm icon , and 
c) drag wind farm B to the super wind farm icon.

A and B will then appear as a turbine groups in the super wind farm.
d) perform the wind farm calculation for the super-wind farm
e) inspect the result for A and B individually.



#18 Re: WAsP » why are wind data generalized at 10-minute periods » 2015-01-05 12:31:09

Dear Sinisa Knezevic, the answer 1)  relating to the correlation between a mast and a turbine some hundred meters away - or more - may be closest to the truth, and building you wind statistics on e.g. 1-min-average data instead of 10-min-average data would hardly make a change - and that would also apply to the predicted power production.
However, that does not mean that it is unimportant what happens on 1-min scale; in special cases where you want to study wake effects and wake-meandering  in large wind farms you might have to measure your wind with e.g. 1-min resolution - but then we move into research and development; for standard wind power production estimations 10-min data would normally be sufficient.

#19 Re: Map Editor » Adding two maps together from two different UTM Zones » 2014-10-06 11:05:27

Hi Phil, you have done exactly what I would have done - and what can be done for the moment. Your implicit suggestion is of course very relevant: the ability to just add two maps with different (neighboring) projections, leaving it completely to the Map Editor, automatically, to perform the necessary projection transformation of one of the added map. So thank you for this suggestion!
We will write it down  as a "Feature Request" in our priority list.

Ole Rathmann.

#20 Re: WAsP » Wasp produces a very unstable wind profile » 2014-10-03 15:19:01

Hi Anna, so you are trying to perform an extended self-prediction. Please check that you have located your testing object - a turbine or a reference-mast at the same position as the met-mast - and of course in the same WAsP project where you have your met-mast with the tab-file, and your generalized wind climate object  - and then of course with the proper digital map. Once the Generalized Wind climate has been created you gradually change the height of your test-object and inspect the resulting predicted wind to get the profile.

If that doesn't solve your problem, please contact us on WAsPSupport and attach the workspace or relevant files.


#21 Re: WAsP » Suitable Measurement height for Wasp Calculation » 2014-08-18 10:59:08

The closer the mast measurement height is to the turbine hub-heigt, the better, since we reduce the wind modelling uncertainty (reducing the height extrapolation). So, in your case, you should use the 80m-measurement.


#22 Re: WAsP » WAsP wake modelling » 2014-05-26 10:33:56

Hi Hans-Peter (from Siemens), the Park-model in WAsP is discribed in the follwing report and paper:
a) Jensen, N.O (1983). A Note on Wind Generator Interaction. Risø-M-2411,
b) Katic, I, Højstrup J. and Jensen, N.O. A Simple Model for Cluster Efficiency. Proceedings of the 1986 European Wind Energy Conference and Exhibition, Rome, Italy, October 7-9, paper C6.

Both are available from the literature-page of the WAsP web-site:

a) contains the basic N.O.Jensen wake model (single wake) used in the Park-model while b) contains the description of the wake-wake interaction (the empirical sum-of-squares of speed-deficits rule). Please notice that the Park-model uses reflection of the individual wakes in the ground surface to represent wake interaction with the ground surface as well as a partial-overlap factor (how much of a certain rotor is covered by the wake from a certain upwind turbine).

Ole Rathmann.

#23 Re: Scripting and automation » Developer lisence » 2014-03-26 14:13:20

Hi, I think (not sure) that the price for a  Developer's License is in the order of 3 times the standard price (for WAsP11: around 11,000 EUR) -  but you will have to contact the sales personnel at WASPLICENCE@dtu.dk for a concrete offer.

Ole Rathmann

#24 Re: WAsP » Parameter : Sub-sectors in roughness map analysis » 2014-03-26 12:36:55

In the WAsP IBZ-flow-model (up to WAsP10 the ONLY flow model) hte surface roughness distribution as seen from a certain point (e.g. a met-mast or a turbine) is represented by a roughness rose with typically 12 or 16 sectors (as selected by the user). For each sector the roughness rose contains the effective rougness value for the consequtive distance-ranges from the point and outwards (e.g. 0-500m, 500-2300m, 2300-7000m). When evaluating these ranges and the corresponding effective roughnesses each sector is divided in subsectors (default 9) and the roughness variations in each sub-sector outwards are then aggregated (averaged) into sequence of ranges in the sector.
If you lower the number of subsectors (to increase calculational speed) the roughness rose evaluation will loose details and thus get more uncertain.

#25 Re: Climate Analyst » Manual TAB generation and Climate Analyst 2 » 2014-02-20 14:47:59

Hi Donitz, since the OWC-generator in WACA works with a pre-defined number of speed-bins I cannot rule out that the last speed-bin is treated in a little bit special way.

Board footer

Powered by FluxBB

[ Generated in 0.017 seconds, 11 queries executed - Memory usage: 672.9 KiB (Peak: 706.3 KiB) ]