Am Montag 12 Juni 2006 01:10 schrieb Ampere K. Hardraade: > On Saturday 10 June 2006 13:15, Tony Pelton wrote: > > heck, even taking the records, and stuffing those records, as they are > > now, into XML would be a start. > > Already in XML format... > > http://www.cs.yorku.ca/~cs233144/export_cyyz.svg > http://www.cs.yorku.ca/~cs233144/export_eddf.svg > http://www.cs.yorku.ca/~cs233144/export_eddh.svg > http://www.cs.yorku.ca/~cs233144/export_etou.svg > http://www.cs.yorku.ca/~cs233144/export_ksfo.svg
Which brings me to an idea. What if the airport format is enriched svg. That way the physical airport layout is in svg and might be viewed with a standard svg viever/editor. Converting electronic airport charts to svg works already. The logical layout (taxiway names, aprons, tower locations etc.) is then put on top of that (i.e. extra tags and attributes). Don't know wether svg editors will preserve unknown tags and attributes. If they do, the physical airport layout can then be changed with a standard svg drawing program (e.g. inkscape). Thomas _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
