Latest Contributions by ShanaBritt

Jack: Zip+4 is more granular than just 5 digit zip code. The additional 4 digit extension to the zip code represents a delivery area, a city block, a group of appartments, or PO Box for example within a 5 digit zip code region. If you are using the ArcGIS World Geocoding Service it allows you to include the zip code extension, which must be in a separate field from the 5 digit zip code.  ... View more

Joe: First I would use the US – Single House locator style instead of the SingleField style. You can still search using the full address field against the Single House locator, which has the grammar to handle the Utah street naming convention. The Single Field locator style does not have the same grammar and is more of a lookup or exact match type of locator, plus if you are using it as a geocode service, there is a memory for suggestions. -Shana ... View more

The custom single house unit locator you are referencing was created back at version 10.0 or 10.1 and shared on the forums and was not an official out of the box address locator style shipped with ArcGIS Desktop. The out of the box locator styles have changed since that custom single house with units locator style was created and the Single House Subaddress locator style that is included with ArcGIS 10.6.1 has different output fields that more mimic the output fields of the World Geocoding Service. You are correct that the output field names come from the locator style. Is the poor information that the vendor is referring to the field names or something else? ... View more

Cassandra: Based on my understanding of your data, without seeing its attributes, I'm suggesting the following options. If you use the Create Address Locator tool in ArcMap or Pro: A.Join attributes first in the reference data 1. Perform a spatial join or use the Identity tool (Advanced licence required) combine the attributes for the city ward polygons to the streets layer. 2. Use the results of step 1 to build a locator based on the Dual Range style and map the 'Additional Field' field from the locator style to the field in the reference data that contains the city ward names.  After the locator is created, you must open the locator properties > Outputs section and set 'Write user-specified additional output fields' to "Yes" in order for the field to show up in the geocode result.  3. When you geocode the address against this address locator the 'UserFld' in the geocode output will include the value that was mapped to the 'Additional Field'. You could only select Ward or Precincts not both in a single locator. B. Info about composites  1. Build a locator for the streets. 2. Build a locator based on the city ward polygons 3. Create a composite locator that contains the locators from steps 1&2. 4. The composite locator can be used to search for either a street address or a city ward. If the input is a street address that included a city ward (123 w main st, ward name)  an no match was found for the street address, the input would  fall back and match to the city ward locator for just the ward name. If you use the Create Locator tool in Pro:You could create a single locator that referenced multiple reference datasets (street lines:StreetAddress role, city ward polygons:City role, police precinct polygons:POI role) and add multiple additional fields that can reference fields from all three datasets (roles). When you geocode the address or use the Locate pane the additional fields that are mapped to each role will be returned for the input result that is matched to that address type. For example, if you only map fire district to the StreetAddress role as an additional output field and searched for the just the city ward, the fire district output field would not get included in the city ward match. In the scenario described above with the StreetAddress,City, and POI roles used to build a single locator you could search for a street address and the city ward info be included in the output; search for city ward; or police precinct. After building the single locator with the Create Locator tool you can open the locator properties and turn off output fields that you don't want in the geocode result. In the screenshot below is an example of the additional custom output fields I added to a locator that came from 2 of 3 reference datasets used to create the locator. The additional fields show up after ExtraInfo output field. The locator that you build in Pro will return suggestions in the Locate pane w/o needing to be published as a service and publishing as a service would be the only way that you could use the locator in ArcMap. You can use point or polygon data for postal codes, but we suggest using polygons to build the locator based on the Postal role to get the best reverse geocoding experience. Here are additional topics related to building locators with the Create Locator tool in Pro. Let me know if I missed any of your questions. Tips for preparing reference data—ArcGIS Pro | ArcGIS Desktop  Fundamentals of combining multiple locators into a composite locator—ArcGIS Pro | ArcGIS Desktop  ... View more