I need to provide information about the mission, and the platforms, instruments and sensors associated with the resource.
Overview
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.
Recommendations
Documentation 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.
Conceptual Model
MI_AcquisitionInformation includes the following entities:
⎯ 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.
Implementation (XML)
<gmi:MI_AcquisitionInformation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.isotc211.org/2005/gmi http://www.ngdc.noaa.gov/metadata/published/xsd/schema.xsd"
xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gco="http://www.isotc211.org/2005/gco"
xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:srv="http://www.isotc211.org/2005/srv" xmlns:gml="http://www.opengis.net/gml/3.2"
xmlns:gsr="http://www.isotc211.org/2005/gsr" xmlns:gss="http://www.isotc211.org/2005/gss"
xmlns:gts="http://www.isotc211.org/2005/gts" xmlns:gmx="http://www.isotc211.org/2005/gmx"
xmlns:gmi="http://www.isotc211.org/2005/gmi">
<gmi:instrument>
<!--
The MI_Instrument class provides a description of the instrument used to collect the data. Use the id attribute to provide
a unique identifier for the instrument in this file. This id will be used to reference the instrument information from
platform descriptions in the same file.
-->
<gmi:MI_Instrument id="InstrumentShortName">
<!--
This is a citation to reference material that describes the instrument. Any number of these can be included in a metadata record.
-->
<gmi:citation>
<gmd:CI_Citation>
<gmd:title>
<gco:CharacterString>Title for reference material</gco:CharacterString>
</gmd:title>
<gmd:date>
<gmd:CI_Date>
<gmd:date>
<!--
The date is given in ISO 8601 format (see https://en.wikipedia.org/wiki/ISO_8601).
-->
<gco:Date>2016-01-01</gco:Date>
</gmd:date>
<gmd:dateType>
<gmd:CI_DateTypeCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication">publication</gmd:CI_DateTypeCode>
</gmd:dateType>
</gmd:CI_Date>
</gmd:date>
<gmd:citedResponsibleParty>
<gmd:CI_ResponsibleParty>
<gmd:individualName>
<gco:CharacterString>Author Name</gco:CharacterString>
</gmd:individualName>
<gmd:role>
<gmd:CI_RoleCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_RoleCode" codeListValue="originator">originator</gmd:CI_RoleCode>
</gmd:role>
</gmd:CI_ResponsibleParty>
</gmd:citedResponsibleParty>
</gmd:CI_Citation>
</gmi:citation>
<!--
This is a permanent and unique identifier for the instrument. Typically the InstrumentShortNames are unique.
-->
<gmi:identifier>
<gmd:MD_Identifier>
<!--
Identifiers should include information about the authority that assigns the identifiers.
-->
<gmd:authority>
<gmd:CI_Citation>
<gmd:title>
<gco:CharacterString>Name of the authority for the identifier.</gco:CharacterString>
</gmd:title>
<gmd:date>
<gmd:CI_Date>
<gmd:date>
<!-- The date is given in ISO 8601 format (see https://en.wikipedia.org/wiki/ISO_8601). -->
<gco:Date>2016-01-01</gco:Date>
</gmd:date>
<gmd:dateType>
<gmd:CI_DateTypeCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication">publication</gmd:CI_DateTypeCode>
</gmd:dateType>
</gmd:CI_Date>
</gmd:date>
</gmd:CI_Citation>
</gmd:authority>
<gmd:code>
<gco:CharacterString>InstrumentShortName</gco:CharacterString>
</gmd:code>
</gmd:MD_Identifier>
</gmi:identifier>
<gmi:type>
<gco:CharacterString>Instrument type</gco:CharacterString>
</gmi:type>
<gmi:description>
<gco:CharacterString>Instrument Description</gco:CharacterString>
</gmi:description>
<!--
The identifier is used to reference the platform that the instrument is mounted on.
-->
<gmi:mountedOn xlink:href="#PlatformShortName"/>
</gmi:MI_Instrument>
</gmi:instrument>
<!--
The operation is used to provide information about the mission during which the data were collected.
-->
<gmi:operation>
<gmi:MI_Operation>
<gmi:description>
<gco:CharacterString>Mission description.</gco:CharacterString>
</gmi:description>
<!--
This is a permanent and unique identifier for the mission.
-->
<gmi:identifier>
<gmd:MD_Identifier>
<gmd:authority>
<gmd:CI_Citation>
<gmd:title>
<gco:CharacterString>Name of the code authority</gco:CharacterString>
</gmd:title>
<gmd:date>
<gmd:CI_Date>
<gmd:date>
<!--
The date is given in ISO 8601 format (see https://en.wikipedia.org/wiki/ISO_8601).
-->
<gco:Date>2016-01-01</gco:Date>
</gmd:date>
<gmd:dateType>
<gmd:CI_DateTypeCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_DateTypeCode" codeListValue="revision">revision</gmd:CI_DateTypeCode>
</gmd:dateType>
</gmd:CI_Date>
</gmd:date>
<gmd:citedResponsibleParty>
<gmd:CI_ResponsibleParty>
<gmd:organisationName>
<gco:CharacterString>Organization name</gco:CharacterString>
</gmd:organisationName>
<gmd:contactInfo>
<gmd:CI_Contact>
<gmd:address>
<gmd:CI_Address>
<gmd:electronicMailAddress>
<gco:CharacterString>email address for organization</gco:CharacterString>
</gmd:electronicMailAddress>
</gmd:CI_Address>
</gmd:address>
</gmd:CI_Contact>
</gmd:contactInfo>
<gmd:role>
<gmd:CI_RoleCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_RoleCode" codeListValue="resourceProvider">/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/gmi:MI_Operation/gmi:identifier/gmd:MD_Identifier/gmd:authority/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:role/gmd:CI_RoleCode</gmd:CI_RoleCode>
</gmd:role>
</gmd:CI_ResponsibleParty>
</gmd:citedResponsibleParty>
</gmd:CI_Citation>
</gmd:authority>
<gmd:code>
<gco:CharacterString>Mission Identifier</gco:CharacterString>
</gmd:code>
</gmd:MD_Identifier>
</gmi:identifier>
<gmi:status>
<!--
The MD_ProgressCode can have values of completed, historicalArchive, obsolete, onGoing, planned, required, or underDevelopment.
-->
<gmd:MD_ProgressCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#MD_ProgressCode" codeListValue="onGoing">onGoing</gmd:MD_ProgressCode>
</gmi:status>
<gmi:type>
<!--
The MI_OperationTypeCode can have a value of real, simulated, or synthetic.
Other values can be added to the codelist if necessary.
-->
<gmi:MI_OperationTypeCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#MI_OperationTypeCode" codeListValue="real">real</gmi:MI_OperationTypeCode>
</gmi:type>
<!--
A hierarchy of missions is possible.
-->
<gmi:parentOperation gco:nilReason="inapplicable"/>
</gmi:MI_Operation>
</gmi:operation>
<gmi:platform>
<gmi:MI_Platform id="PlatformShortName">
<!--
This is a citation to reference material that describes the platform. Any number of these can be included in a metadata record.
-->
<gmi:citation>
<gmd:CI_Citation>
<gmd:title>
<gco:CharacterString>Title for reference material</gco:CharacterString>
</gmd:title>
<gmd:date>
<gmd:CI_Date>
<gmd:date>
<!--
The date is given in ISO 8601 format (see https://en.wikipedia.org/wiki/ISO_8601).
-->
<gco:Date>2016-01-01</gco:Date>
</gmd:date>
<gmd:dateType>
<gmd:CI_DateTypeCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication">publication</gmd:CI_DateTypeCode>
</gmd:dateType>
</gmd:CI_Date>
</gmd:date>
<gmd:citedResponsibleParty>
<gmd:CI_ResponsibleParty>
<gmd:individualName>
<gco:CharacterString>Author Name</gco:CharacterString>
</gmd:individualName>
<gmd:role>
<gmd:CI_RoleCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_RoleCode" codeListValue="originator">originator</gmd:CI_RoleCode>
</gmd:role>
</gmd:CI_ResponsibleParty>
</gmd:citedResponsibleParty>
</gmd:CI_Citation>
</gmi:citation>
<!--
This is a permanent and unique identifier for the platform. Typically the PlatformShortNames are unique.
-->
<gmi:identifier>
<gmd:MD_Identifier>
<gmd:code>
<gco:CharacterString>PlatformShortName</gco:CharacterString>
</gmd:code>
</gmd:MD_Identifier>
</gmi:identifier>
<gmi:description>
<gco:CharacterString>Platform description</gco:CharacterString>
</gmi:description>
<!--
The identifier is used to reference the instrument that is mounted on this platform.
-->
<gmi:instrument xlink:href="#InstrumentShortName"/>
</gmi:MI_Platform>
</gmi:platform>
</gmi:MI_AcquisitionInformation>
Implementation (NcML)
Usage
Crosswalks
Notes
Overview
Content Tools