Catalog metadata: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
No edit summary
(→‎Wiki articles: + FlightGear hangars#Third party sites)
(23 intermediate revisions by 4 users not shown)
Line 1: Line 1:
Tags with '''catalog metadata''' can be added to aircraft to help searching and filtering them, for example in future versions of the [[Aircraft Center|aircraft center]], so that a user can quicker find the aircraft of interest.
Tags with '''catalog metadata''' can be added to aircraft to help searching and filtering them, for example in the launcher or future versions of the [[Aircraft Center|aircraft center]], so that a user can quicker find the aircraft of interest.


{{FGCquote
{{Package Management}}
  |the goal here is to almost get rid of a centralised aircraft repo anyway, and have a decentralised development system with the only central point being the aircraft package manager for end users. Then 99% of people never care where the aircraft is stored while it’s developed.
 
  |{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33413096/
== Status/news ==
    |title=<nowiki>Re: [Flightgear-devel] FGDATA split without Aircraft. Addon in SVN.
Now that James has merged the preview and [[splash screen]] changes, he wants to start a concerted effort to improve the metadata of all the aircraft in FGaddon. This means:  
(re)Suggesting a Submodule approach. (Re)Proposing a per-Aircraft
 
repository</nowiki>
* Ensuring there is a suitable "long" description
    |author=<nowiki>James Turner</nowiki>
* Adding or updating ratings
    |date=<nowiki>2015-02-13</nowiki>
* Ensuring variant or primary info is correct
  }}
* Ideally adapting to the new preview/splash system (but not required)
}}
* Adding metadata tags, for better searching/usability the future


{{FGCquote
All of these are intended to help users browsing the aircraft, via the launcher or other methods. The proposal by James is to post about this on the forum, and ask for volunteers to pick aircraft, and submit patches or updates to myself and some other willing reviewers (Stuart has also volunteered as reviewer, but more people are welcome). Aside form ensuring high quality, we also need to ensure that aircraft maintainers are given the opportunity to update their own aircraft. Any co-volunteers to manage the process, and especially suggestions on how to manage this in a way that is friendly towards aircraft maintainers, but also gives a reasonable chance that 90% of aircraft in FGaddon have up to date metatdata by the next release, are welcome. I am sure we will have the usual debate on subjectivity of ratings, but, that’s another thing the reviewers will have to deal with. (James Turner suggested there is some criteria on the wiki from the last time we did this?) (There is a task on me to link the tagging system into the aircraft search, so that searching on "fighter" or "glass-cockpit" brings up appropriate matches. This tends to work out anyway when aircraft have a long-description text, but it is still very beneficial to the launcher to have some meta-data about how aircraft are used).<ref>{{cite web
  | The goal is that no one except people working on an individual aircraft should care where it’s developed at all (on GitHub, in a private SVN repo, stored as sheets of paper in a filing cabinet). SCM systems are not distribution/release systems, we’ve simply been using them in that fashion by accident.
  |url   = https://sourceforge.net/p/flightgear/mailman/message/35688820/  
  |{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33550567/
  |title = <nowiki>[Flightgear-devel] Improving FGaddon aircraft meta-data </nowiki>
    |title=<nowiki>Re: [Flightgear-devel] FGData size reduction</nowiki>
  |author = <nowiki> James Turner </nowiki>  
    |author=<nowiki>James Turner</nowiki>
  |date   =  Feb 26th, 2017
    |date=<nowiki>2015-03-06</nowiki>
  |added  = Feb 26th, 2017
  }}
  |script_version = 0.40
}}
  }}</ref>


== Catalogs ==
The overall aim is to support a decentralized development system with the only central point being the aircraft package manager for end users.<ref>{{cite web
    |url = http://sourceforge.net/p/flightgear/mailman/message/33413096/
    |title = <nowiki>Re: [Flightgear-devel] FGDATA split without Aircraft. Addon in SVN. (re)Suggesting a Submodule approach. (Re)Proposing a</nowiki>
    |author = <nowiki>James Turner</nowiki>
    |date = <nowiki>2015-02-13</nowiki>
}}</ref>.  Users can simply add a hangar URL for FGUK, Lake of Constance or similar, and browse those aircraft within the launcher. 


