Hi Torsten What are the plans now for apt.dat.gz and nav.dat.gz ? Will this prehistorical data files still be shipped with flightgear base package 2.8.0 ? As far as I understand flightgear is ready to read the newer formats and also the airport scenery tools are ready to use the newer formats. And there are some tendencies to keep this data out of the base package anyway and having a new organized data distribution (which is my favorite).
I am still comparing 810 data with 850 data for some older airport work done by flightgear contributors. Once this task has finished I will send converted data to the xplane database to be integrated where it makes sense and where I couldn't find original contributor (some airports have already been updated meantime by xplane contributors, so it is necessary to compare every airport and decide which one has more advanced or "better" data). I think it is a good choice to go for the new data format even because contributors are asked to send their edits to robin peels xplane datacenter since many years. Unfortunately 810 xplane data format will not be updated anymore, so without roadmap for a change there is only the possibility to have a own flightgear data distribution, missing huge updates from the last couple of years probably. On the other hand some terrasynced scenery data will be out of data sync probably for some months with the change, but I guess this is the part which can be updated out of core release cycles and base package anyway. Cheers, Yves Am 02.06.2012 um 21:36 schrieb Torsten Dreyer <tors...@t3r.de>: > Hi, > > in just a bit more than two weeks from now we reach June, 17th, marking > the first milestone for the release of next FlightGear version: the > "feature freeze" period. > > If you have some great and exciting new features for FlightGear on your > local disc but not yet pushed the gitorious repository - now is the time! > > Two questions have to be discussed and answered until the release > branches get created on July, 17th: > > 1) What's the version number of the new release? > a) 2.8.0 > b) 3.0.0 > > 2) Which aircraft do we ship in the base package? > a) just the c172 > b) same as before > c) [name your preferred aircraft] > > 3) Should we keep last year's commit policy for aircraft during the > feature freeze? > a) yes > b) no > > Regards, > Torsten > > > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel