Generate Global Land Cover Test Site tapes
Generate Global Land Cover Test Site tapes for MSS, TM, and AVHRR data. Tapes, tape labels, and mappers are generated and tape verification is performed.
- HEADDIR
- Header file directory. The name of the directory in which the MSS, TM, and AVHRR header files exist. This directory specification should NOT include the site, only the general directory below which many sites may reside.
- DATADIR
- Data file directory. The name of the directory in which the "mss", "tm", and "avhrr" sub-directories exist. Each sub-directory must contains it's respective data files.
- SITE
- Site name. The name of the site for which the archive tapes are to be generated.
- NAME
- User name. The user name as it is to appear on the generated tape labels.
- LOGFILE
- Log file. The name of the file to which processing messages will be written. An extension of ;log is assumed.
- DELFLG(NO)
- Delete flag. Flag indicating whether to delete data files below DATADIR once a data set has been successfully written to tape. Header and ancillary files within HEADDIR are never deleted.
= YES: Delete data files = NO : Do not delete data files
- STACKFLG(YES)
- Stacker flag. If STACKFLG=YES, it is assumed that 10 ANSI labeled tapes have been loaded into an automatic tape stacker. If 10 tapes is not enough to process all of the data, the operator will be prompted to reload the stacker. If STACKFLG=NO, each ANSI labeled output tape must be individually loaded.
= YES: Stacker is being used = NO : Do not use stacker
The directory [data.head.kop019na]" will be examined for header files. The header files are read to determine which MSS, TM, and AVHRR data is to be written to tape. Once a data set has been successfully copied to tape and verified, it will be deleted (since DELFLG=YES). The data files are located in "[mydata.kop019na.tm]", "[mydata.kop019na.mss]", and "[mydata.kop019na.avhrr]". The automatic tape stacker will not be used.
Process AVHRR, MSS, and TM data per data set. Each data set is defined as the amount of data that will fit on one CD (about 600 megabytes). A data set may span output tapes, but an individual file will never span an output tape. A header file will exist for each data set to be processed (See User Note 1). The header file is read to extract the information required to generate the output tapes. The output tapes are generated (see User Notes 3, 4, and 5 for the tape format of each data set). Once an output tape and tape label are generated, a mapper listing is generated for the output tape just created (see User Note 2). The mapper listing is compared to the header file information to verify that the output tape was successfully generated.
kop019na;mss;hdr1 MSS data, 1st data set kop019na;mss;hdr2 MSS data, 2nd data set kop019na;tm;hdr1 TM data, 1st data set kop019na;tm;hdr2 TM data, 2nd data set kop019na;tm;hdr3 TM data, 3rd data set kop019na;avhrr;hdr1 AVHRR data, 1st data set kop019na;avhrr;hdr2 AVHRR data, 2nd data set kop019na;avhrr;hdr3 AVHRR data, 3rd data set kop019na;doc AVHRR ancillary data kop019na;gif AVHRR GIF kop019na_dem;img AVHRR DEMFor each header file not found, a warning message will be logged.
Header for AVHRR data set #1 Ancillary data file GIF file DEM file AVHRR scenes for period 1-12 Header for AVHRR data set #2 AVHRR scenes for period 13-24 Header for AVHRR data set #3 AVHRR scenes for period 25-36More than one tape may be required to contain a data set, depending on the number of AVHRR scenes. A data set is defined as the amount of data that will fit on one CD (about 600 megabytes). One scene will never span an output tape.
Header for MSS data set #1 (output tape #1) MSS scenes 1 and 2 MSS scenes 3 and 4 (output tape #2) Header for MSS data set #2 (output tape #3) MSS scenes 5 and 6 MSS scenes 7 and 8 (output tape #4)If not all 8 MSS scenes are available, the above format will be appropriately truncated.
Header for TM data set #1 (output tape #1) TM scene #1, bands 1-4 TM scene #1, bands 5-7 (output tape #2) Header for TM data set #2 (output tape #3) TM scene #2, bands 1-4 TM scene #2, bands 5-7 (output tape #4) Header for TM data set #3 (output tape #5) TM scene #3, bands 1-4 TM scene #3, bands 5-7 (output tape #6)If not all 3 TM scenes are available, the above format will be appropriately truncated.
For MSS data files (1 scene): SITE_DATE_mssBAND;img Example: kop019na_050674_mss1;img kop019na_050674_mss2;img kop019na_050674_mss3;img kop019na_050674_mss4;img For TM data files (1 scene): SITE_DATE_tmBAND;img Example: kop019na_090784_tm1;img kop019na_090784_tm2;img kop019na_090784_tm3;img kop019na_090784_tm4;img kop019na_090784_tm5;img kop019na_090784_tm6;img kop019na_090784_tm7;img For AVHRR data files (1 scene): SCENEID_SITE_final;img Example: ao11042192200808_kop019na_final;img