Versions Compared

Old Version 11

changes.mady.by.user John Kozimor

Saved on

compared with

New Version 12

changes.mady.by.user Ted Habermann

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Excerpt
hiddentrue

I need to provide information about the mission, and the platforms, instruments and sensors associated with the resource.

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)

<?xml version="1.0" encoding="UTF-8"?>
Code Block
<gmi:MI_
Requirement
AcquisitionInformation xmlns:
gmi
xsi="http://www.
isotc211
w3.org/
2005
2001/
gmi
XMLSchema-instance"
xmlns
  xsi:
gts
schemaLocation="http://www.isotc211.org/2005/
gts" xmlns:gco="
gmi http://www.
isotc211.org/2005/gco"
ngdc.noaa.gov/metadata/published/xsd/schema.xsd"
    xmlns:gmd="http://www.isotc211.org/2005/gmd" 
xmlns:
srv
gco="http://www.isotc211.org/2005/
srv
gco"
    xmlns:
gmx
xlink="http://www.
isotc211
w3.org/
2005
1999/
gmx
xlink"
 xmlns:
gss
xs="http://www.
isotc211
w3.org/
2005
2001/
gss
XMLSchema"
    xmlns:
gsr
srv="http://www.isotc211.org/2005/
gsr
srv" 
xmlns:gml="http://www.opengis.net/gml/3.2"
    xmlns:
xlink
gsr="http://www.
w3
isotc211.org/
1999
2005/
xlink
gsr" 
xmlns:
xsi
gss="http://www.
w3
isotc211.org/
2001
2005/
XMLSchema-instance
gss"
xsi:schemaLocation
    xmlns:gts="http://www.isotc211.org/2005/
gmi 
gts" xmlns:gmx="http://
ngdc
www.
noaa
isotc211.
gov
org/
metadata/published/xsd/schema.xsd
2005/gmx"
    xmlns:gmi="http://www.isotc211.org/2005/gmi">
    <gmi:
citation>
instrument>
<gmd:CI_Citation> 
<!--
The
document
that
contains
the
requirement
--> 
     The MI_Instrument class provides a description of
<gmd:title> 
the instrument used to collect the data. Use the id attribute to provide
<gco:CharacterString>Quality
Procedures</gco:CharacterString> 
       a unique identifier for
</gmd:title> <gmd:date> 
the instrument in this file. This id will be used to reference the instrument information from
            platform
<gmd:CI_Date> 
descriptions in the same file.
        -->
<gmd:date/
<gmi:MI_Instrument id="InstrumentShortName">
            <!--
<gmd:dateType> 
        This is a citation to reference material that describes the instrument. Any number of these can
<gmd:CI_DateTypeCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_DateTypeCode"
be included in a metadata record.
            -->
codeListValue="publication"/>
<gmi:citation>
                <gmd:CI_Citation>
</gmd:dateType>
</gmd:CI_Date>
<gmd:title>
</gmd:date>
<gmd:citedResponsibleParty> 
<gco:CharacterString>Title for reference material</gco:CharacterString>
<gmd:CI_ResponsibleParty>
</gmd:title>
                    <gmd:
organisationName>
date>
<gco:CharacterString>NOAA IOOS Program Office</gco:CharacterString> 
<gmd:CI_Date>
</gmd
<gmd:
organisationName>
date>
<gmd:role> 
            <!--
