[geos-devel] geos for perl

[Charlie Savage]

In the 2.2.xs series you'll have to regenerate your SWIG bindings.  Also 
if I remember correctly, python.i was missing in the distribution (but 
it is in the CVS branch).

I'd recommend using CVS head though since the SWIG bindings were redone 
to use the geos c api and were integrated into the geos build system.

Last, note that Ari did some work a while back on perl bindings but that 
was against the 2.2.x series.

Charlie

Kralidis,Tom [Burlington] wrote:
> Hi,
> 
> After some discussion on postgis-users, I thought I'd shift things over
> here.
> 
> We have a requirement in which we have much geospatial data which is NOT
> in PostGIS (shapefile, MySQL, MapInfo, etc.).  PostGIS contains
> functionality we desire, i.e., buffer, distance, etc.  Porting
> everything to PostGIS/PostgreSQL is not an option.
> 
> Since PostGIS is an add-on to PostgreSQL, we started to investigate the
> innards of PostGIS and how tied it is to PostgreSQL.
> 
> It seems that PostGIS is a set of natively defined functions, and
> additional functions if one compiles with geos.  Our spatial
> requirements would initially be:
> 
> - point-in-polygon
> - distance
> - buffers
> 
> Technology-wise, we would prefer if this was accessible via Perl.  geos
> has python and ruby swig bindings via swig.
> 
> What is the state of affairs w.r.t. geos' swig support?  For example, I
> tried building the python bindings just to see, however I had swig
> errors complaining about missing .i files.
> 
> Thanks
> 
> ..Tom
> 
> _______________________________________________
> geos-devel mailing list
> geos-devel at geos.refractions.net
> http://geos.refractions.net/mailman/listinfo/geos-devel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3237 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.osgeo.org/pipermail/geos-devel/attachments/20060906/fad8031c/smime.bin