Book Image

Applying and Extending Oracle Spatial

Book Image

Applying and Extending Oracle Spatial

Overview of this book

Spatial applications should be developed in the same way that users develop other database applications: by starting with an integrated data model in which the SDO_GEOMETRY objects are just another attribute describing entities and by using as many of the database features as possible for managing the data. If a task can be done using a database feature like replication, then it should be done using the standard replication technology instead of inventing a new procedure for replicating spatial data. Sometimes solving a business problem using a PL/SQL function can be more powerful, accessible, and easier to use than trying to use external software. Because Oracle Spatial's offerings are standards compliant, this book shows you how Oracle Spatial technology can be used to build cross-vendor database solutions. Applying and Extending Oracle Spatial shows you the clever things that can be done not just with Oracle Spatial on its own, but in combination with other database technologies. This is a great resource book that will convince you to purchase other Oracle technology books on non-spatial specialist technologies because you will finally see that "spatial is not special: it is a small, fun, and clever part of a much larger whole".
Table of Contents (20 chapters)
Applying and Extending Oracle Spatial
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Table Comparing Simple Feature Access/SQL and SQL/MM–Spatial
Index

Space curve based partitioning


In this section, we will describe an example to show how to use a space curve value as the partition key to achieve partitioning that is similar to X and Y-based partitioning. This approach has some advantages and disadvantages when compared to multi-key range-based partitioning. We can use a single partition key instead of the multi-column partition key. If a new partition is to be added by splitting any of the existing partitions, multi-key partitions are harder to manage if only one partition needs to be split based on the first value of the partition key. On the other hand, the multi-key partitioning provides an easy-to-use method for coming up with initial partitions that have the same number of rows in each partition.

For this example, we will use the land_parcels table to show the concept of spatial-based partitioning for tables with non-point geometry data. Before we create the partitioned table, we will first revisit the space curve concepts. We learned...