Hi
Having edited airports there are a few things that tools like TaxiDraw
provide that are invaluable;
1) super-imposing the airport layout on top of a scaled background image to
allow placement of taxiways etc in proportion to the RL layout.
2) providing lat/long readout for any point on the layout.
3) showing centre lines for runways/taxiways.
4) catering for such things as edge lighting and centre line lighting etc.
5) exporting the beacon information to stg files
not to mention; layering info, (even biezer curves will need layering at the
interfaces), surface types etc.
If a program like Inkscape can duplicate this and is multiplatform then by
all means.....
As you might have gathered, I have no experience with Inkscape and am
looking for comments and affirmations rather than flame-wars...
I believe a more generic and structured approach to the apt format is
desirable as long as there isn't a re-adjustment period that means we are
left devoid of current capabilities.
I also see merit in maintaining a commonality between x-plane ad fgfs as it
increases the resources available for further development albeit on a
cooperative basis.
We also need to keep in mind that a number of people have devoted a large
amount of time and effort to interfacing with the apt.dat format, I feel
their voices should be most prominent when any change like this is
considered.
:-D ene
From: Thomas Förster <[EMAIL PROTECTED]>
Reply-To: FlightGear developers discussions
<flightgear-devel@lists.sourceforge.net>
To: FlightGear developers discussions
<flightgear-devel@lists.sourceforge.net>
Subject: Re: [Flightgear-devel] apt.dat changes ?
Date: Mon, 12 Jun 2006 09:50:12 +0200
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
_________________________________________________________________
Need more speed? Get Xtra Broadband @
http://jetstream.xtra.co.nz/chm/0,,202853-1000,00.html
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
