Skip to content

define wms content by getCapabilities response #480

@kaestli

Description

@kaestli

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)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions