[gdal-dev] The use of geometry_columns of the Pg driver

[Ari Jolma]

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 at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/gdal-dev