Curtis L. Olson writes: > I should also say this really cool to be able to incorporate this data > directly. In terms of fixes though 72000 is an insane amount. For > anyone wanting to actaully draw these on a map, there is going to have > to be some sort of data reduction strategy. Does the DAFIFT file give > any hints or ranking of which are the more important or more widely > used fixes? There's about 15 fixes right on or very near the KSFO > airport property.
Different intersections and fixes server different purposes: the ones around KSFO are probably parts of various instrument approaches, and we would need most or all of them to simulate ATC or an approach-certified GPS. Just around Ottawa TCA, we have quite a few intersections. Here are the ones you'll find on an enroute chart, serving both for navigation through the Ottawa area and for transition from enroute to approach: LORKA EBNYR ASHTN AGLIN THURO AVVON REEDO ULAMO LANRK CYRIL HUXLY FANOL But those don't tell nearly the whole story. Most instrument approaches add more waypoints that don't appear on the enroute charts. For example, the ILS or NDB 32 approach adds the TEXEN GPS fix, while the ILS or NDB 07 approach adds the VISOL GPS fix. And so on. The DAFIF contains quite a few additional fields, including a usage code -- you could use that as a filter for generating different kinds of maps. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
