No objection here.
On Fri, Sep 7, 2012 at 12:56 PM, Andrea Aime
<[email protected]>wrote:
> Hi,
> remember when we talked about the geometry metadata table for Oracle?
>
> Well, I'm now back with the same issue for SQL Server, which is aggravated
> by the
> fact that SQL Server seems not to have any native way to describe the
> srid and geometry type of a table.
>
> Any objection about adding the same extra parameter we added to the Oracle
> to
> the SQL Server one?
>
> Btw, some days ago I was looking at the simple feature specification for
> SQL
> and the geometry_columns table structure is defined there, it was not a
> PostGIS
> invention.
> From the spec page 2-21:
>
> -----------------------
>
> The GEOMETRY_COLUMNS table or view consists of a row for each geometry
> column in the database.
> The data stored for each geometry column includes:
> • the identity of the feature table of which it is a member,
> • the spatial reference system ID,
> • the type of geometry for the column,
> • the coordinate dimension for the column,
> • the identity of the geometry table that stores its instances, and
> • the information necessary to navigate the geometry tables in the case of
> normalized geometry storage.
>
> -----------------------
>
> There is also a diagram showing the column names, it's not 100% equal to
> the PostGIS one, but
> very close, in particular from page 3-2
>
> CREATE TABLE GEOMETRY_COLUMNS (
> F_TABLE_CATALOG NOT NULL,
> F_TABLE_SCHEMA VARCHAR(256) NOT NULL,
> F_TABLE_NAME VARCHAR(256) NOT NULL,
> F_GEOMETRY_COLUMN VARCHAR(256) NOT NULL,
> G_TABLE_CATALOG VARCHAR(256) NOT NULL,
> G_TABLE_SCHEMA VARCHAR(256) NOT NULL,
> G_TABLE_NAME VARCHAR(256) NOT NULL,
> STORAGE_TYPE
> VARCHAR(256) INTEGER,
> GEOMETRY_TYPE INTEGER,
> COORD_DIMENSION INTEGER,
> MAX_PPR INTEGER,
> SRID INTEGER REFERENCES SPATIAL_REF_SYS,
> CONSTRAINT GC_PK PRIMARY KEY
> (F_TABLE_CATALOG, F_TABLE_SCHEMA, F_TABLE_NAME, F_GEOMETRY_COLUMN)
> )
>
> Given that we are using the PostGIS structure already for Oracle and I
> believe H2 as well,
> I would keep on using it for SQL Server as well.
>
> Cheers
> Andrea
>
>
> --
> ==
> Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
> information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 962313
> mob: +39 339 8844549
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> GeoTools-Devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
