Great ! I was not very happy to have to code with C/libGEOS again. Even if I don't directly instantiate the GeometryCollection class, intersection method sometimes returns such an object and I have to deal with this case.
Thanks Pascal 2008/10/4 <[EMAIL PROTECTED]> > Hi Pascal, > > Rings are underdocumented, but safe; the design of collections is not > quite complete and I am trying to discourage unnecessary use of > collections, but you can count on all collections having a "geoms" > attribute for access to members of the collection. > > Sean > > > Hi, > > > > Some libGEOS C "objects" are not decribed in the Shapely manual, even if > > the > > corresponding Python class exists : Collection or LinearRing for > instance. > > > > What does it mean ? Is it only a difference between the documentation and > > the library itself or is there any problem/risk to use these classes ? > And > > in this case, what do I do when I call the "intersection" method and I > get > > a > > Collection/LinearRing instance ? > > > > Pascal > > _______________________________________________ > > Community mailing list > > [email protected] > > http://lists.gispython.org/mailman/listinfo/community > > > > > _______________________________________________ > Community mailing list > [email protected] > http://lists.gispython.org/mailman/listinfo/community >
_______________________________________________ Community mailing list [email protected] http://lists.gispython.org/mailman/listinfo/community
