This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Nan, >Date: Tue, 8 Jun 1999 22:04:51 -0600 (MDT) >From: Nan Rosenbloom <address@hidden> >Organization: UCAR/NCAR >To: Steve Emmerson <address@hidden> >Subject: Re: 19990608: sparse grids >Keywords: 199906082237.QAA09694 In the above message, you wrote: > when I refer to a sparse grid, I mean that I do not represent the > background points. I write the netcdf file in xyt format, with > the grid as an unlimited dimension, filling only data values, > leaving background points out of the file (3261 pts). > i.e., the full grid is not represented. only non-background points are > represented. To use ncview I want to _add_ the background points > and create a file of the full grid (all 5520 cells). Since so > much of the information will be background values set to missing, > I was wondering if you have a new trick to handle sparse grids > such as this. > > Here is a header from a typical file: > netcdf txT3 { > dimensions: > month = 2412 ; > grid = UNLIMITED ; // (3261 currently) > variables: > float tx(grid, month) ; > > thank you. > > nanr I understand. No, I don't have a trick for handling sparse grids such as this. If ncview can't handle them, then you might look at other application packages (e.g. VisAD). I'm afraid I don't know enough about such packages to make a recommendation. -------- Steve Emmerson <http://www.unidata.ucar.edu>