-
Notifications
You must be signed in to change notification settings - Fork 16
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
Comments
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. |
This is a good question... In Coverages I suggested that one could add a query parameter to I think at minimum we would need to advertise the extent in the storageCRS in the collection description. |
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":
|
For example, see below.
The text was updated successfully, but these errors were encountered: