Thanks for the help, but seeing as we're still running 9.3, I don't know if the bug fix you provided will work. I've started compiling a new composite geocoder from scratch and checking each individual locator as I go. I'll be sure to update as things progress.
Try the following thread. About half way down (posted on 2/09/11) I give a workaround to a bug that will be fixed at 10.0 SP3.http://forums.arcgis.com/threads/22064-New-geocoding-engine-is-terribleBrad
Currently I am trying to build a composite geocoder so that I do not have to run multiple locators and export .dbf tables of unmatched addresses for each. When I create the composite, the first (and most effective) locator does not work (does not produce any results). However, when I run them all individually, and in the same order as were specified in the composite, there is no issue. All I am trying to do is expedite the process as there are a lot of datasets that need geocoding. Any ideas on why the composite will not work when the individuals will? Any help or input is appreciated. Thanks!
サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか?無料アカウントを登録してください。
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.