topic Re: Does the Alias street name or alternate table need to include a shape? in Addressing Questions

Does the Alias street name or alternate table need to include a shape?

ChetShuler — Mon, 31 Aug 2020 16:53:29 GMT

I tried everything. I have a table with a common id field and can't get it work. Thinking about creating another centerline dataset to include the shape.

Re: Does the Alias street name or alternate table need to include a shape?

ShanaBritt — Tue, 01 Sep 2020 01:33:21 GMT

Chet:

If you are trying to create a locator that supports alternate street names, the street centerline feature class must include a shapefield and the alternate name table should have an objectid. Both the street centerline and alternate name table should have a common field that is used to join the data together.

What application and tool are you using to build the locator?

Re: Does the Alias street name or alternate table need to include a shape?

ChetShuler — Tue, 01 Sep 2020 12:13:02 GMT

Im using US Dual Range Address..

Yes I have an Object ID and ID fields in both datasets. Do the field names how to match? (Centerline field is ID and Alt Table is StreetID)

Also I'm using a table created by a consultant which is using all upper case characters in the Alt Table.

Re: Does the Alias street name or alternate table need to include a shape?

ShanaBritt — Wed, 02 Sep 2020 15:18:56 GMT

Chet:

The field names do not have to match. When you build the locator are you setting the JoinID to ID for the centerline and JoinID to StreetID for the alternate name table?

Are you building the locator in ArcMap or ArcGIS Pro?

One way you could test if the difference in case is making a difference is to join the alternate name table to the centerline layer based on the ID and StreetID fields. Then identify one of the streets that should have an alternate name to see if the joined data is displayed or just scroll to the end of the attribute table to see if the joined data is there. There should also be a validation button or check when performing the join.

Re: Does the Alias street name or alternate table need to include a shape?

ChetShuler — Wed, 02 Sep 2020 16:37:42 GMT

ArcMap

Join didn't work.. I have many to one.. The Relates shows all the aliases.. Is that the problem?

Re: Does the Alias street name or alternate table need to include a shape?

ShanaBritt — Thu, 03 Sep 2020 06:07:58 GMT

Chet:

Sorry I misspoke, the relate is what you needed to do in order to see that the aliases were linked to the street layer.

1. If you have access to ArcGIS Pro it would be interesting to see if you are successful with creating the locator with the alternate name table and the uppercase values.

2. If the values in the alternate name table are in the same case as the street centerline data does searching for alternate names with the locator work?

3. Does your alternate name table look similar to the images in this topic for alternate street name? Fundamentals of alternate name tables—ArcGIS Pro | Documentation

Re: Does the Alias street name or alternate table need to include a shape?

ChetShuler — Thu, 03 Sep 2020 14:29:07 GMT

I have the relates working.. But the geocoder will not locate using an alternate name.. I must have missed a setting or option somewhere.. yes the table looks similar..

The image shows Roosevelt as the primary street name.. And the alternate names listed below the Master Address Alt table.

Alternate table view below..

I'm going to try Pro if I can find the tools.

Re: Does the Alias street name or alternate table need to include a shape?

ChetShuler — Thu, 03 Sep 2020 15:27:33 GMT

Its not recognizing or searching the field with the alternate names.

Re: Does the Alias street name or alternate table need to include a shape?

ShanaBritt — Thu, 03 Sep 2020 15:45:33 GMT

Chet:

You can use the following topics to help with creating the locator. The locator created with the Create Locator tool in Pro cannot be used in ArcMap unless it has been published from Pro as a service. When in the Create Locator tool you will need to use the StreetAddress role and map ID from the centerline layer to StreetJoinID. Then expand the optional parameters to see the alternate name tables parameter and chose the alternate name table role of Alternate Street Name and set Street JoinID to StreetID in the alternate name table.

Create a locator—ArcGIS Pro | Documentation

Create Locator (Geocoding)—ArcGIS Pro | Documentation

See the preferred street name section of Additional tuning options—ArcGIS Pro | Documentation

-Shana

Re: Does the Alias street name or alternate table need to include a shape?

ChetShuler — Thu, 03 Sep 2020 16:29:59 GMT

Well may be a bit off topic but I got an error that usually isn't issue.. I have some line segments or outlying streets and median cuts without street names. It appears Pro doesn't like it?? If that's true I have some work to do to correct my original issue..

Re: Does the Alias street name or alternate table need to include a shape?

JoeBorgione — Thu, 03 Sep 2020 17:11:44 GMT

