To further that thought, I'd like to request dates added above the first line of airport data in each apt.dat file. I've tested info lines added to my apt.dat file and CVS FG has not had any issue reading the data. I do need to verify older versions will be able to still access it correctly. <!--Updated layout 12/18/09, Peter Brown --> In revising taxiways and layouts I find it to be helpful, and feel it may be in this case as well.
Thanks, Peter Sent from Smooth Water Sports, your Malibu Boat Dealer -----Original Message----- From: syd adams <adams....@gmail.com> Date: Fri, 18 Dec 2009 16:42:45 To: FlightGear developers discussions<flightgear-devel@lists.sourceforge.net> Subject: Re: [Flightgear-devel] --config nav.dat Maybe we could add a KSFO.dat , KHAF.dat, etc, somewhere in the Scenery/ section as a start... Its something I've always hoped for , anyway :) Cheers On 12/18/09, John Denker <j...@av8n.com> wrote: > Extended LOC volumes are fairly common. > Extended GS volumes are not so common, but > definitely exist. > > If anybody wants an example of an approach that > does require an extended service volume for the > GS (and LOC) ... take a look at KIAH ILS RWY 26R > > http://204.108.4.16/d-tpp/0912/05461IL26R.PDF > > =========================== > > The interesting wrinkle is that the current FG > apt.dat does not know that these navaids have > extended service volumes. > > 4 30.00716100 -095.36220300 91 11155 18 269.949 IOND KIAH 26R > ILS-cat-III > 6 30.00828100 -095.33396100 91 11155 10 300269.949 IOND KIAH 26R GS > 12 30.00599400 -095.36231900 84 11155 18 1.700 IOND KIAH 26R > DME-ILS > > >From time to time I hear someone recommend "let > Robin take care of it upstream". > > That's fine as a long-term strategy, but it doesn't > work in the short term, especially given how rarely > FG updates its copy. Also it is inconsistent with > the way FG handles other things, notably the very > powerful > > --config > > option that can be used on the command line or in the > .fgfsrc file. > > AFAICT the --config option is presently not, alas, > powerful enough to update the navaid database. > > Suggestion: It would be nice to have a configurable > _list_ of filenames to scan for navaid data: > nav.dat nav-2.dat et cetera. > > That way users could maintain short supplemental > files that would > a) tide them over during the oh-so-long time that > it takes to get updates into the "official" nav.dat > b) preserve the supplemental information across > updates of the "official" file. > c) not require the user to unpack and edit the > big "official" file. Conventional patch > utilities do not perform well on this task. > > Some cleverness needs to be applied to distinguish > the case where a navaid is being _replaced_ versus > the case where a navaid with a similar name is being > simply _added_. A simple "+" and "-" convention > should suffice. > > Similar remarks apply to apt.dat but that's more > complicated. I haven't thought about the details. > Adding and subtracting on an airport-by-airport > basis (as opposed to line-by-line) would be better > than nothing. > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
