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

Part 2: missing capability of reporting collection extent in a non CRS84-CRS #777

Open
rouault opened this issue Dec 2, 2022 · 1 comment

Comments

@rouault
Copy link
Contributor

rouault commented Dec 2, 2022

Part 1 has a provision, in the /collection response, for a extent.spatial.crs member. In Part 1, it is optional and, if specified, restricted to CRS84 / CRS84h.
Part 2 doesn't unlock that restriction to other CRS.
Ideally we'd also want to be able to specify the spatial extent in multiple CRSs, because reprojection of the bounding box expressed in one CRS to another one might add significant "padding". e.g from CRS84 to a projected nativeCRS, when the area of interest is at high latitudes

@cportele cportele added the Part 1: Core Issue related to Part 1 - Core label Jan 16, 2023
@cportele cportele added this to Backlog in Part 1: Core via automation Jan 16, 2023
@jerstlouis
Copy link
Member

jerstlouis commented Jan 30, 2023

In OGC API - Maps (Coverages TODO), we defined "storageCrsExtent" (in addition to the WGS84 extent):

opengeospatial/ogcapi-maps#45 (comment)

See also http://docs.ogc.org/DRAFTS/20-058.html Requirement 46 D and Example 8.

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 Part 2: CRS
Development

No branches or pull requests

3 participants