You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have checked that this issue has not already been reported.
I have checked that this bug exists on the latest version of hydomt_fiat.
Reproducible Example
When using new composite areas that need to be divided to fall in different aggregation areas, the resulting splitted polygons have the values for ground elevation and ground floor height of the original polygons extents.
Current behaviour
When using new composite areas that need to be divided to fall in different aggregation areas, the resulting splitted polygons have the values for ground elevation and ground floor height of the original polygons extents and not the splitted ones:
The splitted polygons should have their individual ground elevation and ground floor height be calculated. This means that this part should be moved earlier in the code:
hydomt_fiat version checks
Reproducible Example
When using new composite areas that need to be divided to fall in different aggregation areas, the resulting splitted polygons have the values for ground elevation and ground floor height of the original polygons extents.
Current behaviour
When using new composite areas that need to be divided to fall in different aggregation areas, the resulting splitted polygons have the values for ground elevation and ground floor height of the original polygons extents and not the splitted ones:
The split part takes place here:
hydromt_fiat/hydromt_fiat/workflows/exposure_vector.py
Lines 1453 to 1459 in 7ca85e8
Desired behaviour
The splitted polygons should have their individual ground elevation and ground floor height be calculated. This means that this part should be moved earlier in the code:
hydromt_fiat/hydromt_fiat/workflows/exposure_vector.py
Lines 1453 to 1459 in 7ca85e8
Task list
Additional context
No response
The text was updated successfully, but these errors were encountered: