CDO

Hi Anna,

whithout the data it is not possible to say what is going wrong. Can you upload a test file, one timestep is enough.

-Karin

Hi Karin,
thank you very much.
Attached you will find a test file.
Thank you again.
Anna

Your coordinate variables x and y have the units 'deg' but it should be e.g. 'degrees_east' or rather 'degrees_north'. To change these attributes for coordinate variables you can use NCO's ncatted.

ncatted -O -a units,x,o,c,"degrees_east" -a units,y,o,c,"degrees_north" test.nc tmp.nc

and using tmp.nc as input file to remap it for example to a 1x1 degrees grid with

cdo remapbil,r360x180 tmp.nc outfile.nc

-Karin

Thank you Karin! I really did not know that deg was not fine. In my many tests I had already used nco ncatted to change name x to lon and y to lat, but I never thought about "deg".
Thank you so much.
Anna

CDO follows the CF convention: http://cfconventions.org/cf-conventions/cf-conventions.html#latitude-coordinate

Hi Ralf,
thank you for the clarification!
Regards,
Anna

nco programms support all types of netcdf file structures since they are general netcdf tool. that's why you can change almost every detail with them like adding arbitrary attributes to a data avariable. CDO in constrast concentrates on gridded data along the lines of climate and weather prediction use cases. Therefore the CF-convention is used as a basic standard for netcdf files in order to identify things like grids, vertical coordinates and different time axis. CDO also supports the WMO standard for weather prediction called GRIB.