[Thread Prev][Thread Next][Index]

Re: [ferret_users] How to LIST all data points



Hi Diane,

Ferret automatically "strides" the data when doing a text listing, making it convenient to just get a look at the numbers without the listing wrapping around on the screen.  The qualifier LIST/WIDTH=  lets you set the length of the row, in order to write out all of the data, so just make that big enough to list all the data.  You could also look at setting the precision used, though the default precision already gives only a few digits of precision.

Another kind of listing that's often more useful is one with longitude, latitude, variable (in the case of a 2-D variable).  Define 2-D variables which are the longitude at each x,y location and latitude at each x,y location:

yes? let xlon = x[gx=var] + 0*y[gy=var]
yes? let ylat = 0*x[gx=var] + y[gy=var]

then unravel these into 1-D lists, giving them titles and units so the file gets a useful header,

yes? let/units=degrees_east/title="longitude" xpts = xsequence(xlon)
yes? let/units=degrees_north/title="latitude" ypts = xsequence(ylat)
yes? let/like=var var_xy = xsequence(var)

yes? list/norow/clobber/file=output.dat xpts, ypts, var_xy

Similar things can be done to unravel grids with more dimensions.


On 6/5/2019 7:31 AM, Dianne Deauna wrote:
Hello everyone,

I was trying to extract section data from a gridded netcdf file for plotting and also to get raw data. However when I use LIST, it only displays the data points for every other longitude/latitude on the section. Is there a limit to the number of points which Ferret can display? Or is there a command to make sure that it displays data for all points?

Would appreciate any suggestions. Thank you very much!

--
Josephine Dianne L. Deauna
Graduate student
School of the Earth, Ocean and Environment
University of South Carolina USA
--
Ansley Manke
NOAA/PMEL Science Data Integration Group
7600 Sand Point Way NE
206-526-6246

[Thread Prev][Thread Next][Index]
Contact Us
Dept of Commerce / NOAA / OAR / PMEL / Ferret

Privacy Policy | Disclaimer | Accessibility Statement