For those interested, I've commited code based on Ari's patch to support tables with multiple geometry columns. See ticket 1476 and/or updated PG driver documentation for the details
Le Wednesday 12 November 2008 10:38:28 Ari Jolma, vous avez écrit : > Open ticket 1476 seems to be discussing this issue. > http://trac.osgeo.org/gdal/ticket/1476 > > Ari > > Ari Jolma wrote: > > The Pg driver consults geometry_columns for the list of layers in the > > database and for the geometry type of a layer. But it does not consult > > it for the geometry column itself. For example: > > > > I have a table "points", which is created with shp2psql and it is fine > > with OGR. Then I decide to add another geometry column, which will > > contain the points transformed somehow. I can now either add this as a > > new entry in the geometry_columns table or edit the existing entry to > > have the new column name. In either scenario OGR is by default a bit > > lost. I need to use SQL to get an OGR layer of the points with the > > new, alternative coordinates. > > > > Should this disregard of column names in geometry_columns be > > considered a bug or feature? > > > > Best regards, > > > > Ari > > > > _______________________________________________ > > gdal-dev mailing list > > gdal-dev@lists.osgeo.org > > http://lists.osgeo.org/mailman/listinfo/gdal-dev > > _______________________________________________ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/gdal-dev _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
