Re: GTE DUATS and weather graphics/etc.

["D.F.S." <dfs@xmission.com>]

> I would say perl would be the best place to start. We could then easily
> translate the perl module into a wrapper around a C library - particularly
> if we are careful on designing the interface.
> 

I would have to vote for perl.

I'm a confirmed C bigot, but for this type of thing, processing files and 
html and other random bits of info, I think Perl wins hands down.

A look at the Database we were talking about and plans to parse it is a
perfect example.

This will probably take 1/4 the code in perl to do this than with C.

As soon as we can get it posted someplace, I'll get started on that.

I plan to split the different record types out into different files.

Just to keep it simple, look at the file descriptions just posted.
many of the files have multiple record types:

Take AWY.

DESCRIPTION OF THE RECORD TYPES:  
--------------------------------  
  
    'AWY1' RECORD TYPE CONTAINS THE BASIC AND MINIMUM   
    ENROUTE ALTITUDE(MEA) DATA FOR EACH AIRWAY POINT/SEGMENT.  
    THERE IS ONE AWY1 RECORD FOR EACH AIRWAY POINT/SEGMENT.  
  
    'AWY2' RECORD TYPE CONTAINS THE AIRWAY POINT DESCRIPTION.  
    THERE IS ONE AWY2 RECORD FOR EACH AIRWAY POINT.  
  
    'AWY3' RECORD TYPE CONTAINS THE TO CHANGEOVER POINT NAVAID  
    DESCRIPTION (VOR AND JET AIRWAYS ONLY).  
    THERE IS ONE RECORD FOR EACH TO CHANGEOVER POINT NAVAID DESCRIPTION.  
  
    'AWY4' RECORD TYPE CONTAINS TEXTUAL INFORMATION REGARDING  
    REMARKS ABOUT THE AWY POINT DATA.  EACH AWY4 RECORD  
    CONTAINS ONE LINE OF TEXT.  THERE CAN BE 0 TO 2 AWY4  
    RECORDS.  
  
    'AWY5' RECORD TYPE CONTAINS TEXTUAL INFORMATION REGARDING  
    EXCEPTIONS TO THE STANDARD AWY CHANGEOVER POINT DATA.  EACH AWY5  
    RECORD CONTAINS ONE LINE OF TEXT.  THERE CAN BE 0 TO 2 AWY5  
    RECORDS.  


It would be much better from a database viewpoint to have all these
different record types in different files or tables and relate
them to each other than to try and dig thru and parse this jumble
of stuff every time you need a piece of data.

Marc





-
Archives of linux-aviation: http://mail.nl.linux.org/lists/linux-aviation/
To unsubscribe: send the command "unsubscribe linux-aviation" in the body
of a mail message to <Majordomo@mail.nl.linux.org>.