topic Re: Geocoding help in ArcGIS Pro Questions

Geocoding help

BrianBulla — Fri, 16 Feb 2018 21:05:16 GMT

Hi,

Just looking for some clarification on how geocoding works in Pro. I have created a Geocoder based on a point layer of address points. It seems to be working as desired when I type addresses into the 'Locate' window. But when I use the same locator in the Geocode Addresses Geoprocessing tool, the exact same address that I type in the Locate window comes up as 'U' - unmatched.

All of my settings in the Geocoder are set to default. All I did was specify which fields to use for Number, Road Type, etc.

Also, the list of addresses I am geocoding is actually the table of addresses that make up the point layer the geocoder is based on. So I would think I would get a 100% match rate, but I am not.

Any advice on how to tweak my geocoder is appreciated.

Thanks!

Re: Geocoding help

ShanaBritt — Thu, 22 Feb 2018 20:13:09 GMT

Brian:

Are you able to share a screenshot of the table you used as input in the Geocode Addresses tool or the address locator?

If the table contains the 'Shape' field it should be removed from the table. The street address (380 new york street) should also be in a single field and city, state, zip in their own respective fields or the full address (380 new york st, redlands, ca) in a single field in the table.

-Shana

Re: Geocoding help

JoeBorgione — Thu, 22 Feb 2018 20:24:23 GMT

I haven't yet worked in pro; just wondering if the default settings in it include MATCH WITHOUT ZONE = FALSE like in ArcGIS desktop 10.5.1.

Brian Bulla, does your data include city, zip and state?

Re: Geocoding help

BrianBulla — Thu, 22 Feb 2018 20:34:35 GMT

Hi Shana,

The table is just a table (.xls to be exact), so there is no 'Shape' field. The screenshot below shows you my settings for the Geocoder.

After tweaking the settings I was able to get a much better match score, but there were always a few that would never match. I have circled one of the addresses that would never match. As you can see in the next screenshot, the address that won't geocode through the 'Geocode Addresses' tool can be found when using the 'Locate', both using the same geocoder.

Re: Geocoding help

BrianBulla — Thu, 22 Feb 2018 20:42:48 GMT

No. I am using a single field with the street address and the city name. It is a custom geocoder based on address points that are local to us. I would expect to get a 100% match since the addresses I am trying to geocode are exactly the same as those the geocoder is based on.

Re: Geocoding help

ShanaBritt — Wed, 07 Mar 2018 16:32:29 GMT

Joe, The Match without zone property is the same for Pro. The US Address and General styles are essentially the same in Pro as in ArcMap. There may be times where the Pro version of the style template might be more current than the style included with ArcMap because of the development and release cycle of Pro.

Re: Geocoding help

ShanaBritt — Wed, 07 Mar 2018 16:38:30 GMT

Brian,

It would be more helpful if you could provide the locator you created or a screen shot of the Durham locator properties Reference data tables page like the one below and the 'About the locator' page from the properties. You could create a locator package if you wanted to share it here or send it to me in private message.

Re: Geocoding help

BrianBulla — Fri, 16 Mar 2018 17:35:04 GMT

Hi Shana,

Sorry for the delayed response. This is my first day back in the office since attending the Dev Summit. I have attached the locator.

Re: Geocoding help

ShanaBritt — Thu, 22 Mar 2018 16:34:12 GMT

Brian,

For the address that is circled in the screenshot is the street type in the field "CL" or "ci"? I think the value is an uppercase "i" versus a lowercase "L" , which is shown in the locate pane. I created a table with the address in question and found that "jaywin ci" doesn't match in either the table when batch geocoding or in the Locate pane.

Re: Geocoding help

BrianBulla — Thu, 22 Mar 2018 17:34:08 GMT

Hi Shana,

It is a lowercase 'L' (l). Here are a couple more screenshots to show you what is happening.

The labelled point layer of addresses is the layer I created the Geocoder from. As you can see "1625 Jaywin Circle" is a valid address as it exists in the point layer, but when I type it in the Locate toolbar, it does not get a match with my custom Geocoder.

But....when I type the address in as "1625 Jaywin Cl" it does get a match. A few times a year I geocode addresses that get typed into a database, so I need a geocoder that gets as many matches as possible to avoid too much manual coding of points. I just don't understand how the coder is not matching addresses like this, that seem to be typed in properly.

Here are some of the settings from the Geocoder. From the fields I use I should be getting a match regardless of using 'Circle' or 'Cl', since I have both those fields defined.

And here are the attributes for this particular address, from the point file the Geocoder references:

I'm a bit confused as to why it doesn't work. This Geocoder is definitely working better than anything I ever tried in ArcMap, but still in ArcPro I would like it to work even better still.

Thanks. If you have any other ideas, please let me know.

Re: Geocoding help

BrianBulla1 — Mon, 16 Apr 2018 18:41:27 GMT

Hi sbritt-esristaff‌. Just wondering if there are any updates to this thread you were helping me out with?

On my end, I have rebuilt my geocoder but I'm still having the same issue as before where it will find 'Jaywin Cl' but not 'Jaywin Circle'.

If there is anything you'd like me to try, just let me know.

Thanks,

Re: Geocoding help

ShanaBritt — Tue, 17 Apr 2018 17:31:07 GMT

Brian:

