Yves > -----Original Message----- > From: HB-GRAL [mailto:flightg...@sablonier.ch] > Sent: 10 December 2011 10:25 > To: FlightGear developers discussions > Subject: Re: [Flightgear-devel] apt.dat update (lowercase names etc.) > > Am 10.12.11 07:52, schrieb Tuomas Kuosmanen: > > Wouldn't it be useful to somehow flag the airport as > > closed/restricted/whatever in the data, so that nav displays and gps/fms > > units could show a different airfield symbol if desired for closed > > airports? Does the data format support this? > > There is one "field" left in apt.dat airport line which is deprecated. > This would be the only possibility to set a flag (0=open, 1=closed ?), > but I think with this flag set FG apt.dat is not compatible anymore with > original xplane data. > > I guess some "external" apt.dat readers around use the [X] somehow ? > > (Remark: What I wrote about FAA and "Cl" is wrong, there are three > states in US data: CI - closed indefinitely; CP - closed permanently; O > - operational, so closed in apt.dat should mean "CP" I think.) >
I think the difference between CI and CP is too subtle to matter to us. If we only have a binary value then we should think O = 1, 'not O' = 0 where 'not O' = CI or CP. If we can have a ternary value then O = nil or undefined, CI = 0 and CP = 1 Works for me anyway. Vivian ------------------------------------------------------------------------------ Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
