[postgis-users] Best approach to store multi-object geometrical composition
sky.l1ne at msn.com
Mon Nov 15 02:37:57 PST 2010
There is a need to store an entity that consists of few different objects - i.e. point, polygon, etc. so one row of database has one object that consists of them. The first approach is kinda obvious - form geometry collections and save them as one binary object, but then there are problems with output (of course i can make multipoint from points and multiline from lines, but in few cases there is no proper aggregate type for my composition). So i'm looking forward to saving each kind of child object in related tables so during processing we could get them and display as respecive type (say in Geoserver via OpenLayers). But what if i have a lot of such objects? Such approach may cause serious performance issues, and in specific case where PostGIS application itself was intended to boost performance, it's unacceptable. Maybe there are some other best practices to deal with above described problem? Thanks in advance for your help.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the postgis-users