>
> https://github.com/rnorris/viking/compare/MapnikRenderingLayer
>
A few updates have been applied.
Split Mapnik rendering into a separate thread pool, with a default value of 1
to avoid any potential multi threading issues.
GUI control can increase the number of threads used so the adventuro
> From: g...@ir.bbn.com
> To: rw_nor...@hotmail.com
> CC: viking-devel@lists.sourceforge.net
> Subject: Re: [Viking-devel] Viking Map Generation with Mapnik C++ Library.
> Date: Mon, 2 Feb 2015 09:40:10 -0500
>
>
> Robert Norris
Robert Norris writes:
> Tiles are cached in directory specified in the Mapnik Rendering layer
> property (it defaults to ~/.viking-maps/MapnikRendering - so for
> different stylesheets it's wise to change this to a specific directory
> per style) - the cache is always in the OSM Slippymap layout
> From: g...@ir.bbn.com
> To: rw_nor...@hotmail.com
> CC: viking-devel@lists.sourceforge.net
> Subject: Re: [Viking-devel] Viking Map Generation with Mapnik C++ Library.
> Date: Sun, 1 Feb 2015 11:22:58 -0500
>
>
> Wow, that'
Wow, that's very cool.
It would be really nice if the mapnik dependency could somehow be
additional rather than either/or. From a packaging viewpoint, I'd like
to see a way to have
base viking
viking-mapnik
but perhaps what's unwarranted as it's not clear that mapnik is that
heavy.
Thinki
