I'd say this is really a data issue, but it's one the catalog is probably just expected to deal with. The ACCESS-OM2 01deg_jra55v13_ryf9091 product includes files with the following names, e.g.:
ocean_daily_3d_temp.nc
ocean_daily_3d_temp_01.nc
Stripping the time info to produce the file_id results in both sets of files being included in the same dataset. However, in this case the ocean_daily_3d_temp.nc files are on a different grid than the ocean_daily_3d_temp_01.nc files.
This type of issue is potentially also occurring in other (probably COSIMA) data products also.
It's still not an ideal solution, but it would be safer to replace dates with something (e.g. XX in this case) instead of stripping them.
Describe the bug
I'd say this is really a data issue, but it's one the catalog is probably just expected to deal with. The ACCESS-OM2
01deg_jra55v13_ryf9091product includes files with the following names, e.g.:ocean_daily_3d_temp.ncocean_daily_3d_temp_01.ncStripping the time info to produce the
file_idresults in both sets of files being included in the same dataset. However, in this case theocean_daily_3d_temp.ncfiles are on a different grid than theocean_daily_3d_temp_01.ncfiles.This type of issue is potentially also occurring in other (probably COSIMA) data products also.
It's still not an ideal solution, but it would be safer to replace dates with something (e.g. XX in this case) instead of stripping them.