On Mon, Jul 27, 2009 at 8:14 PM, Jeff Whitaker wrote:
> Chris Petrich wrote:
>>
>> Hi,
>>
>> I get a Topology Exception with GEOS 3.1:
>>
>> import mpl_toolkits.basemap as bm
>> print "GEOS version: ", bm._geoslib.__geos_version__
>> print "basemap version: ", bm.__version__
>>
>> m = bm.Basemap(wi
Chris Petrich wrote:
> Hi,
>
> I get a Topology Exception with GEOS 3.1:
>
> import mpl_toolkits.basemap as bm
> print "GEOS version: ", bm._geoslib.__geos_version__
> print "basemap version: ", bm.__version__
>
> m = bm.Basemap(width=1200,height=800, \
> resolution='l',projecti
Hi,
I get a Topology Exception with GEOS 3.1:
import mpl_toolkits.basemap as bm
print "GEOS version: ", bm._geoslib.__geos_version__
print "basemap version: ", bm.__version__
m = bm.Basemap(width=1200,height=800, \
resolution='l',projection='laea',\
lat_0=55,lon_0
I committed the original example into the svn, and I admit that I was
not careful with the code. I agree that the arguments should be float
(the doc does say that set_alpha takes float).
The example is now updated to use floats (svn r7300).
Regards,
-JJ
On Mon, Jul 27, 2009 at 9:15 AM, Michiel
In svn 7298 I changed a key chunk of code that was working fine, so I
would like to explain why I fixed it when it wasn't broken, and ask for
review and testing, or at least keeping your eyes open for anything I
may have overlooked.
In the course of making the very simple change to support scal
Hi everybody,
Should the set_alpha method of a graphics context accept a string (instead of a
number) as an argument? Currently, some backends (agg, ps, pdf) accept strings
such as "0.2", whereas others (svg, cairo, Mac OS X) do not. Usually that is
not a problem, since in almost all cases set
