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

Summary


The chapter first showed how a standardized geometry type and methods can aid in the creation of solutions to spatial problems that can not only run on just one database, but also with editing, any other database supporting that common geometry data type, internal description, and methods that derive from the SQL/MM and OGC SFA 1.x standards.

The issues for data storage that arise from having singly inherited and multiply-inherited geometry data types were examined with a common approach for using all three databases and their types presented.

Oracle's ST_GEOMETRY hierarchy imposes a highly standardized approach to object declaration and use, whereas PostgreSQL's and SQL Server 2012's singly inherited types provide partial implementations of the same standards. This can be seen in the execution of methods like ST_Area against non-polygon geometry objects, while Oracle does not allow inappropriate method execution. In addition, Oracle does not allow ST_GeometryN and ST_NumGeometries...