[OSM-talk] simplifying mapnik layout definition

Robert (Jamie) Munro rjmunro at arjam.net
Wed May 28 00:46:00 BST 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Andreas Barth wrote:
| * Dave Stubbs (osm.list at randomjunk.co.uk) [080527 18:01]:
|> I don't think inferring the LineSymbolizer is a good idea. But if you
|> want to write a preprocessor to do the scale extraction I think that
|> might help a lot.
|
| ok - though it might happen I'll fiddle with it anyways for start. Let's
| see ...
|
|
|> Personally I'd like to see an end to the XML syntax as it's hard to
|> read, but that's more work than it's worth right now (to me at least).
|
| Any better idea than xml in your mind? Going away from XML might be an
| option, but none I'll probably start with (simply for the ease of
| getting started).

How about YAML? You could either write a script to convert YAML to XML,
and use the XML as normal, or possibly you could write a python script
that read the YAML and built the styles in mapnik directly as in:
http://trac.mapnik.org/wiki/GettingStarted

PyYAML (http://pyyaml.org/wiki/PyYAML) is really simple to use. You feed
it python lists and dictionaries containing each other, and it outputs
YAML code, which is easy to read and easy to edit as long as you are
careful with the whitespace (like python). Feed it YAML code and it
returns lists and dictionaries.

Robert (Jamie) Munro
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkg8nTUACgkQz+aYVHdncI29mgCgrD/zYFV0lX3PYTIDgNYXP01P
AqsAn2NoU5OqWFbwpuQ7tG4rkzdFJhrw
=FDPf
-----END PGP SIGNATURE-----




More information about the talk mailing list