-
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
Add CI? #1
Comments
I agree -- once I am done drafting out a README for the repo I will work on adding a workflow for PRs and pushes to master. |
I'm not sure if this is just a personal issue, but the STAC validator doesn't seem to be fetching the specifications properly:
It looks like the source code for the validator hasn't been updated in nearly a year, so we may have to push for some updates to be made before it is useful for testing. In the meantime, could you check if the follow works for you?
|
I would ping @m-mohr on this. He has been very helpful in the past. |
STAC Validator is a bit outdated unfortunately, I'm not sure it supports the latest versions yet. @jbants has developed it. Any news, James? I think for now I'd go with a normal JSON Schema Validator that can pull in the external references. |
Added some basic CI using |
Things got on speed today... I started working on a STAC validator, for node though. Other people are working on refreshing the python implementations. |
Based on the discussion in radiantearth/stac-spec#781 (comment), it sounds like the python stac validator may be working now. Should we give it a try again? https://github.com/m-mohr/stac-node-validator/blob/master/COMPARISON.md |
One caveat: You are using an external JSON Schema for validating your extension, which is currently only supported by the Node Validator. But for general validation against the STAC Core and other extensions, the Python validator works just fine. It's the "Validates External / Custom Extensions" entry in the table... Edit: Although I now see there's the --custom flag, which might work... |
Can you help me understand this? What is the external JSON schema you are referring to? |
@rabernat See my comment here, which should explain it based on an example: https://github.com/NCAR/esm-collection-spec/pull/23/files#r482980123 |
Thanks for the feedback. Again, I think there is some confusion around esm-collection-spec. The catalog in this repo does not yet attempt to use esm-collection-spec. For now, we are simply trying to catalog indivudal zarr stores in a standard STAC catalog hierarchy. So there is no external schema. |
Okay, yeah, I'm indeed a bit confused. |
There are basically two scenarios:
|
Fantastic work Charles! This is really a great start!
You may want to consider adding a github action to run the STAC validator on the catalog. I know it won't validate yet, but this will help in the future.
The text was updated successfully, but these errors were encountered: