Hi
Hallo Thomas !
Thomas Förster wrote:
> 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).
This idea actually _does_ have appeal - hey, I'm right now busy with
creating an SVG drawing - but I see one drawback here:
Airport-creators or -maintainers are not _forced_ to think of the
logical layout. Let's assume some flight simulation does not honour the
logical layout at all and we'll experience people submitting airports
without _any_ logic, not even the direction of the taxiway centerline,
just consisting of the outlines of taxiways and runways.
In order to do it 'right' (TM, yes, I know ;-) I'd prefer to have an
airport description language that consists of nothing but the logical
layout at least for those objects, that relate to the core airport
operations (runway, taxiway, apron, tower location), forcing the user
to create a logical sense behind _every_ object. Yes, I feel that this
path might be a bit steep in the beginning but I believe it's the only
one that saves us from major trouble once we expect every airfield to
contain a certain amount of logic and realizing that noting's there.
Opinions ?
I must admit that from reading some explanations on the 8.50 format I
still didn't understand which route this new format is heading for - I
simply failed to find the logic in the description ....
Regards,
Martin.
--
Agreed.... if I understand you ....placing "blobs" on a layout just to get
the outline right is not productive in the long run.... it might solve an
immediate problem but doesn't contribute to the maintenance of that data....
hence curves are going to be necessary to allows whatever tools to enforce
the "certain amount of logic" ideal....
...as mentioned I believe there will be a degree of resistance if it is
perceived that current tools (that people are familiar with) won't be
"valid"... I don't believe this is a reason not to pursue the "certain
amount of logic" ideal, but a reason to mitigate a migration path that
everyone involved, understands.
:-D ene
_________________________________________________________________
Shop til you drop at XtraMSN Shopping http://shopping.xtramsn.co.nz/home/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
