Skip Headers
Oracle® Spatial and Graph Developer's Guide
12c Release 1 (12.1)

E17896-14
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

Changes in This Release for Oracle Spatial and Graph Developer's Guide

This preface contains:

Changes in Oracle Database 12c Release 1 (12.1)

The following are changes in Oracle Spatial and Graph Developer's Guide for Oracle Database 12c Release 1 (12.1).

New Features

The following features are new in this release:

NURBS Curve Support

Support for non-uniform rational B-spline (NURBS) curve geometries is included in this release. NURBS curves allow representation of free-form shapes with arbitrary shapes. NURBS representation allows control over the shape of the curve because control points and knots guide the shape of the curve, and they allow complex shapes to be represented with little data.

For more information, see Section 1.13, "NURBS Curve Support in Oracle Spatial and Graph".

Height Information Approximated for Certain 3D Geodetic Operations

In the previous release, height information was ignored for certain operations on three-dimensional geodetic geometries. With this release, the height is approximated and included in calculations for these operations.

For more information, see Section 1.11, "Three-Dimensional Spatial Objects", including Table 1-2, "How Geodetic 3D Calculations Are Performed".

New Spatial Metadata Views (3D Themes, Scenes, Viewframes)

ALL_SDO_xxx and USER_SDO_xxx metadata views have been added for 3D themes, scenes, and viewframes. For descriptions of these views, see Section 2.9, "Other Spatial Metadata Views".

These views are relevant to several new functions listed under "New and Changed SDO_UTIL Subprograms".

New and Changed Aggregate Functions

The following new spatial aggregate function has been added (spatial aggregate functions are documented in Chapter 20):

New and Changed SDO_CS Subprograms

The following new subprograms have been added to the SDO_CS package, which is documented in Chapter 21:

New and Changed SDO_GEOM Subprograms

The following new subprogram has been added to the SDO_GEOM package, which is documented in Chapter 24:

New and Changed SDO_PC_PKG Subprograms

The following new subprograms have been added to the SDO_PC_PKG package, which is documented in Chapter 28:

The following significant changes have also been made:

  • For SDO_PC_PKG.CLIP_PC, the include_custom_dims parameter can be used to return point cloud blocks that contain custom dimensions in addition to regular dimensions.

  • For SDO_PC_PKG.INIT, the pc_other_attrs parameter can be used to specify metadata for point cloud pyramiding.

New and Changed SDO_TIN_PKG Subprograms

The following new subprograms have been added to the SDO_TIN_PKG package, which is documented in Chapter 30:

The following significant changes have also been made:

  • For SDO_TIN_PKG.INIT, the tin_other_attrs parameter can be used to specify metadata for TIN pyramiding.

New and Changed SDO_UTIL Subprograms

The following new subprograms have been added to the SDO_UTIL package, which is documented in Chapter 32:

The following significant changes have also been made:

  • SDO_UTIL.AFFINETRANSFORMS has default values for all parameters except the first (geometry). This can simplify coding when you need to specify nondefault values for only a few parameters.

  • SDO_UTIL.CIRCLE_POLYGON has an additional format that includes the start_azimuth and end_azimuth parameters.

  • SDO_UTIL.SIMPLIFY has the new optional parameter remove_loops, which enables you to ensure that a simplified line string geometry for not contain any self-crossing loops in the middle. (SDO_UTIL.SIMPLIFYVW also has the remove_loops parameter.)

New SDO_GEOM_MBR Operator

SDO_GEOM_MBR is a SQL operator that is functionally identical to the SDO_GEOM.SDO_MBR function, but provides better performance.

For SDO_GEOM_MBR operator usage information and an example, see the SDO_GEOM.SDO_MBR function reference section.

New SDO_POINTINPOLYGON Operator

The new SDO_POINTINPOLYGON operator (technically a table function takes a set of rows whose first column is a point's x-coordinate value and the second column is a point's y-coordinate value, and returns those rows that are within a specified polygon geometry.

SPATIAL_VECTOR_ACCELERATION System Parameter (VPA)

To accelerate the performance of spatial operators, it is recommended that you enable the Vector Performance Accelerator (VPA) feature by setting the SPATIAL_VECTOR_ACCELERATION database system parameter to the value TRUE. (This feature and associated system parameter are authorized for use only by licensed Oracle Spatial and Graph users, and the default value for the parameter is FALSE.) You can set this parameter for the whole system or for a single session.

For more information, see Section 1.19, "SPATIAL_VECTOR_ACCELERATION System Parameter".

Other Changes

The following other changes have been made in this book:

  • The product name has been changed from Oracle Spatial to Oracle Spatial and Graph, also referred to as Spatial and Graph.

  • The section previously titled "SDO_AGGR_UNION Example" in Appendix C, "Complex Spatial Queries: Examples" has been deleted. That section had recommended: "For better performance when aggregating many rows, break your aggregation into groupings so that each is always 50 geometries or fewer." However, because of enhancements to SDO_AGGR_UNION effective with Release 12.1, if you are using Spatial and Graph with SPATIAL_VECTOR_ACCELERATION=TRUE (see Section 1.19), that statement and the example using nested aggregates are no longer recommended, and nested aggregates can actually be slower than a single aggregate.

    However, if you are using Oracle Locator, nested aggregates or SDO_AGGR_SET_UNION are recommended. For more information, see Section C.4 ("SDO_AGGR_UNION Example") in the Release 11.2 version of Oracle Spatial Developer's Guide.