[Tilesathome] Strange rendering issue

[Ed Loach]

Gregory wrote:

> It's also happening on some London tiles immediately to the
> west of the
> Greenwich Meridian.
> 
> I've had one further idea on this. Given the small values for
> longitude
> at this point I wonder whether they're getting represented
> using
> scientific notation at some point in the process, which may be
> confusing
> some point further down the line that's trying to parse those
> strings
> back as numbers?
> 
> Unfortunately I'm not really familiar enough with the t at h code
> to find
> the error itself at the moment.

If it helps, checking for 2047,1347...

* The SVG is also wrong.
* Checking the .osm files I find data.osm, dataclose-areas.osm and
dataclose-areas-area.center.osm.
* The first two of those only seem to differ in their end of line
character
* The last of those seems quite different. Generator has been
updated to "Osmosis 0.29", the <bounds> line seems to have been
removed, ways have been sorted into date/time order, and areas have
extra properties such as:
    <tag k="osmarender:areaCenterLat" v="52.302471360323906"/>
    <tag k="osmarender:areaCenterLon" v="-0.027389477811061762"/>
    <tag k="osmarender:areaSize" v="2.822190547924208E-7"/>
* If all the above looks correct, then I'm using or/p to transform
the .osm file to .svg (I tried switching to Osmarender=XSLT but only
got a blank z12 tile).

Thanks

Ed