(USA) Data suggestion for WinPilot users

[Tuno]

Okay, this is partially a plug for my own web site, but after helping
a couple of WinPilot users set up their data files, I want to offer
these suggetions to other users who might be struggling with the same
setup questions:

(1) As mentioned on WinPilot's web page, the airspace data downloaded
there is based on obsolete DAFIF. Skip it! (Especially if you fly near
Phoenix.) The .TXT file (OpenAir(TM) format) you get at www.justsoar.com
is what you should specify in the "Additional Airspace" field of the
"FILES" setup section. That's all you need for accurate airspace.

(2) If you provide a turnpoint file at www.justsoar.com to provide
your geographic area of interest (recommended), the turnpoint file you
get back is the same file appended with all of the FAA's airports in
the same area (i.e., those that are not already in your original
turnpoint file), based on *latest* FAA airport data (a different
database than the what the airspace comes from). If you do this, then
do NOT specify any states under "Aeronautical Info", if you don't want
redundant airport entries displayed on the map.

~ted/2NO

[Frank[_1_]]

Ted,

Nice! I signed up

Frank (TA)

On Apr 23, 11:56*am, Tuno > wrote:
> Okay, this is partially a plug for my own web site, but after helping
> a couple of WinPilot users set up their data files, I want to offer
> these suggetions to other users who might be struggling with the same
> setup questions:
>
> (1) As mentioned on WinPilot's web page, the airspace data downloaded
> there is based on obsolete DAFIF. Skip it! (Especially if you fly near
> Phoenix.) The .TXT file (OpenAir(TM) format) you get atwww.justsoar.com
> is what you should specify in the "Additional Airspace" field of the
> "FILES" setup section. That's all you need for accurate airspace.
>
> (2) If you provide a turnpoint file atwww.justsoar.comto provide
> your geographic area of interest (recommended), the turnpoint file you
> get back is the same file appended with all of the FAA's airports in
> the same area (i.e., those that are not already in your original
> turnpoint file), based on *latest* FAA airport data (a different
> database than the what the airspace comes from). If you do this, then
> do NOT specify any states under "Aeronautical Info", if you don't want
> redundant airport entries displayed on the map.
>
> ~ted/2NO

[Frank[_1_]]

Ted,

Since you are obviously responding to one of the many WinPilot
frustrations that the developer won't respond to, would you consider
expanding your website to include an 'unofficial' WinPilot users
forum?

Just a thought.... ;-)

Frank



On Apr 23, 11:56*am, Tuno > wrote:
> Okay, this is partially a plug for my own web site, but after helping
> a couple of WinPilot users set up their data files, I want to offer
> these suggetions to other users who might be struggling with the same
> setup questions:
>
> (1) As mentioned on WinPilot's web page, the airspace data downloaded
> there is based on obsolete DAFIF. Skip it! (Especially if you fly near
> Phoenix.) The .TXT file (OpenAir(TM) format) you get atwww.justsoar.com
> is what you should specify in the "Additional Airspace" field of the
> "FILES" setup section. That's all you need for accurate airspace.
>
> (2) If you provide a turnpoint file atwww.justsoar.comto provide
> your geographic area of interest (recommended), the turnpoint file you
> get back is the same file appended with all of the FAA's airports in
> the same area (i.e., those that are not already in your original
> turnpoint file), based on *latest* FAA airport data (a different
> database than the what the airspace comes from). If you do this, then
> do NOT specify any states under "Aeronautical Info", if you don't want
> redundant airport entries displayed on the map.
>
> ~ted/2NO