Date: Fri, 29 Mar 2024 07:51:29 -0400 (EDT) Message-ID: <464785392.159.1711713089897@gs-ed-prod-wiki1.earthdata.nasa.gov> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_158_1888335570.1711713089897" ------=_Part_158_1888335570.1711713089897 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
In adding the AircraftID characteristic, I noticed that there ma= y be some discrepancy between what the DIF-UMM_ECHO Mapping.xlsx file says = (v1.9) and how the ingest is actually happening.
Looking at rows 489-492 in particular:
However, in practice, it doesn't seem like it actually ingests that way.= For one thing, it seems to be invalid to have multiple "gmi:identifi= er" tags. In the ingest ISO that we are currently sending, it looks l= ike this:
<gmi:platform>
<eos:EOS_Platform id=3D"PLATFORM_IDENTIFIER">
<gmi:identifier>
<gmd:MD_Identifier>
<gmd:code>
<gco:CharacterString>PLATFORM_SHORT_NAME</gco:CharacterString>=
</gmd:code>
<gmd:description>
<gco:CharacterString>PLATFORM_LONG_NAME</gco:CharacterString><=
br>
</gmd:description>
</gmd:MD_Identifier>
</gmi:identifier>
<gmi:description>
<gco:CharacterString>PLATFORM_DESCRIPTION</gco:CharacterString>=
;
</gmi:description>
<gmi:instrument xlink:href=3D"#INSTRUMENT_ID"/>
</eos:EOS_Platform>
</gmi:platform>
Essentially, the Short Name is in the "gmd:code" part of the identifier,= but the Long Name is the "description" of the identifier (and not a separa= te identifier). The description of the platform itself is not "Type:"= but rather seems to actually be the description of the platform.
My guess is the spreadsheet is incorrect in this case, and that the way = we are writing the ISO is indeed the correct way to specify short name, lon= g name, etc. (After ingesting, when we look at the UMM, for instance,= the fields seem to be populated based on the values above).
A related note, too, is that if the value of PLATFORM_DESCRIPTION is lon= ger than 80 characters, it throws a warning message about it. While t= his may be a necessary restriction for something on the back-end, it's not = really clear from the spreadsheet, and many of our platform descriptions ma= y be longer than 80 characters. We could truncate, but it would make = these descriptions somewhat less useful.
Mostly need clarification as to the "proper" way to ingest platforms.