ERA5-Land data grid mismatch on recently downloaded data vs older data

Over the last ~month I re-downloaded ERA5-Land t2m data (hourly 1950-2023). The data have the same number of lat/lon grid points as the data I downloaded a 1-1.5 years ago, but the data grids don’t match any more. For example, the ERA5-Land land-sea mask no longer matches, nor do any of the other nc files I regridded to match the old ERA5-Land data I downloaded in 2023.
Has there been a change to the lat/lon grid structure or formatting in the ERA5-Land data?

Can you give the numbers of the displacement? What’s the origin? I’d like to check on my side too

Are the files netcdfs? I think this might have to do with the change in the grib/netcdf converter from grib_to_netcdf to cfgrib, it seems the lat/lon coordinates are not well preserved (-89.7999999999983 instead of -89.8 for instance)

Yes both files are netcdf.

Where are you seeing the discrepancy in lat/lon? I have exact 0.25 intervals in both datasets .

I was looking at the 0.1º data, so it might be a different issue. Anyway, with the change in converter, discrepancies in the resulting netcdfs are to be expected:

It is important to understand that given the intrinsic differences between GRIB and netCDF there is not a one size fits all approach when converting GRIB to netCDF. We aim to provide users with some sensible default options, but given the code used to perform the conversion is open source and documented it is possible for users to fine tune the conversion to their requirements if needed.

https://confluence.ecmwf.int/display/CKB/GRIB+to+netCDF+conversion+on+new+CDS+and+ADS+systems#GRIBtonetCDFconversiononnewCDSandADSsystems-Whywearechanging

Hi all, thanks for the replies! I am also looking at the 0.1 degree data as Matt indicated.
Yes, the files are netcdf (nc) files that I downloaded both times.
If the GRIB to nc converter varies this would make sense.

I output the latitude values in Xarray for the older nc t2m data from 2023:
[ 90. , 89.9, 89.8, …, -89.8, -89.9, -90. ]

And for the newer t2m zipped nc data I downloaded in the last few months:
[ 90. , 89.9, 89.8, …, -89.8, -89.9, -90. ]

So I don’t see an immediate difference, but if I calculate the difference in latitude values and print that, I do see tiny differences:
[ 0.00000000e+00, -1.52587890e-06, -3.05175780e-06, …,
3.05175948e-06, 1.52588058e-06, 0.00000000e+00]