We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug At the collection level, pyQuARC was not flagging temporal extents that did not match with the granules.
Example UMM-C Record: C2066317191-LARC
Expected behavior pyQuARC should flag the Beginning and Ending Date Times.
For the beginning date time, 2017-06-01T00:00:00.000Z was provided at the collection level, but the granule is 2017-06-01T01:10:32Z.
For the ending date time, 2023-01-31T00:00:00.000Z was provided at the collection level, but the granule is 2023-01-29T15:48:31Z.
The text was updated successfully, but these errors were encountered:
binni979
No branches or pull requests
Describe the bug
At the collection level, pyQuARC was not flagging temporal extents that did not match with the granules.
Example
UMM-C Record: C2066317191-LARC
Expected behavior
pyQuARC should flag the Beginning and Ending Date Times.
For the beginning date time, 2017-06-01T00:00:00.000Z was provided at the collection level, but the granule is 2017-06-01T01:10:32Z.
For the ending date time, 2023-01-31T00:00:00.000Z was provided at the collection level, but the granule is 2023-01-29T15:48:31Z.
The text was updated successfully, but these errors were encountered: