Curtis L. Olson writes:
> > Dave, > > Reference this image: > > http://www.flightgear.org/Gallery/Link/KSJC-signex4.html > > The sign would be defined by "Y<c>". > > - Capital letters are yellow on black. > - Lowercase letters are black on yellow > - '<' and '>' get mapped into arrows. > - We don't have a symbol for arrows pointing in other directions. > > > Additionally, does anyone have a description for the various letters > > used in the default.apt file, or is it necessary to e-mail Robin > > directly? > > I have made the FAQ for this file format available on the FlightGear > web page: > > http://www.flightgear.org/Docs/AirNav/AptNavFAQ.FlightGear.html OK, thanks a lot for all that. > > > FWIW, ground ATC control needs some sort of encoding of > > taxiway and hold point names in order to give plausible directions, > > so automatic placement of taxiway signage should come for free > > on the back of this. > > Robin's database has space for the taxiway names, but this information > is not been entered for any airports. If we had this info, we might > be able to make a plausible stab at autogenerating runway/taxiway > signs. Would not be an easy chore though ... > Yes, thats what I was getting at. I didn't realise he had a name space though - I was assuming I'd have to make my own database. I still think I'll have to infact, since the information in Robin's is very much orientated towards rendering the taxiways and aprons, rather than describing them as a network. At the very minimum I'd probably need to add some junction and hold fields. Cheers - Dave -- [EMAIL PROTECTED] _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