<gmd:CI_RoleCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_RoleCode"
         The date is given in ISO 8601 format (see https://en.wikipedia.org/wiki/ISO_8601).
codeListValue="author"/> 
       -->
</gmd:role>
</gmd:CI_ResponsibleParty>
<gco:Date>2016-01-01</gco:Date>
</gmd:citedResponsibleParty>
</gmd:CI_Citation> 
    </
gmi
gmd:
citation>
date>
<gmi:identifier>
<!--
The
unique
identifier
of
the
requirement
-->
<gmd:MD_Identifier> 
        
<gmd:
code>
dateType>
<gco:CharacterString>QC015</gco:CharacterString>
</gmd:code>
</gmd:MD_Identifier> </gmi:identifier>
<gmd:CI_DateTypeCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication">publication</gmd:CI_DateTypeCode>
<gmi:requestor>
<!--
The
person
or
group
that
requested
the
requirement
-->
<gmd:CI_ResponsibleParty> 
      </gmd:dateType>
<gmd:organisationName>
<gco:CharacterString>HI
Draft
Reqs<
</
gco
gmd:
CharacterString>
CI_Date>
</gmd:organisationName> 
        </gmd:date>
<gmd:contactInfo> 
                <gmd:
CI_Contact> </gmd:CI_Contact>
citedResponsibleParty>
</gmd:contactInfo> 
            <gmd:
role>
CI_ResponsibleParty>
<gmd:CI_RoleCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_RoleCode" codeListValue="originator"/> 
            <gmd:individualName>
</gmd:role>
</gmd:CI_ResponsibleParty>
</gmi:requestor>
<gmi:recipient>
<!--
The
person
or
group
that
received
the
requirement
-->
<gmd:CI_ResponsibleParty>
<gco:CharacterString>Author Name</gco:CharacterString>
<gmd:individualName>
<gco:CharacterString>Ted
Habermann<
</
gco
gmd:
CharacterString>
individualName>
</gmd:individualName> 
               <gmd:
organisationName>
role>
<gco:CharacterString>IOOS
IPT
Metadata
Working
Group</gco:CharacterString>
<
<gmd:CI_RoleCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_RoleCode" codeListValue="originator">originator</gmd:
organisationName>
CI_RoleCode>
<gmd:contactInfo>
<gmd:CI_Contact> 
</gmd:role>
<gmd:address>
</gmd:CI_ResponsibleParty>
                    </gmd:citedResponsibleParty>
<gmd:CI_Address> 
           </gmd:CI_Citation>
<gmd:electronicMailAddress>
</gmi:citation>
            <!--
                This is a
<gco:CharacterString>ted.habermann@noaa.gov</gco:CharacterString> 
permanent and unique identifier for the instrument.  Typically the InstrumentShortNames are unique.
            -->
</gmd:electronicMailAddress> 
       <gmi:identifier>
</gmd:CI_Address>
<gmd:MD_Identifier>
                    <
/gmd:address>
!--
</gmd:CI_Contact> 
        Identifiers should include
</gmd:contactInfo> 
information about the authority that assigns the identifiers.
<gmd:role>
<gmd:CI_RoleCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_RoleCode"
-->
codeListValue="pointOfContact"/> 
    <gmd:authority>
</gmd:role>
</gmd:CI_ResponsibleParty>
</gmi:recipient>
<gmi
<gmd:
priority>
CI_Citation>
<gmi:MI_PriorityCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#MI_PriorityCode" codeListValue="high"/>
</gmi:priority>
<gmi:requestedDate>
<gmi
<gmd:
MI_RequestedDate>
title>
<gmi:requestedDateOfCollection>
<gco:DateTime>2007-02-02T00:00:00</gco:DateTime> 
      <gco:CharacterString>Name of the authority for the identifier.</
gmi
gco:
requestedDateOfCollection>
CharacterString>
<gmi:latestAcceptableDate gco:nilReason="unknown"/>
</gmi:MI_RequestedDate> 
    </
gmi
gmd:
requestedDate>
title>
<gmi:expiryDate
gco:nilReason="unknown"/>
<gmi:satisifiedPlan> <!-- The plan for satisfying the requirement -->
<gmi
<gmd:
MI_Plan>
date>
<gmi:status> 
                  <gmd:
MD_ProgressCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#MD_ProgressCode"
CI_Date>
codeListValue="planned"/>
</gmi:status> 
       <gmd:date>
<gmi:citation>
<gmd:CI_Citation>
<gmd:title> 
<!-- The date is given in ISO 8601 format (see https://en.wikipedia.org/wiki/ISO_8601). -->
<gco:CharacterString>This
is
the
title
of
the
plan</gco:CharacterString>
</gmd:title>
<gco:Date>2016-01-01</gco:Date>
<gmd:date> 
                </gmd:date>
<gmd:CI_Date> 
                           
<gmd:
date/> 
dateType>
<gmd:dateType> 
                         
<gmd:CI_DateTypeCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication">publication</gmd:CI_DateTypeCode>
codeListValue="publication"/>
   </gmd:dateType>
                                </gmd:
dateType>
CI_Date>
                            </gmd:
CI_Date> 
date>
                        </gmd:
date> 
CI_Citation>
<gmd
</gmd:
citedResponsibleParty>
authority>
                    
<gmd:
CI_ResponsibleParty>
code>
<gmd:individualName>
<gco:CharacterString>InstrumentShortName</gco:CharacterString>
                    </gmd:code>
<gco:CharacterString>Author
of
the
Plan<
</
gco
gmd:
CharacterString>
MD_Identifier>
            </gmi:identifier>
</gmd:individualName>
<gmi:type>
                <gco:CharacterString>Instrument type</gco:CharacterString>
<gmd
</gmi:
organisationName>
type>
            
<gmi:description>
                
<gco:
CharacterString>Organization that wrote the plan<
CharacterString>Instrument Description</gco:CharacterString>
            </gmi:description>
            <!--
</gmd:organisationName> 
             The identifier is used to reference the platform that the instrument is mounted on.
<gmd:contactInfo> 
          -->
            <gmi:mountedOn xlink:href="#PlatformShortName"/>
<gmd:CI_Contact>
</gmi:MI_Instrument>
    
</gmi:instrument>
    <!--
        The operation is used to provide information about the mission during which the data were collected.
<gmd:onlineResource>
-->
    <gmi:operation>
        <gmi:MI_Operation>
            <gmi:description>
<gmd:CI_OnlineResource>
<gco:CharacterString>Mission description.</gco:CharacterString>
            </gmi:description>
            <!--
                This is a permanent
<gmd:linkage> 
and unique identifier for the mission.
            -->
            <gmi:identifier>
                <gmd:MD_Identifier>
<gmd:URL>URL
of
the
plan</gmd
<gmd:
URL>
authority>
                        <gmd:CI_Citation>
</gmd:linkage> 
        <gmd:title>
</gmd:CI_OnlineResource> 
<gco:CharacterString>Name of the code authority</gco:CharacterString>
</gmd:onlineResource> 
</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:
CI_Contact>
role>
                                </gmd:
contactInfo>
CI_ResponsibleParty>
<gmd:role/>
</gmd:citedResponsibleParty>
                        </gmd:CI_
ResponsibleParty>
Citation>
                    </gmd:
citedResponsibleParty>
authority>
</gmd:CI_Citation>
</gmi:citation>
<gmd:code>
<gmi:operation>
<!-- An operation
is
like
a
project.
It
can
be
defined
in
a
hierarchy (parent/child) -->
<gco:CharacterString>Mission Identifier</gco:CharacterString>
<gmi:MI_Operation> 
    </gmd:code>
<gmi:citation>
</gmd:MD_Identifier>
            </gmi:identifier>
<gmd
<gmi:
CI_Citation>
status>
                <!--
<gmd:title> 
        The MD_ProgressCode can have values of completed, historicalArchive, obsolete, onGoing, planned, required, or underDevelopment.
<gco:CharacterString>NOAA
IOOS
Metadata
Project Description</gco:CharacterString>
 -->
                <gmd:MD_ProgressCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#MD_ProgressCode" codeListValue="onGoing">onGoing</gmd:MD_ProgressCode>
            </
gmd
gmi:
title>
status>
            <gmi:type>
<gmd:date> 
<!-- 
                    The MI_OperationTypeCode can have a value of real, simulated, or synthetic.
<gmd:CI_Date> 
           Other values can be added to the codelist if necessary.
<gmd:date/
-->
                <gmi:MI_OperationTypeCode 
codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#MI_OperationTypeCode" codeListValue="real">real</gmi:MI_OperationTypeCode>
<gmd:dateType>
</gmi:type>
            <!--
                A hierarchy of missions
<gmd:CI_DateTypeCode
is possible.
            -->
            <gmi:parentOperation gco:nilReason="inapplicable"/>
        </gmi:MI_Operation>
    </gmi:operation>
codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_DateTypeCode"
<gmi:platform>
        <gmi:MI_Platform id="PlatformShortName">
            <!--
                This is a citation to reference material that
codeListValue="publication"/> 
describes the platform. Any number of these can be included in a metadata record.
            -->
</gmd
<gmi:
dateType>
citation>
                <gmd:CI_Citation>
</gmd:CI_Date>
  <gmd:title>
                        <gco:CharacterString>Title for reference
<
material</
gmd
gco:
date>
CharacterString>

                    
</gmd:
CI_Citation>
title>
</gmi
<gmd:
citation>
date>
<gmi
<gmd:
status> 
CI_Date>
                            <gmd:
MD_ProgressCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#MD_ProgressCode" 
date>
codeListValue="onGoing"/> 
<!--
</gmi:status> 
           The date is given in ISO 8601 format (see
<gmi:parentOperation>
https://en.wikipedia.org/wiki/ISO_8601).
<gmi:MI_Operation>
        -->
<gmi:citation> 
    <gco:Date>2016-01-01</gco:Date>
<gmd:CI_Citation>
</gmd:date>
                            
<gmd:
title>
dateType>
<gco:CharacterString>The IOOS Integrated Project Team</gco:CharacterString> 
<gmd:CI_DateTypeCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication">publication</gmd:CI_DateTypeCode>
                            
</gmd:
title>
dateType>
<gmd:date>
</gmd:CI_Date>
                    </gmd:date>
                    <gmd:
CI_Date>
citedResponsibleParty>
                        <gmd:CI_ResponsibleParty>
<gmd:date/> 
        <gmd:individualName>
<gmd:dateType>
<gco:CharacterString>Author Name</gco:CharacterString>
                            
</gmd:individualName>
<gmd:CI_DateTypeCode
 
                <gmd:role>
                                <gmd:CI_RoleCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_
DateTypeCode"
RoleCode" codeListValue="originator">originator</gmd:CI_RoleCode>
codeListValue="publication"/> 
</gmd:role>
                        
</gmd:
dateType> 
CI_ResponsibleParty>
                    </gmd:citedResponsibleParty>
                </gmd:CI_
Date>
Citation>
            
</gmi:citation>
</gmd:date>
<!--
                This is a permanent and unique identifier for the platform. Typically the PlatformShortNames
</gmd:CI_Citation>
are unique.
            -->
</gmi:citation>
<gmi:identifier>
                <gmd:MD_Identifier>
<gmi:status> 
         <gmd:code>
<gmd:MD_ProgressCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#MD_ProgressCode"
 <gco:CharacterString>PlatformShortName</gco:CharacterString>
                    </gmd:code>
codeListValue="onGoing"/>
 </gmd:MD_Identifier>
            </gmi:identifier>
            <gmi:description>
</gmi:status> 
             <gco:CharacterString>Platform description</gco:CharacterString>
<gmi:parentOperation/>
</gmi:description>
            <!--
</gmi:MI_Operation> 
       The identifier is used to reference the instrument that is mounted on
</gmi:parentOperation>
this platform.
            -->
</gmi:MI_Operation>
</gmi:operation>
<gmi:instrument xlink:href="#InstrumentShortName"/>
        </gmi:MI_
Plan>
Platform>
    </gmi:
satisifiedPlan>
platform>
</gmi:MI_
Requirement>
AcquisitionInformation>

Implementation (NcML)

Usage

 

Crosswalks

Notes