Search icon
Subscription
0
Cart icon
Close icon
You have no products in your basket yet
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Applying and Extending Oracle Spatial

You're reading from  Applying and Extending Oracle Spatial

Product type Book
Published in Sep 2013
Publisher Packt
ISBN-13 9781849686365
Pages 568 pages
Edition 1st Edition
Languages

Table of Contents (20) Chapters

Applying and Extending Oracle Spatial
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
1. Defining a Data Model for Spatial Data Storage 2. Importing and Exporting Spatial Data 3. Using Database Features in Spatial Applications 4. Replicating Geometries 5. Partitioning of Data Using Spatial Keys 6. Implementing New Functions 7. Editing, Transforming, and Constructing Geometries 8. Using and Imitating Linear Referencing Functions 9. Raster Analysis with GeoRaster 10. Integrating Java Technologies with Oracle Spatial 11. SQL/MM – A Basis for Cross-platform, Inter-operable, and Reusable SQL Table Comparing Simple Feature Access/SQL and SQL/MM–Spatial
Use of TREAT and IS OF TYPE with ST_GEOMETRY Index

Cross-platform representation


There are two aspects to representing spatial data in a standards compliant, cross-platform manner:

  • Geometry type definition (what can be represented and stored)

  • Internal geometric description (how each object is physically described)

These will be covered in the following sections:

Outlining the SQL/MM ST_GEOMETRY type

The SQL/MM standard provides access for the database designer and developer to a geometry type hierarchy that can be used for both storage and application development. This is shown by the following diagram.

Oracle's MDSYS.ST_GEOMETRY is a database implementation of this SQL/MM geometry hierarchy, whose actual implementation is depicted graphically as in the following diagram (created using SQL Developer's Data Modeling extension).

Note

The MDSYS schema prefix is actually not needed for the Oracle SQL/MM types due to the presence of global synonyms and as long as no other object has the same name in the current connected schema.

As can be seen Oracle...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime}