On Jan 1, 2011, at 5:09 PM, Jan-willem De Bleser wrote: > Hi, > > When mapping osm data with Mapnik 0.7.1, I've run into a few roads > that will not be displayed if any of the (unrelated) nodes in the osm > file have tags. Attached is a very basic python rendering script that > renders everything as a black line, the osm file with a diff that adds > a tag to a node not part of the road, and the resulting png files. The > osm is a download (via JOSM) of an area near Santa Fe, NM, where I'm > mapping a few ski slopes. > > I've fiddled around with the road and with the tagged node to no > avail. Enabling debugging didn't give me any information about which > roads were and were not rendered by which layers. > > Any suggestions as to what the cause might be?
Yes, it appears to be a bug in the osm plugin. The XML parsing in the plugin find nodes like <node ../> and pushes them into its "way" type container, while it finds nodes like <node ...>...</node> and pushes them into a "node" container that looks to not get properly rendered. But, honestly since I did not write the plugin it is hard to see exactly what is happening. > Have I neglected > something important? I'm pretty sure this is simply a bug in the driver and I have cc'ed Nick W (the author) hoping he can take a look. If he cannot, then we'll need a ticket so this issue does not get lost. My only solution for you at this point would be to switch to using osm2pgsql + postgis plugin which breaks nodes/ways out into separate tables and makes it easier to construct layers/styles to display one or both. > > Cheers, > Jw > <test.py><ski.osm><ski.diff><map1.png><map2.png>_______________________________________________ > 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
