It should be feasible to add a number of things to xcsoar such as CTA / CTR / RADIO etc etc etc. However I have a worry around the modifying of a standard without agreement with the other users of that standard.
Robin
thorner@... wrote:
>
> Ideally an updated Openair airspace standard but failing that, an ability in
> XCSoar recognise the difference between a CTR (Control Zone) and a CTA
> (Control Area) would be desirable.
>
> kabmorgan wrote:
> >
> > Here's the Winpilot User Guide
> >
http://www.winpilot.com/UsersGuide/UserAirspace.asp> >
> > I've just tried inserting an AT line, but the label doesn't show up on the
> > map in XCSoar. Is this is what is being asked for?
> >
> > Keith
> >
> >
> >
> > Robin Birch wrote:
> >>
> >> Must admit, I wasn't aware of a newer standard. Is there one, if so
> >> where can I find it?
> >>
> >> Robin
> >>
> >>
thorner@... wrote:
> >>> What chance is there of enabling the ability of XCSoar to recognise the
> >>> "Radio" (VHF Frequency) and "CTA" (Control Area) statements in the now
> >>> outdated 1999 version 1.0 of the OpenAir airspace format.
> >>> As it stands, there is no difference between a "CTR" Control Zone
> >>> (SFC-?) and a Control Area (CTA)
> >>> with upper (AH) and lower levels (AL) above the ground level (SFC).
> >>> Alternatively, can you specify which later version of the OpenAir
> >>> airspace format is recognised by XCSoar?
> >>>
> >>> OpenAir Airspace format 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
> >>>
> >>>
> >>> -------------------------------------------------------------------------
> >>> Check out the new SourceForge.net Marketplace.
> >>> It's the best place to buy or sell services for
> >>> just about anything Open Source.
> >>>
http://sourceforge.net/services/buy/index.php> >>> _______________________________________________
> >>> Xcsoar-user mailing list
> >>>
Xcsoar-user@...
> >>>
https://lists.sourceforge.net/lists/listinfo/xcsoar-user> >>>
> >>
> >>
> >> -------------------------------------------------------------------------
> >> Check out the new SourceForge.net Marketplace.
> >> It's the best place to buy or sell services for
> >> just about anything Open Source.
> >>
http://sourceforge.net/services/buy/index.php> >> _______________________________________________
> >> Xcsoar-user mailing list
> >>
Xcsoar-user@...
> >>
https://lists.sourceforge.net/lists/listinfo/xcsoar-user> >>
> >>
> >
> >
>
> --
> View this message in context:
http://www.nabble.com/OpenAir-Format-in-XCSoar-tp17957479p17997901.html> Sent from the xcsoar-user mailing list archive at Nabble.com.
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
>
http://sourceforge.net/services/buy/index.php> _______________________________________________
> Xcsoar-user mailing list
>
Xcsoar-user@...
>
https://lists.sourceforge.net/lists/listinfo/xcsoar-user>
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php_______________________________________________
Xcsoar-user mailing list
Xcsoar-user@...
https://lists.sourceforge.net/lists/listinfo/xcsoar-user