Converts a direct-access unformatted file to an NDF DA2NDF
"Data", "Quality" or "Variance". To create a variance or quality array the NDF must already
exist. ["Data"] !) value for NOPEREC causes the size of first dimension to be used. "Data" the NDF is
modified rather than a new NDF created. It becomes the new current NDF. Unusually for an
output NDF, there is a suggested default—the current value—to facilitate the inclusion of
variance and quality arrays. [40,30,20] would create 40 columns by 30 lines by 10 bands. "_BYTE", "_WORD", "_REAL", "_INTEGER", "_INT64", "_DOUBLE", "_UBYTE",
"_UWORD" corresponding to signed byte, signed word, real, 64-bit integer, integer, double
precision, unsigned byte, and unsigned word respectively. See SUN/92 for further details. An
unambiguous abbreviation may be given. TYPE is ignored when COMP = "Quality" since the
QUALITY component must comprise unsigned bytes (equivalent to TYPE = "_UBYTE") to be a
valid NDF. The suggested default is the current value. ["_REAL"] ngc253.dat to the NDF called ngc253. The NDF is two-dimensional: 100 elements in x by 60
in y. Its data array has type _REAL. The data records each have 8 real values. ngc253q.dat to an existing NDF called ngc253 (such as created in the first example). The NDF is
two-dimensional: 100 elements in x by 60 in y. Its data array has type _UBYTE. The data records
each have 100 unsigned-byte values. ngc253.dat to the NDF called ngc253. The NDF has the
current shape and data type is unsigned word. The current number of values per record is used. the direct-access file’s array is written to the NDF array as selected by COMP. When the NDF is being modified, the shape of the new component must match that of the NDF. This enables more than one array (input file) to be used to form an NDF. Note that the data array must be created first to make a valid NDF. Indeed the application prevents you from doing otherwise.
Other data items such as axes are not supported, because of the direct-access file’s simple structure.