{{FGCquote
Most importantly we can improve the end-user browsing and discovery experience by enforcing some required meta-data, images and similar in the catalogs, and we can manage the install process so that users don’t get confused about where to move an aircraft file.<ref>{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33586444/
  |If you wish to dig into the package system, and create some tooling so it’s easy to publish releases from a Git repo to a web-host, please do. The current script is in fgmeta; see ‘create_catalog.py’ which runs over FGData of course, but you can imagine something similar for any SCM store containing several aircraft. There’s additional features that can be added of course, such as support for ‘beta’ or ‘testing’ versions of aircraft, being able to exist alongside stable versions. That would require some C++ hacking on the client side but pretty straightforward stuff I think.
     |title=<nowiki>Re: [Flightgear-devel] FGDATA and Jenkins </nowiki>
  |{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33550567/
     |title=<nowiki>Re: [Flightgear-devel] FGData size reduction</nowiki>
     |author=<nowiki>James Turner</nowiki>
     |author=<nowiki>James Turner</nowiki>
     |date=<nowiki>2015-03-06</nowiki>
     |date=<nowiki>2015-03-11</nowiki>
  }}
}}</ref>
}}


{{FGCquote
FGMeta contains a <code>create_catalog.py</code> script which runs over FGAddon but could be used against another aircraft store containing multiple aircraft to generate a catalog used by the launcher in combination with a webhost to publish aircraft to users.<ref>{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33550567/
  |For all other aircraft, the intention for both these nightly builds and official releases is to use the aircraft catalog + package system, which is based around HTTP rather than an SCM system. I’m working at the moment on integrating the client parts into the launcher GUI.
     | title=<nowiki>Re: [Flightgear-devel] FGData size reduction </nowiki>
  |{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33586444/
     |title=<nowiki>Re: [Flightgear-devel] FGDATA and Jenkins</nowiki>
     |author=<nowiki>James Turner</nowiki>
     |author=<nowiki>James Turner</nowiki>
     |date=<nowiki>2015-03-11</nowiki>
     |date=<nowiki>2015-03-06</nowiki>
  }}
}}</ref>
}}


{{FGCquote
The catalog is just an XML file, and the other files needed are the thumbnail images for each package, and the package Zip files themselves; The system is deliberately designed to be able to be hosted statically on any web provider. The <code>create_catalog.py</code> gives one example of creating a suitable catalog XML file, but any other approach is also valid.<ref>{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33586444/
  |This is the way to decentralise aircraft deployment and discovery - ‘we’ (the project) will provide an official hangar of course but the idea is any end-user can add the hangar URL for FGUK, Lake of Constance or similar, and get those aircraft. Most importantly we can improve the end-user browsing and discovery experience by enforcing some required meta-data, images and similar in the catalogs, and we can manage the install process so that users don’t get confused about where to move an aircraft file.<br/>
<br/>
(Many end users struggle with the aircraft zips, they’re unsure if they need to extract them or not, and whereabouts to copy them, and what paths to set so the aircraft is usable. The package system is designed to avoid those issues)
  |{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33586444/
     |title=<nowiki>Re: [Flightgear-devel] FGDATA and Jenkins</nowiki>
     |title=<nowiki>Re: [Flightgear-devel] FGDATA and Jenkins</nowiki>
     |author=<nowiki>James Turner</nowiki>
     |author=<nowiki>James Turner</nowiki>
     |date=<nowiki>2015-03-11</nowiki>
     |date=<nowiki>2015-03-11</nowiki>
  }}
}}</ref>
}}


{{Package Management}}
== Supported Tags ==
== Supported Tags ==
{{Note|Please do not extend this list without discussion and agreement.}}
{{Note|Please do not extend this list without discussion and agreement.}}


The tags are translation / search keys, not human-readable strings. Any additions or changes mean updated translation files. The catalog-generator script will reject aircraft with non-standard tags!
The tags are translation and search keys, not human-readable strings. Any additions or changes mean updated translation files. The catalog-generator script will reject aircraft with non-standard tags!


Tags are designed to be inclusive, not exclusive, to give the broadest range of search results. If multiple tags apply, use them - for example the DC-3 has had multiple civilian and military roles.
The definitive list of tags can be found here: https://sourceforge.net/p/flightgear/fgmeta/ci/next/tree/python3-flightgear/flightgear/meta/aircraft_catalogs/catalogTags.py
Tags are designed to be inclusive, not exclusive, to give the broadest range of search results. If multiple tags apply, use them. The DC-3 for example have had multiple civilian and military roles.


