[OSM-talk] Fw: calling all python coders for slippy map help
Raphaël Jacquot
sxpert at sxpert.org
Sun Nov 19 23:12:24 GMT 2006
Robert (Jamie) Munro wrote:
> It's queue should be ordered by a function of age of edits outstanding,
> amount of edits outstanding and higher resolutions first (because higher
> resolutions are faster to generate and small changes are more likely to
> be visible only in higher resolutions). Alternatively, it could just
> render all tiles in a fixed order, skipping those that haven't changed
> since last time.
>
> If it were an hourly batch job, what happens if it doesn't finish within
> the hour?
>
> Robert (Jamie) Munro
how about having the process check a process queue every minute when it
has nothing to do, or after processing a tile from the db server ?
have a table like
job number | zoom level | tile x | tile y
that's filled by the API whenever stuff needs updated.
if multiple edits happen in the same tile, the job will remain there as
long as it's not processed
if you can't find a job for a particular tile, create a new job...
of course job number needs be a monotonously growing value
More information about the talk
mailing list