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

Allow extra_fields in Column #8

Open
martinfleis opened this issue Aug 11, 2022 · 3 comments
Open

Allow extra_fields in Column #8

martinfleis opened this issue Aug 11, 2022 · 3 comments

Comments

@martinfleis
Copy link

Hi,

thanks for this extension! I would like to store a bit more details for some columns than name, description, and type. I can technically do that already but I guess that doing so would violate the spec. Can we include an extra_fields option, similarly to the one in providers?

@TomAugspurger
Copy link
Collaborator

I think that JSON schema allows for arbitrary additional fields on any object. They just don't get validated. I think that pystac uses extra_fields for stuff that isn't necessarily from an extension.

So you're certainly free to store additional information there. But if you think it'd be generally useful then it'd make sense to standardize it as an optional field here.

@ankostis
Copy link

ankostis commented Nov 1, 2022

Some extra fields to consider (and hopefully STAC Browser to be able to search):

  • tags: arbitrary text
    -labels (hierarchical tags with some delimiter eg foo.bar)

@feefladder
Copy link

Additional extra field:
License
For example, if some columns are considered sensitive data, they would have a proprietary license, whereas the other columns would have an open license. The example I am working on now is in-situ measurements, of which the location can be considered sensitive.

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

4 participants