All Activity

Sure, everything is possible. I have reached out to via DM to see if this is something we could collaborate on.

Let's say you have 100TB of data. You split it into 1000 geographical tiles and then compress it and put it into a torrent. Downloading 10GB is manageable on todays broadband connections.

You could split the timeseries data into geographical tiles. Torrenting is a very good way to share big files too.

Thank you for your suggestion, we have not seen academic torrents before. However, I am not sure that it would be a good set for the New European Wind Atlas dataset. Our dataset would almost double the amount of data available via that platform. It is also unclear to me how users would be able to subset the data so they could get what they are interested in and not the full dataset. We are almost finished repackaging the data into a format that should allow users to download around 10 years of data for a single point. We are doing performance testing to determine the new limits for this repackaged data. It should launch early next year.

Are you still having this issue? I am not able to replicate it. If I select say downloading 2005-01-01 for Wind Speed at a point near Copenhagen, I get the NetCDF file for that point.

Support is telling me that i shouldn't request data longer than 6 months. This is obviously useless. Everybody wants long term data. Pls put the whole archive online through torrents. https://academictorrents.com/ Like so.

Yes, in Brazil we sometimes need to. It's an unusual situation, but in some projects we have very large areas available for projects. I've even tried joining two shapefiles downloaded via wordcover, but they don't fit together perfectly

same

Yes, there was recently another case that had this problem. The solution there was like this:

Hello and thank you for this great plugin. I am using the plugin and for the CORINE dataset, I don't have any problems. However, when I use WorldCover, I receive the following error. Could you please help, me to solve this issue? Many thanks GDAL command output: Creating output C:/Users/jama/AppData/Local/Temp/processing_EIXjaH/0a5161e0f997460a8de8b01247b4f4b6/OUTPUT.xtf of format Interlis 2. Traceback (most recent call last): File "C:\PROGRA~1\QGIS33~1.11\apps\Python312\Lib\site-packages\osgeo_utils\auxiliary\gdal_argparse.py", line 229, in main self.doit(**kwargs) File "C:\PROGRA~1\QGIS33~1.11\apps\Python312\Lib\site-packages\osgeo_utils\gdal_polygonize.py", line 355, in doit return gdal_polygonize(**kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\PROGRA~1\QGIS33~1.11\apps\Python312\Lib\site-packages\osgeo_utils\auxiliary\util.py", line 62, in enable_exceptions_wrapper return fun(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^ File "C:\PROGRA~1\QGIS33~1.11\apps\Python312\Lib\site-packages\osgeo_utils\gdal_polygonize.py", line 149, in gdal_polygonize dst_ds = drv.CreateDataSource(dst_filename) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\PROGRA~1\QGIS33~1.11\apps\Python312\Lib\site-packages\osgeo\ogr.py", line 723, in CreateDataSource return _ogr.Driver_CreateDataSource(self, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ RuntimeError: ILI2 Create(): model file not specified in destination filename. Process returned error code 1 Results: {'OUTPUT': 'C:/Users/jama/AppData/Local/Temp/processing_EIXjaH/0a5161e0f997460a8de8b01247b4f4b6/OUTPUT.xtf'} Clipping to bounding box... Unable to execute algorithm Could not load source layer for INPUT: C:/Users/jama/AppData/Local/Temp/processing_EIXjaH/0a5161e0f997460a8de8b01247b4f4b6/OUTPUT.xtf not found Unable to execute algorithm Could not load source layer for INPUT: C:/Users/jama/AppData/Local/Temp/processing_EIXjaH/0a5161e0f997460a8de8b01247b4f4b6/OUTPUT.xtf not found Execution failed after 14.35 seconds Loading resulting layers Algorithm 'Get WorldCover landcover polygons' finished

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.