[Tile-serving] [osm2pgsql] Geometric column for relations (#116)

[Paul Norman]

> In my application I have to decide where I have the perfomance hit: during query / rendering or during update.

A nasty relation can take **hours** to build a geometry for.

Also keep in mind that geometry for relations is ill-defined. Consider all the logic that goes into multipolygons. As a simple example, take a relation with a closed way, an open way, a node, and a relation as members. How do you form a geometry from that?

It really sounds like you want a non-rendering database (e.g. pgsnapshot, pgsimple), perhaps as a different  postgresql schema within the same postgresql database.

---
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/osm2pgsql/issues/116#issuecomment-32211614
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20140113/c33b14ad/attachment.html>