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
This issue is a direct result of the dimension name mangling performed by iris.save.
In this particular case, the mesh_dim_name is 'dim0', and the cf_var.dimensions are ('time_0', 'dim0_0'). Hence the traceback from cf_var.dimensions.index.
🐛 Bug Report
Given two valid CF-UGRID netCDF mesh files, the first of which has the following netCDF
dimensions
:The second of which has the following netCDF
dimensions
:I easily can use
iris
to load these files into as single cube list and then save to a single combined netCDF file as follows:Inspecting the
dimensions
ofcombined.nc
gives:😢
Consequently, attempting to then load
combined.nc
results in the following traceback:This issue is a direct result of the dimension name mangling performed by
iris.save
.In this particular case, the
mesh_dim_name
is'dim0'
, and thecf_var.dimensions
are('time_0', 'dim0_0')
. Hence the traceback fromcf_var.dimensions.index
.As a quick temporary workaround, I can monkey-patch iris.experimental.ugrid.load._build_mesh_coords with this weak-contract:
However, clearly we should address this issue in a more robust way.
Note that, I can supply data on request to recreate this issue.
The text was updated successfully, but these errors were encountered: