On Thu, May 12, 2011 at 9:28 AM, Sandro Santilli <s...@keybit.net> wrote: > On Thu, May 12, 2011 at 11:16:19AM -0400, J Smith wrote: >> On Thu, May 12, 2011 at 2:19 AM, Sandro Santilli <s...@keybit.net> wrote: >> > Right. In the PHP binding I've made a single function taking an associative >> > array for all the parameters (building a GEOSBufferParameter object). >> > >> >> Yeah, I noticed that and decided to follow suit. I'd like the two to >> be reasonably close together in terms of their APIs and conventions >> aside from the usual language quirks and conventions. > > Speaking of which... how did you deal with prepared geoms ? > I didnt' make any use of those from the PHP binding. Dunno if I want > them to be transparent or explicit. >
FWIW, Shapely has a prep() function that prepares a geometry. The result has a subset of the normal geometric object methods. http://gispython.org/shapely/docs/1.2/manual.html#prepared-geometry-operations -- Sean _______________________________________________ geos-devel mailing list geos-devel@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/geos-devel
