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

Collection extent: End inclusive or exclusive #934

Open
m-mohr opened this issue Jun 28, 2024 · 3 comments
Open

Collection extent: End inclusive or exclusive #934

m-mohr opened this issue Jun 28, 2024 · 3 comments
Assignees
Labels
Part 1: Core Issue related to Part 1 - Core

Comments

@m-mohr
Copy link
Contributor

m-mohr commented Jun 28, 2024

Is the end timestamp that is specified in the extents.temporal.interval property of a Collection as second element of each subarray inclusive or exclusive? I can't find it defined in the specification.

@cportele cportele self-assigned this Jun 29, 2024
@cportele cportele added the Part 1: Core Issue related to Part 1 - Core label Jun 29, 2024
@cportele cportele moved this from Backlog to To be drafted in Features Part 1: Core Jun 29, 2024
@cportele
Copy link
Member

You are correct, it is not clearly stated. For me it was always clear that for both the spatial and temporal extent that the ends are inclusive.

The current requirement is worded as "each feature in the collection SHALL be inside the extent described by the first time interval in the interval array." The wording is similar for the spatial extent.

I think, instead of "inside" we should use the spatial and temporal predicates from CQL2 to state the requirement, in particular since CQL2 is now approved. I will create a PR.

As an aside, in CQL2 intervals are closed at both ends.

@cportele
Copy link
Member

cportele commented Jul 1, 2024

Meeting 2024-07-01: @cportele will create a pull request as proposed in his comment.

@m-mohr
Copy link
Contributor Author

m-mohr commented Jul 1, 2024

Thank you, Clemens. That's a very welcome clarification as we were discussing that in STAC recently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Part 1: Core Issue related to Part 1 - Core
Projects
Status: To be drafted
Development

No branches or pull requests

2 participants