Duncan

For me, it worked fine when I did this: MaxPower = Site.AsICalculatingHierarchyMember.CalculationByType(5).Associates.WindTurbineGenerator.SelectedPerformanceTable.PointWithHighestPower.Power MsgBox(MaxPower)

Hello, There is an object called ReportingAssistant which you can use to get the effects you want. For using a US/UK style decimal marker, there is a function called FormatValueWithPointDecimal. This was added to help making correct XML output, I think. Anyway, the full line would look like this: Builder.InsertClosedTableDataElement ReportingAssistant.FormatValueWithPointDecimal(Site.AsIWaspSite.Elevation) For rounding off the non integer part, you can use another function called NumberFormat, in which you can pass a standard VB formatting string using zero and hash markers, for example: Builder.InsertClosedTableDataElement ReportingAssistant.NumberFormat(Site.AsIWaspSite.Elevation,"0000") This will give you something like 0478 for a height like 478,23 You can use a hash for optional digits, then you'll get just 478 Builder.InsertClosedTableDataElement ReportingAssistant.NumberFormat(Site.AsIWaspSite.Elevation,"#000") Hope that helps! Duncan.

Hi "windmueller" I think you might be asking not for the HTML command, but the correct syntax in your script code to find the power on a power curve. If so, then you're almost right in your guess. It's a bit more long-winded, though. Site.AsICalculatingHierarchyMember.CalculationByType(5) .... because number 5 is for ProductionRose. Then... .Associates.WindTurbineGenerator.SelectedPerformanceTable ...then... .PointWithHighestPower.Power ... which returns a float. A long chain of properties, but I hope it gets you what you need.

No problem. We have received the files now, thanks. We will get back to you by email. Duncan.

Hello, We have responded to these questions in the other thread where you posted: http://www.wasptechnical.dk/Forum/viewtopic.php?id=844 You will receive an email from our support system asking you to clarify the question and send some example data. Duncan.

Hello Kedx3mmm, Thanks for your questions. It seems you have three separate issues here, and in fact none of them relate to the Map Editor. I can immediately clarify that if you get an OWC file, you can import them into WAsP and use them for wind resource assessment work. In the other two cases, we need more information and the problem seem specific to you. I will raise items in the support system and invite you to continue the discussion there. You will get some email messages about this. Duncan.

If you need a approximate indication of the wind resources anywhere on earth, you could try the Global Wind Atlas. http://www.globalwindatlas.com/map.html

Hello, Sorry, but we don't plan to fix this in WAsP 10 or WEng 2. WAsP 10 has been unsupported for a long time now: it's been almost three years since we released WAsP 11. Upgrades are available here https://www.wasp.dk/WAsP/WAsP-order Duncan

Please also note that the fix we made against the changes in Google Earth was only applied to WAsP version 11.

Hello WAsP users, We have made a release 'E' of WAsP 11.4 to fix a problem which some users experienced when trying to paste site locations into the hierarchy from clipboard, or to insert them from file. Please download a new installer from here http://wasptechnical.dk/Services/Redirect.aspx?token=916e0845-0235-4308-ac36-45261285d488 Sorry to all those affected. Best wishes, Duncan.

The test release is ready. The actual release will follow about 5-10 working days' time. Email if you need a test version.

Hello everyone. I'm sorry for the lack of news. We have made good progress and now have some builds which we are testing internally. It might be possible to release something soon. I'm thinking in then next week. Meanwhile, anyone interested in testing or desperate for a fix is welcome to email me and we'll add you to the beta testing group. Best wishes, Duncan.

Hi Fabien, Thanks for your post. Lots of the team are on holday just now, but your question has been noted and I hope we can give you the information you need before too long. Best wishes, Duncan.

Thanks very much for your contributions. We have decided to try to restore at least part of the functionality. You will be able to launch the displayed information in Google Earth, but there will be no way we can automatically set the camera location and do other more advanced features. I hope we can make an update in the next few weeks. Duncan.

A little update. We will use the 11.4 release to roll out a fix for offshore calculations, and we will not include any new wind farm calculations in the release. We still plan to put them into the next 11.5 release, which will likely be after the summer. Duncan.

Recent updates to Google Earth have changed things so that we can no longer manipulate the program from WAsP. This is apparently an irreversible change and they are not going to provide any alternatives. We can restore some of the functionality by working in a different way, but other parts will be harder or impossible to fix. Please, help us to decide what to do about this problem. Tell us whether and how you use the WAsP in conjunction with Google Earth. Do you ever use the sync spatial view button to launch Google Earth? If so, do you only want to view your data one time or do you care that the view and selection is synchronised between the programs? Do you use the geo-referenced image capture feature? Best wishes, Duncan.

Hello. Sorry, but please explain more. You tried to open some KML into the Map Editor? What error message did you see? What did it say? Duncan.

Hello again Vob, Well, we released 11.3 without this feature but we are planning 11.4 and we hope to put this in. Can you give us any more insight into your "other uses"? How would you take these numbers out and how would you use them afterwards? Duncan.

Hello patient friends. At last we have a public release for you which includes the extrapolation tool. Get it from here: http://wasptechnical.dk/Services/Redirect.aspx?token=beb65a1c-1341-452a-a10d-4e6e1872bb51 It will be uploaded to the WAsP Web site later today, I think. Duncan.

Hi, I have asked Ray to reply here. He's the best qualified to help. Expect something in the next 36 hours. Duncan.

Ray wrote this: The Timeout attribute allows the user to override the internal scripting timeout used by WAsP whenever a script is run. The Timeout value is specified in seconds. A default timeout value of 60 seconds will be used if the attribute is not specified. The Timeout attribute is only read when WAsP is started. This means that if you edit the attribute while WAsP is running you will need to restart WAsP before the change takes effect.

You can add an attribute to the DOM root of the script XML. Here is an example 10 second one.

Hello. We have a beta release of WAsP 11.3 which includes the tool for extrapolation. If anyone wants to try the beta, please email me. Otherwise, I think the actual release of 11.3 will happen in the next couple of weeks. Duncan.

Hi, A utility program to help is now made, and is being tested internally. If you want to send me the lib file, I can run the utility on that for you and give you an immediate (provisional) result. Duncan.

To any users who are experiencing problems like this, please try installing the latest WAsP 10 update (Feb 2014), which is build 0017. http://www.wasp.dk/Download/Software/WAsP10_Installation If that doesn't help, please contact us at wasp support.