#
# $Id: README,v 1.1.1.1 2006/03/09 01:10:56 nieves Exp $
#

These sample scripts are meant to illustrate how the GINIview program
can be invoked within DA to automate the generation, manipulation and
display of satellite images from the data files received from the
noaaport system.

INSTALLATION -
	The folder named "dasatscripts" can be placed in the main
	DA directory, so that usually it becomes
	
	c:\Program Files\DigitalAtmosphereWS\dasatscripts

	If this is not the case the scripts have to be edited
	accordingly.

	The images created are saved in the "export" subdirectory.
	If the data files must be downloaded, they get saved in the
	"data" subdirectory.

NOTES -

The scripts are divided in two groups, called "local" and "net".

1) local - The "local" type are meant to be used in the case that
the nbsp noaaport server is in the same local network as the PC
where DA is installed. In that case, the data directory of the
server is exported via samba, and then that directory is mounted
in the PC as drive "Z". The scripts do not have to download any
data since that is already in the PC's disk, so the scripts simply
execute the GINIview program directly.

2) net - The "net" scripts are for DA users that do not have
a noaaport server in the local network, or that for whatever
reason wish to download the data from a remote noaaport server.
Then prior, to the GINIview command, the scripts download the relevant
data file. The sample scripts here use my test server to download the data,
but any other could be used (and the scripts modified appropriately).

In my test server, the data files have names like

	tign01_yyyymmdd_hhmm.gini	(super national, imager visible)
	tign04_yyyymmdd_hhmm.gini	(supernational , 3.9 ir)
	tige01_yyyymmdd_hhmm.gini	(east conus, imager visible)
	tign04_yyyymmdd_hhmm.gini	(east conus, 3.9 ir)

and so on. A copy of the most recent file is named similarly, but without
the yyymmdd_hhmm; e.g.

	tign01.gini

These latest files are the ones that the sample scripts download and then
send to GINIview to produce the image file.

The scripts can be scheduled to run periodically, etc.

-
Jose F Nieves <nieves@ltp.upr.clu.edu>
Wed Mar  8 20:43:08 AST 2006


