[fdo-users] coordinate system bug?
Brad Nesom
kidsmake6 at msn.com
Mon Apr 21 17:43:25 EDT 2008
Yes I have verified that the sdelayers have the correct coordinate definition. However it was just explained to me by esri that the srid in sde is a moving target. each time sde finds any variation (not sure why it htinks there is any variation) it creates a new srid value (random) and assigns the description see below. From esri support >>>3. As we discussed, the 3rd party software maybe should read the auth_srid to get the Oracle spatial coordinate system definition. But in general cases, if a layer is not from Oracle spatial, there may not be the auth_id value. ESRI's ID (comparable to Oracle's SRID)http://arcweb.esri.com/arcwebonline/services/pcs_alpha.htmNAD_1983_StatePlane_Oklahoma_North_FIPS_3501 32124 Oracle Database 10g Release 10.2.0.3.0 - ProductionSQL> select distinct SRID from sde.spatial_references; SRID---------- 1 2 3 4 5 6 7 8 9 10 11 SRID---------- 12 13 14 15 16 17 18 19 20 21 22 SRID---------- 23 24 25 26 27 28 29 30 31 32 33 SRID---------- 34 35 36 37 38 39 40 41 42 43 44 SRID---------- 45 46 47 48 49 50 51 52 53 54 55 SRID---------- 56 57 58 59 60 61 62 63 64 65 66 SRID---------- 67 68 69 70 71 72 73 74 75 76 77 SRID---------- 78 79 80 81 82 83 84 85 86 87 88 SRID---------- 89 90 91 92 93 94 95 96 97 98 99 SRID---------- 100 101 102 103 104 105 106 107 108 109 110 SRID---------- 111 112 113 114 115 116 117 118 119 120 121 SRID---------- 122 123 124 125 126 127 128 129 130 131 132 SRID---------- 133 134 135 136 137 138 139 140 141 142 143 SRID---------- 144 145 146 147 148 149 150 151 152 153 154 SRID---------- 155 156 157 158 159 160 161 162 163 164 165 SRID---------- 166 167 168 169 170 171 172 173 174 175 176 SRID---------- 177 178 179 180 181 182 183 184 185 186 187 SRID---------- 188 189 190 191 192 193 194 195 196 197 198 SRID---------- 199 200 201 202 203 204 205 206 207 208 209 SRID---------- 210 211 212 213 214 215 216 217 218 219 220 SRID---------- 221 222 223 224 225 226 227 228 229 230 231 SRID---------- 232 233 234 235 236 237 238 239 240 241 242 SRID---------- 243 244 245 246 247 248 249 250 251 252 253 SRID---------- 254 255 256 257 258 259 260 261 262 263 264 SRID---------- 265 266 267267 rows selected.SQL> select description, auth_srid, SRTEXT from sde.spatial_references where SRID in (86, 180, 133);DESCRIPTION AUTH_SRID---------------------------------------------------------------- ----------SRTEXT-------------------------------------------------------------------------------- 41106PROJCS["NAD_1983_StatePlane_Oklahoma_North_FIPS_3501_Feet",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",1968500.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-98.0],PARAMETER["Standard_Parallel_1",35.56666666666667],PARAMETER["Standard_Parallel_2",36.76666666666667],PARAMETER["Latitude_Of_Origin",35.0],UNIT["Foot_US",0.3048006096012192]]DESCRIPTION AUTH_SRID---------------------------------------------------------------- ----------SRTEXT--------------------------------------------------------------------------------UNKNOWNUNKNOWNSQL>
From: orest.halustchak at autodesk.comTo: fdo-users at lists.osgeo.orgDate: Mon, 21 Apr 2008 14:25:41 -0700Subject: RE: [fdo-users] coordinate system bug?
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 NesomSent: Monday, April 21, 2008 9:50 AMTo: FDO Users Mail ListSubject: [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.01CS_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.
_________________________________________________________________
Pack up or back up–use SkyDrive to transfer files or keep extra copies. Learn how.
http://www.windowslive.com/skydrive/overview.html?ocid=TXT_TAGLM_WL_Refresh_skydrive_packup_042008
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/fdo-users/attachments/20080421/4caac43c/attachment-0001.html
More information about the fdo-users
mailing list