Search Results sdo_srid_list

Overview

MDSYS.SDO_CS is the core Oracle Spatial coordinate system package body responsible for spatial reference system (SRS) management and coordinate transformation within the Oracle database. In the Oracle EBS 12.1.1 and 12.2.2 environments, this package is part of the MDSYS schema owned by Oracle Locator/Spatial, and it underpins any EBS functionality that stores, validates, or converts geospatial data. Its principal business function is to translate coordinates between different spatial reference identifiers (SRIDs), reconcile Oracle-native SRID definitions with EPSG standards, and maintain the metadata catalog that defines datums, ellipsoids, coordinate systems, projections, and transformation paths. Because the EBS schema does not own this package, applications interact with it indirectly through geospatial features such as GIS integrations, customer or asset location tracking, and any custom tables with SDO_GEOMETRY columns.

Key Procedures and Functions

The package exposes 122 documented procedures and functions. The transformation routines form the operational core: TRANSFORM_ORIG and TRANSFORM_ORIG_WITH_ARCS convert geometry between coordinate systems, while TRANSFORM_LAYER and TRANSFORM_LAYER_WITH_ARCS apply the same logic to entire spatial layers. VIEWPORT_TRANSFORM supports display-oriented conversions for map rendering.

The SRS definition and validation routines include VALIDATE_WKT and INTL_VALIDATE_WKT, which verify well-known text descriptions, and INTERNAL_READ_PROJ_FROM_WKT, which parses projection information from WKT input. INTERNAL_DET_SRID_WKT resolves SRID values from WKT declarations.

Transformation chain resolution is handled by DETERMINE_DEFAULT_CHAIN, DETERMINE_CHAIN, INTERNAL_DET_CHAIN, and INTERNAL_DET_CHAIN_VARCHAR, which compute the ordered sequence of operations required to move between two reference systems. Mapping routines MAP_ORACLE_SRID_TO_EPSG and MAP_EPSG_SRID_TO_ORACLE reconcile Oracle's internal identifiers with the EPSG registry, while INTERNAL_EPSG_PARAM_TO_LEGACY supports backward compatibility with earlier parameter formats.

Administrative routines manage operation preferences and chains: CREATE_CONCATENATED_OP, CREATE_PREF_CONCATENATED_OP, DELETE_OP, and ADD_PREFERENCE_FOR_OP allow DBAs and developers to define, remove, and prioritize concatenated transformation operations. Collectively these procedures implement the SRID list and SDO_SRID_LIST logic that users reference when searching for sdo_srid_list, the dependency that catalogues available spatial reference identifiers.

Tables Accessed

SDO_CS reads and writes an extensive set of MDSYS metadata tables. SDO_COORD_REF_SYS, SDO_COORD_SYS, SDO_COORD_AXES, SDO_DATUMS, SDO_ELLIPSOIDS, SDO_PRIME_MERIDIANS, and SDO_UNITS_OF_MEASURE define the fundamental reference system catalog. Transformation definitions and parameters are drawn from SDO_COORD_OPS, SDO_COORD_OP_METHODS, SDO_COORD_OP_PARAMS, SDO_COORD_OP_PARAM_USE, SDO_COORD_OP_PARAM_VALS, and SDO_COORD_OP_PATHS. Transformation chains and preferences reside in SDO_SRID_CHAIN, SDO_TFM_CHAIN, SDO_PREFERRED_OPS_SYSTEM, and SDO_PREFERRED_OPS_USER. SDO_SRID_LIST and SDO_CS_SRS hold SRID enumerations, while CS_SRS and EPSG_PARAM/EPSG_PARAMS retain legacy definitions. Supporting tables include MDERR, TFM_PLAN, TMP_COORD_OPS, NTV2_SEQUENCE, NTV2_XML_DATA, and SDO_TRANSIENT_RULE/SDO_TRANSIENT_RULE_SET. The package also references SDO_GEOMETRY and its array types, plus utility objects such as DBMS_LOB, DBMS_OUTPUT, XMLTYPE, XMLAGG, and XDBURITYPE accessed through APPS synonyms.

Usage Notes

SDO_CS is invoked whenever EBS or custom code must transform, validate, or resolve spatial coordinates. In practice it is called from PL/SQL stored procedures and triggers that manipulate SDO_GEOMETRY columns, from Oracle Forms or OAF pages displaying geospatial data, and from concurrent programs performing batch coordinate conversion or data migration. Direct invocation is uncommon in standard EBS; most calls originate from Oracle Spatial operators, the SDO_CS API layer, or GIS middleware. Developers troubleshooting SRID assignments or transformation errors—such as when querying sdo_srid_list to enumerate valid reference systems—will encounter this package through dependency chains. Because SDO_CS is owned by MDSYS and marked VALID, modifications are restricted to Oracle-supplied patches, and the package is referenced by nineteen other database objects that depend on its transformation behaviour remaining consistent across EBS releases.