Each feature in the primary reference data represents a street segment with two ranges of addresses that fall along that street segment, one for each side of the street. This alternate name table role can be used when the primary locator role is Street Address. The Alternate House Range role allows you to create locators for street addresses that have alternate house number ranges, such as when the range values may be different on both sides of the street segment when the street is extended into a new development. Optionally, you can specify fields that contain the parity and language code. It must also have an address join field that contains an ID that can be used to link to the primary reference data by mapping the Address Join ID field from both the primary and alternate name table roles. To use an alternate name table for a locator with the Alternate House Number role, it must have either an individual field that contains the house number or individual fields that contain From house number and To house number information for the address point. Each address you want to search must be present in the primary reference data and alternate name table. This alternate name table role can be used with the primary locator role is Point Address. For example, the primary address point feature class contains the native language house numbers, such as 2Б or 4Г, and the alternate name table contains the transliterated house numbers, such as 2B or 4G. The Alternate House Number role allows you to create locators for addresses that have alternate house numbers or alternate house number ranges, such as a when you want to model English transliteration of Cyrillic house numbers. Roles can be used to geocode an address based on the alternate name for the primary features.Īdministrative areas lower than Subregion The following table shows the alternate name table roles and the ID fields that are used to link to the supported primary locator roles provided with ArcGIS Pro.

Setting the Street Join ID from the primary locator role to the field in the primary reference data that corresponds to the join ID in the Alternate Street Name role will pull in alternate names for all corresponding records. Street Address primary locator role is commonly used to model addresses along street segments, but the street name for the addresses may have alternate names. When building a locator that uses an alternate name table role, an ID field for the corresponding field value in both the primary reference data and alternate name table is required. Once created, a locator contains a snapshot of the primary reference data and alternate name table that is used for geocoding, as well as indexes and local addressing knowledge that help return the best match during the geocoding process. The alternate name table role provides the appropriate fields that should be used when building the locator to support alternate names. An alternate name table role can be used in conjunction with the primary locator role to build a locator that allows you to search against features in the primary reference data that is referenced by more than one name in the alternate name table. This is done by choosing the locator role that fits your data. The first step to building a locator is defining what type of data you have with which to build it.

Alternote tables