------------------------------------------------------------------------------- Oracle11g Spatial Release 11.2.0.1 Release ------------------------------------------------------------------------------- Installation ------------ Refer to the Spatial User Guide for instructions on how to install Spatial. Oracle Spatial User's Guide and Reference Part Number B10826-01 (i) Connect as SYSTEM AS SYSDBA and create the MDSYS user. Run the $ORACLE_HOME/md/admin/mdprivs.sql file. (ii) Connect as SYS as SYSDBA and run the script catmd.sql. This script is in $ORACLE_HOME/md/admin. This will install the Spatial product. New Features in 11gR2 ---------------------- Oracle Spatial 11g Release 2 (11.2) includes new features. Index Maintenance Required Before and After Upgrade for WFS and CSW Data If you are using Spatial Web Feature Service (WFS) or Catalog Services for the Web (CSW) support, and if you have data from a previous release that was indexed using one or more SYS.XMLTABLEINDEX indexes, you must drop the associated indexes before the upgrade and re-create the indexes after the upgrade. For more information, see Section A.2. New Spatial Aggregate Function The following new spatial aggregate function has been added (spatial aggregate functions are documented in Chapter 20): * SDO_AGGR_SET_UNION New SDO_GEOM Subprograms The following new subprograms have been added to the SDO_GEOM package, which is documented in Chapter 24: * SDO_GEOM.SDO_ALPHA_SHAPE * SDO_GEOM.SDO_CONCAVEHULL * SDO_GEOM.SDO_CONCAVEHULL_BOUNDARY * SDO_GEOM.SDO_TRIANGULATE New SDO_UTIL Subprograms The following new subprograms have been added to the SDO_UTIL package, which is documented in Chapter 32: * SDO_UTIL.INTERIOR_POINT * SDO_UTIL.FROM_KMLGEOMETRY * SDO_UTIL.TO_KMLGEOMETRY New SDO_WFS_LOCK Subprogram The following new subprogram has been added to the SDO_WFS_LOCK package, which is documented in Chapter 33: * SDO_WFS_LOCK.EnableDBTxns SDO_NN_DISTANCE Performance Improvement with FIRST_ROWS Hint The implementation of the SDO_NN_DISTANCE ancillary operator has been changed to provide improved performance when you specify the FIRST_ROWS optimizer hint. For an example of using the FIRST_ROWS hint, see the SDO_NN_DISTANCE reference section in Chapter 19. Support for Google Maps with Spatial Applications Support for Google Maps with Oracle Spatial applications has been enhanced. You can now specify a use case name of USE_SPHERICAL with the SDO_CS.TRANSFORM function or the SDO_CS.TRANSFORM_LAYER procedure, to have Spatial use spherical math (used by Google Maps) instead of ellipsoidal math in its projections. For more information, see Section 6.12, "Google Maps Considerations". Support for Workspace Manager with WFS You can perform database transactions and Oracle Workspace Manager workspace maintenance operations in the same session with WFS transactions (WFS-T). In the previous release, only WFS queries from one or more workspaces were supported. For information about using WFS with Workspace Manager, see Section 15.5. Cross-Endian Operations Supported for Transportable Tablespaces Containing Spatial Indexes For the SDO_UTIL.INITIALIZE_INDEXES_FOR_TTS procedure (documented in Chapter 32), transportable tablespaces containing spatial indexes are now supported across endian format platforms (big-endian to little-endian, or little-endian to big-endian). They were not supported in the previous release. Support for Very Large Geometries (More Than 1,048,576 Ordinates) A new script is available if you need to support geometries with more than 1,048,576 ordinates; however, using that script involves significant extra work, some database downtime, and some considerations and restrictions. For information, see Section A.3. SDO_UTIL.PREPARE_FOR_TTS Deprecated Effective with Oracle Database Release 11.2, the SDO_UTIL.PREPARE_FOR_TTS procedure is deprecated. You do not need to call that procedure before performing a transportable tablespace export operation. What's New in GeoRaster? This section describes new and changed features of Oracle Spatial GeoRaster for Oracle Database 11g Release 2 (11.2). Java API GeoRaster now includes a Java API, which consists of interfaces and classes that support features available with the GeoRaster feature of Oracle Spatial. For more information, see Section 1.13. Ground Control Point (GCP) Support You can use ground control points (GCPs) to georeference GeoRaster objects. The support for this feature includes several new data types and PL/SQL subprograms, as well as enhancements to some existing types and subprograms. For information, see the following: * Section 1.6.2, "Georeferencing Using GCPs" * Section 2.3.5, "SDO_GEOR_SRS Object Type" (includes all GCP-related information) * Section 2.3.6, "SDO_GEOR_GCP Object Type" * Section 2.3.7, "SDO_GEOR_GCP_ COLLECTION Collection Type" * Section 2.3.8, "SDO_GEOR_GCPGEOREFTYPE Object Type" * SDO_GEOR.deleteControlPoint procedure * SDO_GEOR.georeference (new function formats for using GCPs) * SDO_GEOR.getControlPoint function * SDO_GEOR.getGCPGeorefMethod function * SDO_GEOR.getGCPGeorefModel function * SDO_GEOR.getSRS function (includes GCP-related information) * SDO_GEOR.setControlPoint procedure * SDO_GEOR.setGCPGeorefMethod procedure * SDO_GEOR.setGCPGeorefModel procedure * SDO_GEOR.setSRS procedure (includes GCP-related information) * Appendix A, "GeoRaster Metadata XML Schema" (includes new GCP-related elements) Reprojection of GeoRaster Objects You can reproject a GeoRaster object to a different Oracle Spatial coordinate system by using the new SDO_GEOR.reproject, which is documented in Chapter 4. Optimized Blocking to Reduce Padding Space For raster data that is blocked, you can specify the new OPTIMALPADDING keyword to cause any user-specified blockSize value for storage parameters to be adjusted automatically to an optimal value to reduce padding space. For more information, see the descriptions on the blocking and blockSize keywords in Table 1-1, "storageParam Keywords for Raster Data" in Section 1.4.1. You can also use the new SDO_GEOR_UTL.calcOptimizedBlockSize procedure (documented in Chapter 6) to calculate an optimal blockSize value that will use less padding space in the GeoRaster object storage, and you can apply the result in any subprogram that has the storageParam parameter. Grid Interpolations The new SDO_GEOR.evaluateDouble function (documented in Chapter 4) evaluates a direct location based on neighboring cell values by using a specified interpolation method, and returns the raster values (double precision numbers) for the specified bands or layers for that location. Polygon-Based Clipping in Queries The SDO_GEOR.getRasterSubset and SDO_GEOR.subset procedures (documented in Chapter 4) are enhanced. In previous releases, only the MBR (rectangle) of the query polygon was used. Now, you can also clip the query result along the (irregular) polygon boundary. setModelCoordLocation Procedure The new SDO_GEOR.setModelCoordLocation procedure (documented in Chapter 4) enables you to change the cell coordinate system from CENTER to UPPERLEFT or from UPPERLEFT to CENTER. It applies only to georeferenced GeoRaster objects, and it automatically adjusts the functional fitting coefficients of the GeoRaster SRS accordingly to reflect the change (to ensure that the relationship between cell coordinates and model coordinates does not change). getCellValue Function Allows Multiple Bands or Layers The SDO_GEOR.getCellValue function (documented in Chapter 4) is enhanced to return cell values of multiple layers or bands for a specified location. In previous releases, it returned only a single cell value of a specified layer or band. getGeoreferenceType Function Return Values The SDO_GEOR.getGeoreferenceType function (documented in Chapter 4) can return the following values for georeference type in addition to those documented in the previous release of this manual: 5 for cubic polynomial, 6 for quadratic rational polynomial, or 7 for quadratic polynomial.