On 30/04/2020 18:55, J Conrado wrote:
Please,
Please can someone explain to me why I have this difference: in Python
int16 SST(y, x) and with ncdump -h short SST(y, x)
Presumably on your computer a (signed) short integer is a (signed)
sixteen bit integer. That's rather unhelpful of ncdump.
Hi,
I read my netcdf data and I did:
print(f)
print("f.variables[SST] ",f.variables["SST"])
and I had:
f.variables[SST]
int16 SST(y, x)
_FillValue: -1
long_name: ABI L2+ Sea Surface (Skin) Temperature
standard_name: sea_surface_skin_temperature
_Unsigned: true
Dear Members,
Is there a way to get the time:origin attribute from a netcdf
file as string using the Python netcdf?
with best regards,
Sudheer
--
http://mail.python.org/mailman/listinfo/python-list
On Wed, Jun 5, 2013 at 9:07 PM, Sudheer Joseph sjo.in...@gmail.com wrote:
Dear Members,
Is there a way to get the time:origin attribute from a
netcdf file as string using the Python netcdf?
Attributes of the NetCDF file and attributes of each of the variables can
the time:origin attribute from a
netcdf file as string using the Python netcdf?
Attributes of the NetCDF file and attributes of each of the variables can
be accessed via the dot-operator, as per standard Python.
For instance, suppose that your NetCDF file has a Conventions attribute,
you can access
