User's Guide

ARCH8MM

Utility to convert LAS images from NDF format files

Function:

Convert National LANDSAT Archive Production System (NDF) image and header files on disk to LAS.

Parameters:

Input file. The root name of the NDF data files. Appropriate extensions will be added to INFILE for specific data files that are to be read (See User Note 2). Host file naming conventions must be used. Output image. The name of the LAS image to be created. LAS file naming conventions must be used. DEM Flag. Process the DEM data file associated with IN. The DEM is stored as INTEGER*2 data, and the source data files are named differently than the image data files (See User Note 2).

       = NO:  Process image data only
       = YES: Process DEM data only

Examples:

  1. ndf2las infile=00095070400010007 out=[sgs6.disk99.user]unit007

    The NDF formatted image specified by INFILE will be converted into the LAS image specified by OUT. The NDF header file 00095070400010007;nhdr will be read to update the output DDR.

  2. ndf2las infile=00095070400010008 out=[sg1.dsb5.user]unit008 demflg=yes

    The NDF formatted DEM image specified by INFILE will be converted into the LAS image unit008;img. The DEM-specific NDF header will be read, and the output DDR will be updated.

Description/Algorithm

The NDF header file for INFILE is opened and read to obtain image size and format information. This information is passed to TRANSLAS-IN to ingest the image data specified in the files whose root is specified by INFILE. After TRANSLAS-IN completes, the DDR is updated with information extracted from the NDF header file.

Nonfatal Error Messages:

  1. [ndf2las-bddr] Error updating bddr

    An error occured when attempting to update a band dependent DDR record. Processing will continue.

  2. [ndf2las-data] Unable to locate <xxxx>

    The information specified by <xxxx> could not be located in the NDF header file. Information relating to this field will not be updated in the output DDR.

  3. [ndf2las-odatum] Unable to handle other datum codes

    There is an invalid datum code. Only WGS84, NAD83, NAD27 and ELLIPSOID are valid output datum codes from NLAPS. If an invalid datum code is encountered, the DDR datum field will be flagged invalid and processing will continue.

Fatal Error Messages:

  1. [ndf2las-alloc] Error allocating dynamic memory

    An error was detected while trying to allocate dynamic memory. If the error persists contact the system administrator.

  2. [ndf2las-bip] Unsupported type

    Band Interleaved by Pixel (BIP) data storage is not supported by the current NLAPS implementation. Contact the system administrator.

  3. [ndf2las-corner] Unable to locate CORNER data

    No corner information was available for this scene. Update the NDF header with correct corner information and rerun.

  4. [ndf2las-data] Unable to locate <xxxx>

    The information specified by <xxxx> could not be located in the NDF header file. Conversion of the scene is not possible without this field.

  5. [ndf2las-fatal] Fatal error encountered

    The error message that is displayed immediately preceding this message is the specific error that was encountered. Processing is terminated.

User Notes:

  1. Fatal and nonfatal errors are listed are from subroutines. For all nonfatal errors, processing will continue, however the DDR element relating to missing items will not be updated or validated.

  2. Naming conventions are as follows for NDF formatted files required for this function:

    	<infile>_I<file#>.dat		Image data files
    	<infile>_D.dat			DEM data file
    	<infile>I.nhdr			Image NDF header file
    	<infile>D.nhdr			DEM NDF header file
    
    The <file#> specified above always begins with 1 and increments through the number of bands included with this NDF product, up to a maximum of 7.

  3. A related function is NDFIN. If any changes are made to the NHDR2DDR code in NDF2LAS, corresponding changes must be made in the same code modules within the NDFIN code.