Currently the max precip locations of all of the storms are located in the collections.json which is a child of the main catalog.json stac...
if a catalog is designed to contain multiple collections (one for each duration) this is probably a good design.
if a catalog is unique to a given duration (which seems to be the practical use to date) then it may be wise to move the location summaries up to the parent catalog stac as an item/asset.
this way a quick summary can be found of the inputs and outputs from the parent catalog.
just a suggestion.
Currently the max precip locations of all of the storms are located in the collections.json which is a child of the main catalog.json stac...
if a catalog is designed to contain multiple collections (one for each duration) this is probably a good design.
if a catalog is unique to a given duration (which seems to be the practical use to date) then it may be wise to move the location summaries up to the parent catalog stac as an item/asset.
this way a quick summary can be found of the inputs and outputs from the parent catalog.
just a suggestion.