> In real life, pilots (and ATC) uses terminal procedures of > each airport when approaching or departing. Example for KSFO: > http://flightaware.com/resources/airport/KSFO#terminalprocedures > > What about adding real SID/STAR procedures to FG? This will > make flying and communicating with ATC in FG more realistic. Not necessarily. When there is a radar service - and most airports I know do have a radar service - there are published procedures but they are usually not used because the approach controller guides you to the final approach by assigning the pilot individual headings, so called radar vectors. > > But there are three problems (as i understand this): > > 1. Where to find the database of SID/STAR of *all* airports? They are published in the AIP of the airports country. You can find the relevant AIP for europe at http://www.ead.eurocontrol.int/ and they change every now and then. > > 2. Database will be large. So we will have another big file > in FG distibutive, such as nav.dat.gz, awy.dat.gz, etc. This > means that FG will get more time to start and will use more > memory (?). Yes it will be large. It should be an optional feature to load. > > 3. Copyrights and law. Is it ok to use this type of data in FG? > Won't we have law problems with other authors? EUROCONTROL says on their site: <quote> Reproduction is authorised for personal use only provided the source is duly acknowledged. All other uses are prohibited. </quote>
I think it could be a cool feature but your biggest problem would be collecting the data and copyright issues. Greeting, Torsten ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
