[Tilesathome] New Osmarender/Batik Issue

[Dodi]

Hi Brent,
this behaviour is same from osmarender4 ...

I spotted this earlier ... but could not decide if it is bug or required 
behaviour designed by 80n. Maybe we should ask him :)

easiest way to stop generating <use xlink:href...> is to comment-out/remove

    <xsl:call-template name="renderArea">
      <xsl:with-param name="instruction" select="$instruction"/>
      <xsl:with-param name="pathId" select="concat('area_', at id)"/>
    </xsl:call-template>

at lines 867-870 in osmarender.xsl

another way is to make area path generation same as way generation (this was 
present in osmarender6 alpha 4) but it breaks "beziercurvehinting" without 
svg file preprocessing

..waycleanup.pl  should be used before beziercurve hinting (I mention it 
several time before [ 
http://svn.moonbase.sk/FreemapSlovakiaDiSK/waycleanup.pl ]  which produce 
smaller svg by removing unreferenced svg path definition).

Dodi


----- Original Message ----- 
From: "Brent Easton" <b.easton at exemail.com.au>
To: "Dodi" <dodi at moonbase.sk>
Cc: <tilesathome at openstreetmap.org>
Sent: Friday, November 23, 2007 10:52 PM
Subject: New Osmarender/Batik Issue


Hi Dodi,

Sorry to bother you again, but looks like another Osmarender issue:

Tile: 2052 1361
Way: 8131246 (Thames River, waterway=riverbank)

The data in the .osm file looks fine, but Osmarender is emitting the 
following:

      <g class="waterway-riverbank">
<path id="area_8131246" d="M   C 0,0 529.253504988145,1512.37605217907 
608.078 1725.40444523807
    <... bunch of nodes removed ...>
  C 1491.01943144629,901.300748887736 1500.318,915.999972194995 1500.318 
915.999972194995 Z"/>
        <use xlink:href="#area_8131246" class="waterway-riverbank"/>
      </g>

Regards,
Brent.
____________________________________________________________
Brent Easton
Analyst/Programmer
University of Western Sydney
Email: b.easton at uws.edu.au