The Union (Analysis) tool returns 'Error 999999' for some data when writing an output to an enterprise geodatabase.
上次发布: November 20, 2019ArcGIS for Desktop
漏洞 ID 编号
BUG-000126742
已提交
November 13, 2019
上次修改时间
June 5, 2024
适用范围
ArcGIS for Desktop
找到的版本
10.6.1
操作系统
Windows OS
操作系统版本
10.0 64 Bit
状态
Will Not Be Addressed
开发团队已考虑过该问题或请求,并决定不会解决该问题。 问题的“其他信息”部分可能包含进一步说明。
附加信息
The issue occurs because the SpatialReference XYResolution is not set to default and probably due to the difference between the modified XYRes and the set XYTolerance. For more information on fixing the data, refer to ArcGIS Blog: Geoprocessing, Resolution, Tolerance, and Hair (https://www.esri.com/arcgis-blog/products/arcgis-pro/analytics/geoprocessing-resolution-tolerance-and-hair/).
The issue in this case is overlapping polygons in the ConveyanceDivision feature class. There are multiple polygons with barely overlapping boundaries (close to XYTol width), so during the union process, 'nearly' slivers are generated. Slivers do not fall within the parameters for a feature in a file geodatabase (FGDB) to collapse and remove. When inserted into an enterprise geodatabase (EGDB), a shape validation process that is different than for FGDB takes place on the server side and the features are rejected (due to the validation assuming they are collapsing) and cause failure.
Kindly asked the analyst for a copy of the repaired data and a copy of the EGDB output successfully generated.
解决办法
Determine features rejected using CopyFeatures to copy the FGDB union output to the EGDB. To fix the issue:
Identify the polygons that overlap (CheckGeometry on the FGDB union output identifies some) and edit the polygons manually so the boundaries meet correctly.
Use a copy of the data for this. After fixing the data Spatial Reference according to the instructions in ArcGIS Blog: Geoprocessing, Resolution, Tolerance, and Hair, use the Integrate tool to integrate the data (leave the XYTolerance parameter at its default). Run the Integrate tool on each individual input first (and maybe more than once on each. The boundaries that overlap move) and run Integrate on both at the same time. Use these integrated feature classes in the Union tool. The Union tool runs fine with the output set to an EGDB output.