=== Aircraft types ===
=== Aircraft types ===
* ga
 
* helicopter
* <code>aerobatic</code>
* fighter
* <code>airship</code>
* interceptor
* <code>balloon</code>
* glider - But does this includes the Space Shuttle, Virgin Galactic's SpaceShipeOne, as well?
* <code>bizjet</code>
* spaceship
* <code>bomber</code>
* bomber
* <code>cargo</code>
* tanker
* <code>carrier</code>
* cargo
* <code>fighter</code>
* passenger
* <code>ga</code>
* bizjet - Not just for jets, but I can't think of a better term
* <code>glider</code>
* reconnaissance
* <code>groundvehicle</code>
* airship
* <code>helicopter</code>
* balloon
* <code>interceptor</code>
* trainer - Used in a pilot training role
* <code>passenger</code>
* <code>racer</code>
* <code>spaceship</code>
* <code>tanker</code>
* <code>trainer</code>
* <code>transport</code>
* <code>ultralight</code>
* <code>unpowered</code>
* <code>uav</code>
* <code>reconnaissance</code>
* <code>seacraft</code>
* <code>crop-duster</code>
* <code>bush-plane</code>


=== Manufacturers ===
=== Manufacturers ===
Intention here is to provide logical groupings, not to track corporate history - so the MD-80 and MD-11 would get the 'douglas' tag, which will likely translate to 'Douglas / McDonell-Douglas' in the UI. The 717 could get the boeing and douglas tags. Also not supposed to be an exhaustive list, this is so we can search on 'all glass-cockpit Boeing and Airbus aircraft'. It might be worth actively lying in the tags, i.e group all Hawker-Siddley / BAC / Avro aircraft under the Vickers tag.
The intention here is to provide logical groupings, not to track corporate history. For example the MD-80 and MD-11 would get the <code>douglas</code> tag, which will likely translate to "Douglas / McDonell-Douglas" in the user interface. The Boeing 717 could get the <code>boeing</code> and <code>douglas</code> tags. Also it is not supposed to be an exhaustive list. This is so we for example can search for "all glass-cockpit Boeing and Airbus aircraft". It might be worth actively lying in the tags, in essence group all Hawker-Siddley/BAC/Avro aircraft under the <code>vickers</code> tag.
 
* <code>airbus</code>
* <code>antonov</code>
* <code>arado</code>
* <code>atr</code>
* <code>avro</code>
* <code>bae</code>
* <code>bell</code>
* <code>bleriot</code>
* <code>boeing</code>
* <code>bombardier</code>
* <code>caudron</code>
* <code>cessna</code>
* <code>consolidated</code>
* <code>dassault</code>
* <code>diamond</code>
* <code>dornier</code>
* <code>douglas</code>
* <code>embraer</code>
* <code>eurocopter</code>
* <code>fairchild</code>
* <code>fairey</code>
* <code>focke-wulf</code>
* <code>fokker</code>
* <code>general-dynamics</code>
* <code>gotha</code>
* <code>grumman</code>
* <code>handley-page</code>
* <code>hawker</code>
* <code>heinkel</code>
* <code>ilyushin</code>
* <code>junkers</code>
* <code>kawasaki</code>
* <code>lockheed</code>
* <code>mc-donnell-douglas</code>
* <code>messerschmitt</code>
* <code>mikoyan-gurevich</code>
* <code>mitsubishi</code>
* <code>north-american</code>
* <code>northrop</code>
* <code>pilatus</code>
* <code>piper</code>
* <code>republic</code>
* <code>robin</code>
* <code>rockwell</code>
* <code>saab</code>
* <code>short</code>
* <code>sopwith</code>
* <code>spad</code>
* <code>sukhoi</code>
* <code>supermarine</code>
* <code>tupolev</code>
* <code>vickers</code>
* <code>vought</code>
* <code>wright</code>
* <code>yakovlev</code>


* boeing
* cessna
* douglas
* lockheed
* vickers
* piper
* diamond
* airbus
* beechcraft
* mig
* fokker
* ilyushin
* antonov
* embrarer
* bombardier
* saab


=== Eras ===
=== Eras ===
Logical groupings, not historical accuracy - some aircraft are going to have a lot of these, e.g. the B-52. Again the goal is intelligent searches: 'show me all WW2 fighters'. Would like to avoid this getting political too, comments on that are welcome
Logical groupings, not historical accuracy. Some aircraft are going to have a lot of these, for example the B-52. Again the goal is intelligent searches: "show me all WW2 fighters". Wee would like to avoid this getting political too and comments on that are welcome.


