matplotlib-users Mailing List for matplotlib

florisvb <flo...@gm...> writes:
> I'm trying to get my pdf outputs from matplotlib to work properly in
> illustrator, but keep having the issue that illustrator does not recognize
> the computer modern fonts (eg. CMR10 etc). Everything else seems to work
> perfectly.
Is there any error message from illustrator? If you view the pdf file in
Acrobat Reader and choose the document information dialog, what type
does it list the CMR10 font as? I think this would usually be Type 1,
and there could be some problem with how Type-1 fonts get embedded.
> text.usetex: True
Do you need usetex or is matplotlib's built-in formula rendering
sufficient? In the latter case TrueType versions of the various fonts
are embedded, which just might work better than Type 1.
-- 
Jouni K. Seppänen
http://www.iki.fi/jks

On 9/15/12 8:05 AM, Joachim Saul wrote:
> Hi there,
>
> in basemap coastlines are apparently (always?) drawn as closed polygons not exceeding the map boundary, i.e. when the coastline intersects with the map boundary the polygon is continued along the map boundary until the next intersection point. The somewhat annoying side effect of this is a map boundary that appears thicker where it crosses landmasses. See for instance on http://matplotlib.org/basemap/users/examples the example "Plot hurricane tracks from a shapefile" where clearly the upper and left map boundaries are thicker where they cross the western U.S. or northern Canada. Another example where this effect is particularly pronounced is the example "Draw great circle between NY and London" on the same page. The effect gets worse if running these examples without antialiasing. Apparently only the upper and left boundaries are affected, whereas the lower and right boundaries are plotted properly.
>
> It looks to me as if this might simply be a bug due to the coastline not aligning perfectly with the map boundary, perhaps because of some roundoff error. Is there a way to avoid this? Wouldn't it be better to draw the coastlines not as closed polygons but as collections of line segments?
>
> Cheers,
> Joachim
>
Joachim: I've noticed this myself, but have not found any solution. I 
suppose I could add an option to treat coastlines as line segments, but 
then you would not be able to use the fillcontinents method. Here's 
what happens now when a Basemap instance is created:
1) the intersection between the coastline polygons and the map boundary 
is computed using the geos C library.
2) the coastline polygons are clipped at the map boundary
3) the coordinates of the coastline polygons are transformed to map 
projection coordinates
Then, when the drawcoastlines or fillcontinents methods are called only 
the polygons inside the map projection region are drawn. This saves *a 
lot* of time when you're using high-resolution coastlines in a small map 
region. There is a similar process for political boundaries, but since 
they are line segments you don't see the "thickening" around the map edges.
Maybe one solution would be to clip the polygons to a region slightly 
larger than the actual map projection region.
-Jeff

Hi there,
in basemap coastlines are apparently (always?) drawn as closed polygons not exceeding the map boundary, i.e. when the coastline intersects with the map boundary the polygon is continued along the map boundary until the next intersection point. The somewhat annoying side effect of this is a map boundary that appears thicker where it crosses landmasses. See for instance on http://matplotlib.org/basemap/users/examples the example "Plot hurricane tracks from a shapefile" where clearly the upper and left map boundaries are thicker where they cross the western U.S. or northern Canada. Another example where this effect is particularly pronounced is the example "Draw great circle between NY and London" on the same page. The effect gets worse if running these examples without antialiasing. Apparently only the upper and left boundaries are affected, whereas the lower and right boundaries are plotted properly.
It looks to me as if this might simply be a bug due to the coastline not aligning perfectly with the map boundary, perhaps because of some roundoff error. Is there a way to avoid this? Wouldn't it be better to draw the coastlines not as closed polygons but as collections of line segments?
Cheers,
Joachim

Bump for this topic; I'd still love to know what the right thing is to do
here.
On Mon, Aug 20, 2012 at 10:08 PM, Daniel Hyams <dh...@gm...> wrote:
> Hmm, I just found out that if I change path.Path.contains_point to use
> "point_on_path" instead of "point_in_path", the containment tests work
> properly. I'm not that familiar with the path code...is the difference
> that one is testing for polygonal insideness, and one is testing for
> literally being on the "stroke"? If so, do we have to make sure that the
> proper one is called if there are no polygons involved in the path?
>
>
> On Mon, Aug 20, 2012 at 9:28 PM, Daniel Hyams <dh...@gm...> wrote:
>
>> I've run into a strange problem with contains() on an arrow; there is a
>> large area to the left of the arrow that insists that it is contained
>> within the arrow. Small runnable sample attached.
>>
>> I've looked at the path for the arrow, and it looks fine to me. I even
>> went so far as to hack a STOP onto the end of the path, but that resulted
>> in the same behavior.
>>
>> Can anyone else confirm this behavior? matplotlib 1.1.1 is what I'm
>> using. Seen on both Windows, Linux, and OSX.
>>
>> --
>> Daniel Hyams
>> dh...@gm...
>>
>
>
>
> --
> Daniel Hyams
> dh...@gm...
>
-- 
Daniel Hyams
dh...@gm...