On Sep 24, 2010, at 12:00 AM, Noli Sicad wrote:

> Dane,
> 
> Would mapnik can be easily incorporated to Thuban?  Thuban uses
> Wxpython and it is purely python GIS.
> 

Mapnik is a library, so should be well suited for being called as a renderer by 
any application written in C++ or Python (and some have used Mapnik as the 
desktop rendering engine behind C#/.NET apps.)


> http://thuban.intevation.org/doc/users_manual_for_thuban_1.0/html/c34.html
> 
> Noli
> 
> 
> 
> On 9/24/10, Dane Springmeyer <[email protected]> wrote:
>> 
>> On Sep 23, 2010, at 8:15 PM, Angus Dickey wrote:
>> 
>>> Hi,
>>> 
>>> I am new to Mapnik and was thinking about using Mapnik as the mapping
>>> solution for a desktop GIS application. My initial thoughts were to use:
>>> 
>>> - Python
>>> - wxPython
>>> - Mapnik
>>> 
>> 
>> Sounds fun!
>> 
>>> With other packages (OGR/GDAL, Shapely, pyproj, etc.) if needed.
>> 
>> Yep.
>> 
>>> 
>>> I have looked at the Mapnik samples and API and I know it can make a great
>>> looking map, what I am not sure about is the ability to add a
>>> temporary/dynamic layer.
>> 
>> You have full access in Python for dynamically constructing both styles and
>> layers. I recommend creating your own container for them, then pushing them
>> into a mapnik.Map once you are ready to render.
>> 
>> You can also have a base set of styles+layers in a mapnik.Map that is not
>> temporary and then render temp layers to a different mapnik.Image, then
>> blend the two together using im.blend().
>> 
>>> What I would like to be able to do is have Mapnik set up with static
>>> background mapping data and add markup (or temp layers) to Mapnik made up
>>> of geometry (points/lines/polys) calculated elsewhere.
>> 
>> Sort of. It is not yet exposed in Mapnik properly to push geometries
>> straight into a memory Datasource (only points are wrapped via
>> PointDatasource), so its easier to read from disk (even if you create all
>> definitions of the layer on the fly).
>> 
>>> Is this possible in Mapnik? I see there are some provisions for a "Memory
>>> Datasource" but it looks like it only supports points?
>> 
>> Right. Basically we've been waiting on a proper wkt/wkb parsing support.
>> 
>> However, you can actually do this right now if you have shapely installed,
>> see:
>> 
>> http://code.google.com/p/mapnik-utils/source/detail?r=1049
>> 
>> NOTE: depends on Mapnik trunk.
>> 
>>> 
>>> Anyone have any thoughts on how this might be done? I thought about having
>>> a text based OGR layer (GeoJSON?) added to Mapnik and changing this file
>>> on disk; doesn't really seem like a good idea though...
>> 
>> Its a fine idea and one that is used by nikweb. But yes, it would feel nicer
>> to push them in dynamically and for now see the above script and let me know
>> your comments. Alberto Valverde was the clever Mapnik developer that added
>> the shapely wkb reading support, which I think is meant to be temporary but
>> works nicely from my limited tests.
>> 
>> Dane
>> 
>>> 
>>> Any info or thoughts are appreciated.
>>> 
>>> Thanks,
>>> 
>>> ~Angus
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Mapnik-users mailing list
>>> [email protected]
>>> https://lists.berlios.de/mailman/listinfo/mapnik-users
>> 
>> _______________________________________________
>> Mapnik-users mailing list
>> [email protected]
>> https://lists.berlios.de/mailman/listinfo/mapnik-users
>> 

_______________________________________________
Mapnik-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/mapnik-users

Reply via email to