Tool Name: nagg
Syntax:
nagg [-h | --help]
nagg [-n
number] [-t list | -l file] [-g criterion] [-S] [-A seconds] [-d directory] [-O origin] [-D domain] INPUT…
Purpose:
nagg is NPP granule aggregation and packaging utility.
Description:
The command line utility nagg is the NPP granule
aggregation utility for grouping NPP data record granules into aggregate and
package files.
Aggregates include time contiguous, and gap-filled series of
the same type of granules together in the same file. Packages include
different, but related type granule aggregates with same temporal and spatial
extent together in the same file.
Input parameter INPUT is a list of one or more files.
Output of nagg is a file or set of files named according to the NPP file
naming convention. Output files are alignment with the bucket boundary as
defined in the Control Book. Fill
granules are added when there are no granules available for "slots"
in a bucket. Leading and trailing fill
granules are not generated for the first and last output files respectively. Therefore,
first and last output files may be partial files that consist of fewer granules
than requested.
nagg is non-destructive. It
will not overwrite existing files.
Geolocation file names can be approximate such that only the
beginning parts up to creation date are matched. E.g., if the sensor data file defines its
geolocation file as:
“GMTCO_npp_d20100906_t0701368_e0703013_b00004_c20111024161933653314_noaa_ops.h5”,
the tool will accept any file
matching the following pattern and will use the one with the latest creation timestamp.
GMTCO_npp_d20100906_t0701368_e0703013_b00004_c*.h5
Other considerations:
1. nagg can deaggregate files by setting -n 1 and operating on aggregate files.
2. nagg can aggregate files by setting -n N and operating on a directory of single granule files.
3.
nagg
can reaggregate by setting -n N
to a number different from the number of granules in the input files.
Options and Parameters:
|
-n, --number N The number of granules in each aggregate file; must be greater than zero. If not specified, default is 1 (single granule files). -t, --type list list specifies a comma
separated list of NPP record type mnemonics. Unless -S is specified the granule
types will be packaged together. Types must be compatible to be packaged
together. (Use -h
to list valid package groupings). -l, --like file Package like the example file in number or type
list. Options on the command line override the example. If both -l and -t are omitted, then the first NPP data product file encountered will be
used as the example file. -g criterion criterion is the criterion for searching the Geolocation granules no | 0: aggregate product files with no geolocation granules yes | 1: allow approximate matching of geolocation input filenames (default) strict | 2: require exact matching of geolocation input filenames (-g
no is to be supported in future implementation.) -A, --aggregate seconds (To be supported in future implementation) The number of seconds in each aggregate file. Aggregation Size is a fixed number of granules per file equal to seconds divided by the period of the granule rounded up to the next integer number of granules If –l, -t, –n and –A are omitted, then the first NPP data product file encountered will be used to determine the –t list and –n number. -S, --simple Simple aggregates are produced. Each type is packaged separately. -d, --directory directory Directory where the output files
should be placed. Default
is present working directory. -O, --origin origin The origin identifier, a four-character string in the output filename. Only the first four characters will be used. If less than four characters, the origin will be pre-pended with the character “X”. Default is “XXXX”. -D, --domain domain The domain identifier, a three-character string in the output filename. Only the first three characters will be used. If less than three characters, the origin will be pre-pended with the character “x”. Default is “XXX”. -h, --help Prints command syntax; also lists
valid types and packaging groupings. |
Exit Status:
|
0 |
Succeeded. |
|
>0 |
An error occurred. |
Version: 1.0.1-beta1
Last revised: 2012/3/2