From: James T. <jam...@kd...> - 2017-07-04 18:08:26
|
Jumping in, I am on holiday until the 16th, and won't be looking a the computer much. But, we already have a ton of this code - sids, stars, approaches, tagging missed approach segments, fly-over vs fly-by waypoints. Yes we need some better data sources, especially with direct routing replacing airways in many areas, and having airspace data would help the map displays, but the current API is specifically designed to support G430, G1000 and similar class devices. Adding RNAV approaches is eminently doable, see the the RNavController base class which the GPS/FMS layer uses to allow new waypoint / route segments to define how they are flown and drive CDIs Kind regards, James Sent from my iPad > On 4 Jul 2017, at 18:09, David Megginson <dav...@gm...> wrote: > > Excellent start! Do they have approaches and enroute available as well? (A STAR is a standard published transition from enroute to approach, but not the approach itself.) |