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

define wms content by getCapabilities response #480

Open
kaestli opened this issue Sep 11, 2019 · 0 comments
Open

define wms content by getCapabilities response #480

kaestli opened this issue Sep 11, 2019 · 0 comments

Comments

@kaestli
Copy link

kaestli commented Sep 11, 2019

Rather than defining the web service to retrieve different layers (wms request=getMap), I'd suggest to provide / expect metadata describing the request=getCapabilities service; that service does not only provide the list of layers available, but also extended metadata on these layers (e.g. layer-specific projection lists, abstracts etc.)
Further, the layer list would be dynamic, not requiring the change of dcat metadata if layers are added/removed.
(improvement, actually not of the dcat definition but of the way how it is used, and of the depending applications)

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

No branches or pull requests

1 participant