In the not so far future, there will be a much inproved system to submit airport layouts. Read about it on http://developer.x-plane.com/2013/12/airport-authoring-sharing-airports/ And our scenery generation tools are in a much better shape than before, so more frequent scenery rebuilds will be possible.
> Date: Fri, 7 Mar 2014 15:14:35 +0100 > From: email@example.com > To: firstname.lastname@example.org > Subject: Re: [Flightgear-devel] apt.dat > > On 03/06/2014 11:07 PM, Thomas Riemer wrote: > > d) What does that lat, lon actually refer to? (This turns out to > > be an interesting question in > > general for real airports) anyone? > > Probably, it is the ARP. > http://en.wikipedia.org/wiki/Airport_reference_point It is a standard > location published in your national AIP. > > > 1) lines in apt.dat that start with code 10 - that is not > > specified in the apt documentation from x-plane > > Taxiways, defined as rectangles. A heritage from the old v810 data > format. Airports with these lines are not updated yet to the new format. > Look for the description of these lines in: > http://data.x-plane.com/file_specs/Apt810.htm > > > 2) lines in apt.dat that start with 99 - again not specified in the > > docs. ?? Anyone? > > EOF (end of file) If there are several lines with this code... it is > probably an error. > > AFAIK, all tools in FlightGear and TerraGear just ignore this line. > > > I've heard the name Robin Peel - perhaps those should be sent to > > him... > > Sometimes, it is difficult to reach Robin: he usually takes months to > answer an e-mail. > > I'm sure there are good reasons for this. He is probably a busy person > in real life and, at the end of the day, an updated apt.dat is not as > important in X-Plane as it is in FlightGear. But I'm sure this lack of > responsiveness from Robin's side is going to affect the quality of our > scenery. > > The standard answer when someone asks how to update an airport is "draw > the layout in WED and send the data to Robin". This policy is something > the FligthGear community has to reconsider seriously. Drawing the > airport in WED takes from one evening to one week, depending on the > complexity of the airport. But this is only the beginning. The process > of sending the airport to Robin, getting an answer from him, waiting for > an update of apt.dat and waiting an update of our sceneries takes at > least a year, and most probably more. And you have to repeat the > complete process if Robin didn't merge your data correctly, as > unfortunately have happened in the past. > > Regards > > -- > Juan Vera del Campo (juanvi) > > > ------------------------------------------------------------------------------ > Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. > With Perforce, you get hassle-free workflows. Merge that actually works. > Faster operations. Version large binaries. Built-in WAN optimization and the > freedom to use Git, Perforce or both. Make the move to Perforce. > http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk > _______________________________________________ > Flightgear-devel mailing list > Flightgearemail@example.com > https://lists.sourceforge.net/lists/listinfo/flightgear-devel