Top 5 Recent Articles
ARTICLES CATEGORIES
- Algorithms (22)
- All (399)
- Biography (1)
- Blog (44)
- Business Requirements (1)
- Commentary (1)
- Conversion (2)
- Customers (2)
- Data Models (1)
- Education (2)
- GeoRaptor (13)
- GPS (1)
- Image Processing (2)
- Import Export (8)
- Licensing (2)
- LiDAR (1)
- Linear Referencing (4)
- Manifold GIS (3)
- Mapping (1)
- MySQL Spatial (7)
- Networking and Routing (including Optimization) (5)
- Open Source (18)
- Oracle Spatial and Locator (194)
- Partitioning (1)
- PostGIS (36)
- Projections (1)
- Published Articles (1)
- qGIS (1)
- Recommendations (1)
- Services (1)
- Software Change Log (1)
- Source Code (37)
- Space Curves (9)
- Spatial Database Functions (109)
- Spatial DB comparison (1)
- Spatial XML Processing (11)
- SQL Server Spatial (92)
- Standards (3)
- Stored Procedure (17)
- Tessellation or Gridding (10)
- Tools (2)
- Topological Relationships (1)
- Training (2)
- Triangulation (2)
Tip #2: Spatial Indexing and Primary Keys
For fast and efficient search and retrieval all columns containing spatial data should have a spatial index created on them.
For Oracle an index can be created on any SDO_GEOMETRY column regardless as to whether the table has a primary key or not. This is because Oracle uses an internal, unique, ROWID pseudo-column in its indexes: the ROWID links a leaf in the spatial index to the table’s actual row on disk (in the table’s tablespace).
However, SQL Server 2008 “Katmai” requires that all tables must have a primary key before a spatial index can be constructed. The primary key can be based on one or more columns in the table with those columns being of any data type.
The table I loaded for Tip #1, TAS_LGA, can have its primary key constructed as follows:
1. Make the column that will become the primary key “NOT NULL”
alter table dbo.tas_lga alter column lga_pid char(15) not null;
2. Declaratively define the primary key on our not null column lga_pid as follows:
alter table dbo.tas_lga add constraint tas_lga_pk primary key (lga_pid);
We are now in a position to create our spatial index. Microsoft’s spatial index requires you define the bounding box of the spatial index. For our TAS_LGA table this will be the complete extent of the data. This can be discovered as follows:
select min( a.geog.STEnvelope().STPointN(1).STX) as minx, min( a.geog.STEnvelope().STPointN(1).STY) as miny, max( a.geog.STEnvelope().STPointN(3).STX) as maxx, max( a.geog.STEnvelope().STPointN(3).STY) as maxy from gisdb.dbo.tas_lga a;
minx miny maxx maxy
143.813480017165 -43.8603741008445 148.503628803775 -39.1918359319521
Now that we know the extent of our data we can create a spatial index as follows:
CREATE SPATIAL INDEX tas_lga_geog_idx ON tas_lga (geog) USING GEOMETRY_GRID WITH ( BOUNDING_BOX = ( 143, -44, 149, -39), GRIDS = (LEVEL_1 = HIGH, LEVEL_2 = HIGH, LEVEL_3 = HIGH, LEVEL_4 = HIGH), CELLS_PER_OBJECT = 16);
Documentation
- MySQL Spatial General Functions
- Oracle LRS Objects
- Oracle Spatial Exporter (Java + pl/SQL)
- Oracle Spatial Object Functions
- Oracle Spatial Object Functions (Multi Page)
- PostGIS pl/pgSQL Functions
- SC4O Oracle Java Topology Suite (Java + pl/SQL)
- SQL Server Spatial General TSQL Functions
- SQL Server Spatial LRS TSQL Functions