I've just put Osmarender 2.0 up on the wiki at <a href="http://wiki.openstreetmap.org/index.php/Osmarender2.xsl">http://wiki.openstreetmap.org/index.php/Osmarender2.xsl</a> and a new rules file at <a href="http://wiki.openstreetmap.org/index.php/Osm-map-features2.xml">
http://wiki.openstreetmap.org/index.php/Osm-map-features2.xml</a>.<br><br>There is a whole lot of new stuff in it and some things might not work right yet:<br><br>* Support for Areas. Since areas are only supported by one client at the moment, you can also fake an area by creating a way and tagging it as if it were an area (eg amenity=parking). If you do this you'll need to change them from ways the areas once full area support is available.
<br><br>* Streets now end with a butt linecap rather than a rounded linecap. If you prefer a rounded linecap you can just change the relevant style attributes in the rules file.<br><br>* A new attribute on the rule element enables the elements to which the rule applies to be specificed (e="node|segment|way|area"). This improves performance and provides greater control.
<br><br>* <rule k="foo" v="*"> allows a rule to be applied to all elements that have a key of foo with any value<br><br>* <rule k="*" v="foo" > allows a rule to be applied to all elements that have any key with a value of foo
<br><br>* The e, k and v attributes can now take a list of possible values (eg k="highway|class" v="primary|major")<br><br>* Nodes, segments and ways that have a tag with a key that starts with svg: will have that tag value applied to the corresponding rendered element. So for example, a way with a tag like svg:font-style=italic would result in the text on that way being rendered in italic. This is not an ideal solution as its not a good idea to put rendering information in the database, but it does provide a way to have fine control over the appearance of the output without too much messing around.
<br><br>* Street names are now centered half-way along the way to which they belong.<br><br>* Street names can now be drawn in the opposite direction along a way by specifying the tag name_direction=-1 on a segment or way.
<br> <br>* Ways are now rendered using paths rather than as a series of segments. This should improve performance and reduce the size of the .svg file<br><br>* Various bug fixes to enable the generated svg to be viewed in tools like Inkscape, etc.
<br><br><br>The rules file has been updated to take advantage of the above changes. Other notable changes include:<br>* Symbols for petrol station, golf course and gate<br>* Better looking one-way markers<br>* Some styles for areas (park, parking, water, land)
<br>* A set of rules that overlay JOSM style nodes, segments and ways over the top of the rendered ways (for debugging and identifying segments that go in the wrong direction)<br>* A rule for highway=steps<br><br>Enjoy<br>
Etienne<br><br><br>