ol-stac attempts to generate a default visualization for assets displayed on a map. Without additional metadata, it typically falls back to stretching values from the minimum to the maximum, which is prone to outliers and can result in poorly balanced visualizations.
By including statistical metadata such as min, max, median, and stddev, we can compute better visualizations; for example, using the mean ± 2σ (~95% of values) for a better visualization stretch instead of the full min/max extent (and if no min/max is provided, the min/max is the actual data type min/max).
I've looked through zarr.json for any statistical values but couldn't find any, and the STAC metadata doesn't include them either.
Any ideas on how to improve this? Specifically, would it be feasible to add statistics to the STAC assets and/or bands?
ol-stac attempts to generate a default visualization for assets displayed on a map. Without additional metadata, it typically falls back to stretching values from the minimum to the maximum, which is prone to outliers and can result in poorly balanced visualizations.
By including statistical metadata such as min, max, median, and stddev, we can compute better visualizations; for example, using the mean ± 2σ (~95% of values) for a better visualization stretch instead of the full min/max extent (and if no min/max is provided, the min/max is the actual data type min/max).
I've looked through zarr.json for any statistical values but couldn't find any, and the STAC metadata doesn't include them either.
Any ideas on how to improve this? Specifically, would it be feasible to add statistics to the STAC assets and/or bands?