search

NASA-IMPACT / hls-vi

0 stars 0 forks source link

Correct AssociatedBrowseImageUrls #27

Closed chuckwondo closed 1 month ago

chuckwondo commented 1 month ago

The URLs in the XML metadata files are incorrect, as they are simply copied from the original HLS metadata.

In tests/fixtures/HLS-VI.S30.T13RCN.2024128T173909.v2.0.cmr.xml, we have this:

  <AssociatedBrowseImageUrls>
    <ProviderBrowseUrl>
      <URL>https://data.lpdaac.earthdatacloud.nasa.gov/lp-prod-public/HLSS30.020/HLS.S30.T13RCN.2024128T173909.v2.0/HLS.S30.T13RCN.2024128T173909.v2.0.jpg</URL>
      <Description>Download HLS.S30.T13RCN.2024128T173909.v2.0.jpg</Description>
    </ProviderBrowseUrl>
    <ProviderBrowseUrl>
      <URL>s3://lp-prod-public/HLSS30.020/HLS.S30.T13RCN.2024128T173909.v2.0/HLS.S30.T13RCN.2024128T173909.v2.0.jpg</URL>
      <Description>This link provides direct download access via S3 to the granule</Description>
    </ProviderBrowseUrl>
  </AssociatedBrowseImageUrls>

In tests/fixtures/HLS-VI.L30.T06WVS.2024120T211159.v2.0.cmr.xml, the AssociatedBrowseImageUrls is empty, and it is also empty in the original HLS metadata file tests/fixtures/HLS.L30.T06WVS.2024120T211159.v2.0/HLS.L30.T06WVS.2024120T211159.v2.0.cmr.xml.

@madhuksridhar, do the L30 metadata files not contain such URLs?

chuckwondo commented 1 month ago

After chatting with @madhuksridhar, we will simply remove the URLs from the metadata fixture files, as Cumulus should be the one to populate them during ingestion.