I've been watching this thread, and in Pro 2.6 I just used create locator for a street role with alt-names without any trouble. Not sure if I'm missing something in this post or not. Here in Utah we have both named streets and numbered streets. So we have S Main St or S 3305 E. However, each named street has a numeric equivalent. Sometimes, you never know what the address is going to come in as, the primary name or the numeric alternative. Here is a snapshot of my primary centerlines feature class as well as the alt names table:

If I enter 3565 S Mason Vista Way or 3565 S 7330 W, I get the same location.

Creating the alt names table is easy: I just select all those streets that have an Alpha name, and then export just those fields I need for the Numeric equivalent to a table. All of our streets have a UniqueID field so that is my join item:

Re: Does the Alias street name or alternate table need to include a shape?

ShanaBritt — Fri, 04 Sep 2020 00:49:12 GMT

Chet:

What was the error that you received?

-Shana

Re: Does the Alias street name or alternate table need to include a shape?

ChetShuler — Wed, 09 Sep 2020 11:45:15 GMT

For the alias table.. A required input calls for street name. This would be the aliases or alternate street name field??

It appears the missing street name is not fatal.. Its a data transfer error..

Sorry for the late reply.. Been out of town..

And I appreciate your help..

Re: Does the Alias street name or alternate table need to include a shape?

ShanaBritt — Wed, 09 Sep 2020 17:35:19 GMT

Chet:

The yellow messages are warnings and if you were using Pro 2.6 I believe that warning message would have a link to a help topic for more explanation, but it looks like an issue with the street data is causing an error with building the locator, not the warning about the empty value for one of the records. Run the Check Geometry tool on your data to see if there are any geometry errors. If there are multipart features or true curves in the data, the tool will fail to build the locator.

Which version of Pro are you using?

Re: Does the Alias street name or alternate table need to include a shape?

ChetShuler — Wed, 09 Sep 2020 17:49:39 GMT

The Check Geometry error now.. I have my centerline file in SQL. Its telling me I need a shapefile or Personnel GDB to run it..

I thought for sure I updated to 2.6.0...

Re: Does the Alias street name or alternate table need to include a shape?

ShanaBritt — Fri, 11 Sep 2020 16:03:50 GMT

Chet:

Since your data is in sde you won't be able to use the Check Geometry tool, you will have to use topology rules to check for the geometry errors that the tool looks for. If you have edit privileges or are able to edit a version of the data, you can check for multiple parts with the Must Be Single Part rule. This link also has a list of the rules for line features. If you upgrade to Pro 2.6.1 and run the Create Locator tool again with the same data, do you get a different error?

-Shana

Re: Does the Alias street name or alternate table need to include a shape?

ChetShuler — Wed, 16 Sep 2020 19:29:30 GMT

Sorry I been busy map making..

Today is a different day.. I finally got Pro to create a locator. What did I do different I have no idea. Other than I stored it to another location.. I'll test that again tomorrow.. However the results are not even close the actual address.. Also it accepted the alias names but I'm getting the same result. Actual address is not close. Also trying to locate the intersections using aliases will not return a result.. Hopefully I will have some free time tomorrow to review all the options.. But I'm getting closer ..

It's crazy been creating locators for 15 years.. I have no idea why I can get this to work..

Re: Does the Alias street name or alternate table need to include a shape?

ChetShuler — Wed, 16 Sep 2020 19:33:21 GMT

Thanks for sharing.. Yes I have some streets that are state routes that are numbered.. I'm going review my fields tomorrow.. I got side tracked with requests..

Thanks again..

Re: Does the Alias street name or alternate table need to include a shape?

ShanaBritt — Fri, 18 Sep 2020 07:45:25 GMT

Chet:

How far off are the address matches from where they should be?

Is your locator a single role or multirole locator?

There are some additional options that can be set that were added to ArcGIS Pro 2.6 for preferred names for city and street names, see Preferred street name for more details.

Re: Does the Alias street name or alternate table need to include a shape?

ChetShuler — Mon, 21 Sep 2020 18:44:36 GMT

I'm using the US Address Dual Range as a style. I did create a locator just using the Primary Table. Works just fine.

Centerline is my primary. ID is my join field,

Master_Address_ Alt is my Alternate Table. StreetID in Alt Join field and AltName is the name.

I enter 1510 Germantown Rd and get a correct return.

I enter 1510 SR 4 and get nothing. The null value is from another database with auto numbers the field.