On Monday 29 November 2004 09:17, Chris Metzler wrote: > Looking cool! > > I'm curious whether you have ideas on how to generate traffic data > (flights and flightplans) for the aircraft that the TrafficManager > and AIManager will handle. Are you thinking of doing real-world > flights? If so, is there a good place to harvest that data? Thoughts > on how to convert it into flightplans of the style you use?
Many ideas, but no real solutions yet. I have made a few example traffic files by hand, based on airline and airport time tables and some imagination. Flight plans are currently autogenerated by FlightGear. Nothing fancy, but just a set of waypoints connecting the center point of the departure and arrival airports, using a runway for take-off. I don't know of any good data source for traffic schedules. Eventually, I'm hoping to be able to use the data from projectAI (http://www.projectai.com), using a conversion tool that exports their data into a FlightGear format xml file. I'm unable to contact them, however, because their contact email addresses appear not to be working. I'm thinking about making my conversion script available for download, so that users could download their own favorite PAI files and convert them to flightgear format. AFAICT, that wouldn't be in violation of their licence. I've also started writing a small tutorial on creating traffic files, but that's not ready for release yet. > > Given the work that still needs to be done, there's clearly no > urgency to this. I'm just curious what direction you're going > . . . Aside from finishing the tutorial and updating the pai-conversion script, I'm trying to add more realistic airport parking and taxi behavior. Once that's in place separation handling would be next. This is indeed not something that I expect to finish off soon. > > Anyway, cool stuff. > > -c Cheers, Durk _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
