I need to provide information about the mission, and the platforms, instruments and sensors associated with the resource.
The Acquisition Information package is used for describing the acquisition of imagery and gridded datasets. This package includes fields for describing hardware (platforms, instruments, sensors, etc), requirements, plans, operations and objectives.
- Add platform identification information to the metadata.
- Add platform description information to the metadata.
- Add instrument identification information to the metadata.
- Add instrument description information to the metadata.
- Add an operations statement describing the scientific endeavor(s) to which the series/collection is associated to the metadata.
MI_AcquisitionInformation includes the following information:
⎯ MI_Instrument, designations of the measuring instruments used to acquire the data;
⎯ MI_Operation, designations of the overall data gathering program to which the data contribute;
⎯ MI_Platform, designations of the platform from which the data were taken;
⎯ MI_Objective, the characteristics and geometry of the intended object to be observed;
⎯ MI_Requirement, the user requirements used to derive the acquisition plan;
⎯ MI_Plan, the acquisition plan that was implemented to acquire the data.
Two additional classes are required to provide information on the acquisition of the data. These are:
⎯ MI_Event, describes a significant event that occurred during data acquisition. An event can be associated with an operation, objective, or platform pass, and
⎯ MI_PlatformPass, identifies a particular pass made by the platform during data acquisition. A platform pass is used to provide supporting identifying information for an event and for data acquisition of a particular objective.
The XML implementations shown above work well in systems designed to manage metadata in internationally accepted XML dialects. Typically these systems manage metadata for collections and, in many cases, they are separate from the actual data files (or granules). Historically, the metadata in files has been generated and used by analysis and visualization tools. It is written and read by tools that understand the specifics of the data format and the organization and naming of the metadata elements. The ISO standards shown above provide an organization and a set of names. Can we take advantage of those in the granules?
We have recently explored this idea with a standard transform between ISO metadata and NcML, a simple XML dialect originally developed as part of the netCDF ecosystem that includes groups and attributes and translated easily to the structure of an HDF file. The NcML version of the ISO 19115 quality information is shown below. This representation includes all of the ISO content and can be transformed back into ISO when it is appropriate.