Using the Define Projection tool to alter the coordinate system of a feature dataset leads to inconsistent and heterogenous coordinate system assignment.
上次发布: December 6, 2017ArcSDE/Enterprise Geodatabase
漏洞 ID 编号
NIM084357
已提交
September 4, 2012
上次修改时间
April 2, 2025
适用范围
ArcSDE/Enterprise Geodatabase
找到的版本
10.1
操作系统
Windows OS
操作系统版本
2008 64 Bit
状态
Will Not Be Addressed
开发团队已考虑过该问题或请求,并决定不会解决该问题。 问题的“其他信息”部分可能包含进一步说明。
附加信息
We apologize that we were unable to address this issue within the current product support cycle. If the issue continues to affect your work in a supported release, please contact Technical Support.
解决办法
Use the Project (Data Management) tool to alter the projection of the feature dataset. Utilize a model or Python script to establish a schema standard and paramaterized the application of a coordinate system.From ArcCatalog:After running the Define projection tool and checking to see that the sde_spatial_referencess table has the correct coordinate system under srtext:1. Open ArcCatalog, connect to the geodatabase. Right-click the Feature Class,sde.TestShape.2. Export >TestShape_Export.3. Use the SQL Server Management Studio, check the sde_layers table. Now it has the SRID set to a new number and the spatial references table has auth_srid set to 26996 (to match NAD_1983_StatePlane_Missouri_East_FIPS_2401 set using the Define Projection tool), Srtext is set to NAD_1983_StatePlane_Missouri_East_FIPS_2401.4. Check constraint on sde.TestShape changed set to STSRID = 26996.5. Can load data in the correct coordinate because the check constraint is now updated to 0.Changing the SRID value stored in the shape column in the feature class table in the SQL Server database, resets the SRID value in the Feature class properties>General tab.From SQL Server:Modify check constraint from the SQL Server Management Studio.