Hi David, I'd welcome a patch on this - that would be great.
It's worth noting that we're trying to keep the interfaces harmonized across service types as much as possible - however I had a look at WCS and WFS to see if there is anything similar and there isn't - so in this case I think it's fine just to extend the WMS content metadata section. I think it would be more in keeping with the rest of the library if it was a dictionary at this level rather than another type of object - as you can see here most things at the content metadata level are lists/strings/dictionaries etc: http://trac.gispython.org/lab/browser/OWSLib/trunk/owslib/interfaces.py#L139 Anyway a patch would be welcomed! Also it would be good to work this into a test somewhere - if you have a capabilities XML document that supports this we could use that as a basis for testing. Cheers, Dominic On 03/12/09 17:20, David Winslow wrote: > Hi all, > > For a project I'm working on, I'd like to access the Attribution field > on some layers in a WMS capabilities document. I'd love to use OWSLib > (looks like it would be a lot easier to use than parsing the XML > directly), but when I try to retrieve the Attribution I just get an > empty string (or None if there is no attribution for the layer.) I was > expecting an object with the title, logo URL, and link for the Attribution. > > Digging into the code a bit I see that Attribution is parsed in exactly > the same way as Name and Title, so it will always be a string. Would it > be reasonable to change this to an object or dictionary with the fields > I mentioned above? > > I would be happy to put together a patch if there's interest. > > -- > David Winslow > OpenGeo - http://opengeo.org/ > _______________________________________________ > Community mailing list > [email protected] > http://lists.gispython.org/mailman/listinfo/community _______________________________________________ Community mailing list [email protected] http://lists.gispython.org/mailman/listinfo/community
