Thanks David.  FYI this has been fixed in r1730, per our IRC discussion.
 
..Tom
 


________________________________

        From: [email protected]
[mailto:[email protected]] On Behalf Of David
Winslow
        Sent: Wednesday, 25 May 2011 17:59
        To: gispython.org community projects
        Subject: [Community] Problems with latest trunk
        
        
        Hey all, 

        I'm working on getting GeoNode ready for a beta release (from
the branch where we normally use OWSLib trunk instead of a pegged
revision from SVN.)  I had to peg the revision to r1717, which is fairly
out of date (11 revisions and almost 2 months old).  It seems that
changes in r1718 to the way keywords in CSW metadata documents are
parsed means that OWSLib now only finds the first <keyword> from each
<MD_Keywords> element; afaik the schema allows multiple keywords there
and GeoNode currently relies on that being parsed out.  A sample
metadata document which exhibits the problem is attached.  We're
currently using GeoNetwork for the CSW service, by the way.

        I also ran into trouble with the change introduced with r1727;
this one causes OWSLib to raise an exception:

        Traceback (most recent call last):
          File "test.py", line 4, in <module>
            gn.getrecordbyid(["d62d748a-8716-11e0-b45d-0024d7173e24"],
outputschema=namespaces['gmd'])
          File "/home/dwins/Projects/OWSLib/owslib/csw.py", line 277, in
getrecordbyid
            self._parserecords(outputschema, esn)
          File "/home/dwins/Projects/OWSLib/owslib/csw.py", line 398, in
_parserecords
            self.records[identifier] = MD_Metadata(i)
          File "/home/dwins/Projects/OWSLib/owslib/iso.py", line 36, in
__init__
            self.xml = etree.tostring(md.getroot())
        AttributeError: 'Element' object has no attribute 'getroot'

        --
        David Winslow
        OpenGeo - http://opengeo.org/

_______________________________________________
Community mailing list
[email protected]
http://lists.gispython.org/mailman/listinfo/community

Reply via email to