[fdo-users] coordinate system bug?

[Orest Halustchak]

Hi Brad,

The provider gets the coordinate system information from SDE. It doesn't go directly against the Oracle metadata in this case and is independent of whether the server is Oracle, SQL Server, etc. It uses whatever the SDE api returns as the coord sys wkt. Map 2008 and 2009 include the ability to recognize either Oracle or ESRI variations of the wkt value, so it's unclear why some of these cases end up not being recognized. I assumed that you verified that the sde layer definitions all use the identical coordinate system definition?

Thanks,
Orest.

From: fdo-users-bounces at lists.osgeo.org [mailto:fdo-users-bounces at lists.osgeo.org] On Behalf Of Brad Nesom
Sent: Monday, April 21, 2008 9:50 AM
To: FDO Users Mail List
Subject: [fdo-users] coordinate system bug?


I have been working on a problem with esri for quite some time. I have an oracle database storing my ArcSDE data as SDO geometry (supported on oracle 10g 2.3 and arcsde 9.2). I use several parameters in my keyword to load the data and only use esri to load. The significant parameters to this issue are the srid and the geometry type being 41106 and sdo_geometry respectively. After having scaling problems other problems with displaying units in arcmap for over 2 years esri finally blamed the problem on a bug in oracle (they would give me the bug number). Stating that the oracle wkt is not an international standard and thus has problems being recognised in the esri software. The wkt 41106 is exactly the same as the esri system NAD 1983 StatePlane Oklahoma North FIPS 3501 (Feet).prj with the exception of the name (Oklahoma 3501, Northern Zone (1983, US Survey feet))(which by the way is the same as the autodesk ok83-nf with no problems there). ESRI said this was the cause of the oracle bug.
I know that sde is having a problem relating this wkt because if I build a feature dataset and assign the esri system to it, then load the data into that dataset (in esri products the dataset determines the coordinate system of all feature classes contained within), It assigns the wkt to the feature class until you go and reassign the esri system to the feature dataset (this is the workaround esri provided). All is well until something like a load, truncate or new feature class is added to the dataset.
Now my question.
In map 3d 2008 or 2009, when I get connected via FDO the list of coordinate systems is inconsistent (see attached jpg sdelistinmap.jpg). If I look at my oracle metadata all srids are assigned the 41106. Where does map pull the coordinate system information for the arcsde fdo data type? is it from the sde layer definition?
Any help or understanding would be grand.





select * from mdsys.cs_srs where srid = 41106
/
-------------------------------------------------------------------------------
CS_BOUNDS(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES
-------------------------------------------------------------------------------
PROJCS["Oklahoma 3501, Northern Zone (1983, US Survey feet)", GEOGCS ["NAD 83 (
ontinental US)", DATUM ["NAD 83 (Continental US)", SPHEROID ["GRS 80", 6378137,
298.257222101]], PRIMEM [ "Greenwich", 0.000000 ], UNIT ["Decimal Degree", 0.01
CS_NAME                                                                    SRID
-------------------------------------------------------------------- ----------
 AUTH_SRID
----------
AUTH_NAME
-------------------------------------------------------------------------------
WKTEXT
-------------------------------------------------------------------------------
CS_BOUNDS(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES
-------------------------------------------------------------------------------
45329251994330]], PROJECTION ["Lambert Conformal Conic"], PARAMETER ["Standard_
arallel_1", 35.566667], PARAMETER ["Standard_Parallel_2", 36.766667], PARAMETER
["Central_Meridian", -98.000000], PARAMETER ["Latitude_Of_Origin", 35.000000],
CS_NAME                                                                    SRID
-------------------------------------------------------------------- ----------
 AUTH_SRID
----------
AUTH_NAME
-------------------------------------------------------------------------------
WKTEXT
-------------------------------------------------------------------------------
CS_BOUNDS(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES
-------------------------------------------------------------------------------
ARAMETER ["False_Easting",   1968500.0000], UNIT ["U.S. Foot", 0.3048006096012]

________________________________
More immediate than e-mail? Get instant access with Windows Live Messenger.<http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_instantaccess_042008>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/fdo-users/attachments/20080421/1b84d2a2/attachment.html