RE: GTE DUATS and weather graphics/etc.

[Rob Prior <RPrior@creo.com>]

If it's the bootstrap approach to aircraft performance that you're looking
for, here's three articles on AvWeb that do just that, complete with Excel
spreadsheets (haven't tried, but they should load into StarOffice just
fine... 8-)

Fixed-Pitch-Propelled: http://www.avweb.com/articles/bootstp1/
Variable-Pitch-Propelled: http://www.avweb.com/articles/bootstp2/
Turning Performance: http://www.avweb.com/articles/bootstp3/

-Rob Prior
 Airframe Aircraft Portraits
 http://home.istar.ca/~airframe/


-----Original Message-----
From: D.F.S. [mailto:dfs@xmission.com]
Sent: Monday, January 31, 2000 09:20
To: linux-aviation@nl.linux.org
Subject: Re: GTE DUATS and weather graphics/etc.


> 
> On Sat, Jan 29, 2000 at 05:46:52PM -0800, Eugene Leitl wrote:
> > Kenyon D. Cox writes:
> > 
SNIP
> The "modules"
> could be defined in an obvious way so that people could work on them
> independently without too much trouble. Some of the obvious ones are;
> 
>   o Aircraft performance predictions (like take off distances estimated
from
>       density altitude computations derived from weather observations,
etc.)

There is a method kicking around that looks interesting.

It is called the bootstrap approach and with a few test flights to nail down
4-5 parameters opens up a huge amount of info and performance projections.

The guy has a book, but it runs 65 bucks and then the guy has the gall
to charge $45.00 for a diskette of spreadsheets.

There are some free articles on avweb along with a few spreadsheets.


>   o Route selection (including constraints like fuel availability, and
>      possibly some type of route optimization).

It would be good to add logic so that a flight plan package, say fplan,
would
pick airports within say an ever widening elipse or rectangle giving
priority along the route of flight. It would them submit them to an external
program, maybe even a system command called "Approve_airport" or something
which would return a yea or nay or maybe a prefered alternate. 
This could easily be stubbed to a shell script that would approve anything. 
We could build different programs written in nearly anything appropriate 
to do the processing.
It could be anything from Shell to C, Perl to python. 
This would leave the most flexibility for all sorts of conditions and 
requirements.
This would allow all sorts of processing for other non-aviation, but trip
or personal priorities as well. Stuff like:
Does Podunk Intl. have car rentals?
Does Podunk City have a Motel 6?
Does Podunk City Have a Greyhound Bus Terminal? (For annoying Pax).

Some of this stuff could be in a local database and some may be
based on a custom processing script that goes out to the web to someplace
like Motel6.com or Hertz.com and looks stuff up.

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>.
-
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>.