[OSM-dev] Defining aread for re-rendering; Was: JOSM patch to request T at H renders

Robert Hart Robert.Hart at BuroHappold.com
Fri Mar 23 15:44:50 GMT 2007

> -----Original Message-----
> From: dev-bounces at openstreetmap.org
[mailto:dev-bounces at openstreetmap.org]
> On Behalf Of Martin Spott
> Sent: 23 March 2007 15:18
> To: dev at openstreetmap.org
> Subject: [OSM-dev] Defining aread for re-rendering;Was: JOSM patch to
> request T at H renders
> Hi Frederic,
> Frederik Ramm wrote:
> > [...] The ideas have already been laid out
> > - the API must, on upload, compute the tile number affected by the
> > upload and either increase a "version counter" or set a "dirty flag"
> > for this tile [...]
> Just a side note:
> I'm preparing for doing something pretty similar with my Landcover DB
> and FlightGear Scenery. Here I'm defining the area for re-processing
> the Scenery by calculating a bounding box around a change set and
> storing this in a separate table - which makes the whole thing
> work independently from the chosen tile-size.

In OSM uploads occur for individual objects, i.e. one upload per node,
segment or way. It would therefore be necessary to merge nearby
bounding-boxes, otherwise you will end up with a large number of very
small boxes.


This message has been scanned for viruses by MailControl - www.mailcontrol.com

More information about the dev mailing list