[OSM-talk] Osmarender 3.0

[Jens.Kammann at dlr.de]

Hi Etienne,
 
Thanks - now I know where to look in case of unknown elements...

However, now I am facing scaling issues with the resulting SVG file:
If I download the London-Aerea within JOSM, I get a pretty dense map
consisting of many ways:
http://osm.kn.op.dlr.de/debug/london_JOSM.png

Applying osmrenderer on this dataset:
http://osm.kn.op.dlr.de/debug/data.osm results in 
http://osm.kn.op.dlr.de/debug/data.svg

I get different output areas (bounding boxes) depending on the viewer:
The adobe-Plugin seems to show the largest extract of the map:
http://osm.kn.op.dlr.de/debug/london_Adobe.png

Batik-Squiggle shows a much smaller extract:
http://osm.kn.op.dlr.de/debug/london_squiggle.png

And finally batik-rasterizer displays the smallest area:
http://osm.kn.op.dlr.de/debug/london_rasterizer.png

I played around with the "width" and "area" paramter of
batik-rasterizer, but I am not able to extend the area even close to the
output of the adobe-plugin (which sure enough only show a subset of the
area stored in the data.osm file)

Do you have any ideas what could have gone wrong?

Regards,
    Jens
 
_