I apologize for the delay, I've been working to meet some deadlines for Pro development and haven't been able to circle back to this issue. I have an idea I need to test out and will try to get a response to you this week. What I believe is happening is that the abbreviation you are using for 'Circle' in the reference data is not part of the logic in the locator style, so it doesn't know what to do with it.

A quick note about the field mapping of the locator in your most recent screen shot...

The 'Full Street Name' locator field is not used for address matching, so it is not necessary for it to be mapped to a field in your reference data. The content of the field when mapped is written to the geocode result for labeling if needed. You have a few options for field mapping based on the fields in your reference data. If the "ROAD_FULL" field in the reference data contains all of the street components, it can be mapped to the 'Street Name' field from the locator with no other components mapped (directions, prefix type, suffix type), then map the zone fields like city, state, zip code. If using the US Addresses - Single House Subaddress map "ROAD_FULL" to 'Street Name' and the "UNIT TYPE" and "UNIT NUMBER" fields to 'SubAddr Type' and 'SubAddr Unit'. In the existing locator properties, you could also use the "ROAD TYPE FULL" field to map to 'Suffix Type'.

-Shana

Re: Geocoding help

BrianBulla — Wed, 18 Apr 2018 12:27:17 GMT

Hi Shana Britt,

Thanks for the information. Currently I am experimenting with both US Address - Single House as well as Single House Subaddress.

With our Civic Number, we sometimes have a Civic Number Suffix. So there could be a 234 Mackenzie Ave as well as a 234A Mackenzie Ave. Is there a field-mapping in the Single House Subaddress I can use for this?? Currently neither of the styles mentioned above are catching these addresses with a suffix on the Civic Number.

Also, when using the Subaddress style locator you mentioned to map ROAD_FULL to StreetName, but in the Subaddress mapping there is a FullStreetName mapping so I have done it there. Should I switch it to map to StreetName??

Thanks,

Re: Geocoding help

ShanaBritt — Fri, 15 Jun 2018 16:51:31 GMT

Brian,

Sorry for the delayed response, I've been busy with finishing up certifying the next release of ArcGIS Desktop and needed to mock up some of the data based on your screen shots to determine what was wrong and how to fix it.

1. The reason "1625 Jaywin Circle" didn't match was because of the fields you used for field mapping when building the address locator, which was based on the 'TYPE_SHORT' field. This field contained and abbreviation ('Cl') for "Circle" that was not part of the street suffix type aliases grammar in the address locator style.Aliases provide a mechanism to support word substitution beyond what is provided by spelling substitution. Whichever alias form is found in the reference or input data is treated as equivalent. Below is the alias section for Circle in the grammar for the address locator style which does not include 'Cl'. If you had used 'ROAD_TYPE_FULL' field when building the locator searching for "1625 Jaywin Circle" would have found a match in the Locate pane.

Before:

<def name="_ST_Circle" is_alias_list="true">
<alt>Circle</alt>
<alt>Cir</alt>
<alt>Ci</alt>
<alt>Circulo</alt>
<alt>Circ</alt>
<alt>Circl</alt>
<alt>Corcle</alt>
<alt>Cr</alt>
<alt>Crcl</alt>
<alt>Crcle</alt>
<alt>Crl</alt>
</def>

If you use this article as a guide, you can modify the address locator template to add the 'Cl' abbreviation to the Circle street suffix type to look like the following.How To: Add city aliases to the address locator style

At step 2 in the article search for "suf_type_ext" then scroll down or search for "Circle" until you get to the section I referenced above. After modifying the USAddress.lot.xml recreate the address locator and you should be able to get matches in the Locate pane and when geocoding the table if the street suffix type in the input address is 'Circle' or 'Cl'.

After:

<def name="_ST_Circle" is_alias_list="true">
<alt>Circle</alt>
<alt>Cir</alt>
<alt>Ci</alt>
<alt>Circulo</alt>
<alt>Circ</alt>
<alt>Circl</alt>

<alt>Cl</alt>
<alt>Corcle</alt>
<alt>Cr</alt>
<alt>Crcl</alt>
<alt>Crcle</alt>
<alt>Crl</alt>
</def>

2. Here are some screen shots to clarify my previous explanation about which fields in the reference data in your screenshots that could be used for building the locator. It is not required to map Full Street Name in order to get matches when geocoding, it is only used as an output field when batch geocoding. It's there to use for labeling if you did not had a field that could be used for labeling the geocoded point.

Mock data:

----------------

Possible field mappings:

---------------------------------

3. To handle the house number suffix when using the US Address - Singlehouse Subaddress style to build a locator, concatenate the house number, house number suffix and/or house number prefix in a single field and use the new field to map to House Number when building the locator. See the difference in the mock data example for FULL_CIVIC_NUM and this example includes FULL_CIVIC_NUM.

Results based on the locator field mappings above:

---------------------------------------------------------------------

Re: Geocoding help

BrianBulla — Thu, 21 Jun 2018 13:34:14 GMT

Hi Shana Britt‌

Sorry for the delay getting back to you. I have just done some more testing and for some reason everything is working now. Jaywin Cl and Jaywin Circle are both being found with the locator. Of course, I think my locator has been modified somewhat since the one we started looking at when I first created this post. Perhaps even the latest ArcPro update has made an impact??

Anyways, I do have it working now. I'll test things a bit more and see if I can tweak it based on your suggestions.

Thanks!!