Closed m-mohr closed 4 months ago
IMO, the problem is in the multiple definitions of gsd
. One given here is not inline with the one given here ? Personally, we apply the latter one and use gsd
both at item and assets level:
For example, gsd defined for an Item represents the best Ground Sample Distance (resolution) for the data within the Item. However, some assets may be lower resolution and thus have a higher gsd.
I think the confusion resides in the former definition that tries to describe the instrument and not the item. The rule of thumb should always be that we describe metadata of a product item, not the procedure that led to it.
This will likely be solved with Bands RFC as then you can just use raster:spatial_resolution
.
In a recent discussion about a landcover product, we struggled with gsd again.
Thoughts? I feel like it's useful to have an easy way to search across collections for spatial resolution without needing to dig into bands. Also, makes summarizing easier as you don't necessarily need to implement Item Asset Definitions and look into specific items.
Origin: https://github.com/stactools-packages/esa-cci-lc/issues/7