I have a postgis dataset that is a series of fish collection trawls with the geometry fields for the endpoints and for the line between the endpoints. It seemed like the easiest way to do analysis on the endpoints separately of the line the endpoints create at the time. Two geometry colums with differnt names and different indexes. I'd do it differently now, but it seemed to work well then.
Doug Doug Newcomb USFWS Raleigh, NC 919-856-4520 ext. 14 [email protected] --------------------------------------------------------------------------------------------------------- The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of Interior. Life is too short for undocumented, proprietary data formats. "Peter N. Schweitzer" <pschweit...@usgs To .gov> [email protected], Sent by: PostGIS Users Discussion postgis-users-bou <[email protected]. [email protected] net> actions.net cc Subject 07/13/2009 11:17 Re: [postgis-users] AM PostGIS-PostgreSQL Please respond to PostGIS Users Discussion <postgis-us...@po stgis.refractions .net> Chris Hermansen wrote: > I should have mentioned that it's not considered good practice to > have more than one geometry column per table, and hence more than > one geometry object per row. This makes sense if you think of rows > as representational instances of real world objects. Hmmm. I'm storing two geometry columns, because in one I have the geographic (unprojected) coordinates, and in the other the coordinates in some projection. This is to support several different map interfaces some of which are projected, others not. Since the points don't change frequently, I can generate the projected coords once and then simply use them rather than recalculate them on every web hit. It's denormalized, but seems sensible to me. Would you disagree with this method? Peter -- Peter N. Schweitzer (MS 954, U.S. Geological Survey, Reston, VA 20192) (703) 648-6533 FAX: (703) 648-6252 email: [email protected] <http://geology.usgs.gov/peter/> _______________________________________________ postgis-users mailing list [email protected] http://postgis.refractions.net/mailman/listinfo/postgis-users
<<inline: graycol.gif>>
<<inline: pic06900.gif>>
<<inline: ecblank.gif>>
_______________________________________________ postgis-users mailing list [email protected] http://postgis.refractions.net/mailman/listinfo/postgis-users
