[Thread Prev][Thread Next][Index]
[ferret_users] Keeping var attributes and type from data access via OPeNDAP
Hi,
I'm rebuilding a database of a local subset of Pathfinder SST data.
To save space NODC uses short integers to store the SST data and I'm
also willing to do that on my local subset. I used the attached script
to check if the variable attributes were being saved in my local file as
in the original.
Apparently, ferret automatically offsets the data and does not store the
add_offset attribute in the local file. When I make a plot of the
difference between the local and the original variable I see that it is
less than the scale factor so it's not a problem but still it a bit
disturbing not being able to save a subset exactly as in the original.
I've already addressed this issue before and would like make sure I'm
not missing any new ferret commands to handle var attributes.
Any hints will be appreciated.
Cheers,
Paulo
P.S. I take this opportunity to point out that there is a typo error in
the manual, sec 3.1.8.7
------------------------------------
3.1.8.7 Packed data in NetCDF files
...
yes? SET ATT/OUTTYPE=input elev
Is should be SET VAR, not SET ATT, right ?
\canc mode verif
def sym ncf "19850101011910-NODC-L3C_GHRSST-SSTskin-AVHRR_Pathfinder-PFV5.2_NOAA07_G_1985001_night-v02.0-fv01.0.nc"
use "http://data.nodc.noaa.gov/thredds/dodsC/pathfinder/Version5.2/1985/($ncf)"
CANCEL MODE upcase_output
SET ATT/OUTPUT=all sea_surface_temperature
SET VAR/OUTTYPE=input sea_surface_temperature
save/file=nodc_pathf_WIberia.cdf/clobber/x=-16:-5/y=32:44\
sea_surface_temperature
say '----------------------------------------------------------------------'
sp ncdump -h nodc_pathf_WIberia.cdf | grep -A10 sea_surface_temperature\(time
say '----------------------------------------------------------------------'
!sp wget http://data.nodc.noaa.gov/pathfinder/Version5.2/1985/($ncf)
sp ncdump -h ($ncf) | grep -A10 sea_surface_temperature\(time
[Thread Prev][Thread Next][Index]
Contact Us
Dept of Commerce /
NOAA /
OAR /
PMEL /
Ferret
Privacy Policy | Disclaimer | Accessibility Statement