Retrieve Multiple Candidates with General Single Field Locator Type (v10)

[JoeBorgione]

I have a fairly extensive point feature class that is used instead of addresses for 9-1-1 dispatch.  So if some one calls in and says "I'm in the Acme Bank and it's getting robbed" all we need to do is type in Acme Bank and we'll get a hit.  For this I'm using a General Single Field locator.

However, if there are multiple "Acme Banks" all over the dispatch area, and I interactivley geocode "Acme Bank" I only get one returned.  Not all of them.  I'm hoping to get all of them; that way we can interogate the caller by asking " Are you at the one on Main St? or the one on Elm St? or the one on 2nd Ave?"

Is there a way to get this sort of behavior?

[JoeBorgione]

I have a fairly extensive point feature class that is used instead of addresses for 9-1-1 dispatch.  So if some one calls in and says "I'm in the Acme Bank and it's getting robbed" all we need to do is type in Acme Bank and we'll get a hit.  For this I'm using a General Single Field locator.

However, if there are multiple "Acme Banks" all over the dispatch area, and I interactivley geocode "Acme Bank" I only get one returned.  Not all of them.  I'm hoping to get all of them; that way we can interogate the caller by asking " Are you at the one on Main St? or the one on Elm St? or the one on 2nd Ave?"

Is there a way to get this sort of behavior?

Well here I am again answering my own post, and thanking Brad N at ESRI for his insight. 

If you use the Geocoding Tool bar to locate an address, (as I have been doing) it will only return one candidate.  However, if you use the actual FIND TOOL (the Binos) (as I WILL be doing) you'll get the entire list.

[NianweiLiu]

However, if you use the actual FIND TOOL (the Binos) (as I WILL be doing) you'll get the entire list.

I have a similar situation but I am not getting multiple candidates either even on the find tool.
I have  a parcel layer and I am trying to use single field on parcel id to create a locator. It's has parcel 2 id fields with 1-n relationship, one is polygon id(1), another is tax id (N) and the layer is joined with both id in the attributes. In a condo case, there will be multiple records with same poly id but different tax id.

I tried different combinations including using one id as key and the other as alternate name, or alias table, so the user can enter either polygon id or tax id to get a location. It works, but the problem is that it does not return multiple candidates when the polygon id is entered. It only returns one, and seems randomly pick one out of the list. For example, there is a parcel polygon id ABC, and it related to 2 tax id A01 and A02. When user enters ABC, it should return both as candidate, but it only returns one with score 100.

I have altered using either one as key field, but get basically same result.

Maybe I should instruct the locator return multiple candidates even it's score as 100? How?

[JoeBorgione]

I have a similar situation but I am not getting multiple candidates either even on the find tool.
I have  a parcel layer and I am trying to use single field on parcel id to create a locator. It's has parcel 2 id fields with 1-n relationship, one is polygon id(1), another is tax id (N) and the layer is joined with both id in the attributes. In a condo case, there will be multiple records with same poly id but different tax id.

I tried different combinations including using one id as key and the other as alternate name, or alias table, so the user can enter either polygon id or tax id to get a location. It works, but the problem is that it does not return multiple candidates when the polygon id is entered. It only returns one, and seems randomly pick one out of the list. For example, there is a parcel polygon id ABC, and it related to 2 tax id A01 and A02. When user enters ABC, it should return both as candidate, but it only returns one with score 100.

I have altered using either one as key field, but get basically same result.

Maybe I should instruct the locator return multiple candidates even it's score as 100? How?

That sounds just like what was happening to me.  I hate to sound like a parrot, but do you have sp3 AND the specific Geocoding Patch for it installed?

Let me see if I have this right:

Your primary table is your Parcel Feature class with the Parcel ID as the key field.
Your alternate table is the Tax ID table
Your joinitem is the Parcel ID

I think that v10 creates an index for the join item in both primary and alt names, but to be sure, you could create your own index for them.  One thing that I had a problem with as well was making sure I mapped all the fields correctly.  Staring at points, lines and polygons on a screen for the past 20+ years is beginning to take it's toll on my eyes!

Hope this helps-

[NianweiLiu]

Yes I do have Sp3 and the "ArcGIS 10.0 SP3 (Desktop, Engine, Server) Geocoding General Maintenance Patch " installed. In fact I am a little bit suspicious one of them actually caused some other problem, because the new  %ArcGIS%\Locators\USAddress.lot.xml template shows version 10.1 (revision 91 as of 09/08/2011), which is ahead of other templates as well as ArcGIS itself.

The field you listed is one of the combinations I tried. My ideal configuration is actually to use a pre-joined spatial view as primary because I want to take advantage of the "user_fld", which is a derived column out of the tax table. I have also tried use objectid to join the alternative table because the view was produced out of same objectid column.

Anyway, it's not a huge deal because all those record would have same location coordinates. It's just nice to know that there are multiple tax records on the same location immediately from the locator result.