I'd suggest that contributions should consist of any sort of archive files that contain everything which is necessary to define the object and it's location .... like
for EDLN. I'm convinced I'll find a way to merge the objects and provide useful packages to Curt and the user community,
It's not easy to update an airport like that, since the airport model requires a suitably sized/shaped hole in the terrain. This works well for objects sitting *on* the terrain though, with 1 slight limitation - if 2 people are working on different airports in the same tile then updates from 1 person would overwrite the changes from another if the entire stg file was provided. A database gets around this problem, since objects are only allocated to tiles when the data is exported to the scenery.
_______________________________________________ Flightgear-devel mailing list Flightgearemail@example.com http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d