[IDV #BDE-406856]: Problem writing a head with the text point metadata GUI.

Hi all-

> > We got this post from a user on our forums.  Does this look like
> > something that is a bug, or is the user doing something wrong?  I tried
> > using it myself and couldn't figure out what I was doing.
> >
> As Tom pointed out the data was wrong. Because it is space separated the IDV 
> sees 8 columns of data. The date and time columns need to be merged. and 
> either the "COA128/000" field needs to be split so there are separate 
> FlightName and Value fields or the first Value column specification needs to 
> be dropped.

You should be able to use the colspan attribute for the time and not need to 
put the
T in:

(index)->(Time,FlightName(Text),Value(Text),Latitude,Longitude,Value1(Text),Valu
e2(Text),FlightPlan(Text))
Time[fmt="MM/dd/yyyy HH:mm:ss" colspan="2"],FlightName(Text)[],Value(Text)[],Lat
itude[ unit="degrees" ],Longitude[unit="degrees" ],Value1(Text)[],Value2(Text)[]
,FlightPlan(Text)[]
08/03/2009 07:05:20 COA128 000 14.633333 -63.900002 490 360 Norm
08/03/2009 07:07:20 COA128 000 14.850000 -64.050003 480 360 Norm
08/03/2009 07:08:21 COA128 000 14.966666 -64.116669 490 360 Norm

but you'll definitely need to fix the / as the others have said.

Don Murray


> The GUI is writing things out correctly in that it just writes out what the 
> user specified.
> 
> -Jeff
> 
> 
> > -----------------------------------------------------------------------
> >
> > I started with a file of data values, separated by spaces.
> >
> > 08/03/2009 07:05:20 COA128/000 14.633333 -63.900002 490 360 Norm
> > 08/03/2009 07:07:20 COA128/000 14.850000 -64.050003 480 360 Norm
> > 08/03/2009 07:08:21 COA128/000 14.966666 -64.116669 490 360 Norm
> >
> > I brought this into McIDAS-V using the File Chooser Data
> > Sources>General>Files/Directories. The data type was Text Point Data
> > files. The first time, I read it in without a header and used the Point
> > Data GUI to set up the data format. This works to read in the data and
> > display it. The header I wrote from the GUI was
> >
> > (index)->(Time,FlightName(Text),Value(Text),Latitude,Longitude,Value1(Text),Value2(Text),FlightPlan(Text))
> > Time[ fmt="MM/dd/yyyy HH:mm:ss"
> > ],FlightName(Text)[],Value(Text)[],Latitude[ unit="degrees" ],Longitude[
> > unit="degrees" ],Value1(Text)[],Value2(Text)[],FlightPlan(Text)[]
> >
> > When I put those together, and tried to read them into McIDAS-V, I could
> > read them in but could not display the data.
> >
> > (index)->(Time,FlightName(Text),Value(Text),Latitude,Longitude,Value1(Text),Value2(Text),FlightPlan(Text))
> > Time[ fmt="MM/dd/yyyy HH:mm:ss"
> > ],FlightName(Text)[],Value(Text)[],Latitude[ unit="degrees" ],Longitude[
> > unit="degrees" ],Value1(Text)[],Value2(Text)[],FlightPlan(Text)[]
> > 08/03/2009 07:05:20 COA128/000 14.633333 -63.900002 490 360 Norm
> > 08/03/2009 07:07:20 COA128/000 14.850000 -64.050003 480 360 Norm
> > 08/03/2009 07:08:21 COA128/000 14.966666 -64.116669 490 360 Norm
> >
> >
> > Tom W. then looked at the header and gave me the following corrections,
> > which fixed the problem...
> >
> >
> > From Tom:
> > Joleen --
> >
> >
> > > Joleen --
> > >
> > > There are two problems:
> > >
> > > 1. The date-time field is ambiguous because of the space.
> > > To fix this: change the template to be "MM/dd/yyy'T'HH:mm:ss"
> > > (that is put 'T' in place of the space)...then edit
> > > your file to put a T between the date and time.
> > >
> > > 2. Apparently the "Value" field is the "000" after the "/" after
> > > COA128? If so, then the "/" needs to be changed to a space; right
> > > now, it parses this as though the 000 is the Latitude....
> > >
> > > Hope that helps....
> > >
> > > tom
> >
> >
> >
> > Here's the beginning of the file that works....
> >
> > (index)->(Time,FlightName(Text),Value(Text),Latitude,Longitude,Value1(Text),Value2(Text),FlightPlan(Text))
> > Time[ fmt="MM/dd/yyyy'T'HH:mm:ss"
> > ],FlightName(Text)[],Value(Text)[],Latitude[ unit="degrees" ],Longitude[
> > unit="degrees" ],Value1(Text)[],Value2(Text)[],FlightPlan(Text)[]
> > 08/03/2009T07:05:20 COA128 000 14.633333 -63.900002 490 360 Norm
> > 08/03/2009T07:07:20 COA128 000 14.850000 -64.050003 480 360 Norm
> > 08/03/2009T07:08:21 COA128 000 14.966666 -64.116669 490 360 Norm
> >
> >
> > I am wondering if the GUI which writes the header is working as expected
> > when writing the header. I don't seem to have a problem looking at the
> > data if it is brought in this way.
> >
> > Thanks,
> > Joleen
> > ---------------------------------------------------
> >
> >
> 


Ticket Details
===================
Ticket ID: BDE-406856
Department: Support IDV
Priority: Normal
Status: Closed