[geos-devel] Second beta for ffi-geos extension now available

Daniel Azuma dazuma at alumni.caltech.edu
Thu May 12 12:46:00 EDT 2011

Just a little opinion on this, as I'm actually starting to use ffi-geos. If it is to be the de facto ruby binding for GEOS, it should expose the same flexibility that GEOS provides, including control over when and whether to produce a prepared geometry, so that clients that need that level of control can have it. A transparent implementation is very useful and could also be done, but it should be an optional API that can be turned on or off.


On 12 May, 2011, at 08:57, J Smith wrote:

> On Thu, May 12, 2011 at 11:50 AM, Sandro Santilli <strk at keybit.net> wrote:
>> So both Python and Ruby made the "PreparedGeometry" type explicit.
>> I was thinking more of a .prep() function returning void and internally
>> holding a prepared version to transparently use in all prepared-aware
>> methods. This would kind of follow PostGIS use, where you actually don't
>> even explicitly call the "prepare" which happens based on an heuristic
>> (the second time you run a predicate on a geometry that geometry gets
>> prepared). The advantage of transparency would be there's no API change
>> but automatic performance improvement.
> I'd be open to that sort of thing. I'm still in beta after all.

More information about the geos-devel mailing list