[McIDAS #HMV-801244]: ASCII file display in McIDAS-X

Hi Sohail,

re:
> I followed your instruction,
> Checked the MCPATH and try to implement the TXT2MD command. Here are the
> screenshots
> 
> *echo $MCPATH*

Your MCPATH setting is correct.

re:
> All the files are residing in the workdata folder which are in the *MCPATH 
> *env
> variable.  But still, have this problem.

Your invocation of TXT2MD has two or three problems:

1) the name of the ASCII text file that you specify in the TXT2MD command
   line is too long

   I detailed in a previous email that the name of the input file you
   specify in the TXT2MD command line must follow the old McIDAS naming
   convention of 8.3 - 8 characters before the '.' (period), the '.' (period)
   and then up to a 3-letter suffix.  The name of the file you specified
   not only had the full pathname of the file, the basename of the file
   is 9.3, not 8.3.

2) there needs to be information added to the text file that describes the
   fields in the file so that TXT2MD will know the values in the file
   actually are

3) one must specify the schema to be used for the MD file to be created

I'm afraid that you don't quite understand how to import the data into
McIDAS.  Section 15.7 in the materials used in the McIDAS training
session should be of help:

https://www.unidata.ucar.edu/software/mcidas/current/workshop/data_import.html

re:
> 1. Can you please give me an example of TXT2MD for the given files i have
> sent you or any other ASCII file.?

Please review the materials in the training section on importing foreign
datasets into McIDAS (section 15.7 that I referred to above).

re:
> 2. *AXFORM* command says that it creates an ASCII files which are in my
> case GOES_VIS.001 and GOES_VIS.HDR. Which of them is ASCII file then?

The Remarks portion of the built in HELP for AXFORM state which files
are ASCII and which are binary:

Remarks:
   AXFORM creates a set of files which contain data from sarea. These
   files maybe ported to other non-McIDAS systems. Data is represented
   as 2 dimensional arrays of binary or ASCII fields whose dimensions
   are those of the original sarea lines/elements.

   An ASCII output text file documents the format of the output data files.
   It contains a listing for each of the data files generated. Output files
   are assigned unique extensions:
     .HDR (header file) - This file contains ASCII text describing sarea
                          and the contents of the output data files.
     .nnn (data files) - These files contain binary data for a single
                         calibration of a specific band.
                         (nnn ranges from 001 to 999)
     .Ann (data files) - These files contain ASCII data for a single
                         calibration of a specific band.
                         (nn ranges from 01 to 99)
     .LAT (latitude file) - If NAV=YES, binary file contains a 2
                            dimensional array of latitudes corresponding
                            to the elements within the output data files.
     .LON (longitude file) - If NAV=YES, binary file contains a 2
                             dimensional array of longitudes corresponding
                             to the elements within the output data files.
     .ALT (latitude file) - If NAV=YES, ASCII file contains a 2
                            dimensional array of latitudes corresponding
                            to the elements within the output data files.
     .ALN (longitude file) - If NAV=YES, ASCII file contains a 2
                             dimensional array of longitudes corresponding
                             to the elements within the output data files.

re:
> 3. Can you please guide about that.?

See above.

I want to say again that I do _NOT_ think that going dumping satellite image
data in ASCII, creating an MD file, gridding the POINT data in the MD file
and then turning the gridded data into an image will get you where you want
to be, so all of this effort will likely be of no use to you (other than
an intellectual exercise).

re:
> I need your favor if you kindly contact Leon Majewski, if he can be helpful
> for the HDF3 to AREA format. Its long time he doesn't reply  me.

The email that I got from the folks at SSEC (and that I sent you in a
previous email) warned us that Leon is very busy, so he may be slow in
replying.  I do not think that my contacting him would make him respond
any quicker to your request for a way to create image data in McIDAS
AREA file format.  In fact, an email from me might just make him go
slower.

I sense a reluctance on your part to my suggestion that you try and get
FY2G imagery in AREA format from the SSEC Data Center.  Am I misreading
the situation, or is there something going on that I am not aware of?

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: HMV-801244
Department: Support McIDAS
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.