Well, I never did complete my series of posts describing our indexing scheme. I guess I ought pick it up again now.
We've gone through some preliminaries so far, describing why we'd like spatial index, what a simple indexing might look like, and how we would use that simple scheme internally. Over the next few posts, my plan is to describe the actual scheme we use and give some idea how it is used internally. I'll start with the geometry type, and then cover geography. There's more alike than not.
First, though, let's look back at where we've been.
Recall our simple grid index: we chose a bounding box, and then broke up space into a set of tiles. These tiles were numbered using some scheme. (In our example, we just numbered them in row-major order.)
We can find at least a few points to critique1:
Given that we want to stick with a tiling scheme, we want to find some scheme that will address these issues. I should point out that there is no perfect solution to issue (3), but we would still like to do better than we have.
Next time: Our Basic Multi-Level Grids
1 There are more issues we could pick on, but for the moment, I'm only going to choose the issues we're going to fix.2 We'll come back to some others later in the series.2 I may have inadvertanly missed some issues that we will fix as well. As you can probably tell, it's not like I've planned out these posts too carefully...
Isaac, can you give us some guidance on using the Spatial Index Level settings.
Thanks for the great post "Introduction to SQL Server Spatial". It got us started on path that saved us more than $100K.
Hi Folks, Last time , we highlighted several problems with a simple grid index. If you don't recall---and
Hi Folks, Last time , we highlighted several problems with a simple grid index. If you don't recall
Hi Folks, This post contains no new information; it’s just a rollup of links to spatial indexing posts