Usage of aug tool:

.	./aug_eos5 <file>
This is the default case. For swath files, augmentation tool fills
all dimension scales with zero. For TES grid files, it fills XDim and YDim 
with the values of Latitude and Longitude in data fields respectively. 
For other grid files, it calculates XDim and YDim automatically. 
Other dimension scales in grid files are filled with zero.  

.	./aug_eos5 -i <file> 
All dimension scales created by augmentation tool are filled with 
natural numbers except XDim and YDim in grid files. XDim and YDim 
are filled the same way as the default case.

.	./aug_eos5 -f <mapping file> <file>
The layout of mapping file is as follows:
 
0|1|2[*] <dimension> <geolocation field>|<file>

For option 0, the value of third column is classified as geolocation field. 
The values of geolocation field are used to fill the corresponding 
dimension scale.

For option 1, the value of third column is classified as file 
containing the values which are used to fill the corresponding dimension scale. 
Its layout is as follows:

11.111
12.22
...

It should be noted that the number of values in the file must be 
equal to the corresponding dimension size, and XDim and YDim in grid files 
are only allowed to use option 1.

For option 2, the dimension scale is filled with natural numbers. 
The denotation* is optional. If it is chosen, the remaining dimension scales, 
which are not listed in mapping file, are filled with natural numbers as well; 
otherwise they are not considered as netCDF variable although they are 
netCDF dimension scales. In such case, not only will the denotation * 
save input time, it will also reduce typos. 


Examples:
If there are three dimesions (nTimes, nLevels, and nTimesTotal) in a file,

        2* nTimes #all there use natural numbers
or
        0 nTimes Time 	   #use geolocation field
        0 nLevels Pressure #use geolocation field
			   #no instruction for nTimesTotal, 
			   #so it is not a netCDF variable
	If using check_c to validate any data field relating to nTimesTotal,
	check_c will report "NetCDF: Variable not found"  
or
        0 nTimes Time       #use geolocation field
        1 nLevels data_file #use data file
        2 nTimesTotal       #use natural numbers
or
        0 nTimes Time #use geolocation field
        2* nLevels    #both nLevels and nTimeTotal use natural numbers


Option 1 and 2 are new features added in Aug Tool 2.0.

Multiple mapping choices for file containing more than one grid or swath 
is added as another new feature in Aug Tool 2.0. For example, if there are 
two swaths, BrO and BrO column, both have nTimes dimension. For BrO option 0
is desired; for BrO column option 2 is desired. Mapping file could be 
written as follows: 

	swath name: BrO
	0 nTimes Time #use geolocation field
	swath name: BrO column
	2 nTimes #use natural numbers
 
For multiple grids, the mapping file could be written as follows:

	grid name: NadirDayGrid
	2 nLevels #use natural numbers
	grid name: NadirNightGrid
	0 nLevels Pressure # use data field
or
	grid name: NadirDayGrid
	2 nLevels #use natural numbers
	grid name: NadirNightGrid
	#no instruction for nLevels, so it is not a netCDF variable

It should be noted that in both cases all of the swath or grid names 
must be present in mapping file.