Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tiled/subset metadata distinction #8

Open
drwelby opened this issue Dec 17, 2021 · 0 comments
Open

Tiled/subset metadata distinction #8

drwelby opened this issue Dec 17, 2021 · 0 comments

Comments

@drwelby
Copy link

drwelby commented Dec 17, 2021

Placeholder for discussion on how to best represent metadata specific to a tile or other subset of a larger dataset.

Example:

A satellite pushbroom sensor collects a strip of data that is then divided into tiles. The strip could have a large amount of cloud cover, but one tile might be relatively cloud free.

In our current implementation we may process only one tile so there are no records for neighboring tiles. We represent strip-level metadata using standard EO extension tags, but then tile-specific values using a tile: prefix. This is largely because we only store metadata at the tile level.

It could be argued that the tile's metadata should only represent the tile itself, and that the strip should be represented by a STAC collection.

Since the question is likely to be repeated, I'd like to gather opinions towards a "best practice".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant