[Tilesathome] close-areas producing very long ways -> inkscape crashing

[Damian Sulewski]

Opening the data_PID_close-areas.osm in JOSM and simplifying the large
way to about 3000 nodes helped. Inkscape can render the tile.

Damian

Am Freitag, den 19.10.2007, 17:39 +0200 schrieb Damian Sulewski:
> Hi,
> 
> here is what i found out trying to render tile 142 88 z8:
> 
> First off all: the t at h client crashes when inkscape tries to render this
> tile.
> 
> 1. I tried to load the data-PID.osm into JOSM this did not work, looked
> into it and found several nodes without lat lon values. Just a line like
>  
> <node id='7234234' />  
> 
> this looked strange and i deleted them, josm could load the file but
> inkscape still crashed. 
> -- where did the nodes came from? (they were used in ways!)
> 
> 2. IMPORTANT:
> Transfered data-PID.osm to svg using xmlstarlet and tried to render it
> with inkscape, THIS WORKS (but oceans are not shown)
> Transfered data-PID-close-areas.osm to svg and tried to render it:
> inkscape crash.
> 
> vim showed me that the first way created by close-areas has exactly 5988
> nodes, so i splited this into 6 ways with about 1000 nodes and gues
> what: inkscape was able to render it, but without oceans (because of my
> splitting i think)
> 
> Question, could close-areas.pl check the length of a way and cut it in
> pieces so inkscape can render it? 
> 
> Greetings,
> 
> Damian
> 
> 
> 
> 
> 
> _______________________________________________
> Tilesathome mailing list
> Tilesathome at openstreetmap.org
> http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/tilesathome