There are two tables that are defined by the OGC standard for use with spatial column databases.<\/p>\n
These tables (with a potential for a variation on name) are used in all spatial database systems that support the OGC. Even ESRI uses this method with their SDE data model.<\/p>\n
One can choose to use these tables or create them as views to support other views. For example I may have a table of features, and a table for locations. In my database I dont care if a feature has mixed geometries (points lines or polygons) because that is just an attribute of the thing I am interested in.\u00a0 (<\/strong>ESRI tries to make you tie everything to a point, line or polygon, and then attributes. This is backwards, and wrong).<\/p>\n In any case, in my database, I can create views that organize my data into a flat file type dataset, with only one type of geometry per view. I would then want to use a view to make my spatial_reference sys tables, to catalog the views.<\/p>\n I have found that spatialreference.org<\/a> is really useful for working with the projects and creating these tables. There is even a link to get the SQL insert statement for the spatial reference that you are interested in.<\/p>\n <\/p>\n Here is the create code for each of the tables if this helps.<\/p>\n <\/p>\n AND<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" Spatial Reference Tables are the metadata of your spatial database: There are two tables that are defined by the OGC standard for use with spatial column databases. geometry_columns – this table stores your catalog of data, where to find the geometry column, the dimensions of the coordinate system, the geometry type, and the SRID – … Continue reading Spatial Reference Tables<\/span> Spatial References help:<\/h3>\n
CREATE TABLE [dbo].[spatial_ref_sys](\r\n [srid] [int] NOT NULL,\r\n [auth_name] [varchar](256) NULL,\r\n [auth_srid] [int] NULL,\r\n [srtext] [varchar](2048) NULL,\r\n [proj4text] [varchar](2048) NULL,\r\n PRIMARY KEY CLUSTERED\r\n (\r\n [srid] ASC\r\n )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]\r\n ) ON [PRIMARY]<\/pre>\n
CREATE TABLE [dbo].[geometry_columns](\r\n [f_table_catalog] [varchar](128) NOT NULL,\r\n [f_table_schema] [varchar](128) NOT NULL,\r\n [f_table_name] [varchar](256) NOT NULL,\r\n [f_geometry_column] [varchar](256) NOT NULL,\r\n [coord_dimension] [int] NOT NULL,\r\n [srid] [int] NOT NULL,\r\n [geometry_type] [varchar](30) NOT NULL,\r\n CONSTRAINT [geometry_columns_pk] PRIMARY KEY CLUSTERED\r\n (\r\n [f_table_catalog] ASC,\r\n [f_table_schema] ASC,\r\n [f_table_name] ASC,\r\n [f_geometry_column] ASC\r\n )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]\r\n ) ON [PRIMARY]<\/pre>\n
<\/pre>\n