Using Oracle 19c, we try to configure a user-defined projected CRS following the documentation section 6.9.2 "Creating a Projected CRS".
The COORD_OP_METHOD of our choice is 9810 "Polar Stereographic (variant A)" as we need the Scale Factor parameter.
After the INSERTS are done, querying the new CRS from CS_SRS does not contain the projection.
I suspect that this is due to missing LEGACY_NAME and LEGACY_PARAM_NAME fields in the underlying tables, as you can see by this:
SELECT m.COORD_OP_METHOD_ID, m.COORD_OP_METHOD_NAME, m.LEGACY_NAME, p.PARAMETER_NAME, u.LEGACY_PARAM_NAME
FROM SDO_COORD_OP_METHODS m
INNER JOIN SDO_COORD_OP_PARAM_USE u ON u.COORD_OP_METHOD_ID = m.COORD_OP_METHOD_ID
INNER JOIN SDO_COORD_OP_PARAMS p ON p.PARAMETER_ID = u.PARAMETER_ID
WHERE m.COORD_OP_METHOD_ID = 9810;
Here is what we executed:
DE1200_CoordinateSystem_Changes.txt (5.27 KB)I'm not allowed to modify SDO_COORD_OP_PARAM_USE in order to set the fields manually.
What I expected is:
m.LEGACY_NAME = 'Polar_Stereographic'
u.LEGACY_PARAM_NAME = 'Latitude_Of_Center' WHERE u.PARAMETER_ID=8801
u.LEGACY_PARAM_NAME = 'Central_Meridian' WHERE u.PARAMETER_ID=8802
u.LEGACY_PARAM_NAME = 'Scale_Factor' WHERE u.PARAMETER_ID=8805
u.LEGACY_PARAM_NAME = 'False_Easting' WHERE u.PARAMETER_ID=8806
u.LEGACY_PARAM_NAME = 'False_Northing' WHERE u.PARAMETER_ID=8806
As a workaround, I filled the LEGACY_WKTEXT field with what I expected from CS_SRS.WKTEXT.
Did I miss something? Why are the respective legacy fields empty? Is my workaround correct?