Hi Dane, I am keen to have something that is easy to maintain, so wanted to preserve the file structure of the original, and I want to use the mapnik2 scale factor work that Carlos did for last year's GSoC, so I am looking for a true mapnik2 style file. I was starting to think about building a style myself from the bottom up....
Therefore, I think that producing a mapnik2 OSM style would be really good, but I wonder if just writing it in XML is the best way? I would like to have a style file (or rather files) that is easy to maintain to encourage people to customise it. Even the 'new' OSM style using entities is quite a daunting thing to modify - adding or deleting a feature is quite hard to fathom. I was playing with the carto 'CSS' stylesheet generator last night and was very impressed with it (especially when coupled with the tilemill front-end to visualise your changes in real time, so I wonder if this might be a better way to go (I am not sure what the real difference is between carto and cascadenik from a users point of view - I had a go at carto first because it seems to be being more actively developed, but I would go with either). Tilemill would be a big selling point for carto though, especially when support for postgresql databases is added. I think it would be worth putting some up-front effort into agreeing the design of the file structure (and documenting it!), to help with usability - I would like to make sure we separate the SQL bits from the style bits, both from a security and an ease of understanding perspective. I would be interested in people's thoughts about pure XML or a CSS version. I am not sure who maintains the current OSM style? They are bound to have ideas about this too. Regards Graham. On 30 April 2011 07:02, Dane Springmeyer <[email protected]> wrote: > 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 > -- Graham Jones Hartlepool, UK.
_______________________________________________ Mapnik-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/mapnik-users
