<DIV>
<DIV>All,</DIV>
<DIV> </DIV>
<DIV>
<DIV>I used ogr2ogr to export a point layer from postgres/postgis into a shapefile ... everything worked fine (I can open it and load/view locations). Then I used a basic SQL statement (-sql "SELECT * FROM ksamples WHERE chloroph=108") and all geometry was lost (cannot load locations), yet ksamples.dbf table is returned ok (only the records having chloroph=108 are in the dbf table).</DIV></DIV>
<DIV> </DIV>
<DIV>Originally I tried to use gdal (ogr), specifically poDS->ExecuteSQL(...) to retrieve spatial locations based on a joined non-spatial table's attribute information.</DIV>
<DIV> </DIV>
<DIV><FONT size=2>pszSQLStatement = "SELECT * FROM test INNER JOIN ksample ON test.c_id = ksample.chloroph WHERE something = 467";</FONT></DIV>
<DIV><FONT size=2>poResultSet = poDS->ExecuteSQL( pszSQLStatement, NULL, NULL );</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>The poResultSet had not spatial attributes, but all the non-spatial values were ok. First, since I am new to gdal and postgis (I am -was- from the ESRI world) I thought it was just my portion of the code ... but as mentioned above ogr2ogr does the same?</FONT></DIV>
<DIV> </DIV>
<DIV>I noticed in the archives of April 05 someone posting a similar issue ... but no solutions that I could find.</DIV>
<DIV> </DIV>
<DIV>Using: FWTools0.9.8, PostgreSQL 1.2.1, PostGIS 1.0.2</DIV>
<DIV> </DIV>
<DIV>Any help/hints are appreciated.</DIV>
<DIV> </DIV>
<DIV>Thanks,</DIV>
<DIV>Thomas</DIV>
<DIV><FONT size=2> </DIV></FONT></DIV><p>
<hr size=1>Yahoo! for Good<br>
<a href="http://store.yahoo.com/redcross-donate3/">Click here to donate</a> to the Hurricane Katrina relief effort.