-
Notifications
You must be signed in to change notification settings - Fork 0
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
how to interpret pystac oneOf validation error #37
Comments
does this section saying AnyOf the extensions need to be specified: https://gist.github.com/rbavery/7c1875b2130dc78c48489b4ba86febb1#file-pystac_validation_error_mlm-txt-L552 conflict with this section which doesn't indicate they are required? https://github.com/crim-ca/mlm-extension?tab=readme-ov-file#bands-and-statistics |
We could remove the extra One thing to consider is that Another thing to consider is that, because the schema is describing GeoJSON-like contents, For example: {
"$comment": "This is the JSON-object 'properties' definition.", # OK
"properties": {
"$comment": "This is the STAC-Item 'properties' field.", # NOT OK (expect schema-type)
"properties": {
"$comment": "This is the JSON-object 'properties' definition for the STAC Item 'properties' field.", # OK
"properties": {
"$comment": "Required MLM pretraining reference.", # NOT OK (expect schema-type)
"mlm:pretrained": {
"const": false
}
}
}
}
} |
❓ Question
Why is validation failing for this pystac item? I did some sleuthing and it seems like the problem might with the jsonschema itself not the STAC Item.
https://www.jsonschemavalidator.net/s/NEnpmfAn
But maybe this is a separate issue and the validator on that website does not reflect the validation we do with pystac.
My other theory is that from the examples, we don't include any that include bands only as a list of strings, though we specify in the readme that this is accepted. I'm wondering if one of raster or eo extension metadata needs to be present if any bands are specified.
here is the gist of the json I'm validating and the error.
https://gist.github.com/rbavery/7c1875b2130dc78c48489b4ba86febb1
The text was updated successfully, but these errors were encountered: