Align fields with STAC specification?

[weiji14]

Just got some great ideas after attending this Cloud-Native Geospatial Event (https://schedule.cloudnativegeo.org) and learned a lot about Spatial Temporal Asset Catalogs (STAC) and OGC API standards! So the people working on those standards have literarlly spent years thinking about metadata, and these are some relevant ones that popped up from scanning through https://github.com/stac-extensions/stac-extensions.github.io:

• Satellite - https://github.com/stac-extensions/sat
• Synthetic Aperture Radar (SAR) - https://github.com/stac-extensions/sar
• Hyperspectral imagery - https://github.com/stac-extensions/hsi

It seems like there are some required fields/attributes which we could definitely ensure are present in our database. Using Sentinel-1 (a SAR satellite) as an example, frequency_band is required, and there's a list of Common Frequency Band Names to select from. See their example sentinel-1.json vs our current Sentinel-1.json

[AdrienWehrle]

Awesome! I signed up for this event but couldn't find the time! I'll go through those projects, thank you a lot!! :smile:

[AdrienWehrle]

Their sentinel-1.json looks super nice! I also not the use of general data set info (such as version number) as fields in all json files. We could/should also include this, can do it automatically when we have a new release! Again, in a goal of traceability, especially if users make local and static copies of the data base!

Also worth noting that our json files have been automatically created from a spreadsheet in a dummy way, only for testing purposes at the moment and without any other modification/improvement (just to explain why they look so ugly!)

[weiji14]

This VEDA-data repo finally got made public, and the JSON files (e.g. https://github.com/NASA-IMPACT/veda-data/blob/39f7fe2eb0abc751f66fe3b934801181530ce44d/json_data/collections/HLSS30.002.json#L1-L56) might be a useful reference, in particular, the spatial bounding box and temporal interval fields.