[OSM-dev] Slippy Map Layer with Maplint output

[Robert (Jamie) Munro]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Frederik Ramm wrote:
> Hi,
> 
>> It would be great if Tiles at Home could render maplint style tiles, and if
>> that were combined with a special request that works like this one:
>> http://www.informationfreeway.org/?lat=7347739.31466&lon=-155530.2096&zoom=15&layers=B00

> Agreed. I have seen that OJW has already designed the tile metadata
> structure with the possibility of multiple layers in mind; a few changes
> to the upload scripts, and it would be possible to upload "normal" as
> well as maplint layers.

> Of course one could also have maplint on a completely different system
> but it would be more efficient to calculate tiles for all layers from
> one set of data that you downloaded.

> However the whole client-server interaction would grow more complex. If
> we required each renderer to have maplint installed and do maplint tiles
> at the same time it does osmarender, then it would be ok, but if we have
> to start negotiations between server and client about which layers to
> render and whether the client is equipped, that would be a nightmare.

I was thinking along the lines of adding another parameter along with
the X&Y of the area to be rendered for rendering style. The tiles at home
client uses this parameter to select the right style file (or file set
when working at multiple zooms) to use. We could later extend this for
other kinds of multiple render - perhaps using different colour schemes
to match what people in different countries are used to, different
languages where name tags of multiple languages are available, or
different sets of features for different audiences.

>> http://dev.openstreetmap.org/~ojw/Log/Requests/ seems to be empty most
>> of the time, I think tile at home has a plenty of spare capacity to do this
>> at the moment.
> 
> Don't overestimate it - as soon as metadata is avaialable again, I will
> continue running my weekly "find all tiles that need updating according
> to lates planet.osm" job, and this usually fills up the queue for 24 hours.

But that's 24 hours out of the 168 hours between planet file releases.
That still leaves 144 hours for Maplint :-). We could have a system that
always puts Maplint requests at the back of the queue if necessary. This
way, it would never interfere with normal rendering. I'm sure we can get
more Tiles at home capacity (I don't run it yet, and I could probably run
it on several machines), but if the current capacity is only full for 24
hours / week, we have lots to spare.

Robert (Jamie) Munro
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF5hWZz+aYVHdncI0RAkZhAKCm9oBkXKZquxfBgiWF6i7DKZ4BXQCfSGDB
YW8OOci2jBC/nBhgauYkY4g=
=sAyc
-----END PGP SIGNATURE-----