* early-pioneers
* <code>1910s</code>
* ww1
* <code>1920s</code>
* 1920s
* <code>1930s</code>
* 1930s
* <code>1940s</code>
* golden-age
* <code>1950s</code>
* ww2
* <code>1960s</code>
* 1950s
* <code>1970s</code>
* 1960s
* <code>1980s</code>
* 1970s
* <code>1990s</code>
* vietnam
* <code>2000s</code>
* coldwar
* <code>2010s</code>
* korean
* <code>coldwar</code>
* 1980s
* <code>early-pioneers</code>
* 1990s
* <code>golden-age</code>
* gulfwar1
* <code>gulfwar1</code>
* 2000s
* <code>gulfwar2</code>
* <code>vietnam</code>
* <code>ww1</code>
* <code>ww2</code>


=== Aircraft Features ===
=== Aircraft Features ===
This could get long, as always trying to focus on tags people might search on - 'show me all the VTOL aircraft' or 'show me all the biplanes'. Some will be very useful in improving the user-experience, if the plane is tagged with seaplane we might be able to force a water start (not for amphibious obviously).
This could get long, as always trying to focus on tags people might search for, for example: "show me all the VTOL aircraft" or "show me all the biplanes". Some will be very useful in improving the user experience; If the plane is tagged with seaplane we might be able to force a water start (but not for amphibious aircraft obviously).


* prototype
* <code>aerobatic</code>
* experimental - For X1 and similar X-planes
* <code>airship</code>
* ifr - Panel and equipment (radios, lighting) suitable for IFR flight
* <code>amphibious</code>
* fixed-gear
* <code>biplane</code>
* retractable-gear
* <code>canard</code> - Canard planform
* tail-dragger
* <code>castering-wheel</code>
* carrier-hook - Do we need a separate tag for carrier-capable?
* <code>combat</code>
* stol - For short-takeoff
* <code>delta</code> - Delta planform; Vulcan, Concorde, Space Shuttle
* vtol - For the Harrier, F-35 if it ever works, and the Osprey
* <code>etops</code> - ETOPS capable aircraft, presumably implies twin-engined
* floats
* <code>experimental</code> - For X1 and similar X-planes
* amphibious
* <code>fictional</code>
* cannard - Cannard planform
* <code>fixed-gear</code>
* delta - Delta planform; Vulcan, Concorde, Space Shuttle
* <code>floats</code>
* variable-geometry - For Tomcats and the like
* <code>glass-cockpit</code>
* supersonic
* <code>low-wing</code>
* glass-cockpit
* <code>mid-wing</code>
* refuel - Supports air-to-air refeuling
* <code>high-wing</code>
* seaplane - Flying boat or float plane
* <code>h-tail</code>
* etops - ETOPS capable aircraft, presumably implies twin-engined
* <code>hud</code>
* biplane
* <code>ifr</code> - Panel and equipment (radios, lighting) suitable for IFR flight
* triplane
* <code>lifting-body</code>
* pressurised - Pressurised cabin
* <code>pressurised</code> - Pressurised cabin
* <code>prototype</code>
* <code>refuel</code> - Supports air-to-air refeuling
* <code>retractable-gear</code>
* <code>seaplane</code> - Flying boat or float plane
* <code>skis</code>
* <code>stol</code> - For short-takeoff
* <code>supersonic</code>
* <code>supercharger</code>
* <code>t-tail</code>
* <code>tail-dragger</code>
* <code>tricycle</code>
* <code>tail-hook</code>
* <code>triplane</code>
* <code>twin-boom</code>
* <code>v-tail</code>
* <code>variable-geometry</code> - For Tomcats and the like
* <code>vtol</code> - For the Harrier, F-35, and the Osprey
* <code>wing-fold</code> - usually for carrier aircraft
* <code>water-drop</code>


=== FlightGear Features ===
=== FlightGear Features ===
* combat - Support this various MP combat / bomb-able options
* <code>combat</code> - Support this various MP combat / bomb-able options
* dual-controls - Supports copilot over MP
* <code>dual-controls</code> - Supports copilot over MP
* tow - Supports glider towing over MP
* <code>tow</code> - Supports glider [[towing]] over MP
* rembrandt - Supports Rembrandt, obviously
* <code>rembrandt</code> - Supports Rembrandt, obviously


