Urban Wind Field: URock v2023a - Issue with the extend of the created wind raster

[AlexandraStankulova]

Describe the bug A clear and concise description of what the bug is. After launching the Urban Wind Field calculation, UMEP succeeds in creating the Wind Field Raster file but it results with wrong extend. It results rotated and some pieces of the requered area of analysis (the one corrispoding to the area of "Raster template to use as output") are missing.

Here I add the Log data:

QGIS version: 3.34.11-Prizren QGIS code revision: 2904bcec Qt version: 5.15.13 Python version: 3.12.6 GDAL version: 3.9.2 GEOS version: 3.12.2-CAPI-1.18.2 PROJ version: Rel. 9.4.0, March 1st, 2024 PDAL version: 2.6.3 (git-version: b5523a) Algorithm started at: 2024-11-20T11:19:31 Algorithm 'Urban Wind Field: URock v2023a' starting… Input parameters: { 'ATTENUATION_FIELD' : '', 'BUILDINGS' : 'D:/University/PHD/02_ICARUS/GIS/QGIS_PROJECT/PreparationData_Wind/BuildingFootprint/N1_BuildingFootprint.shp', 'HEIGHT_FIELD_BUILD' : 'UN_VOL_AV', 'HORIZONTAL_RESOLUTION' : 5, 'INPUT_PROFILE_FILE' : '', 'INPUT_PROFILE_TYPE' : 0, 'INPUT_WIND_DIRECTION' : 142, 'INPUT_WIND_HEIGHT' : 10, 'INPUT_WIND_SPEED' : 0.7, 'LOAD_OUTPUT' : True, 'OUTPUT_FILENAME' : 'urock_output', 'RASTER_OUTPUT' : 'D:/University/PHD/02_ICARUS/GIS/QGIS_PROJECT/PreparationData_Wind/DSM/N1_DSM.tif', 'SAVE_NETCDF' : True, 'SAVE_RASTER' : True, 'SAVE_VECTOR' : True, 'UROCK_OUTPUT' : 'D:\University\PHD\02_ICARUS\GIS\QGIS_PROJECT\OutputData\URock_Wind Raster\Wind Raster_9\N1', 'VEGETATION' : None, 'VEGETATION_CROWN_BASE_HEIGHT' : '', 'VEGETATION_CROWN_TOP_HEIGHT' : '', 'VERTICAL_RESOLUTION' : 5, 'WIND_HEIGHT' : '1.5' }

Writing settings for this model run to specified output folder (Filename: RunInfoURock_YYYY_DOY_HHMM.txt) Initiating algorithm Creates an H2GIS Instance and load data Creates the stacked blocks used as obstacles Rotates obstacles to the right direction and calculates geometry properties Roughness zone properties are:

• z0: 0.05299433083208913
• d: 0.1589829924962674
• Hr: 5.238831747832245
• H_ob_max: 15.0
• lambda_f: 0.010115677193492125 Creates the 2D R?ckle zones Creates the 2D grid Initializes the 3D grid within R?ckle zones Deals with building zones superimposition Deals with vegetation zones superimposition Initialize the 3D wind in the grid Rasterize the data Apply the wind solver equations Iteration 1 (max 500) - eps = 0.154219 >= 0.0001

Iteration 51 (max 500) - eps = 0.178511 >= 0.0001

Iteration 101 (max 500) - eps = 0.118241 >= 0.0001

Iteration 151 (max 500) - eps = 0.079372 >= 0.0001

Iteration 201 (max 500) - eps = 0.052431 >= 0.0001

Iteration 251 (max 500) - eps = 0.035147 >= 0.0001

Iteration 301 (max 500) - eps = 0.022968 >= 0.0001

Iteration 351 (max 500) - eps = 0.014954 >= 0.0001

Iteration 401 (max 500) - eps = 0.009638 >= 0.0001

Iteration 451 (max 500) - eps = 0.006131 >= 0.0001

Execution completed in 502.90 seconds (8 minutes 23 seconds) Results: {'OUTPUT_FILENAME': 'urock_output', 'UROCK_OUTPUT': 'D:\University\PHD\02_ICARUS\GIS\QGIS_PROJECT\OutputData\URock_Wind ' 'Raster\Wind Raster_9\N1'}

Loading resulting layers Algorithm 'Urban Wind Field: URock v2023a' finished

Desktop (please complete the following information):

• OS: Windows
• QGIS Version: 3.34.11

Screenshots Here screenshot of the DSM and building polygons extend:

Here screenshot or the output (the Wind Field raster file):

[j3r3m1]

Thank you for reporting. Can you please share your data ?

[AlexandraStankulova]

Yes, definetely. Here I attach the data that I have used:

Data_WindField.zip

Thank you for the help.

[AlexandraStankulova]

And here I attach also the output raster fille that I obtained:

urock_outputWS.zip

Thank you in advance.

[j3r3m1]

OK I have also faced the error. This is solved in the new version that you can directly download from the github page as a zip.

However, several points need to be highlighted:

• you use an input raster which has the same size as the building footprint. You should have a bigger domain for the building footprint since the buildings outside your input raster might affect the wind in the smaller domain.
• in rural areas such as the one you are processing, it is better to include vegetation
• the vertical resolution of 5 is high in comparison of building height. You can have a try with 3 m and compare with your simulation at 5 meters. If you consider the difference is negligible, then keep 5. Otherwise 3 m is more appropriate (even though it will be longer to run).

Let me know if everything is fine. If so you can close the issue.