OpenAir Airspace Format

[karaka29211]

In the manuals for XCSoar, it is noted that XCSoar uses a subset of the Openair format.

"The following are the list of supported airspace types. All other airspace types will be drawn as type ”Other”: Class A, Class B, Class C, Class D, Class E, Class F, Prohibited areas, Danger areas,
Restricted Areas, CTR, No Gliders, Wave, Other."

Can someone state the exact features that  XCSoar uses including the abbreviations used for Danger Areas etc?
This is the original OpenAir format, alternatively, which features of this format does XCSoar not use?
Cheers

*    Version 1.0
*    December 10, 1998
*    Updated October 15, 1999
*
*
*  AIRSPACE related record types:
*  ==============================
*
* AC class    ;    class = Airspace Class, see below:
*     R restricted
*     Q danger
*     P prohibited
*     A Class A
*     B Class B
*     C Class C
*     D Class D
*     GP glider prohibited
*     CTR CTR
*     W Wave Window
*
*
*  AN string        ;     string = Airspace Name
*  AH string        ;     string = Airspace Ceiling
*  AL string        ;     string = Airspace Floor
*  AT coordinate    ;    coordinate = Coordinate of where to place a name label on the map (optional)
*                   ;     NOTE: there can be multiple AT records for a single airspace segment
*    
*    
*    TERRAIN related record types:
*    ==============================
*
*    TO    {string}                 ; Declares Terrain Open Polygon; string = name (optional)
*    TC    {string}                 ; Declares Terrain Closed Polygon; string = name (optional)
*    SP style, width, red, green, blue    ; Selects Pen to be used in drawing
*    SB red, green, blue                         ; Selects Brush to be used in drawing
*
*
*    Record types common to both TERRAIN and AIRSPACE
*    =================================================
*
*    V x=n            ;     Variable assignment.
*                     ;     Currently the following variables are supported:
*                     ;     D={+|-}    sets direction for: DA and DB records
*                     ;                     '-' means counterclockwise direction; '+' is the default
*                     ;                     automatically reset to '+' at the begining of new airspace segment    
*                     ;     X=coordinate    : sets the center for the following records: DA, DB, and DC    
*                     ;     W=number        : sets the width of an airway in nm (NYI)
*                     ;      Z=number         : sets zoom level at which the element becomes visible
*
*    DP coordinate                     ; add polygon pointC
*    DA radius, angleStart, angleEnd   ; add an arc, angles in degrees, radius in nm (set center using V X=...)
*    DB coordinate1, coordinate2       ; add an arc, from coordinate1 to coordinate2 (set center using V X=...)
*    DC radius                         ; draw a circle (center taken from the previous V X=...  record, radius in nm
*    DY coordinate                     ; add a segment of an airway (NYI)

[John Wharington-2]

Hi,

We use the standard Openair format but we do not parse CTR or GP.
The abbreviations used for danger areas etc depend on how the airspace
file is created; we do not do any further abbreviation.

If you look at the worldwide soaring turnpoint exchange you will see
many examples.


Johnny

On Wed, 2009-01-14 at 15:57 -0800, karaka29211 wrote:

> In the manuals for XCSoar, it is noted that XCSoar uses a subset of the
> Openair format.
> Can someone state the exact features that  XCSoar uses including the
> abbreviations used for Danger Areas etc?
> This is the original OpenAir format, alternatively, which features of this
> format does XCSoar not use?
> Cheers
>
> *    Version 1.0
> *    December 10, 1998
> *    Updated October 15, 1999
> *
> *
> *  AIRSPACE related record types:
> *  ==============================
> *
> * AC class    ;    class = Airspace Class, see below:
> *     R restricted
> *     Q danger
> *     P prohibited
> *     A Class A
> *     B Class B
> *     C Class C
> *     D Class D
> *     GP glider prohibited
> *     CTR CTR
> *     W Wave Window
> *
> *
> *  AN string        ;     string = Airspace Name
> *  AH string        ;     string = Airspace Ceiling
> *  AL string        ;     string = Airspace Floor
> *  AT coordinate    ;    coordinate = Coordinate of where to place a name
> label on the map (optional)
> *                   ;     NOTE: there can be multiple AT records for a
> single airspace segment
> *    
> *    
> *    TERRAIN related record types (WinPilot version 1.130 and newer):
> *    ==============================
> *
> *    TO    {string}                 ; Declares Terrain Open Polygon; string
> = name (optional)
> *    TC    {string}                 ; Declares Terrain Closed Polygon;
> string = name (optional)
> *    SP style, width, red, green, blue    ; Selects Pen to be used in
> drawing
> *    SB red, green, blue                         ; Selects Brush to be used
> in drawing
> *
> *
> *    Record types common to both TERRAIN and AIRSPACE
> *    =================================================
> *
> *    V x=n            ;     Variable assignment.
> *                     ;     Currently the following variables are supported:
> *                     ;     D={+|-}    sets direction for: DA and DB records
> *                     ;                     '-' means counterclockwise
> direction; '+' is the default
> *                     ;                     automatically reset to '+' at
> the begining of new airspace segment    
> *                     ;     X=coordinate    : sets the center for the
> following records: DA, DB, and DC    
> *                     ;     W=number        : sets the width of an airway in
> nm (NYI)
> *                     ;      Z=number         : sets zoom level at which the
> element becomes visible
> *
> *    DP coordinate                     ; add polygon pointC
> *    DA radius, angleStart, angleEnd   ; add an arc, angles in degrees,
> radius in nm (set center using V X=...)
> *    DB coordinate1, coordinate2       ; add an arc, from coordinate1 to
> coordinate2 (set center using V X=...)
> *    DC radius                         ; draw a circle (center taken from
> the previous V X=...  record, radius in nm
> *    DY coordinate                     ; add a segment of an airway (NYI)

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Xcsoar-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xcsoar-user

[karaka29211]

Hi Johnny,
Can you then confirm that where one defines a Danger Area in Openair in XCSoar , the correct attribute for a Danger Area is the term "Other" rather than "Q". This is the feature that needs clarification.
Cheers,

John Wharington-2 wrote

Hi,

We use the standard Openair format but we do not parse CTR or GP.
The abbreviations used for danger areas etc depend on how the airspace
file is created; we do not do any further abbreviation.

If you look at the worldwide soaring turnpoint exchange you will see
many examples.


Johnny

On Wed, 2009-01-14 at 15:57 -0800, karaka29211 wrote:
> In the manuals for XCSoar, it is noted that XCSoar uses a subset of the
> Openair format.
> Can someone state the exact features that  XCSoar uses including the
> abbreviations used for Danger Areas etc?
> This is the original OpenAir format, alternatively, which features of this
> format does XCSoar not use?
> Cheers
>
> *    Version 1.0
> *    December 10, 1998
> *    Updated October 15, 1999
> *
> *
> *  AIRSPACE related record types:
> *  ==============================
> *
> * AC class    ;    class = Airspace Class, see below:
> *     R restricted
> *     Q danger
> *     P prohibited
> *     A Class A
> *     B Class B
> *     C Class C
> *     D Class D
> *     GP glider prohibited
> *     CTR CTR
> *     W Wave Window
> *
> *
> *  AN string        ;     string = Airspace Name
> *  AH string        ;     string = Airspace Ceiling
> *  AL string        ;     string = Airspace Floor
> *  AT coordinate    ;    coordinate = Coordinate of where to place a name
> label on the map (optional)
> *                   ;     NOTE: there can be multiple AT records for a
> single airspace segment
> *    
> *    
> *    TERRAIN related record types (WinPilot version 1.130 and newer):
> *    ==============================
> *
> *    TO    {string}                 ; Declares Terrain Open Polygon; string
> = name (optional)
> *    TC    {string}                 ; Declares Terrain Closed Polygon;
> string = name (optional)
> *    SP style, width, red, green, blue    ; Selects Pen to be used in
> drawing
> *    SB red, green, blue                         ; Selects Brush to be used
> in drawing
> *
> *
> *    Record types common to both TERRAIN and AIRSPACE
> *    =================================================
> *
> *    V x=n            ;     Variable assignment.
> *                     ;     Currently the following variables are supported:
> *                     ;     D={+|-}    sets direction for: DA and DB records
> *                     ;                     '-' means counterclockwise
> direction; '+' is the default
> *                     ;                     automatically reset to '+' at
> the begining of new airspace segment    
> *                     ;     X=coordinate    : sets the center for the
> following records: DA, DB, and DC    
> *                     ;     W=number        : sets the width of an airway in
> nm (NYI)
> *                     ;      Z=number         : sets zoom level at which the
> element becomes visible
> *
> *    DP coordinate                     ; add polygon pointC
> *    DA radius, angleStart, angleEnd   ; add an arc, angles in degrees,
> radius in nm (set center using V X=...)
> *    DB coordinate1, coordinate2       ; add an arc, from coordinate1 to
> coordinate2 (set center using V X=...)
> *    DC radius                         ; draw a circle (center taken from
> the previous V X=...  record, radius in nm
> *    DY coordinate                     ; add a segment of an airway (NYI)


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Xcsoar-user mailing list
[e-mail]
https://lists.sourceforge.net/lists/listinfo/xcsoar-user

[John Wharington-2]

The correct attribute is "Q".

On Wed, 2009-01-14 at 16:44 -0800, karaka29211 wrote:

> Hi Johnny,
> Can you then confirm that where one defines a Danger Area in Openair in
> XCSoar , the correct attribute for a Danger Area is the term "Other" rather
> than "Q". This is the feature that needs clarification.
> Cheers,
>
> John Wharington-2 wrote:
> >
> > Hi,
> >
> > We use the standard Openair format but we do not parse CTR or GP.
> > The abbreviations used for danger areas etc depend on how the airspace
> > file is created; we do not do any further abbreviation.
> >
> > If you look at the worldwide soaring turnpoint exchange you will see
> > many examples.
> >
> >
> > Johnny
> >
> > On Wed, 2009-01-14 at 15:57 -0800, karaka29211 wrote:
> >> In the manuals for XCSoar, it is noted that XCSoar uses a subset of the
> >> Openair format.
> >> Can someone state the exact features that  XCSoar uses including the
> >> abbreviations used for Danger Areas etc?
> >> This is the original OpenAir format, alternatively, which features of
> >> this
> >> format does XCSoar not use?
> >> Cheers
> >>
> >> *    Version 1.0
> >> *    December 10, 1998
> >> *    Updated October 15, 1999
> >> *
> >> *
> >> *  AIRSPACE related record types:
> >> *  ==============================
> >> *
> >> * AC class    ;    class = Airspace Class, see below:
> >> *     R restricted
> >> *     Q danger
> >> *     P prohibited
> >> *     A Class A
> >> *     B Class B
> >> *     C Class C
> >> *     D Class D
> >> *     GP glider prohibited
> >> *     CTR CTR
> >> *     W Wave Window
> >> *
> >> *
> >> *  AN string        ;     string = Airspace Name
> >> *  AH string        ;     string = Airspace Ceiling
> >> *  AL string        ;     string = Airspace Floor
> >> *  AT coordinate    ;    coordinate = Coordinate of where to place a name
> >> label on the map (optional)
> >> *                   ;     NOTE: there can be multiple AT records for a
> >> single airspace segment
> >> *    
> >> *    
> >> *    TERRAIN related record types (WinPilot version 1.130 and newer):
> >> *    ==============================
> >> *
> >> *    TO    {string}                 ; Declares Terrain Open Polygon;
> >> string
> >> = name (optional)
> >> *    TC    {string}                 ; Declares Terrain Closed Polygon;
> >> string = name (optional)
> >> *    SP style, width, red, green, blue    ; Selects Pen to be used in
> >> drawing
> >> *    SB red, green, blue                         ; Selects Brush to be
> >> used
> >> in drawing
> >> *
> >> *
> >> *    Record types common to both TERRAIN and AIRSPACE
> >> *    =================================================
> >> *
> >> *    V x=n            ;     Variable assignment.
> >> *                     ;     Currently the following variables are
> >> supported:
> >> *                     ;     D={+|-}    sets direction for: DA and DB
> >> records
> >> *                     ;                     '-' means counterclockwise
> >> direction; '+' is the default
> >> *                     ;                     automatically reset to '+' at
> >> the begining of new airspace segment    
> >> *                     ;     X=coordinate    : sets the center for the
> >> following records: DA, DB, and DC    
> >> *                     ;     W=number        : sets the width of an airway
> >> in
> >> nm (NYI)
> >> *                     ;      Z=number         : sets zoom level at which
> >> the
> >> element becomes visible
> >> *
> >> *    DP coordinate                     ; add polygon pointC
> >> *    DA radius, angleStart, angleEnd   ; add an arc, angles in degrees,
> >> radius in nm (set center using V X=...)
> >> *    DB coordinate1, coordinate2       ; add an arc, from coordinate1 to
> >> coordinate2 (set center using V X=...)
> >> *    DC radius                         ; draw a circle (center taken from
> >> the previous V X=...  record, radius in nm
> >> *    DY coordinate                     ; add a segment of an airway (NYI)
> >
> >
> > ------------------------------------------------------------------------------
> > This SF.net email is sponsored by:
> > SourcForge Community
> > SourceForge wants to tell your story.
> > http://p.sf.net/sfu/sf-spreadtheword
> > _______________________________________________
> > Xcsoar-user mailing list
> > [hidden email]
> > https://lists.sourceforge.net/lists/listinfo/xcsoar-user
> >
> >
>

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Xcsoar-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xcsoar-user

[robinb-2]

To back up Johnny's statement.  All of the openair formats have Q as danger
and both ourselves and winpilot use Q as danger.  The airspace files that we
use are largely interchangeable between the two packages.

Robin

-----Original Message-----
From: John Wharington [mailto:[hidden email]]
Sent: 15 January 2009 00:53
To: karaka29211
Cc: [hidden email]
Subject: Re: [Xcsoar-user] OpenAir Airspace Format

The correct attribute is "Q".

On Wed, 2009-01-14 at 16:44 -0800, karaka29211 wrote:
> Hi Johnny,
> Can you then confirm that where one defines a Danger Area in Openair in
> XCSoar , the correct attribute for a Danger Area is the term "Other"
rather

> than "Q". This is the feature that needs clarification.
> Cheers,
>
> John Wharington-2 wrote:
> >
> > Hi,
> >
> > We use the standard Openair format but we do not parse CTR or GP.
> > The abbreviations used for danger areas etc depend on how the airspace
> > file is created; we do not do any further abbreviation.
> >
> > If you look at the worldwide soaring turnpoint exchange you will see
> > many examples.
> >
> >
> > Johnny
> >
> > On Wed, 2009-01-14 at 15:57 -0800, karaka29211 wrote:
> >> In the manuals for XCSoar, it is noted that XCSoar uses a subset of the
> >> Openair format.
> >> Can someone state the exact features that  XCSoar uses including the
> >> abbreviations used for Danger Areas etc?
> >> This is the original OpenAir format, alternatively, which features of
> >> this
> >> format does XCSoar not use?
> >> Cheers
> >>
> >> *    Version 1.0
> >> *    December 10, 1998
> >> *    Updated October 15, 1999
> >> *
> >> *
> >> *  AIRSPACE related record types:
> >> *  ==============================
> >> *
> >> * AC class    ;    class = Airspace Class, see below:
> >> *     R restricted
> >> *     Q danger
> >> *     P prohibited
> >> *     A Class A
> >> *     B Class B
> >> *     C Class C
> >> *     D Class D
> >> *     GP glider prohibited
> >> *     CTR CTR
> >> *     W Wave Window
> >> *
> >> *
> >> *  AN string        ;     string = Airspace Name
> >> *  AH string        ;     string = Airspace Ceiling
> >> *  AL string        ;     string = Airspace Floor
> >> *  AT coordinate    ;    coordinate = Coordinate of where to place a

name

> >> label on the map (optional)
> >> *                   ;     NOTE: there can be multiple AT records for a
> >> single airspace segment
> >> *    
> >> *    
> >> *    TERRAIN related record types (WinPilot version 1.130 and newer):
> >> *    ==============================
> >> *
> >> *    TO    {string}                 ; Declares Terrain Open Polygon;
> >> string
> >> = name (optional)
> >> *    TC    {string}                 ; Declares Terrain Closed Polygon;
> >> string = name (optional)
> >> *    SP style, width, red, green, blue    ; Selects Pen to be used in
> >> drawing
> >> *    SB red, green, blue                         ; Selects Brush to be
> >> used
> >> in drawing
> >> *
> >> *
> >> *    Record types common to both TERRAIN and AIRSPACE
> >> *    =================================================
> >> *
> >> *    V x=n            ;     Variable assignment.
> >> *                     ;     Currently the following variables are
> >> supported:
> >> *                     ;     D={+|-}    sets direction for: DA and DB
> >> records
> >> *                     ;                     '-' means counterclockwise
> >> direction; '+' is the default
> >> *                     ;                     automatically reset to '+'

at
> >> the begining of new airspace segment    
> >> *                     ;     X=coordinate    : sets the center for the
> >> following records: DA, DB, and DC    
> >> *                     ;     W=number        : sets the width of an
airway
> >> in
> >> nm (NYI)
> >> *                     ;      Z=number         : sets zoom level at
which
> >> the
> >> element becomes visible
> >> *
> >> *    DP coordinate                     ; add polygon pointC
> >> *    DA radius, angleStart, angleEnd   ; add an arc, angles in degrees,
> >> radius in nm (set center using V X=...)
> >> *    DB coordinate1, coordinate2       ; add an arc, from coordinate1
to
> >> coordinate2 (set center using V X=...)
> >> *    DC radius                         ; draw a circle (center taken
from
> >> the previous V X=...  record, radius in nm
> >> *    DY coordinate                     ; add a segment of an airway
(NYI)
> >
> >
> >
----------------------------------------------------------------------------
--

> > This SF.net email is sponsored by:
> > SourcForge Community
> > SourceForge wants to tell your story.
> > http://p.sf.net/sfu/sf-spreadtheword
> > _______________________________________________
> > Xcsoar-user mailing list
> > [hidden email]
> > https://lists.sourceforge.net/lists/listinfo/xcsoar-user
> >
> >
>

----------------------------------------------------------------------------
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Xcsoar-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xcsoar-user


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Xcsoar-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xcsoar-user

[Peter Bellham]

Currently working on an airspace file. Please could you expand on "we do not parse CTR or GP" - they both seem to me to display and give warnings as expected.

Find in version PPC2002.5.0.0 that airspaces are
     R restricted
     Q danger
     P prohibited
     A Class A
     B Class B
     C Class C
     D Class D
     E Class E  <--------- note, not used by Winpilot ?
     GP glider prohibited
     CTR CTR
     W Wave Window
and that PNA-5.1.9_Beta6a also has F Class F.

Peter

John Wharington-2 wrote

Hi,

We use the standard Openair format but we do not parse CTR or GP.
The abbreviations used for danger areas etc depend on how the airspace
file is created; we do not do any further abbreviation.

If you look at the worldwide soaring turnpoint exchange you will see
many examples.


Johnny

[John Wharington-2]

Sorry, my mistake, we do parse CTR and GP.

On Sun, 2009-01-18 at 08:50 -0800, Peter Bellham wrote:

> Currently working on an airspace file. Please could you expand on "we do not
> parse CTR or GP" - they both seem to me to display and give warnings as
> expected.
>
> Find in version PPC2002.5.0.0 that airspaces are
>      R restricted
>      Q danger
>      P prohibited
>      A Class A
>      B Class B
>      C Class C
>      D Class D
>      E Class E  <--------- note, not used by Winpilot ?
>      GP glider prohibited
>      CTR CTR
>      W Wave Window
> and that PNA-5.1.9_Beta6a also has F Class F.
>
> Peter
>
>
> John Wharington-2 wrote:
> >
> > Hi,
> >
> > We use the standard Openair format but we do not parse CTR or GP.
> > The abbreviations used for danger areas etc depend on how the airspace
> > file is created; we do not do any further abbreviation.
> >
> > If you look at the worldwide soaring turnpoint exchange you will see
> > many examples.
> >
> >
> > Johnny
> >
> >
>

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Xcsoar-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xcsoar-user