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

Clarification on multiple bounding boxes in an extent #519

Closed
cportele opened this issue Mar 15, 2021 · 1 comment
Closed

Clarification on multiple bounding boxes in an extent #519

cportele opened this issue Mar 15, 2021 · 1 comment
Labels
duplicate Part 1: Core Issue related to Part 1 - Core

Comments

@cportele
Copy link
Member

As part of the discussion in #168 we allowed multiple bboxes and time intervals as part of the extent information for a collection, but for Core we basically restricted it to a single bbox/interval. I have not seen any API or client that has used multiple bboxes/intervals so far.

In the discussions in Common (see opengeospatial/ogcapi-common#91) the issue was raised that any client that just looks at the first bbox/interval and uses that will be mislead.

The idea of the change in #168 was to make it extensible for future parts. If no implementation is known to have used the multiplicity yet (we would need to verify this), it might be a good idea to address the issue by clarifying that

  • the first bbox/time interval always includes the complete spatial/temporal extent (e.g., all of the US);
  • the second to nth bbox/time interval would be a more detailed extent specification (e.g., the bboxes of the continental US, Hawai, Alaska).

Clients that just want the simple solution (a single bbox/interval) can just use the first array, just as they do now. Clients that want to process the details can do that, too, with the additional clarification about the first bbox/interval.

Any thoughts?

@cportele cportele added the Part 1: Core Issue related to Part 1 - Core label Mar 15, 2021
@cportele
Copy link
Member Author

I had network problems and GitHub created this issue twice...

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

No branches or pull requests

1 participant