Jump to content

All Activity

This stream auto-updates

  1. Yesterday
  2. Reporting or creating reports with WAT (Web Automation Tool) can be a game-changer for managing your data effectively. This tool automates the collection and presentation of data, making it easier to generate comprehensive reports. If you're juggling multiple tasks and thinking, "I need someone to do my management assignment," incorporating WAT can save you significant time and effort. It's designed to streamline processes, allowing you to focus on analysis and decision-making.
  3. Engaging a management assignment helper can significantly enhance your educational journey, particularly within the realm of business studies. These experts not only provide invaluable insights into complex management theories but also assist in applying these concepts to real-world scenarios. This practical approach to learning not only solidifies your understanding but also prepares you for future professional challenges. By leveraging the expertise of a management assignment helper, you're not just completing assignments; you're building a foundation for success in your career.
  4. Last week
  5. Earlier
  6. Hello! I used to think that WAsP always gives output in the form of annual production (AEP), but I've been told that it is possible to proccess that output and obtain an hourly profile of production. I know that this is a post-WAsP calculation but I could really used some help either to calculate month hourly distribution (24x12 hours) or yearly hourly distribution (8760 hours). Thank you!
  7. Hi, I'm not sure you can do this, but you would need to check with WindPro/EMD. https://www.emd-international.com/windpro/support/ WindPro uses WAsP to do some modelling calculations, but I don't know if there is a way to import files of calculated results which have been generated by WAsP. This is something that was possible in the older version of WindFarmer, but the newer WindFarmer-Analyst performs calculations directly. Duncan.
  8. Hello, I would like to know how to proceed in WindPro to be able to view and use a .WRG file exported by WAsP. Could you help me? Thank you!
  9. The issue is that the time-series data is a raster in the projected space, but not in the lat/lon space. Therefore, the XLAT/XLON have to be two-dimensional, as the values at each point depends on both the x and y dimensions. The approach from David above will give you a non-raster dataset in the new projection. If you want to get a raster back in the new projection, you can use the Windkit tool we have developed, which will "warp" the data from one projection to another, keeping the grid spacing approximately the same. When warping, you will be performing an interpolation, nearest neighbor by default. import windkit as wk import xarray as xr ds = xr.open_dataset("mesotimeseries-Area 2.nc") ds ds_warped = wk.spatial.warp(ds, 3035) ds_warped
  10. Hello, Rogier It worked!!! Thank you very much for your help! Best regards, Guilherme
  11. Hi Dimitri, Is the problem you're seeing due to the change in the coordinate reference that is being used between the (south_north, west_east) indices when compared to (XLAT, XLON)? I've come across these issues when trying to import the NEWA download inputs into other software which requires a standard CRS (converting NEWA downloads into .wrg formats for example). (south_north, west_east) falls on a nice neat grid, with in your situation, 7 columns and 7 rows, but when XLAT/XLON are plotted you don't get neat columns and rows due to the warping resulting in 49 unique pairs (one for each point in the grid). It means that for coordinate transformation then I've had to loop through per point using something similar to below. def ts_coordinate_converter(lon, lat): crs_wkt = 'PROJCRS["unknown",BASEGEOGCRS["unknown",DATUM["unknown",ELLIPSOID["unknown",6370000,0,LENGTHUNIT["metre",1,ID["EPSG",9001]]]],PRIMEM["Greenwich",0,ANGLEUNIT["degree",0.0174532925199433],ID["EPSG",8901]]],CONVERSION["unknown",METHOD["Lambert Conic Conformal (2SP)",ID["EPSG",9802]],PARAMETER["Latitude of false origin",54,ANGLEUNIT["degree",0.0174532925199433],ID["EPSG",8821]],PARAMETER["Longitude of false origin",15,ANGLEUNIT["degree",0.0174532925199433],ID["EPSG",8822]],PARAMETER["Latitude of 1st standard parallel",30,ANGLEUNIT["degree",0.0174532925199433],ID["EPSG",8823]],PARAMETER["Latitude of 2nd standard parallel",60,ANGLEUNIT["degree",0.0174532925199433],ID["EPSG",8824]],PARAMETER["Easting at false origin",0,LENGTHUNIT["metre",1],ID["EPSG",8826]],PARAMETER["Northing at false origin",0,LENGTHUNIT["metre",1],ID["EPSG",8827]]],CS[Cartesian,2],AXIS["(E)",east,ORDER[1],LENGTHUNIT["metre",1,ID["EPSG",9001]]],AXIS["(N)",north,ORDER[2],LENGTHUNIT["metre",1,ID["EPSG",9001]]]]' custom_transformer = pyproj.Transformer.from_crs( pyproj.CRS.from_string(crs_wkt), pyproj.CRS.from_epsg(3035), always_xy=True ) x, y = custom_transformer.transform(lon, lat) return (x, y)
  12. Hi ! I have a question related to NEWA's XLAT/XLON parameters, which I think is relative to this post: When I select an area and download time series for it (eg: t2, U100, Dir100, etc), I see that the .nc file contains 7 'south_north' and 7 'west_east' indexes that correspond (?) to 49 XLAT and 49 XLON parameters. As, David, I want to assign ie: each of the 7 e.g: U100 time-series to a valid EPSG system. I understand that I have 7 pairs (south_north, west_east) and expected to use XLAT/XLON parameters that come to 'readable' EPSG. But why do I have 49 XLATs, XLONs ? Peculiarly, when I select on NEWA just a point and download time-series, then I have 1 pair of (south_north, west_east) and 1 pair of (XLAT,XLON). I will appreciate any help !
  13. 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
  14. Dear Rogier I work with my colleague Dulce and I was also trying to run the tool you shared with us "Get Worldcover landcover polygons". I think we managed to solve the problem indicated previously but we are now having a different error message in our log. At first, it was showing us below message: "(...) Results: {'OUTPUT': 'C:/Users/guilherme.simoes/AppData/Local/Temp/1/processing_knVPBu/0e641317d5d64010967656d3c343bdaf/OUTPUT.gpkg'} Clipping to bounding box... Feature (562) has invalid geometry. Please fix the geometry or change the Processing setting to the "Ignore invalid input features" option. There were errors executing the algorithm. There were errors executing the algorithm. Execution failed after 5.83 seconds (...)" But, then we tried setting a CRS in UTM (with its Zone identified) but it continued showing the same message. Later we tried changing the setting in order to "ignore invalid input features" and it showed another error message: "(...) CRS is EPSG:32633 Traceback (most recent call last): File "C:/Users/guilherme.simoes/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\wasp_scripts\processing_provider\worldcover.py", line 209, in processAlgorithm if clipping_layer.crs().isGeographic(): AttributeError: 'NoneType' object has no attribute 'crs' Execution failed after 0.01 seconds (...)" Do you know what could be wrong? Thank you for your help! Guilherme.
  15. I read your post via Google translate. I suggest that you start by checking the wind resource at your site via Global Wind Atlas. If this is promising, then contact a local wind energy consultant in Turkey. Maybe (3) Ferhat Bingöl | LinkedIn, who is a professor at Izmir Institute of Technology, can guide you in the right direction.
  16. merhaba ben bireysel girişimci olarak rüzgartürbini kurulumu yapmak istiyorum ama bu konuda fazla bilgim yok sizlerden bilgi alma imkanım olurmu acaba teşekkürler
  17. Hi Rogier, That´s exactly what i was searching, thank you a lot!!
  18. Hi David, The projection, given as a proj4 string, is: '+proj=lcc +lat_1=30.0 +lat_2=60.0 +lat_0=54.0 +lon_0=15.0 +a=6370000 +b=6370000 +no_defs'
  19. The timeseries data is defined on a lambert conformal grid. The WKT of the grid can be found in the crs_wkt attribute of the crs variable of the downloaded NetCDF file. It doesn't have an EPSG as it is a custom projection defined specifcally for the NEWA mesoscale simulations.
  20. I'm getting different "south_north/west_east" coordinates when I download a .nc file for either a bbox or a timeseries download for the same area. When I download a bbox - the "south_north/west_east" appears correctly in EPSG:3035. However when I download a timeseries for the same area the "south_north/west_east" gives completely different (negative values), I've examined the .nc file of the time series and it includes the correct (desired) XLAT and XLON equivalent to the requested areas. For comparison I've downloaded a box of data (for both timeseries and the same coordinates for the bbox) using the following code: parameter_url = 'https://wps.neweuropeanwindatlas.eu/api/mesoscale-ts/v1/get-variables' data_url = 'https://wps.neweuropeanwindatlas.eu/api/mesoscale-ts/v1/get-data-bbox' params = { 'southBoundLatitude' : 50.61, 'northBoundLatitude' : 51.0, 'westBoundLongitude' : -4.17, 'eastBoundLongitude' : -3.8, 'height' : [height], 'variable' : ['WS', 'WD'], 'dt_start' : '2018-06-30T00:00:00', 'dt_stop' : '2018-12-31T23:30:00' } The coordinates that come out of this appear starting with: [-216000, -1296000] whereas they should be [3194160, 3325480] if they were in EPSG:3035. Are the time series downloads in a different EPSG from the other sources? If so what is it?
  21. 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).
  22. Rogier

    Forest height

    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.
  23. pjindent

    Forest height

    Hi, Is there an update on this issue? I am also trying to model a site in a forest. I ran into the following issues: 1. I tried downloading the GWA landcover layers directly from the WAsP Map Editor, I can see the landcover IDs assigned to the landcover change lines, however it does not save the landcover ID information in the .map format so I saved it as a .lcv.gml file. I run into the following issues: 1a. I tried to import this file into WAsP and it is "unable to restore a map from the GML file". How do I import the GWA landcover layers in WAsP? 1b. I am able to import the elevation layer as .oro.gml file into WAsP but unable to import landcover layer in .lcv.gml format 1c. Is it possible to combine landcover and orography into a single vector file? Or should I keep them as two separate files and import them separately into WAsP? 2. I found an entry that indicates that WAsP is able to read displacement height directly from landcover layer from version 12.7 onwards: https://www.wasp.dk/news/nyhed?id=735ea5a0-af89-4e78-9a2b-72d232e27b74 . 2a. There is a reference to a spider grid analysis routine - "A new spider grid analysis routine is developed to process WAsP GML land cover maps". What is this and how do I use this? 2b. There is also a reference to a table - "For each cell in the zooming grid, the fraction of the total area fi that each of a total of N land cover types in the land cover table occupies is determined and the roughness length is calculated. The displacement height is taken into account similarly to z0 and is calculated for each cell in the zooming grid." Is the conversion of ID to displacement height and roughness automatically done by WAsP or do I need to use a specific tool/module to do this? 3. Re. the orographic submodule: This section describes advanced wind flow feature like computation of wind speedups due to elevation. Do I specifically need to input a .oro.gml file in WAsP for the Terrain Analysis? Do I also need to input the lcv.gml for displacement heights to be modeled with elevation? I am at a loss to on how to do both these things (combine elevation and landcover inputs into WAsP). Any instructions would be helpful, I have gone through the online course material and I don't see any instructions on how to do this. 4. I am assuming the step to subtract displacement height to account for forest canopies is unnecessary in the current version - 12.8. Is this correct?
  24. Hi, I have WAsP 12.8 and I would like to ask if the user corrections to be applied in the WTGs positions can be imported with the site locations or in another way? I´m working with a lot of turbines and it would be really helpfull. I´ve read that for WAsP 8 there were some scripts to do this, but i haven´t found for 12.8 version. Thanks in advance!
  25. The timezone is UTC, so it is the same everywhere.
  26. We have released new versions of PyWAsP and Windkit. Both versions include breaking changes, but only a small number. The highlights of Windkit include improved interpolation routines, several improvements to the map conversion tools to create polygon data from your roughness line maps, and additional derived fields for weibull wind climates. Full release notes can be found at: https://docs.wasp.dk/windkit/release_notes.html#id1 For PyWAsP the hightlights include a bugfix to the license manager on Windows, so now this should work correctly. We have also updated the dependencies, and aim to follow the SPEC-0 versions of our Scientific Python dependencies. This means that Python 3.10 is the oldest version of Python supported with this release. You can now use WAsP CFD results files for estimating your predicted wind climate, and we have improved the performance of the AEP calculator. Full release notes are found at: https://docs.wasp.dk/pywasp/release_notes.html#id1
  1. Load more activity
×
×
  • Create New...