Hi Graham, The lazy approach is to keep your osm.xml exactly as it is and the just run the well maintained 'upgrade_map_xml.py' over it before deploying. But of course if you want to start leveraging mapnik2 features actively then the lazy approach is not too viable. I would say the next step is to tackle, as a group, creating an osm.xml (plus entities of course) version tailored to Mapnik2 that could be maintained alongside the current osm.xml. I've been waiting for the right time to pitch in to do this. Is now the time?
Dane --- \o/ --- Sent from my phone On Apr 28, 2011, at 1:51 PM, Graham Jones <[email protected]> wrote: > Hi Folks, > I am being lazy.... > I am trying to convert a 'standard' OpenStreetMap mapnik stylesheet (osm.xml > and includes) to mapnik2, but the upgrade_map_xml_keep_ent.py script in trunk > does not seem to work (lots of errors about needing fontset-name rather than > fontset_name etc.). > Does anyone have a version of the script that does work with the current > trunk version of mapnik that I can 'borrow' please? I think it will take me > a while to figure out the difference between the two conversion scripts, so > if someone else has already done it, you could save me a job. > > Thanks > > > Graham. > > -- > Graham Jones > Hartlepool, UK. > > _______________________________________________ > 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
