Latest Contributions by ShanaBritt

Kyle: Are you using ArcMap or ArcGIS Pro? Which version? Will the locator be used in a web app? What is happening with the locator that you have already created? -Shana ... View more

Joe: Whenever you access a locator from a network drive or write results out to a network drive, the performance is going to be slower than when the locator is accessed locally and the results are written out locally when geocoding or processing any data. If the locator only lives on the network drive, try saving the locator as a locator package that is stored on the network drive for others in the organization to copy locally or just add to the project and it will get extracted locally. Here are the best practices for getting the best batch geocoding performance using a local locator on your desktop. Use the latest version of ArcGIS Pro. Use locators created with the Create Locator tool In most cases it is best to create a multirole locator over a composite locator. See Combine multiple data layers into a single locator—ArcGIS Pro | Documentation for more details about multirole locators. Set the number of threads that the locator will use on the machine where the geocoding job will run. Open the Task Manager to determine the number of available cores there are on the machine. Set the number of threads property to Auto, which is one less than the number of cores on the machine. Store the locator and the table to be geocoded on a SSD drive or the fastest drive on the system. Publish the locator as a service and use the service for geocoding. This is the best way to share the locator within an organization. If the locator is published to an ArcGIS Enterprise portal, configure the service to use multiple threads. If there is a portal locator that is not available on the portal, ask your portal administrator to add the locator as a portal utility service, and configure the locator for batch geocoding. ... View more

David: ArcGIS Pro 2.5 is available now. If you are able to install 2.5, run through your workflow again to see if you get the same behavior. It would be great for us to have specific steps and data (table, locator) to further investigate these types of issues so that we can fix them. Did you encounter this behavior with a locator created with the Create Address Locator tool, Create Locator tool, or the ArcGIS World Geocoding Service? -Shana ... View more

Matthew: This issue has only been addressed in ArcGIS Pro with the new locators built with the Create Locator tool. Do you need to use the locator in only ArcMap or also in ArcGIS Server? If you have ArcGIS Server 10.7+ I would suggest creating the locator with the Create Locator tool in ArcGIS Pro and use ArcGIS Pro 2.4+ to publish the locator to ArcGIS Server. The service can be used in ArcMap, but the local version of the locator cannot. -Shana ... View more

I can get this to work as described in the help using a locator created with the Create Address Locator tool in the Find tool and Geocoding toolbar. Unfortunately, batch geocoding a table is not working with the latest versions of ArcMap. If this is functionality that you need I'd suggest either submitting an Enhancement request through Tech Support or add an ArcGIS Idea. ... View more

Kristie: The following technical articles most closely describe how to make the change you are looking for in the *.loc.xml of the locator built with the Create Address Locator tool. You would want to search for the "Suffix types" section and add 'PW' to the list of aliases for Parkway if you want that abbreviation recognized. We do not recommend modifying the the xml of the locator, but if you do, Tech Support wouldn't be able to provide help in maintaining the customized locator. How To: Add a custom highway to the address locator style  How To: Add city aliases to the address locator style  Given that you are transitioning to ArcGIS Pro, I would suggesting building the locator with your existing data using the Create Locator tool using the StreetAddress role to see if that resolves the issue. The locator created with the Create Locator tool in ArcGIS Pro cannot be used in ArcMap unless it has been published as a service from ArcGIS Pro. -Shana ... View more

Michael: Modifying the us_addr.cls was a file that you could modify for street types for locators created prior to ArcMap 10.0 and in ArcView GIS 3.x, so modifying the us_addr.cls would have no affect on a locator built using ArcMap 10.0 or later, or any version of ArcGIS Pro. The technical article referenced in the original post was for ArcView GIS 3.x. ... View more

Asad: What you are attempting to do cannot be done with the ArcGIS World Geocoding Service, as it does not support the same spatial offset capabilities that are described in About finding an address—Help | ArcGIS Desktop . ... View more

Does searching with the spatial offset work for you in the Find tool or Geocoding Toolbar in ArcMap or the Locate pane in ArcGIS Pro when using a locator you created with the Create Address Locator tool, but does not work when batch geocoding a table? ... View more

Joe: I was going to try and recreate the data by hopefully looking at the attributes of the data that was used to build the locator. Are you expecting the match result to include both the city and the metro area? Or the address could be in either the city or the metro area? Is the metro area an alternative to the city name? If so, you could try adding an alternate name table for City using the Alternate City Name alternate name table role. (I know, it’s a mouth full). -Shana ... View more

Joe, do you have a small sample of what the street data looks like? It would help to better understand the problem and your expectations. ... View more

Kevin: I would check the geometry type (shape field) of the street centerline and parcel data to see if it is Z or M or ZM as there are a few bugs related to locators created with the Create Address Locator tool when if the reference data contains bad M extents the features do not show on the map or you cannot zoom to the matched results on the map if the output is saved to a geodatabase. In some cases saving the output to a shapefile resolves the problem, but in other cases removing the M values from the reference data feature class and rebuilding the locator with the M values removed solves the problem. http://support.esri.com/en/knowledgebase/techarticles/detail/35818 I would also check the coordinate system of the reference data for each of the locators participating in the composite and if the same behavior occurs with the individual locators (Street Centerline, Parcel APN, Historical Parcel APN) by themselves. Given the data you described I would create a multirole locator using the Create Locator tool in ArcGIS Pro 2.3+ using the following roles. The multirole locator will use the coordinate system of the reference data first in the list of primary tables PointAddress for Full Address (points) StreetAddress for Street Centerline POI for Parcel APN Map the APN to the Place Name locator role field Include an alternate name table of the historical parcel APN Use a JoinID to link the primary parcel data and historical parcel data together and map it to the Place Join ID field for the POI role and Alternate POI Name alternate name table role. ... View more

Kyle: I don't see anything in comment you linked to that would lead me to believe the new locators and composite locators are unusable. Could you elaborate on your comment? I would definitely recommend using a multirole locator created with the Create Locator tool over a composite locator, but in a few instances you might find the need for a composite locator. ... View more