Hi,
following up the request to show up a title and search on
title, abstract and keyword on the map preview I'm wondering
how to deal with layer groups, that have none of these
attributes.
I believe title must be added as a minimum, abstract
probably too since the group is published in the wms
capabilities as well.
Keywords, hmmm... I could sum up the keywords of the
layers making up the group, but maybe it's just easier
to add the as a configuration option?
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
+1 for additional configuration options, should act just like a real layer in my opinion
Andrea Aime wrote:
Hi,
following up the request to show up a title and search on
title, abstract and keyword on the map preview I'm wondering
how to deal with layer groups, that have none of these
attributes.
I believe title must be added as a minimum, abstract
probably too since the group is published in the wms
capabilities as well.
Keywords, hmmm... I could sum up the keywords of the
layers making up the group, but maybe it's just easier
to add the as a configuration option?
Cheers
Andrea
--
Arne Kepp
OpenGeo - http://opengeo.org
Expert service straight from the developers
Well technically LayerInfo does not have any of these attributes either. They all come from ResourceInfo, which is broken in terms of a resource-publishing split.
As for LayerGroupInfo it seems that this would indicate that it and LayerInfo should share come common super interface... I wonder if it makes sense to push all metadata type stuff into a LayerMedatadaInfo interface. And both LayerInfo and LayerGroupInfo could implement it.
As for the issue with the current ResourceInfo... how would people feel about deprecating those methods and moving them to LayerInfo?
-Justin
Arne Kepp wrote:
+1 for additional configuration options, should act just like a real layer in my opinion
Andrea Aime wrote:
Hi,
following up the request to show up a title and search on
title, abstract and keyword on the map preview I'm wondering
how to deal with layer groups, that have none of these
attributes.
I believe title must be added as a minimum, abstract
probably too since the group is published in the wms
capabilities as well.
Keywords, hmmm... I could sum up the keywords of the
layers making up the group, but maybe it's just easier
to add the as a configuration option?
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Justin Deoliveira ha scritto:
Well technically LayerInfo does not have any of these attributes either. They all come from ResourceInfo, which is broken in terms of a resource-publishing split.
As for LayerGroupInfo it seems that this would indicate that it and LayerInfo should share come common super interface... I wonder if it makes sense to push all metadata type stuff into a LayerMedatadaInfo interface. And both LayerInfo and LayerGroupInfo could implement it.
As for the issue with the current ResourceInfo... how would people feel about deprecating those methods and moving them to LayerInfo?
I would be ok but there is one catch: WFS and WCS reference resources
directly, so we'd loose the ability to build complete capabilities
documents.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
As for the issue with the current ResourceInfo... how would people feel about deprecating those methods and moving them to LayerInfo?
I would be ok but there is one catch: WFS and WCS reference resources
directly, so we'd loose the ability to build complete capabilities
documents.
Right... but with a resource-pub split they should go through layer. So perhaps we are not quite ready for this move. However... it may be possible to just port the capabilities requests over to use layer. I think (at least for wfs) that is the only place where the metadata is really used.
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Justin Deoliveira ha scritto:
As for the issue with the current ResourceInfo... how would people feel about deprecating those methods and moving them to LayerInfo?
I would be ok but there is one catch: WFS and WCS reference resources
directly, so we'd loose the ability to build complete capabilities
documents.
Right... but with a resource-pub split they should go through layer. So perhaps we are not quite ready for this move. However... it may be possible to just port the capabilities requests over to use layer. I think (at least for wfs) that is the only place where the metadata is really used.
A similar thing would happen for WCS, but we'd have to port over the
DescribeCoverage output as well.
Hum... what about workspace/namespace thought?
Layers are not in a workspace.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
A similar thing would happen for WCS, but we'd have to port over the
DescribeCoverage output as well.
Hum... what about workspace/namespace thought?
Layers are not in a workspace.
Good point, we will need Map as a qualifier to pull this off properly.
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.