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
It is a bit tricky where this issue should land. It is indeed about meshkernel(py), but the issue lays in the fact that meshkernel does not support z-values at the moment. Hydrolib-core does have z-values, but these are the only properties that have to be carried around next to the meshkernel instance. They cannot be clipped with the meshkernel algorithm at the moment. I think the best way to fix this properly is to add z-values in meshkernel(py), but I am not sure if that is within the scope. Alternatively, we could do some interpolation of z-values in hydrolib core, since the new nodes/faces will be on the exact same locations as the old ones, this will probably result in identical values, but it would also require refactorings in other functions which would be more work than adding it in meshkernel. I will discuss this with @lucacarniato
Describe the bug
When clipping a netcdf over a geometrylist the
mesh2d_node_x
,mesh2d_node_y
are clipped, butmesh2d_node_z
isn'tTo Reproduce
Steps to reproduce the behavior:
mesh_node2d_x
,mesh_node2d_y
andmesh_node2d_z
before and aftermesh2d_delete
:Expected behavior
A length of
mesh2d_node_z
of 226161 as aremesh2d_node_x
andmesh2d_node_y
.Screenshots
We do think deletion of x and y is as expected. Running
network.plot()
after executing the script above gives a plausible result:Version info (please complete the following information):
The text was updated successfully, but these errors were encountered: