New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SVG patterns in landcover-area-symbols render inconsistently in different metatiles #2750

imagico opened this Issue Aug 14, 2017 · 2 comments


None yet
3 participants

imagico commented Aug 14, 2017

This is a followup on the after-merge discussion in #2727.

There we observed differences in SVG pattern rendering depending on unknown conditions leading to differences between metatiles.

The fact that so far the problem analyzed in #2727 (comment) only seems to occur with kosmtik bothered me. Since in the released version only three landcover patterns use SVGs, quarry does not use polygon-gamma (so would fall under point 4 in the list) and forest uses opacity in addition which might cause additional problems i looked for cases with scrub.

The OSMF servers use much larger metatiles so this is more difficult and due to the not so dense pattern you cannot usually readily see it but here an example:

1 2

As with beach there are more than two variants, the above is the most extreme case i could find. And no, this is not double mapping or so, it can be found in different places. A metatile edge can be seen here:

So yes, this appears to be a real problem and it already shows up in the map.

It affects patterns in landcover-area-symbols - if observations in kosmtik are representative patterns in the normal landcover layer will render incorrectly but consistently with polygon-gamma other than 1 and correctly otherwise (the latter being the current situation for the quarry pattern) polygon-pattern-gamma does not appear to have an effect on this.

@kocio-pl kocio-pl added the general label Aug 14, 2017

@kocio-pl kocio-pl added this to the Bugs and improvements milestone Aug 14, 2017

This was referenced Aug 15, 2017


This comment has been minimized.


kocio-pl commented Aug 20, 2017

Do you think it should be reported as an issue in Mapnik?


This comment has been minimized.


imagico commented Aug 23, 2017

In #2727 (comment) @springmeyer did not consider this a bug. You can still report it but unless this assessment changes a fix from side of Mapnik is probably unlikely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment