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

root layer metadata #4129

Closed
mapserver-bot opened this Issue Apr 4, 2012 · 5 comments

Comments

Projects
None yet
2 participants
@mapserver-bot

mapserver-bot commented Apr 4, 2012

Reporter: mko
Date: 2011/12/16 - 10:52
Trac URL: http://trac.osgeo.org/mapserver/ticket/4129
If there's a named root layer, all WMS metadata we use at LAYER level may be required for the root layer, too. E.g. metadataurl, dataurl, style, authorityurl etc.

According to the current code, the root layer is handled by msWMSGetCapabilities() and the others by msDumpLayer(). This should be harmonized. We should also discuss the possibility to configure the root layer using a common LAYER section in future versions.

@mapserver-bot

This comment has been minimized.

mapserver-bot commented Apr 4, 2012

Author: dmorissette
Date: 2011/12/16 - 16:06
The current logic is that the root layer corresponds to the mapfile as a whole, and then it contains individual layer children for each mapfile layer. That's why we use map-level metadata to produce the root layer capabilities. It's not clear to me what you are trying to achieve that is not possible at the moment... is it just that support for a few metadata entries is lacking at the root level? I didn't look at the code lately, but it may be that some refactoring is required to reuse the same function to output WMS metadata in both cases, without changing the fact that the root layer corresponds to the map as a whole.

@mapserver-bot

This comment has been minimized.

mapserver-bot commented Apr 4, 2012

Author: mko
Date: 2012/01/05 - 21:27
When a rootlayer has a name, it behaves as an ordinary layer and clients may expect common information in capabilities document, such as MetadataUrl, Identifier, Styles etc. Most of it can be solved by copy-paste the relevant code from msDumpLayer() to msWMSGetCapabilities(). But for later major releases, I can also think of using the map-level metadata for the OGC service sections only and reading the root layer from a common layer block. Less code, more features -- harder to configure, because there's only one 'root' layer (otherwise this problem probably wouldn't exist).

@mapserver-bot

This comment has been minimized.

mapserver-bot commented Apr 4, 2012

Author: schpidi
Date: 2012/02/04 - 23:17
Added the patch, slightly adopted, to the inspire sandbox with r13034.

I currently don't see the necessity to change the logic and agree with Daniel to leave it as is.

@mapserver-bot

This comment has been minimized.

mapserver-bot commented Apr 4, 2012

Author: schpidi
Date: 2012/03/19 - 18:04
Closing this ticket as the INSPIRE sandbox has been merged to trunk with d6e40e6 (r13214).

@mapserver-bot

This comment has been minimized.

mapserver-bot commented Apr 5, 2012

attachment http://trac.osgeo.org/mapserver/attachment/ticket/4129/metadataurl_dataurl_authorityurl_identifier.patch :

   Adds the elements AuthorityUrl, Identifier, MetadataUrl, DataUrl to the root layer capabilities section

@ghost ghost assigned Schpidi Apr 5, 2012

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