<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial, helvetica, sans-serif;font-size:10pt"><div style="font-family: arial,helvetica,sans-serif; font-size: 10pt;">I ran across this issue with my data set and my solution was converting all the coordinates into one shared srid like WGS84 (EPSG:4326) from the various input coordinates.<br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: Vincent J. Troisi <Vincent.Troisi@Colorado.EDU><br>To: PostGIS Users Discussion <postgis-users@postgis.refractions.net>; Vincent J. Troisi <vincent.troisi@Colorado.EDU><br>Sent: Monday, December 18, 2006 9:13:33 AM<br>Subject: [postgis-users] Issue with the geometry field in postgresql tables<br><br><div>We want to conduct searches on a table containing a variety of<br>geometry types. The search returns records that satisfy the<br>tests for
intersection, containment, and overlap. Our DBA<br>has discovered an issue with using the geometry field; the<br>field can contain only one geometry definition.<br><br>Does anyone have an approach that we can use to query a<br>spatial field (e.g., geometry) in a table using the standard<br>functions available in postgis? See below...<br><br><br>><br>> Here is the write up for the issue I found out with postGIS <br>> yesterday. The way postgresql handles the geometry column is that you <br>> have specify a spatial reference system ID everytime a geometry column <br>> is created. It then uses the spatial reference ID to enforce the rule <br>> that every geometry entered into that column matches the spatial <br>> reference ID or it will give you an error. It also allows postGIS to <br>> perform convertion on the projections. This causes the problem <br>> because we need to be able to assign different
spatial reference ID to <br>> different datasets. With a fixed spatial reference ID assigned to the <br>> column, it prevents us from using that the column for datasets that <br>> have different spatial reference IDs. <br><br>_______________________________________________<br>postgis-users mailing list<br>postgis-users@postgis.refractions.net<br><a target="_blank" href="http://postgis.refractions.net/mailman/listinfo/postgis-users">http://postgis.refractions.net/mailman/listinfo/postgis-users</a><br></div></div><br></div></div></body></html>