Search Results clip_triangleids




Overview

MDSYS.SDO_TIN_PKG is an Oracle Spatial and Graph server-side PL/SQL package that provides triangulated irregular network (TIN) functionality. A TIN is a vector-based surface representation constructed from a set of irregularly spaced points and the triangle edges that connect them, and it is a standard structure for modeling terrain, elevation, and other continuous surfaces. Within Oracle EBS 12.1.1 and 12.2.2 the package is owned by the MDSYS schema and is classified as an OTHER API, meaning it is not part of the EBS application table or business API surface but is available to EBS components through standard database privileges and synonyms.

The package is relevant to the EBS user search term "sdo_geometry" because its primary inputs and outputs are MDSYS.SDO_GEOMETRY objects. TIN construction, clipping, surface extraction, and DEM conversion all consume or return SDO_GEOMETRY instances, so the package bridges EBS geospatial data stored as standard geometry objects into triangulated surface analysis.

Key Procedures and Functions

The documented API exposes fifteen procedures and functions. The core creation path begins with INIT, which validates and prepares a TIN definition from a base table, base column, block table, partition parameters, extent, tolerance, dimensions, domain, break lines, stop lines, void regions, value attribute tables, and auxiliary XML attributes, returning an SDO_TIN object. CREATE_TIN then materializes the TIN from that object and an input table, with an optional cluster piece data table.

The extraction and query group centers on CLIP_TIN, which returns a pipelined SDO_TIN_BLK_TYPE result set, and CLIP_PTS, CLIP_PTIDS, CLIP_TRIANGLES, and CLIP_TRIANGLEIDS, which return points, point identifiers, triangles, and triangle identifiers respectively. CLIP_TIN_INTO_PC clips TIN output into a point cloud structure. GET_SURFACE_OF_TIN and GET_SURFACE_OF_TIN_FOOTPRINT derive surface and footprint geometry, PROJECT_ORDINATES_ONTO_TIN projects coordinates onto the triangulated surface, and GET_VOLUME_UNDER_TIN computes volume beneath the surface.

Conversion routines include TO_GEOMETRY, which deterministically and parallel-enabled reassembles a geometry from point and triangle BLOBs, and TO_DEM, which populates an SDO_GEORASTER digital elevation model from a TIN at a given block size and pixel resolution. DROP_DEPENDENCIES removes dependency metadata for a base table and column.

Tables Accessed

According to the ETRM metadata the package references DBMS_ASSERT, DBMS_LOB, DBMS_OUTPUT, DUAL, PLITBLM, USER_OBJECTS, UTL_NLA, UTL_NLA_ARRAY_DBL, UTL_NLA_ARRAY_INT, UTL_RAW, and XMLTYPE. These are support objects rather than application tables. DBMS_ASSERT sanitizes dynamically referenced schema and table names, DBMS_LOB and UTL_RAW handle binary point and triangle blocks, UTL_NLA and its array types perform the linear algebra underlying triangulation and coordinate operations, PLITBLM provides PL/SQL interface to BLM data, USER_OBJECTS is used for dependency validation, and XMLTYPE carries auxiliary TIN attributes. The base table, block table, and input table used by INIT and CREATE_TIN are passed as runtime parameters rather than fixed references.

Usage Notes

SDO_TIN_PKG is invoked primarily from custom PL/SQL and SQL rather than from standard EBS forms or concurrent programs. Typical EBS scenarios include terrain analysis, cut-and-fill volume calculation, and elevation surface generation over site or asset geometry stored as SDO_GEOMETRY. Because the package is owned by MDSYS, executing users require EXECUTE privilege on the package along with appropriate access to the base and block tables. The package is referenced by one other PL/SQL package, indicating dependent server-side code that should be considered when validating patches or upgrades. Compatibility applies to EBS 12.1.1 and 12.2.2 databases where Oracle Spatial is installed and the SDO_TIN type and related object types exist.