=== Propulsion ===
=== Propulsion ===
* piston
* <code>afterburner</code>
* radial - Radial piston engined
* <code>diesel</code>
* diesel
* <code>electric</code> - For power-assisted gliders, mostly.
* jet
* <code>jet</code>
* turboprop
* <code>propeller</code>
* 1-engine
* <code>piston</code>
* 2-engine
* <code>radial</code> - Radial piston engined
* 3-engine
* <code>rocket</code>
* 4-engine
* <code>single-engine</code>
* turbocharged - For pistons with a turbo-charger
* <code>supercharged</code>
* afterburner
* <code>turboprop</code> - For pistons with a turbo-charger
* rocket
* <code>twin-engine</code>
* electric - For power-assisted gliders, mostly.
* <code>four-engine</code>
* unpowered - Balloons, etc
* <code>variable-pitch</code>
* <code>fixed-pitch</code>


== Examples ==
== Examples ==
* B-52 would have: bomber, jet. boeing, coldwar, 1960s, vietnam, 1970s, 1980s, gulfwar1, nato, refuel, retractable-gear, ifr
* B-52 would have: <code>bomber</code>, <code>jet</code>, <code>boeing</code>, <code>coldwar</code>, <code>1960s</code>, <code>vietnam</code>, <code>1970s</code>, <code>1980s</code>, <code>gulfwar1</code>, <code>nato</code>, <code>refuel</code>, <code>retractable-gear</code> and <code>ifr</code>.
* Citation would have: cessna, bizjet, jet, 2-engine, glass-cockpit, ifr, retractable-gear
* Citation would have: <code>cessna</code>, <code>bizjet</code>, <code>jet</code>, <code>2-engine</code>, <code>glass-cockpit</code>, <code>ifr</code> and <code>retractable-gear</code>.
* Cub would have: piper, piston, 1-engine, ga, trainer, fixed-gear, 1930s, ww2, tail-dragger
* Cub would have: <code>piper</code>, <code>piston</code>, <code>1-engine</code>, <code>ga</code>, <code>trainer</code>, <code>fixed-gear</code>, <code>1930s</code>, <code>ww2</code> and <code>tail-dragger</code>.


== Adding metadata to aircraft ==
== Adding metadata to aircraft ==
The tags are added to or included into the sim section of the -set.xml file(s) like for example below:
The tags are added to or included into the <code><nowiki><sim></nowiki></code> section of the [[Aircraft-set.xml]] file(s), like for example below:


<syntaxhighlight lang="xml">
<syntaxhighlight lang="xml">
Line 176: Line 247:


<PropertyList>
<PropertyList>
<!-- ... -->


  <sim>
  <sim>
  <!-- ... -->


   <tags>
   <tags>
Line 189: Line 264:
   <tag>ifr</tag>
   <tag>ifr</tag>
   </tags>
   </tags>
  <!-- ... -->


  </sim>
  </sim>
<!-- ... -->


</PropertyList>
</PropertyList>


</syntaxhighlight>
</syntaxhighlight>
== References ==
<references />


