Earthdata Forum

Thanks again for the info. I have requested to be added to that list.

I think it would be helpful if such announcements were made publicly. If they happen on a wiki or a slack workspace that requires permissions to be accessed, a lot of folks are going to have heartburn figuring out what went wrong.

Hello to everyone following this thread. My name is Alicia Aleman, and I'm the Product Owner of the Search Team supporting NASA ESDIS' Search and Discovery applications and services. My team very recently took ownership of CMR-STAC, and I wanted to let you all know that I'm working on a comms strategy to notify the CMR-STAC community of new features, important changes, bug fixes, etc. I hope to have something up and running soon. In the meantime, we'll continue to post updates to existing threads on the forum and in github as we have them. Thanks for your patience.

RE: The loss of the "metadata" field under "assets"...this will be reinstated in the next release of CMR-STAC.

Hi Alicia, thank you for your response! Would you have any idea when the next release is expected?

The XML metadata file is back under assets as seen here:
https://cmr.earthdata.nasa.gov/stac/LPCLOUD/collections/HLSL30_2.0/items/HLS.L30.T01FBE.2018272T213803.v2.0

"metadata": {
"href": "https://cmr.earthdata.nasa.gov/search/concepts/G2198744339-LPCLOUD.xml",
"title": "CMR XML metadata for G2198744339-LPCLOUD",
"type": "application/xml",
"roles": [
"metadata"
]
}

Hi Alicia would you happen to have any updates on the "oops" issue in this thread: viewtopic.php?t=5922

I'm still encountering this issue currently, which makes the LPCloud STAC unusable. Happy to provide any data points, etc.

RE: the "oops" error— We're looking into it, but so far, it doesn't appear to be a CMR-STAC issue but rather something happening upstream with CMR. Status updates on the issue can be tracked in the repo: https://github.com/nasa/cmr-stac/issues/366

An update on communicating changes and releases, as well as reporting and tracking issues...

• Release notes are now available in the CMR-STAC GitHub repo: https://github.com/nasa/cmr-stac/releases. The production release cadence for CMR-STAC is typically every two weeks on Wednesday, and release notes will be posted 2 weeks ahead of scheduled release dates. The next scheduled release to production is 11/20/2024.

• The CMR-STAC GitHub repo will also be The Place for reporting and tracking the status of issues and feature requests going forward. You can check the current list of open issues here: https://github.com/nasa/cmr-stac/issues.

I'm hopeful this streamlined approach to communications will make it easier for everyone to report and track the status of issues, fixes, and new feature requests for CMR-STAC. Please reach out if you have questions or concerns.

Hey All,

This is a bit of a cross post with viewtopic.php?p=21127#p21127.

I wanted to let you know that there has been an update deployed to the CMR-STAC API that, I think, addresses many of the issues identified in this thread. Please let us know if you continue to experience issues.