On-Board Instrument Metadata Server Discussion
Given a number of instruments possessing health, status, and/or metadata packets on an airborne instrument payload network, establish requirements and discuss implementation issues for onboard web service(s) to manage such data.
In June 2008 (action item 0806.7) we talked about having a server that could serve out variable/instrument meta-data in case the instrument maker couldn't provide the facility.
- You have a number of instruments broadcasting CSV packets aboard the aircraft.
- You have one or more programs which can access these packets for display or other processing needs, but the definition of the content of these packets needs to be managed as well.
- The ability for a client application (presumably a display application) to dynamically request the packet metadata is assumed.
- While it is understood that the instrument itself is the logical original source of this information, it is assumed that the instrument may not be the server of metadata information to requestors. A network service or daemon is proposed as a repository of this information.
- We thus envision a server as part of the aircraft infrastructure that manages this metadata.
----Example packets from instruments requiring metadata management:
- WP3D,20080421T000654, 19.0000, 69.4613,-136.6085,1222.6000,-7.4400,...
Q: Should HDR (i.e. CSV packet description) be sent/broadcast periodically or only upon request?
- A: Metadata should provide a variable name, possibly multiple names. Also units, default plot scale, and/or management strategies for missing values are warranted/needed for display apps.
Update From 03/09 Meeting
As a pilot project implement as text files retrievable via http. Use the CSV packet Identifier keyword as the filename. Add directory levels 'iwgadts':