Mashing two dimensions into one definitely isn't CF-compliant! Typically I would expect to see latitude and longitude dimensions whose values take on the late/lon values for the grid. I should say here that most NetCDF visualisation software ( NCview, Panoply, etc.) is built to take in CF-compliant NetCDF files.
With a half-degree grid, 360 values in y and 720 in x sounds like your grid. I think we're gonna need to take a closer look at some of the values in these variables. Hi Sounds like you have a pretty interesting NetCDF on your hands When I try to get latitude and longitude separately, they each have two dimensions, "x" or longitude -720 rows and "y" or latitude -360 columns. Note2: land mask in file: WFD-land-lat-long-z.ncįor example, if I want to extract data for a specific area: latitude (25 to 45 degree north), longitude (34 to 52 degree west), which rows of data should I consider? Currently, when using ncvar_get() function to get the precipitation data, it has two dimensions, "land" -67420 rows and "tstep" -31 columns.
I don't know if the land is row-wise or column-wise from latitude and longitude alone? I can not attach the netcdf file, but I copy the relevant description here.
The "land" is latitude-longitude combination every half-degree spacing, while the "tstep" is day ID (which is from 1 to 31). For example, when reading precipitation data, there are two dimensions: "land" and "tstep". I tried to read precipitation, latitude and longitude data, but could not get it. This is a netcdf file with daily precipitation data in January over the globe.
0 kommentar(er)
