Skip to content

Weird convention for extent.bbox with 6 parameters #260

@rouault

Description

@rouault

/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.

Metadata

Metadata

Assignees

Labels

EditorialEditorial changes and document updates outside of requirements classesOGC API: CommonIssue related to general resources or requirements (see #190)Part 1: CoreIssue related to Part 1 - Core

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions