laptop and a wrench

不具合

Joins unreliable when join field values approach 15 significant digits.

最後に公開された状態: August 25, 2014 ArcGIS for Desktop
不具合 ID 番号 NIM044921
送信されましたApril 30, 2009
最終更新日June 5, 2024
適用対象ArcGIS for Desktop
見つかったバージョン9.3
オペレーティング システムWindows OS
オペレーティング システムのバージョンXP
ステータスWill Not Be Addressed

参考情報

No Public Explanation

対処法

As a general rule, users should not base joins on doubles in File or Personal geodatabase as they are floating point. What you see in the table is an approximation of what’s on disk in binary. It may work, it may not work. There are various factors that will increase the likely hood of there being no match. Alternative workflows:• Base your join on text or integer fields• SQL Server (SDE) and SQL Server Express (available with Desktop – no SDE required) support fixed point (as opposed to floating point) number fields. That is, you can specify a scale and precision. This will allow joins on doubles to work.• I also got it to work in file or personal using the following workflow. As stated above, joins on doubles may or may not work. So, if you use this workflow, you will have to check the join results to make sure everything matched.• I trimmed the double values to just have three decimal places. Since the numbers are distances, I didn’t think this was a problem.o If I then perform the join with no attribute index present, I get 100% match. So, remove the attribute index from the feature class or table in the feature class properties in ArcCatalog. Also, when prompted to create an index when joining, select NO.o If I then perform the join and select the option to keep only matching records, I also get 100% match, with or without an attribute index present.

再現の手順

不具合 ID: NIM044921

ソフトウェア:

  • ArcGIS for Desktop

バグのステータスが変更されたときに通知を受け取る

Esri Support アプリのダウンロード

このトピックについてさらに調べる

ArcGIS エキスパートのサポートを受ける

テクニカル サポートへのお問い合わせ

Esri Support アプリのダウンロード

ダウンロード オプションに移動