You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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.
Hi,
thanks for this extension! I would like to store a bit more details for some columns than
name
,description
, andtype
. I can technically do that already but I guess that doing so would violate the spec. Can we include anextra_fields
option, similarly to the one in providers?The text was updated successfully, but these errors were encountered: