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

Already on GitHub? Sign in to your account

Raster Symbolizer not Scaling #1327

Michbeckable opened this Issue Jul 19, 2012 · 8 comments


None yet
2 participants

Hey, I hope this is the right place to aks questions and discuss about mapnik funtionality and problems.

I am currently using a Raster Symbolizer for hillshading. It works fine except for scaling. The Image is not scaled up, if it is needed bigger because of zoom level in rendering. It is properly scaled down. We have currently moved to a new server, it worked fine before. Maybe there is a library missing?

Our System: Mapnik 2.1.0 pre on Ubuntu 12.04.

The image got the correct GeoTIFF meta information. Mapnik puts it in correct position in rendering (upper left corner is correct) but it is put there and not scaled to fit the current zoom level.


springmeyer commented Jul 19, 2012

Please provide a testcase of a sample mapnik XML, what the image looks like, and what you expect it to look like.

The mapnik xml: http://www.michaelkeutel.de/tegernseeXML.txt
Correct Image: http://www.michaelkeutel.de/image.png
Wrong Image: http://www.michaelkeutel.de/image_wrong.png

In the wrong image I set the hillshading raster image opacity to 1.0 and no composite mode to show its position clearly.
I have already tried different mapnik xml files, even the original osm.xml, but it doesnt work.

Is this a known problem? Did the provided testcase images make the issue more clear?

It seems to depend on the zoom level. If I change the bounds of rendering for mapnikg the hillshade raster image scales properly!


springmeyer commented Jul 25, 2012

@michimichbeck - sounds like a bug, we'll take a look as soon as we have time. Thanks!


springmeyer commented Aug 14, 2012

looking like there is not time to dig into this before the 2.1 release, so I'm pushing off the milestone. We'll try to get to it soon after however.


springmeyer commented Mar 13, 2013

@michimichbeck - sorry I never got to this. Does the problem still persist for you with latest mapnik?

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