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 bbox schema #1243

Closed
drwelby opened this issue Aug 15, 2023 · 3 comments · Fixed by #1260
Closed

Collection bbox schema #1243

drwelby opened this issue Aug 15, 2023 · 3 comments · Fixed by #1260

Comments

@drwelby
Copy link

drwelby commented Aug 15, 2023

The definition of the bbox spatial extents has non-obvious construction:

The first bounding box always describes the overall spatial extent of the data. All subsequent bounding boxes can be used to provide a more precise description of the extent and identify clusters of data.

i.e.
[[extent]] or [[extent], [child], [child]...]

Should the schema try to catch people interpreting the spec as a simple list of bboxes by enforcing either a length of 1 or 3?

Or is that too restrictive and the catch should be passed down to validators like stac-check?

@emmanuelmathot emmanuelmathot added this to the 1.1 milestone Sep 5, 2023
@emmanuelmathot
Copy link
Collaborator

We could add reference to the same spec as geojson RFC for items.

@m-mohr
Copy link
Collaborator

m-mohr commented Oct 5, 2023

Yeah, that makes sense. Two bboxes don't make sense.

So either one or 3 or more.

m-mohr added a commit that referenced this issue Oct 5, 2023
@m-mohr m-mohr linked a pull request Oct 5, 2023 that will close this issue
4 tasks
@m-mohr
Copy link
Collaborator

m-mohr commented Oct 5, 2023

See PR #1260

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants