Search Results valid_lrs_pt
Overview
MDSYS.SDO_LRS is the Oracle Spatial Linear Referencing System (LRS) package shipped with the Oracle database and exposed within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments through the MDSYS schema. The package provides the PL/SQL API for defining, creating, and manipulating LRS geometric segments — linear features such as roads, pipelines, utility lines, and rail corridors that carry measure values (mileage, chainage, or stationing) along their length. In an EBS context, this functionality underpins the spatial and geographic data model used by applications that track assets, networks, and linear infrastructure, allowing a segment to be located by measure rather than by raw coordinate geometry.
The package is declared as AUTHID current_user, meaning its procedures execute with the privileges of the invoking schema rather than the definer, and it is classified in ETRM under the API classification OTHER. The documented interface comprises 205 procedures and functions, of which the core geometric-segment operations and their 3D variants form the primary surface area.
Key Procedures and Functions
The documented routines fall into several functional groups:
- Segment definition: DEFINE_GEOM_SEGMENT and DEFINE_GEOM_SEGMENT_3D establish an LRS geometric segment, automatically populating measure values between a start and end measure and accepting a dimension array and an optional tolerance.
- Segment editing: CLIP_GEOM_SEGMENT and CLIP_GEOM_SEGMENT_3D create a new segment by clipping an existing one between two measures; SPLIT_GEOM_SEGMENT and SPLIT_GEOM_SEGMENT_3D divide a segment at a specified point; CONCATENATE_GEOM_SEGMENTS and CONCATENATE_GEOM_SEGMENTS_3D join connected segments end to end; SCALE_GEOM_SEGMENT adjusts the measure range of a segment.
- Validation: VALID_GEOM_SEGMENT, VALID_GEOM_SEGMENT_3D, VALID_LRS_PT, VALID_LRS_PT_3D, and VALID_MEASURE/VALID_MEASURE_3D verify that geometries, LRS points, and measure values are well formed before use.
- State and topology checks: IS_GEOM_SEGMENT_DEFINED and IS_GEOM_SEGMENT_DEFINED_3D confirm whether a geometry has been initialized as an LRS segment, while CONNECTED_GEOM_SEGMENTS and CONNECTED_GEOM_SEGMENTS_3D test whether segments share endpoints.
- Measurement: GEOM_SEGMENT_LENGTH returns the length of a segment; related routines return measure, point, and offset values along the geometry.
Several functions, including CLIP_GEOM_SEGMENT, are declared DETERMINISTIC and PARALLEL_ENABLE. DETERMINISTIC guarantees the same output for identical inputs, enabling result caching and function-based indexing; PARALLEL_ENABLE permits the function to execute inside a parallel query slave, which is the attribute most commonly searched in this context. These two declarations make the clipping functions suitable for set-based processing across large volumes of spatial rows.
Tables Accessed
The package references the table PLITBLM through APPS synonyms. This internal spatial support table is used in the measure and point computation paths of the LRS operations. The documented package metadata identifies only this single table reference, indicating that the majority of SDO_LRS processing operates on the SDO_GEOMETRY objects passed as parameters rather than persisting intermediate results.
Usage Notes
SDO_LRS is typically invoked from custom PL/SQL, database triggers, or concurrent programs rather than from standard EBS forms, since the package belongs to MDSYS and is not an EBS-owned API. Typical invocation patterns include calling DEFINE_GEOM_SEGMENT to prepare a geometry before storing it in a spatial column, invoking CLIP_GEOM_SEGMENT or SPLIT_GEOM_SEGMENT in set-based DML where the PARALLEL_ENABLE clause allows the work to be distributed, and using the VALID_* functions as pre-insert validation guards. Because the package is declared AUTHID current_user, the invoking schema must hold EXECUTE privilege and any necessary object privileges on referenced tables. In EBS 12.1.1 and 12.2.2 the database release determines the precise SDO_LRS signature set available, so custom code should be validated against the specific 11g or 12c database version underpinning each EBS instance.