Re: [Flightgear-devel] Fixpoints navaids
Am 10.11.11 12:14, schrieb HB-GRAL: Assuming the fix table should contain VFR waypoints mainly, another question might be if the fix table can be filtered (only for the map) into waypoints containing only VPXYZ-Point-Naming and others containing numbers ? Is this a bad idea (for the map) ? Please tell me if this a bad idea. I just added a filter to the fix data on the map: only 5 letters without numbers is shown (as a waypoint) -- map.fgx.ch, activating fix layer Thanks, Yves -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Fixpoints navaids
On 10 Nov 2011, at 07:36, HB-GRAL wrote: - Approach Fix - Intermediate Fix - Final Fix - MAPT - Step down - Fly-by - Fly-over - Co-located - Speed limit (?) Is there any possibility to classify the bare 8.50 fix database somehow, i.e. by name ? I can also start to provide other sources, but then the fix database needs updates outside xplane. Another question is, are current fixes also used for AI Traffic ? Some classification would be useful, but all the thins I think you're actually asking for, are related to approach departure procedures, AKA SIDs / STARs ... or whatever the correct terminology is today :) And in that regard, there's other sources data available, which have a much richer data-syntax (XML) that encodes most of the things you mention above (speeds, fly-over vs fly-by, IAF / FAF points, step down altitudes). FlightGear already supports reading one of these formats (the Level-D 767 format), and there are files available here: http://www.navdata.at/php/sidstar/dl_list.php?addon=LDS767 If you add, inside your Airports/I/C/A structure, the files for an airport, renamed to ICAO.procedures.xml, then the route-manager will load and use it. (based on runway, you can select a SID or STAR, and the waypoints are added to your route) At runtime, it's the various flightgear::Waypt subclasses that model the information mentioned above. And the GPS will attempt to fly the procedures, although compliance with altitude / speed limits is currently missing. Now, one step would be to make the AI traffic use this data if available, but there other issue, I've been busy on other areas since I added this code, so it has bugs - eg holds aren't support correctly, neither are DME arcs, and some DME intercepts don't work. All fixable, but it hasn't been a priority, since the feature is deliberately not exposed too loudly right now :) (Adding support for other input formats is possible, the Level-D format was simply the sanest of the ones offered on navdata.at. Also note the files are free to download, but GPL incompatible, so we couldn't ship them in the core data package) James -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Fixpoints navaids
Am 10.11.11 09:50, schrieb James Turner: On 10 Nov 2011, at 07:36, HB-GRAL wrote: - Approach Fix - Intermediate Fix - Final Fix - MAPT - Step down - Fly-by - Fly-over - Co-located - Speed limit (?) Is there any possibility to classify the bare 8.50 fix database somehow, i.e. by name ? I can also start to provide other sources, but then the fix database needs updates outside xplane. Another question is, are current fixes also used for AI Traffic ? Some classification would be useful, but all the thins I think you're actually asking for, are related to approach departure procedures, AKA SIDs / STARs ... or whatever the correct terminology is today :) And in that regard, there's other sources data available, which have a much richer data-syntax (XML) that encodes most of the things you mention above (speeds, fly-over vs fly-by, IAF / FAF points, step down altitudes). FlightGear already supports reading one of these formats (the Level-D 767 format), and there are files available here: http://www.navdata.at/php/sidstar/dl_list.php?addon=LDS767 If you add, inside your Airports/I/C/A structure, the files for an airport, renamed to ICAO.procedures.xml, then the route-manager will load and use it. (based on runway, you can select a SID or STAR, and the waypoints are added to your route) At runtime, it's the various flightgear::Waypt subclasses that model the information mentioned above. And the GPS will attempt to fly the procedures, although compliance with altitude / speed limits is currently missing. Now, one step would be to make the AI traffic use this data if available, but there other issue, I've been busy on other areas since I added this code, so it has bugs - eg holds aren't support correctly, neither are DME arcs, and some DME intercepts don't work. All fixable, but it hasn't been a priority, since the feature is deliberately not exposed too loudly right now :) (Adding support for other input formats is possible, the Level-D format was simply the sanest of the ones offered on navdata.at. Also note the files are free to download, but GPL incompatible, so we couldn't ship them in the core data package) James Hi James I just noticed that my confusion belongs to looking to the wrong table yesterday in my navaid database. Some ILS markers are separated in 8.50 data, and I will add this to the map. And for further SID/STAR there is a GPL source from former DAFIF data. Looks like this one is also used by ivao/vatsim. Is this data in the scenery too? I will give it a try for the map. Assuming the fix table should contain VFR waypoints mainly, another question might be if the fix table can be filtered (only for the map) into waypoints containing only VPXYZ-Point-Naming and others containing numbers ? Is this a bad idea (for the map) ? And when this all fails ... there are two other sources for navaids, GPL, which I used this summer for getting some other map data. But mainly I will try to follow original 8.50 xplane data, because then it will be in fg scenery too I think. And we are not alone. As I read xplane users following xplane data/routes are a very special celestial phenomena for some virtual ATCs. Cheers, Yves -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Fixpoints navaids
Hi all I tried to add 8.50 .dat version fixes to my map (map.fgx.ch) yesterday. I see that the database contains the name of the fix/waypoint and coordinates and no further cols. Wouldn’t some classification be useful, i.e. - Approach Fix - Intermediate Fix - Final Fix - MAPT - Step down - Fly-by - Fly-over - Co-located - Speed limit (?) Is there any possibility to classify the bare 8.50 fix database somehow, i.e. by name ? I can also start to provide other sources, but then the fix database needs updates outside xplane. Another question is, are current fixes also used for AI Traffic ? Cheers, Yves -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
