H Steve, I have had recommendations that this is not good practice, but I have done this often myself for various reasons, with good success.
As far as I'm concerned, a very useful ability of a spatially enabled RDBMS is to realise that a geometry is only an attribute of an entity, like a date, time, numeric or string type. Real world entities can be represented by multiple geometries, and have multiple dates, etc, associated with them, so this is a perfectly good model, and offers substantial benefits over the (dated) GIS model where the geometry is somehow more special than other attributes of a feature/entity. Cheers, Brent Wood --- On Wed, 9/2/09, [email protected] <[email protected]> wrote: > From: [email protected] <[email protected]> > Subject: [postgis-users] several SRID on one table > To: "PostGIS Users Discussion" <[email protected]> > Date: Wednesday, September 2, 2009, 2:46 AM > > > Hello, > > We need to use a table for > several purposes > with different SRID. > > Is it a good practice to > have several > geometry columns on one table or should we create one table > per SRID? > > What are the pros and cons > of using > several geometry columns on one table? > > > > thanks > > Steve > > > > Steve Toutant, M. > Sc. > > Analyste en géomatique > > Secteur environnement > > Direction des risques biologiques, environnementaux et > occupationnels > > Institut national de santé publique du Québec > > 945, avenue Wolfe > > Québec, Qc G1V 5B3 > Tél.: (418) 650-5115 #5281 > > Fax.: (418) 654-3144 > > [email protected] > > http://www.inspq.qc.ca > > > -----Inline Attachment Follows----- > > _______________________________________________ > postgis-users mailing list > [email protected] > http://postgis.refractions.net/mailman/listinfo/postgis-users > _______________________________________________ postgis-users mailing list [email protected] http://postgis.refractions.net/mailman/listinfo/postgis-users
