STAC Extension and specifications for Sentinel-1 NRB

[abradley60]

Hi @m-mohr,

I am part of a team developing a Sentinel-1 RTC/NRB ARD product for the Australian and Antarctic regions. We plan to make our products available through STAC and want to ensure compliance with the latest specifications.

I understand that the CARD4L extension is being superseded by the CEOS-ARD radar extension, which is still under development. We are also aware of the CEOS Product Family Specification for Normalised Radar Backscatter (v5.5) for compliance. Our products are expected to be available later this year, and we would appreciate your guidance on the best approach moving forward.

We have reviewed some existing examples, such as Digital Earth Africa’s RTC product (e.g., example JSON metadata). We note that this includes the main SAR parameters in the STAC properties, with additional metadata for CEOS compliance in the linked metadata files. The examples in the CARD4L Extension appear to define some of these parameters in the STAC body itself whilst also linking source STAC and additional metadata as suggested in the readme. We are also looking at delivering our products on a burst level and would like to describe the burst id in the STAC document. It appears there are existing fields for this (e.g. sar:relative_burst) which should be used?

Given the evolving CEOS specifications, we would appreciate any insights on best practices for structuring our product metadata in STAC.

Your assistance would be greatly appreciated.

Best regards,
Alex

[m-mohr]

Just want to let you know that I've seen this and it's on my todo list, but it could take a couple of days until I get to it.
OTH, it actually might make sense to hop on a call to go through the questions though. I'm travelling next week, so maybe we can get something on the calendar the week after? Which timezone are you in?

[abradley60]

Thanks @m-mohr. A call sounds great to me. I am working on Australian Central Daylight Time. I should pretty flexible in the evenings if needed, let me know and I can send my email through.

[m-mohr]

@abradley60 Yes, I can't see your email on GitHub, but mine should be public on GitHub. Just send an email through and we can figure our a date and time.