/******************************************************************************

  FILE:  mkblkftr.cnt

         This control file is used with the mkblkftr program
         to create, update, and/or retrieve human-readable documentation
         that contains essential metadata highlighted by keywords
         for a CODAS database of a given cruise.  There will be two
         primary uses for this information: 1) as a quick reference
         cruise "read.me" file and 2) as input to the BIRS (Browse, 
         Inventory, and Retrieval System).

         A single block footer will exist for each cruise and will
         be duplicated in each block.  
         The block footer will consist of the following:

         #DATA_DATES: yyyy/mm/dd hh/mm/ss to yyyy/mm/dd hh/mm/ss  
         #LAT_RANGE: [+/-]  dd mm.tt  to [+/-]  dd mm.tt  
         #LON_RANGE: [+/-] ddd mm.tt  to [+/-] ddd mm.tt 
         #DEPTH_RANGE: dd to dddd m  
         #SAC_CRUISE_ID: xxxxx  
         #PLATFORM_NAME: <free form, ship name>  
         #PRINCIPAL_INVESTIGATOR_NAME: <free form, multiple ok>  
         #PI_INSTITUTION: <free form>  
         #PI_COUNTRY: <free form>  
         #PROJECT: <free form, may be joint>  
         #CRUISE_NAME: <free form>  
         #PORTS: <free form>  
         #GEOGRAPHIC_REGION: <free form>  
         #PROCESSED_BY: <free form, institution>  
         #NAVIGATION: <free form, type such as GPS or transit>  
         #QUALITY_NAV: <excellent> <good> <fair> <poor> <none> 
         #GENERAL_INFORMATION: <free form>   

        The #DATA_DATES:, #LAT_RANGE:, #LON_RANGE:,
        and #DEPTH_RANGE will be obtained automatically from
        the block header during creation of the block footer and
        will remain fixed (not editable).

  INPUT:  1. CODAS block files (*.blk)  
          2. ASCII version of block footer (during PUT1ST and REPLACE)
  OUTPUT: 1. ASCII version of block footer (during CREATE and RETRIEVE)
             xxxxx.bft where xxxxx is SAC_CRUISE_ID (see below)
          2. updated CODAS blockfiles (during PUT1ST and REPLACE)
-------------------------------------------------------------------------------
  CONTROL FILE STRUCTURE:

  dbname:          < CODAS database name >
  sac_cruise_id:   < 5-byte number assigned by SAC >
  execution_option 
                   < create | put1st | retrieve | replace >
  end

  dbname:    /home/kapau/caldwell/adcp/demo/adcpdb/ademo 
-----------------------------------------------------------------------------*/
  dbname:    00681
  sac_cruise_id:   00681
/*  execution_option */
      put1st  
  end

/*****************************************************************************/