Re: [Flightgear-devel] navaids update
Martin Spott a écrit : Salut Jean, jean pellotier wrote: Is nav.dat supposed to be updated from robin X-plane database? If nobody else is going to do that, I'll be updating the file from Robin's most current package during our pre-release phase (however this is going to be defined ). I see the update is done, thanks, (and sorry for windows users waiting for a compatible binary build :) ). It appears that Atlas don't like the new nav.dat.gz, and crash on start up, because some navaids contains empty field for the balise name (i guess it's the balise name). here's a diff where the missing fields are replaced with IXXX. may be the real name is available, but i didn't found the few i checked. and Atlas don't crash anymore. jano 12062c12062 4 47.49051500 -111.20608600 3526 10950 18 238.500 KGFA 21 ILS-cat-I --- 4 47.49051500 -111.20608600 3526 10950 18 238.500 IXXX KGFA 21 ILS-cat-I 12103c12103 4 38.85886700 -094.55694100 1090 10930 18 11.886 KGVW 01 ILS-cat-I --- 4 38.85886700 -094.55694100 1090 10930 18 11.886 IXXX KGVW 01 ILS-cat-I 12393c12393 4 46.5362 -087.54817000 1419 11050 18 76.841 KMQT 08 ILS-cat-I --- 4 46.5362 -087.54817000 1419 11050 18 76.841 IXXX KMQT 08 ILS-cat-I 13389c13389 4 70.33308600 -149.56581800 67 10970 18 107.900 PAKU 05 ILS-cat-I --- 4 70.33308600 -149.56581800 67 10970 18 107.900 IXXX PAKU 05 ILS-cat-I 14125c14125 5 45.29766700 -072.73483300375 11070 18 36.999 CZBM 05L LOC --- 5 45.29766700 -072.73483300375 11070 18 36.999 IXXX CZBM 05L LOC 14255c14255 5 35.27726300 -089.66926600312 11155 18 153.681 KLHC 15 LOC --- 5 35.27726300 -089.66926600312 11155 18 153.681 IXXX KLHC 15 LOC 14372c14372 5 70.25181500 -148.35802800 45 10970 18 106.500 PUO 05 SDF --- 5 70.25181500 -148.35802800 45 10970 18 106.500 IXXX PUO 05 SDF -- 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
Re: [Flightgear-devel] navaids update
Jean == jean pellotier writes: Jean I see the update is done, thanks, (and sorry for windows users Jean waiting for a compatible binary build :) ). It appears that Jean Atlas don't like the new nav.dat.gz, and crash on start up, Jean because some navaids contains empty field for the balise name Jean (i guess it's the balise name). Jean here's a diff where the missing fields are replaced with Jean IXXX. may be the real name is available, but i didn't found Jean the few i checked. Jean and Atlas don't crash anymore. Thanks for the fix. Although it doesn't really matter, Robin is in the habit of indicating no ID with ''. I've written to him about the navaids in question, since having a blank ID field seems to violate his file format specification. Brian -- Brian Schack 19 Xǔchāng Street 2Fphone: 2381 4727 Taipei 100 fax:2381 2145 TAIWAN -- 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
Re: [Flightgear-devel] navaids update
John Denker wrote: On the opposite side of the same coin, the last time I looked, the scenery database listed huge numbers of airports that were unknown to Robin's database. I don't know which scenery database you've been looking at, but it's certainly not been the one which we're using for building the FlightGear World Scenery from, aka. Landcover-DB, the one behind http://[mapserver,scenemodels].flightgear.org/ With probably _very_ few exceptions (one or two), the airport info of 'our' database has been populated from Robin's exports only, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- 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
Re: [Flightgear-devel] navaids update
On 12/19/2009 07:40 AM, Martin Spott wrote: ... Robin's current set of navaids ... contains navaids for airfields which are otherwise unknown to FlightGear, On the opposite side of the same coin, the last time I looked, the scenery database listed huge numbers of airports that were unknown to Robin's database. This has never been a problem AFAIK. Copying the files from Robin's current set of navaids leads to a fault since it contains navaids for airfields which are otherwise unknown to FlightGear, From the keen-grasp-of-the-obvious department: Maybe the code should be made more robust so that this is not a fault condition. This is not the first time in history that code has needed to perform a join on two databases that are not in one-to-one correspondence. -- 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
Re: [Flightgear-devel] navaids update
On 19 Dec 2009, at 16:19, John Denker wrote: Maybe the code should be made more robust so that this is not a fault condition. This is not the first time in history that code has needed to perform a join on two databases that are not in one-to-one correspondence. Well I wrote the code in question, and preferred to reject a corrupt data set rather than blindly carrying on - I am also a bit reluctant to encourage casual users to mess with a somewhat archaic data format. Nevertheless, it's pretty easy to tolerate this case, a fix will appear soon - the problem is some things aren't going to work, notably ILS - runway references. James -- 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
[Flightgear-devel] navaids update
Hi, I've got a question about the navaids, particularly nav.dat. Is nav.dat supposed to be updated from robin X-plane database? The french missing navaids I submited to robin ( approach locators ) are included in recent nav.dat from X-plane, and I was waiting them to come in Flightgear, but apparently we are using the version just before. here's a diff toward our current nav.dat with the missing french locators, if you find some interest in using french airports :) . jano --- fg_nav.dat 2009-12-14 11:22:24.0 +0100 +++ jjano_nav.dat 2009-12-14 11:22:02.0 +0100 @@ -1,6 +1,104 @@ I 810 Version - DAFIF data cycle 2007.09, build 20070106, metadata NavXP810. Copyright © 2007, Robin A. Peel (ro...@xsquawkbox.net). This data is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program (AptNavGNULicence.txt); if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA. This product was developed using DAFIF (the Defense Aeronautical Flight Information File), a product of the US National Imagery and Mapping Agency (NIMA). NIMA requires the following warranty statements: (A) Under 10 U.S.C. 456, no civil action may be brought against the United States on the basis of the content of a navigational aid prepared or disseminated by either the former Defense Mapping Agency (DMA) or the National Imagery and Mapping Agency (NIMA). (B) The DAFIF product is provided as is, and no warranty, express or implied, including, but not limited to the implied warranties of merchantability and fitness for particular purpose or arising by statute or otherwise in law or from a course of dealing or usage in trade, is made by NIMA as to the accuracy and functioning of the product. ©: Neither NIMA nor its personnel will be liable for any claims, losses, or damages arising from or connected with the use of this product. The user agrees to hold harmless the United States National Imagery and Mapping Agency. The user's sole and exclusive remedy is to stop using the DAFIF product. +2 43.9122 002.0644528 323 250.0 AB Albi le Sequestre NDB +2 49.9762 002.80941666361 321 1500.0 ABY Albert Bray NDB +2 43.26527778 005.58638000590 366 250.0 ADC Le Castellet NDB +2 44.1505 000.6738156 400 250.0 AG Agen la Garenne NDB +2 45.7105 000.4269397 404 250.0 AGO Angouleme Brie Champniers NDB +2 44.9558 002.3680 2310 343 250.0 AR Aurillac NDB +2 47.5772 -000.1513305 292 250.0 AS Angers Marce NDB +2 45.8616 006.0205 2205 384 250.0 AT Annecy Meythet NDB +2 44.4422 004.3619676 427 250.0 AUB Aubenas Ardeche Meridionale NDB +2 46.88167000 002.92888955679 306 250.0 AV Avord NDB +2 47.9202 003.5022505 417 250.0 AX Auxerre Branches NDB +2 47.6108 002.7827528 405 250.0 BIC Briare Chatillon NDB +2 45.52027800 004.29889000 1371 299 250.0 BO Saint Etienne Boutheon NDB +2 46.2038 005.2888869 423 250.0 BOR Bourg Ceyzeriat NDB +2 42.4258 009.5375 33 369 250.0 BP Bastia Poretta NDB +2 45.6158 004.99278000 1076 388 250.0 BR Lyons Bron NDB +2 47.0175 002.2816509 375 250.0 BRG Bourges NDB +2 44.3652 -001.1288 92 358 250.0 BRS Biscarrosse Parentis NDB +2 47.2669 006.2025 1348 370 250.0 BSV Besancon la Veze +2 49.4916 002.0294377 391 250.0 BV Beauvais Tille NDB +2 44.5669 003.4691 4062 393 250.0 BX Mende Brenoux NDB +2 46.7216 004.8430656 391 250.0 CC Chalon Champforgeuil NDB +2 45.8044 003.3616 1066 367 250.0 CF Clermond Ferrand Auvergne NDB +2 49.0052 002.7402352 370 250.0 CGZ Paris Charles de Gaulle NDB +2 45.5925 005.88361100840 346 250.0 CH Chambery Aix les Bains NDB +2 48.0077 003.6961545 353 250.0 CHY Chailley NDB +2 44.38527778 001.4155951 348 250.0 CL Cahors Lalbenque NDB +2 43.2225 002.2077489 345 250.0 CS Carcassonne Salvaza NDB +2 43.5228 007.04527778 98 385 250.0 CSC Cannes Mandelieu NDB +2 41.7952 008.7241295 387 250.0 CT Ajaccio Campo dell'Oro NDB +2 48.7591 004.3188604 347
Re: [Flightgear-devel] navaids update
Salut Jean, jean pellotier wrote: Is nav.dat supposed to be updated from robin X-plane database? If nobody else is going to do that, I'll be updating the file from Robin's most current package during our pre-release phase (however this is going to be defined ). here's a diff toward our current nav.dat with the missing french locators, if you find some interest in using french airports :) . I do - been flying there several times in real life and mostly had to do visual navigation because no navaids (neither VOR's nor anything else) had been installed on my routes :-) Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navaids update
Is nav.dat supposed to be updated from robin X-plane database? If nobody else is going to do that, I'll be updating the file from Robin's most current package during our pre-release phase (however this is going to be defined ). Can't the data be commited to CVS now ? pete -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
