Hi Ivan,
Many thanks for the patch. Do we need to introduce a new attribute
'layers' to solve this problem?
(given that we already have 'contents').
I know layers is the WMS term but we settled on contents as a
cross-service way of harmonising things in OWSLib so it would be good to
maintain that consistency (it's described in owslib/interfaces.py)
Regards
Dom
On 27/04/11 09:39, [email protected] wrote:
http://trac.gispython.org/lab/ticket/215
It collects 'roots' of layers into owslib.wms.WebMapService's layers
attribute (there may be any number of such layers, so it is a list),
and each ContentMetadata has attribute children that stores list of
children.
Of course, there may be a better name than 'layers' for the
WebMapService attribute.
Code is also available at my GitHub repository, branch tree:
https://github.com/monoid/owslib/tree/tree
--
Ivan Boldyrev
--
Scanned by iCritical.
_______________________________________________
Community mailing list
[email protected]
http://lists.gispython.org/mailman/listinfo/community
