[OSM-dev] [PATCH] osm2pgsql tile expiry

[Steve Hill]

On Sun, 8 Feb 2009, Martijn van Oosterhout wrote:

> I just realised. You have also created a parse_wkt, which opens up the
> path to limited relation processing even in non-slim mode. (It doesn't
> solve the problem completely, since the whole problem is that non-slim
> doesn't store most of the info required, but for certain types of
> relations it might be sufficient.)

Yes, in order to mark tiles as dirty for deleted objects, I select the 
object from the database prior to deletion and parse it into a list of 
nodes.

I have also cheated to some extent with relations - so that I don't need 
to care how osm2pgsql creates PostGIS objects for relations, I just parse 
the WKT which is being added to the database.  This has the advantage that 
the object generation code can be changed without affecting the tile 
expiry code, although there will be a minor overhead introduced by parsing 
the WKT instead of integrating more directly in the relation processing 
code.

  - Steve
    xmpp:steve at nexusuk.org   sip:steve at nexusuk.org   http://www.nexusuk.org/

      Servatis a periculum, servatis a maleficum - Whisper, Evanescence