Select STAC Extensions to include

[wildintellect]

Is your feature request related to a problem? Please describe. While creating the STAC metadata we should include appropriate extensions. PALSAR mosiacs are SAR based data. Based on documentation, 2019+ metadata is already aligned with the CARD4L specification.

Describe the solution you'd like Likely Extensions: EO and CARD4L Hmm, maybe not EO, and CARD4L is draft?

Describe alternatives you've considered Base STAC

Additional context

[wildintellect]

raster, eo and sar have been suggested by @TomAugspurger

• Does it matter that most of these are draft?

Raster

Seems reasonable enough, was not used by Google or DEA.

SAR

Seems appropriate but some data is only available for 2019, 2020 MOS product (see xml files), and is the same across the entire year. So not very useful within the collection. It might be good to specify the wavelength type L band and polarizations HH, HV and LINCI assets.

EO

PALSAR is an active sensor, EO seems more suited to passive sensors, in particular the bands are polarizations + metadata/masks. DEA did list it as an extension but did use a single field from the extension https://explorer.digitalearth.africa/stac/collections/alos_palsar_mosaic/items

[wildintellect]

SAR completed in 797fb9f1c6fc4fa51ef76132a01a9e2d65b372e0 Having trouble finding an example that implements EO and Raster. DEA did repeat the asset name as the eo:band.

[wildintellect]

Added Raster with ab52ad5 based on example from MODIS Skipping EO, and the only relevant field seems to be the Band name which is the same as the Polarization in SAR.