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

Do we need a spatial extent for each CRS that the server supports #45

Closed
ghobona opened this issue Jul 28, 2020 · 3 comments
Closed

Do we need a spatial extent for each CRS that the server supports #45

ghobona opened this issue Jul 28, 2020 · 3 comments

Comments

@ghobona
Copy link
Contributor

ghobona commented Jul 28, 2020

For example, see below.

{
  "crsSpatialExtents": [
    {
      "bbox": [
        -180,
        -90,
        180,
        90
      ],
      "crs": "http://www.opengis.net/def/crs/OGC/1.3/CRS84"
    },
    {
      "bbox": [
        -20037508.3427892,
        -20037508.3427892,
        20037508.3427892,
        20037508.3427892
      ],
      "crs": "http://www.opengis.net/def/crs/EPSG/0/3395"
    }
]
}
  
@bradh
Copy link
Contributor

bradh commented Jan 16, 2021

This could rapidly get out of hand (e.g. if the server has a full EPSG data set, it'll be thousands of entries). Suggest keeping it to a required entry (e.g. CRS84) and allowing clients to reproject it if needed.

@jerstlouis
Copy link
Member

This is a good question... In Coverages I suggested that one could add a query parameter to /coverage/domainset to retrieve the domainset in a CRS different than the storageCRS.

I think at minimum we would need to advertise the extent in the storageCRS in the collection description.
storageCRSExtent or similarly named property?

@joanma747
Copy link
Contributor

We agreed that listing every CRS will be too verbose. Instead the real "limits" of the extent are defined by the stored "stuff".

Done for storageCRS in Requirement Classes "Geospatial Data Map" and "Dataset Map":

"storageCrsExtent": {
    "spatial" : {
         "bbox" : [ [ 47736, 4421022, 797736, 4734022 ] ]
    }
  },

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

No branches or pull requests

4 participants