Catalog metadata: Difference between revisions
No edit summary |
No edit summary |
||
Line 44: | Line 44: | ||
<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) | (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> | |||
|author=<nowiki>James Turner</nowiki> | |||
|date=<nowiki>2015-03-11</nowiki> | |||
}} | |||
}} | |||
{{FGCquote | |||
|The catalog is just an XML file, and the other files needed are the thumbnail images for each package, and the package .zips themselves; the system is deliberately designed to be host-able 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. | |||
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33586444/ | |{{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> |
Revision as of 02:15, 12 March 2015
Tags with catalog metadata can be added to aircraft to help searching and filtering them, for example in future versions of the aircraft center, so that a user can quicker find the aircraft of interest.
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.
— James Turner (2015-02-13). Re: [Flightgear-devel] FGDATA split without Aircraft. Addon in SVN.
(re)Suggesting a Submodule approach. (Re)Proposing a per-Aircraft
repository.
(powered by Instant-Cquotes) |
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.
— James Turner (2015-03-06). Re: [Flightgear-devel] FGData size reduction.
(powered by Instant-Cquotes) |
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.
— James Turner (2015-03-06). Re: [Flightgear-devel] FGData size reduction.
(powered by Instant-Cquotes) |
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.
— James Turner (2015-03-11). Re: [Flightgear-devel] FGDATA and Jenkins.
(powered by Instant-Cquotes) |
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.
— James Turner (2015-03-11). Re: [Flightgear-devel] FGDATA and Jenkins.
(powered by Instant-Cquotes) |
The catalog is just an XML file, and the other files needed are the thumbnail images for each package, and the package .zips themselves; the system is deliberately designed to be host-able 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.
— James Turner (2015-03-11). Re: [Flightgear-devel] FGDATA and Jenkins.
(powered by Instant-Cquotes) |
Package management |
---|
Background |
Implementation |
Front Ends
|
Related efforts |
Supported Tags
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!
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.
Aircraft types
- ga
- helicopter
- fighter
- interceptor
- glider - But does this includes the Space Shuttle, Virgin Galactic's SpaceShipeOne, as well?
- spaceship
- bomber
- tanker
- cargo
- passenger
- bizjet - Not just for jets, but I can't think of a better term
- reconnaissance
- airship
- balloon
- trainer - Used in a pilot training role
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.
- boeing
- cessna
- douglas
- lockheed
- vickers
- piper
- diamond
- airbus
- beechcraft
- mig
- fokker
- ilyushin
- antonov
- embrarer
- bombardier
- saab
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
- early-pioneers
- ww1
- 1920s
- 1930s
- golden-age
- ww2
- 1950s
- 1960s
- 1970s
- vietnam
- coldwar
- korean
- 1980s
- 1990s
- gulfwar1
- 2000s
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).
- prototype
- experimental - For X1 and similar X-planes
- ifr - Panel and equipment (radios, lighting) suitable for IFR flight
- fixed-gear
- retractable-gear
- tail-dragger
- carrier-hook - Do we need a separate tag for carrier-capable?
- stol - For short-takeoff
- vtol - For the Harrier, F-35 if it ever works, and the Osprey
- floats
- amphibious
- cannard - Cannard planform
- delta - Delta planform; Vulcan, Concorde, Space Shuttle
- variable-geometry - For Tomcats and the like
- supersonic
- glass-cockpit
- refuel - Supports air-to-air refeuling
- seaplane - Flying boat or float plane
- etops - ETOPS capable aircraft, presumably implies twin-engined
- biplane
- triplane
- pressurised - Pressurised cabin
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
- piston
- radial - Radial piston engined
- diesel
- jet
- turboprop
- 1-engine
- 2-engine
- 3-engine
- 4-engine
- turbocharged - For pistons with a turbo-charger
- afterburner
- rocket
- electric - For power-assisted gliders, mostly.
- unpowered - Balloons, etc
Examples
- B-52 would have: bomber, jet. boeing, coldwar, 1960s, vietnam, 1970s, 1980s, gulfwar1, nato, refuel, retractable-gear, ifr
- Citation would have: cessna, bizjet, jet, 2-engine, glass-cockpit, ifr, retractable-gear
- Cub would have: piper, piston, 1-engine, ga, trainer, fixed-gear, 1930s, ww2, tail-dragger
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:
<?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>