Date: Fri, 29 Mar 2024 11:05:49 -0400 (EDT) Message-ID: <319916243.260.1711724749518@gs-ed-prod-wiki1.earthdata.nasa.gov> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_259_801448529.1711724749518" ------=_Part_259_801448529.1711724749518 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The ISO metadata standards include many elements that are identical for = many of the metadata records produced by a particular group. These boilerpl= ate elements can be defined in templates that can be used to start metadata= records being created by members of those groups. Useful boilerplate might= include these elements:
<gmd= :fileIdentifier> <gco:CharacterString>namespace:identifier</gco:CharacterStrin= g> </gmd:fileIdentifier>
Note: ISO 19115-2 identified metadata records using a single character s= tring that often times had to be overloaded to include the information requ= ired for unambiguous identification. ISO 19115-1 replaces the CharacterStri= ng element with an MD_Identif= ier object, which includes code and codeSpace fields. The co= mbination of code and codeSpace fields ensue unambiguous file identificatio= n.
<mdb= :metadataIdentifier> <mcc:MD_Identifier> <mcc:code> <gco:CharacterString>fileIdentifier</gco:CharacterStri= ng> </mcc:code> <mcc:codeSpace> <gco:CharacterString>fileIdentifierNamespace</gco:Chara= cterString> </mcc:codeSpace> </mcc:MD_Identifier> </mdb:metadataIdentifier>
<gmd= :language> <gco:CharacterString>eng; USA</gco:CharacterString> </gmd:language>
Note: ISO 19115 specified the language with a CharacterString element.&n= bsp; ISO 19115-1 replaces the CharacterString element with the defaultLocal= e/PT_Locale object. The PT_Locale object includes fields for Language= , Country, and CharacterSet codes, which provide a more detailed language d= escription. ISO 19115-1 also supports documenting additional language= s with the otherLocale/PT_Locale object.
<gmd= :characterSet> <gmd:MD_CharacterSetCode codeList=3D"codeListLocation#MD_CharacterSetCode" codeListValue=3D"utf8">utf8</gmd:MD_CharacterSetCode> </gmd:characterSet>
<mdb= :defaultLocale> <lan:PT_Locale> <lan:language> <lan:LanguageCode codeList=3D"codeListLocation#LanguageCode" codeListValue=3D"eng; USA">eng; USA</lan:LanguageCode= > </lan:language> <lan:characterEncoding> <lan:MD_CharacterSetCode codeList=3D"codeListLocation#MD_CharacterSetCode" codeListValue=3D"UTF8">UTF8</lan:MD_CharacterSetCode> </lan:characterEncoding> </lan:PT_Locale> </mdb:defaultLocale>
Note: ISO 19115-1 groups the CharacterSetCode with the LanguageCode, and= CountryCode in the PT_Locale object.
<gmd= :hierarchyLevel> <gmd:MD_ScopeCode codeList=3D"codeListLocation#MD_ScopeCode" codeListValue=3D"dataset">dataset</gmd:MD_ScopeCode> </gmd:hierarchyLevel>
Note: ISO 19115 included any number of hierarchyLevels and hierarc= hyLevelNames. In cases with multiple occurrences of each, it was impossible= to associate a given hierarchyLevel with the correct hierarchyLevelName. I= SO 19115-1 addresses this ambiguity with the MD_MetadataScope object that u= nambiguously associates a MD_ScopeCode and the correct name.
<mdb= :metadataScope> <mdb:MD_MetadataScope> <mdb:resourceScope> <mcc:MD_ScopeCode codeList=3D"codeListLocation#MD_ScopeCode" codeListValue=3D"dataset">dataset</mcc:MD_ScopeCode> </mdb:resourceScope> <mdb:name> <gco:CharacterString>LevelName</gco:CharacterString> </mdb:name> </mdb:MD_MetadataScope> </mdb:metadataScope>
<gmd= :dateStamp> <gco:Date>YYYY-MM-DD</gco:Date> </gmd:dateStamp>
Note: ISO 19115 includes a dateStamp for documenting the creation/= revision time for the metadata. Many other times can be important in = the history of metadata maintenance. ISO 19115-1 replaces the datestamp/Dat= e field with the dateinfo/CI_Date object, which enables the type of date to= be specified. ISO 19115-1 expands the date type codelist from 3 valu= es to 16.
<mdb= :dateInfo> <cit:CI_Date> <cit:date> <gco:DateTime>2111-11-11T11:11:11</gco:DateTime> </cit:date> <cit:dateType> <cit:CI_DateTypeCode codeList=3D"codeListLocation#CI_DateTypeCo= de" codeListValue=3D"creation">creation</cit:CI_DateTypeCode>= ; </cit:dateType> </cit:CI_Date> </mdb:dateInfo>
<gmd= :metadataStandardName> <gco:CharacterString>ISO 19115-2 Geographic Information - Metadata = Part 2 Extensions for imagery and gridded data</gco:CharacterString> </gmd:metadataStandardName> <gmd:metadataStandardVersion> <gco:CharacterString>ISO 19115-2:2009(E)</gco:CharacterString>= ; </gmd:metadataStandardVersion>
Note: ISO 19115 includes CharacterStrings for specifying the metad= ata standard and version being used. ISO 19115-1 introduces multiple = CI_Citations for the metadata standard(s) and profile(s) included in a meta= data record. This provides more specific information about the source of th= e metadata standard and acknowledges that a single record can support multi= ple standards (e.g. 19115-1, 19115-2, and 19157) and profiles.
<mdb= :metadataStandard> <cit:CI_Citation> <cit:title> <gco:CharacterString>Standard Title</gco:CharacterString&g= t; </cit:title> <cit:edition> <gco:CharacterString>Standard Edition</gco:CharacterString= > </cit:edition> </cit:CI_Citation> </mdb:metadataStandard>
Many global environmental datasets use a simple latitude/longitude= reference system referred to as WGS 84 or EPSG:4326. This gmd:referenceSys= temInfo describes that reference system as a RS_Identifier with a code and = an authority of the European Petroleum Survey Group (EPSG).
<gmd= :referenceSystemInfo> <gmd:MD_ReferenceSystem> <gmd:referenceSystemIdentifier> <gmd:RS_Identifier> <gmd:authority> <gmd:CI_Citation> <gmd:title> <gco:CharacterString>European Petroleum S= urvey Group (EPSG) Geodetic Parameter Registry</gco:CharacterS= tring> </gmd:title> <gmd:date> <gmd:CI_Date> <gmd:date> <gco:Date>2008-11-12</gco:Date= > </gmd:date> <gmd:dateType> <gmd:CI_DateTypeCode codeList=3D"codeListLocation#CI_DateTy= peCode" codeListValue=3D"publication"> publication</gmd:CI_DateTypeCode>= ; </gmd:dateType> </gmd:CI_Date> </gmd:date> <gmd:citedResponsibleParty> <gmd:CI_ResponsibleParty> <gmd:organisationName> <gco:CharacterString>European Pet= roleum Survey Group</gco:CharacterString> </gmd:organisationName> <gmd:contactInfo> <gmd:CI_Contact> <gmd:onlineResource> <gmd:CI_OnlineResource> <gmd:linkage> <gmd:URL>http://w= ww.epsg-registry.org/</gmd:URL> </gmd:linkage> </gmd:CI_OnlineResource> </gmd:onlineResource> </gmd:CI_Contact> </gmd:contactInfo> <gmd:role gco:nilReason=3D"missing"/> </gmd:CI_ResponsibleParty> </gmd:citedResponsibleParty> = =20 </gmd:CI_Citation> </gmd:authority> <gmd:code> <gco:CharacterString>urn:ogc:def:crs:EPSG:4326</= gco:CharacterString> </gmd:code> <gmd:version> <gco:CharacterString>6.18.3</gco:CharacterStri= ng> </gmd:version> </gmd:RS_Identifier> </gmd:referenceSystemIdentifier> </gmd:MD_ReferenceSystem> </gmd:referenceSystemInfo>
Note: ISO 19115-1 replaces the RS_Identifier with an MD_Identifier and that the online resou= rce has moved out of the contact information and into the citation.
<= mdb:referenceSystemInfo> <mrs:MD_ReferenceSystem> <mrs:referenceSystemIdentifier> <mcc:MD_Identifier> <mcc:authority> <cit:CI_Citation> <cit:title> <gco:CharacterString>European Petroleum Surve= y Group (EPSG) Geodetic Parameter Registry</gco:CharacterString> </cit:title> <cit:date> <cit:CI_Date> <cit:date> <gco:DateTime>2008-11-12T00:00:00</g= co:DateTime> </cit:date> <cit:dateType> <cit:CI_DateTypeCode codeList=3D"codeListL= ocation#CI_DateTypeCode" codeListValue=3D"publication">publication</c= it:CI_DateTypeCode> </cit:dateType> </cit:CI_Date> </cit:date> <cit:citedResponsibleParty> <cit:CI_Responsibility> <cit:role> <cit:CI_RoleCode codeList=3D"codeListLocat= ion#CI_RoleCode" codeListValue=3D"pointOfContact">pointOfContact</cit= :CI_RoleCode> </cit:role> <cit:party> <cit:CI_Organisation> <cit:name> <gco:CharacterString>European Pet= roleum Survey Group</gco:CharacterString> </cit:name> <cit:contactInfo> <cit:CI_Contact> <cit:onlineResource> <cit:CI_OnlineResource> <cit:linkage> <gco:CharacterString>= http://www.epsg-registry.org/</gco:CharacterString> </cit:linkage> </cit:CI_OnlineResource> </cit:onlineResource> </cit:CI_Contact> </cit:contactInfo> </cit:CI_Organisation> </cit:party> </cit:CI_Responsibility> </cit:citedResponsibleParty> <cit:onlineResource> <cit:CI_OnlineResource> <cit:linkage> <gco:CharacterString>http://www.epsg-re= gistry.org/</gco:CharacterString> </cit:linkage> </cit:CI_OnlineResource> </cit:onlineResource> </cit:CI_Citation> </mcc:authority> <mcc:code> <gco:CharacterString>urn:ogc:def:crs:EPSG:4326</= gco:CharacterString> </mcc:code> <mcc:version> <gco:CharacterString>6.18.3</gco:CharacterString= > </mcc:version> </mcc:MD_Identifier> </mrs:referenceSystemIdentifier> </mrs:MD_ReferenceSystem> </mdb:referenceSystemInfo>
Resource and Metadata Constraints:
Many datasets distributed by U.S. Federal Agencies have no restrictions = on their use. They do, however, include a standard disclaimer. This disclai= mer is added to the boilerplate in the resourceConstraints and metadataCons= traints:
<gmd:resourceConstraints> or <gmd:metadataConstraints> <gmd:MD_Constraints> <gmd:useLimitation> <gco:CharacterString>Disclaimer - While every effort has been m= ade to ensure that these data are accurate and reliable within the limits of the current state of t= he art, NASA cannot assume liability for any damages caused by any errors or omissions in th= e data, nor as a result of the failure of the data to function on a particular system. NASA make= s no warranty, expressed or implied, nor does the fact of distribution constitute such a warr= anty.</gco:CharacterString> </gmd:useLimitation> </gmd:MD_Constraints> </gmd:resourceConstraints> or </gmd:metadataConstraints>