[Tilesathome] Zappy weirdness?

[spaetz]

On Thu, Aug 16, 2007 at 12:06:51PM +0100, 80n wrote:
> This is because the planet contains numbers like this:
> 5.1588915616303e-06for nodes that are very close to the meridian.
> 
> The main API used to do this but got fixed some time ago.  It seems
> planet.osm wasn't fixed at the same time.
> 
> I can do something at the Zappy end to convert these to proper numbers.

Wouldn't it be more efficient to fix up the planet generator? I'm not going to touch ruby code, but that's how steve's export looks like:

  $mysql.query "select id, latitude, longitude, timestamp, tags from current_nodes where visible = 1 order by id #{pageSQL(page)}" do |rows|
    rows.each do |row|
      yield row[0].to_i, row[1].to_f, row[2].to_f, read_timestamp(row[3]), read_tags(row[4])

So it seems, it simply takes whatever the database hands us. should we use something for mysql like the format function "http://dev.mysql.com/doc/refman/5.0/en/string-functions.html" to pass us proper numbers? Or is there some ruby magic to output numbers in the right format?

spaetz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 186 bytes
Desc: not available
URL: <http://lists.openstreetmap.org/pipermail/tilesathome/attachments/20070816/fb0e52dd/attachment.pgp>