Jeff Whitaker wrote:
> Chris: I don't consider the pyrex GEOS interface I created for basemap
> a general-purpose binding - it's limited to the only the functionality
> that basemap needs.
sure, but if there was an existing general purpose binding that met your
needs, you wouldn't need this.
Christopher Barker wrote:
> Jeff,
>
> as you mentioned license as one issue in not using shapely, I thought
> you might be interested in this:
>
> Original Message
> Subject: [Community] Proposal to change Shapely license from LGPL to BSD
> From: Sean Gillies <[EMAIL PROTECTED]>
Christopher Barker wrote:
[...]
> As for ctypes vs. pyrex -- I find it ironic that you've chosen pyrex for
> dependency reasons -- there are lot of folks that using ctypes to asve
> the hassles of compiliation, particularly on Windows (see geoGjango, for
> instance). But I guess MPL required com
Jeff,
as you mentioned license as one issue in not using shapely, I thought
you might be interested in this:
Original Message
Subject: [Community] Proposal to change Shapely license from LGPL to BSD
From: Sean Gillies <[EMAIL PROTECTED]>
I propose that the Shapely license be c
Christopher Barker wrote:
> Jeff Whitaker wrote:
>
>> 1) an external dependency on the GEOS lib (which is LGPL).
>>
>
> Would it be any better to depend on an existing python binding GEOS?
> Here's one option:
>
> http://trac.gispython.org/projects/PCL/wiki/Shapely
>
> -Chris
>
>
>
Chri
Christopher Barker wrote:
>
> Jeff Whitaker wrote:
>> 1) an external dependency on the GEOS lib (which is LGPL).
>
> Would it be any better to depend on an existing python binding GEOS?
> Here's one option:
>
> http://trac.gispython.org/projects/PCL/wiki/Shapely
That is what Jeff started with,
Jeff Whitaker wrote:
> 1) an external dependency on the GEOS lib (which is LGPL).
Would it be any better to depend on an existing python binding GEOS?
Here's one option:
http://trac.gispython.org/projects/PCL/wiki/Shapely
-Chris
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Respons
