[postgis-devel] geography_columns + geometry_columns

[Paragon Corporation]

Hmm on closer inspection DB2 has both a geometry_columns and a
st_geometry_columns

Geometry_columns:
http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp?topic=/com.
ibm.db29.doc.spatial/db2z_rsbp4017.htm

ST_Geometry_Columns:
http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp?topic=/com.
ibm.db29.doc.spatial/db2z_rsbp4017.htm

And the structures are different.  I assume this is mandated by the MM spec?

(though our geometry_columns looks more like their st_geometry_columns)

-----Original Message-----
From: postgis-devel-bounces at postgis.refractions.net
[mailto:postgis-devel-bounces at postgis.refractions.net] On Behalf Of Paul
Ramsey
Sent: Wednesday, November 18, 2009 10:09 PM
To: postgis-devel at postgis.refractions.net
Subject: [postgis-devel] geography_columns + geometry_columns

This is more of a 2.0 idea, since ideally it depends on having typmod
support everywhere, but I am trying to think if there's any reason not to
unify geometry_columns and geography_columns into a single view (probably
called geometry_columns, but with an extra column to flag type differences
for apps that care). 

In general naive applications that don't understand geography can still
treat is at geometry-with-epsg-4326 and get perfectly respectable results,
and that's all the metadata table is used for, so... any reason not to add
this as a 2.0 task?

P

--
Paul Ramsey
OpenGeo - http://opengeo.org
PostGIS is Love.

_______________________________________________
postgis-devel mailing list
postgis-devel at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-devel