On 02/03/2010 09:01 AM, Peter Körner wrote:
Great, good to
see things moving along again :-)
Hey ho, let's go! :D
If this sounds acceptable to everyone, I will
drop the current
outdated osm database on ptolemy, and create a new, empty database and
the MMT. People who want access to the MMT should let me know (by
replying to this mail with your TS username). Those people can then
start on the process of importing the database and setting up
I'm "mazder" and I'd like to import the dump and
replication. It would be cool, it so. with more experience with the
render-tools would setup the render chain. Maybe Kai?
I can at least try and answer questions arising from the render-tools
and help set them up. But as it needs root for setting up mod_tile, I
suspect River will want to do that?
River Tarnell wrote:
> Secondly: renderd/mod_tile. I'm open to suggestions here. Currently, I
> plan to run renderd and mod_tile on ptolemy, which means only I will have
We'll need a workflow on how toolserver user can test their
(I'd suggest doing this on the login servers. We'd need mapnik on these
servers - i can supply you with a very easy interface to the rendering
stack ) and how they can be distributed to the toolserver (maybe via
> However, there are quite a few portability
issues with the OSM
> software which I've had to fix. I would appreciate it if someone with
> commit access to OSM's SVN repository would be able to work with me to
> integrate these patches, to make things easier in future.
Kai Krueger schrieb:
I can try and see if I can help here. I have OSM
svn commit access and I
have done some patches to mod_tile and renderd in the past. It however
also wouldn't be hard to get OSM commit access your self if you want, as
as far as I know, Tom Hughes (the osm admin) hands out an account to
anyone who asks. I don't have any experience with anything other than
Linux though, so I don't know how much help I can be with portability
Would you also like to do the setup of renderd/mod_tile? Do you have
experience with tile expiration?
Tile expiration is where it gets a bit murky. There are several
different ways currently to do the tile expiration, all of which seem to
have different merits and issues. So it might be necessary to play
around a bit to see what works best for this setup.
This was a big problem with this on cassini, because we got over 200
styles, so the expiration runs 200 times as long as on the osm live
server -- which is longer than the time until next diff import (1 minute).
The 200 styles might be a problem at the moment, as I don't think any of
the current scripts were designed for that many styles. This would need
to stat/touch a lot of files which might take a while. On the other
hand, I suspect that most of the 200 styles won't have that many tiles
in them, so there might be a bunch of optimizations that can be done
using the meta-tile filepath hierarchy.