User's Guide

INPECON

Copy one 8 mm INPE format tape to multiple archive tape sets.

Function:

Converts one 8 mm INPE format tape to multiple two-tape archive sets. For each scene on the INPE tape, a two-tape archive set is created. The first archive tape contains LANDSAT TM bands 1, 2, and 3; the second tape contains LANDSAT TM bands 4, 5, and 7. Meta data is extracted for each scene processed and is used to maintain the database containing all LANDSAT TM scenes at the EROS Data Center.

Parameters:

STACKFLG(YES)
Stacker flag. If STACKFLG=YES, it is assumed that 10 ANSI labeled tapes have been loaded into an automatic tape stacker (or enough tapes to process the entire INPE tape, if the number of scenes on the INPE tape is known). If 10 tapes are not enough to process the entire INPE tape, 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

SKIPSCEN(--)
Scenes to skip. The sequencial number of the scene(s) to NOT process. If defaulted, all scenes on the input tape will be processed.

NFILES(--)
Number of files. The number of files to skip for the scene(s) specified in SKIPSCEN. An entry for NFILES must be made for every entry specified in SKIPSCEN. A scene in the INPE format will contain 7 files (1 header and 6 data files).

Examples:

  1. LAS> inpecon stackflg=no skipscen=2 nfiles=9

    The INPE tape will be processed without the use of a tape stacker. The operator will be prompted for an input INPE tape as well as for subsequent output archive tapes (two per scene). The second scene on the input tape will not be processed. Nine files will be skipped on the tape since the second scene is not to be processed.

Description/Algorithm:

INPE tapes are formatted as EOSAT Fast Format tapes (Version A). Multiple scenes may be stacked on one 8 mm INPE tape. Each scene consists of a 1536-byte header file followed by 6 data files, each containing one band of data. Bands 1, 2, 3, 4, 5, and 7 of LANDSAT TM data exists for each scene. The first header file on the input INPE tape is read to disk. This header file is used to generate a modified output header file for the archive tape. See the User Notes for information on the header file modifications. This modified header file is written to the archive tape. Bands 1, 2, and 3 are then copied directly from the input INPE tape to the output archive tape. A modified header file is generated for the second archive tape in this set. This header file is written to the second archive tape. Bands 4, 5, and 7 are copied directly from the input INPE tape to the output archive tape. For each tape written, a tape label is generated. For each scene processed, a meta file is generated and moved to the appropriate information management directory. This meta file is used to update the database that maintains records on all LANDSAT TM scenes at the EROS Data Center. Scenes on the INPE tape are transferred to a two-tape archive tape set until the entire INPE tape has been read.

Nonfatal Error Messages:

    None.

Fatal Error Messages:

  1. [inpecon-fatal] Fatal error encountered

    A fatal error was encountered during processing. The error message that is displayed immediately preceding this message is the specific error that was encountered.

  2. [inpehdr-fatal] Fatal error encountered

    A fatal error was encountered during processing. The error message that is displayed immediately preceding this message is the specific error that was encountered.

  3. [inpehdr-format] Unexpected format

    A fatal error was encountered while reading the header file. Ensure the header file has not been corrupted.

  4. [inpemeta-fatal] Fatal error encountered

    A fatal error was encountered during processing. The error message that is displayed immediately preceding this message is the specific error that was encountered.

  5. [inpemeta-format] Unexpected format

    A fatal error was encountered while reading the header file. Ensure the header file has not been corrupted.

  6. [inpemeta-pass] Error passing variables to TAE

    An error occurred passing a TAE variable back to the calling PDF. Contact the system administrator.

  7. [inpemeta-tl] Insufficient number of tape locations

    An insufficient number of tape locations were entered into INPEMETA. Contact the system administrator.

  8. [inpecon-par] Unequal number of parameters entered

    The number of entries made for SKIPSCEN and NFILES must be equal. Re-enter these parameter values and retry.

User Notes:

  1. See the "EOSAT Fast Format Document For TM Digital Products, Effective March 1, 1990" for more information.

  2. All processing on disk takes place in a temporary directory below the users current directory. This temporary directory is deleted at the successful completion of processing.

  3. Both input and output tape drives must be mounted on the same hardware platform. Do not attempt to remote mount either the input or output tape drive.

  4. The following fields within the header file are modified before the header file is written to an archive tape:

    
    	1) The LANDSAT TM bands present on the archive tape
    	2) The sequential tape number within the set
    	3) The number of archive tapes within the set (2)
    

  5. The output tapes are required to be ANSI labeled tapes even though the EOSAT Fast Format tapes generated are not ANSI labeled. Each output tape is read to determine its ANSI label, then rewound and overwritten with Fast Format data. This ANSI label is used to determine the location of the tape within the tape library. The tape location, or identifier is written on the tape label. The tape identifier keyed in by the operator when responding to the mount request will be replaced by the ANSI label read from the tape.

  6. In the event of an error, the following information may be helpful. The final processing step per image is to transfer the meta data file to the data base directory. Consequently, each image with a valid meta data file in the data base directory has been successfully processed. The temporary working directory created by INPECON does not get deleted in the event of an error. This directory will probably contain header and meta data files for the image being processed when an error or user abort occurred.