== Related content ==
== Related content ==
=== Wiki articles ===
* [[Aircraft rating system]]
* [[Aircraft-set.xml]]
* [[FlightGear hangars#Third party sites]] - List of third-party hangars, of which some have an <code>catalog.xml</code> file.
* [[Hangar catalog]]
* [[Simplifying Aircraft Deployment]]
* [[Simplifying Aircraft Deployment]]
=== Forum topics ===
* {{forum link|t=31915|text=Help tag aircraft}} (March-June 2017)
=== Developer mailing list threads ===
* {{cite web |url=http://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/D4E91618-5AE0-4073-98B3-43711E70871A%40mac.com/#msg32375981 |title=<nowiki>[</nowiki>Flightgear-devel<nowiki>]</nowiki> 24 days from freeze: what happened to...}}
* {{cite web |url=http://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/D4E91618-5AE0-4073-98B3-43711E70871A%40mac.com/#msg32375981 |title=<nowiki>[</nowiki>Flightgear-devel<nowiki>]</nowiki> 24 days from freeze: what happened to...}}
=== Source code ===
* {{fgmeta source|path=catalog/catalogTags.py}}


[[Category:Core development projects]]
[[Category:Core development projects]]
[[Category:Aircraft enhancement]]

Revision as of 11:57, 10 October 2020

Tags with catalog metadata can be added to aircraft to help searching and filtering them, for example in the launcher or future versions of the aircraft center, so that a user can quicker find the aircraft of interest.

Status/news

Now that James has merged the preview and splash screen changes, he wants to start a concerted effort to improve the metadata of all the aircraft in FGaddon. This means:

  • Ensuring there is a suitable "long" description
  • Adding or updating ratings
  • Ensuring variant or primary info is correct
  • Ideally adapting to the new preview/splash system (but not required)
  • Adding metadata tags, for better searching/usability the future

All of these are intended to help users browsing the aircraft, via the launcher or other methods. The proposal by James is to post about this on the forum, and ask for volunteers to pick aircraft, and submit patches or updates to myself and some other willing reviewers (Stuart has also volunteered as reviewer, but more people are welcome). Aside form ensuring high quality, we also need to ensure that aircraft maintainers are given the opportunity to update their own aircraft. Any co-volunteers to manage the process, and especially suggestions on how to manage this in a way that is friendly towards aircraft maintainers, but also gives a reasonable chance that 90% of aircraft in FGaddon have up to date metatdata by the next release, are welcome. I am sure we will have the usual debate on subjectivity of ratings, but, that’s another thing the reviewers will have to deal with. (James Turner suggested there is some criteria on the wiki from the last time we did this?) (There is a task on me to link the tagging system into the aircraft search, so that searching on "fighter" or "glass-cockpit" brings up appropriate matches. This tends to work out anyway when aircraft have a long-description text, but it is still very beneficial to the launcher to have some meta-data about how aircraft are used).[1]

Catalogs

The overall aim is to support a decentralized development system with the only central point being the aircraft package manager for end users.[2]. Users can simply add a hangar URL for FGUK, Lake of Constance or similar, and browse those aircraft within the launcher.

Most importantly we can improve the end-user browsing and discovery experience by enforcing some required meta-data, images and similar in the catalogs, and we can manage the install process so that users don’t get confused about where to move an aircraft file.[3]

FGMeta contains a create_catalog.py script which runs over FGAddon but could be used against another aircraft store containing multiple aircraft to generate a catalog used by the launcher in combination with a webhost to publish aircraft to users.[4]

The catalog is just an XML file, and the other files needed are the thumbnail images for each package, and the package Zip files themselves; The system is deliberately designed to be able to be hosted statically on any web provider. The create_catalog.py gives one example of creating a suitable catalog XML file, but any other approach is also valid.[5]

Supported Tags

Note  Please do not extend this list without discussion and agreement.

The tags are translation and search keys, not human-readable strings. Any additions or changes mean updated translation files. The catalog-generator script will reject aircraft with non-standard tags!

The definitive list of tags can be found here: https://sourceforge.net/p/flightgear/fgmeta/ci/next/tree/python3-flightgear/flightgear/meta/aircraft_catalogs/catalogTags.py Tags are designed to be inclusive, not exclusive, to give the broadest range of search results. If multiple tags apply, use them. The DC-3 for example have had multiple civilian and military roles.

Aircraft types

  • aerobatic
  • airship
  • balloon
  • bizjet
  • bomber
  • cargo
  • carrier
  • fighter
  • ga
  • glider
  • groundvehicle
  • helicopter
  • interceptor
  • passenger
  • racer
  • spaceship
  • tanker
  • trainer
  • transport
  • ultralight
  • unpowered
  • uav
  • reconnaissance
  • seacraft
  • crop-duster
  • bush-plane

Manufacturers

The intention here is to provide logical groupings, not to track corporate history. For example the MD-80 and MD-11 would get the douglas tag, which will likely translate to "Douglas / McDonell-Douglas" in the user interface. The Boeing 717 could get the boeing and douglas tags. Also it is not supposed to be an exhaustive list. This is so we for example can search for "all glass-cockpit Boeing and Airbus aircraft". It might be worth actively lying in the tags, in essence group all Hawker-Siddley/BAC/Avro aircraft under the vickers tag.

  • airbus
  • antonov
  • arado
  • atr
  • avro
  • bae
  • bell
  • bleriot
  • boeing
  • bombardier
  • caudron
  • cessna
  • consolidated
  • dassault
  • diamond
  • dornier
  • douglas
  • embraer
  • eurocopter
  • fairchild
  • fairey
  • focke-wulf
  • fokker
  • general-dynamics
  • gotha
  • grumman
  • handley-page
  • hawker
  • heinkel
  • ilyushin
  • junkers
  • kawasaki
  • lockheed
  • mc-donnell-douglas
  • messerschmitt
  • mikoyan-gurevich
  • mitsubishi
  • north-american
  • northrop
  • pilatus
  • piper
  • republic
  • robin
  • rockwell
  • saab
  • short
  • sopwith
  • spad
  • sukhoi
  • supermarine
  • tupolev
  • vickers
  • vought
  • wright
  • yakovlev


Eras

Logical groupings, not historical accuracy. Some aircraft are going to have a lot of these, for example the B-52. Again the goal is intelligent searches: "show me all WW2 fighters". Wee would like to avoid this getting political too and comments on that are welcome.

  • 1910s
  • 1920s
  • 1930s
  • 1940s
  • 1950s
  • 1960s
  • 1970s
  • 1980s
  • 1990s
  • 2000s
  • 2010s
  • coldwar
  • early-pioneers
  • golden-age
  • gulfwar1
  • gulfwar2
  • vietnam
  • ww1
  • ww2

Aircraft Features

This could get long, as always trying to focus on tags people might search for, for example: "show me all the VTOL aircraft" or "show me all the biplanes". Some will be very useful in improving the user experience; If the plane is tagged with seaplane we might be able to force a water start (but not for amphibious aircraft obviously).

  • aerobatic
  • airship
  • amphibious
  • biplane
  • canard - Canard planform
  • castering-wheel
  • combat
  • delta - Delta planform; Vulcan, Concorde, Space Shuttle
  • etops - ETOPS capable aircraft, presumably implies twin-engined
  • experimental - For X1 and similar X-planes
  • fictional
  • fixed-gear
  • floats
  • glass-cockpit
  • low-wing
  • mid-wing
  • high-wing
  • h-tail
  • hud
  • ifr - Panel and equipment (radios, lighting) suitable for IFR flight
  • lifting-body
  • pressurised - Pressurised cabin
  • prototype
  • refuel - Supports air-to-air refeuling
  • retractable-gear
  • seaplane - Flying boat or float plane
  • skis
  • stol - For short-takeoff
  • supersonic
  • supercharger
  • t-tail
  • tail-dragger
  • tricycle
  • tail-hook
  • triplane
  • twin-boom
  • v-tail
  • variable-geometry - For Tomcats and the like
  • vtol - For the Harrier, F-35, and the Osprey
  • wing-fold - usually for carrier aircraft
  • water-drop

FlightGear Features

  • combat - Support this various MP combat / bomb-able options
  • dual-controls - Supports copilot over MP
  • tow - Supports glider towing over MP
  • rembrandt - Supports Rembrandt, obviously

Propulsion

  • afterburner
  • diesel
  • electric - For power-assisted gliders, mostly.
  • jet
  • propeller
  • piston
  • radial - Radial piston engined
  • rocket
  • single-engine
  • supercharged
  • turboprop - For pistons with a turbo-charger
  • twin-engine
  • four-engine
  • variable-pitch
  • fixed-pitch

Examples

  • B-52 would have: bomber, jet, boeing, coldwar, 1960s, vietnam, 1970s, 1980s, gulfwar1, nato, refuel, retractable-gear and ifr.
  • Citation would have: cessna, bizjet, jet, 2-engine, glass-cockpit, ifr and retractable-gear.
  • Cub would have: piper, piston, 1-engine, ga, trainer, fixed-gear, 1930s, ww2 and tail-dragger.

Adding metadata to aircraft

The tags are added to or included into the <sim> section of the Aircraft-set.xml file(s), like for example below:

<?xml version="1.0" encoding="UTF-8" ?>

<PropertyList>

 <!-- ... -->

 <sim>

  <!-- ... -->

  <tags>
   <tag>passenger</tag>
   <tag>boeing</tag>
   <tag>jet</tag>
   <tag>twin-engine</tag>
   <tag>retractable-gear</tag>
   <tag>etops</tag>
   <tag>glass-cockpit</tag>
   <tag>ifr</tag>
  </tags>

  <!-- ... -->

 </sim>

 <!-- ... -->

</PropertyList>

References

Related content

Wiki articles

Forum topics

Developer mailing list threads

Source code