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

Weird convention for extent.bbox with 6 parameters #260

Closed
rouault opened this issue Sep 10, 2019 · 2 comments · Fixed by #263
Closed

Weird convention for extent.bbox with 6 parameters #260

rouault opened this issue Sep 10, 2019 · 2 comments · Fixed by #263
Assignees
Labels
Editorial Editorial changes and document updates outside of requirements classes OGC API: Common Issue related to general resources or requirements (see #190) Part 1: Core Issue related to Part 1 - Core

Comments

@rouault
Copy link
Contributor

rouault commented Sep 10, 2019

/core/openapi/ogcapi-features-1.yaml mentions

        * Lower left corner, coordinate axis 1
        * Lower left corner, coordinate axis 2
        * Lower left corner, coordinate axis 3 (optional)
        * Upper right corner, coordinate axis 1
        * Upper right corner, coordinate axis 2
        * Upper right corner, coordinate axis 3 (optional)

Regarding the Z axis, it seems a bit useless to take the elevation precisely at the LL and UR corners. I guess what people really want is the minimum and maximum elevation of the geometries over the whole collection.

@cportele cportele added Part 1: Core Issue related to Part 1 - Core OGC API: Common Issue related to general resources or requirements (see #190) labels Sep 10, 2019
@cportele cportele added the Editorial Editorial changes and document updates outside of requirements classes label Sep 10, 2019
@cportele
Copy link
Member

This is of course what is meant. In 3D the bbox is a box, not a rectangle.

I will check, if we can update the wording at this stage in the process to make that clearer.

@cportele cportele self-assigned this Sep 10, 2019
cportele added a commit that referenced this issue Sep 11, 2019
@cportele
Copy link
Member

@rouault @pvretano

I have created a pull request, #263. Could you check, if this would be clearer?

As an aside, out of interest I had a look at GeoJSON and their wording has a similar ambiguity/confusion (link):

The value of the bbox member MUST be an array of length 2*n where n is the number of dimensions represented in the contained geometries, with all axes of the most southwesterly point followed by all axes of the more northeasterly point.

cportele added a commit that referenced this issue Sep 16, 2019
Clarification of wording for 3D bounding boxes. resolves #259, resolves #260.

Change approved by the OGC Planning Committee.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Editorial Editorial changes and document updates outside of requirements classes OGC API: Common Issue related to general resources or requirements (see #190) Part 1: Core Issue related to Part 1 - Core
Projects
Development

Successfully merging a pull request may close this issue.

2 participants