Thanks Jon, I am using the generate_tiles.py script with a few small modifications I made. I made the change you suggested and that appears to have solved the problem. The blank tiles previously appeared fine on the far left side of the tile but had random vertical lines running down the right side. Thanks again I think the problem is solved. -Matt
--- On Sun, 6/29/08, Jon Burgess <[EMAIL PROTECTED]> wrote: From: Jon Burgess <[EMAIL PROTECTED]> Subject: Re: [Mapnik-users] empty tiles To: [EMAIL PROTECTED] Cc: [email protected] Date: Sunday, June 29, 2008, 1:52 PM On Sun, 2008-06-29 at 10:05 -0700, Matthew Rushton wrote: > Hi, > I'm using mapnik to render osm data. I have things working > relatively well except for empty tiles (land/sea). They do not get > rendered properly at both high and low zoom levels. I've looked for > documentation or previous questions regarding this and was unable to > find any answers. I was also curious if mapnik had any ability to > "detect" an empty tile and take another action to save disk space > etc... Thanks in advance. > -Matt > What are you using to do the rendering, generate_tiles.py? What do the tile that are 'not rendered properly' look like? I've seen problems before with some tiles appearing black and I believe it was due to a bug in the ImageMagick code called in the 'convert -colors 255' step of that script. You could try removing the convert lines and ask mapnik to save the files in 'png256' format which should be faster as well. I'm not aware of any code to handle the blank sea/land tile case. The mod_tile code mitigates the disk space issues somewhat by storing the images in blocks of 64 which makes the storage of the ~100 byte blank tiles much more efficient. Jon
_______________________________________________ Mapnik-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/mapnik-users
