Latest Contributions by ShanaBritt

Joe: What you have is the correct schema for creating a PointAddress locator that supports subaddresses. When building the locator in the Create Locator tool assign UNIT_DESIG to the 'Unit' locator role field and UnitType to the 'Unit Type' locator role field in the Field Mapping. Is the reference data to build the locator in a file gdb or SDE? If there is an address id for the base address that links to the subaddresses, it would be good to assign that field to the Address Join ID locator role field in Field Mapping. ... View more

In looking at the data in the screenshot you provided and seeing that the Check and Repair Geometry tools had no affect on being able to build the locator with the Create Locator tool, I suspect that there are true curves or arcs in the centerline file, perhaps a cul-de-sac, that is causing the failure. Since curves are only supported in geodatabases, exporting the feature class to a shapefile simplifies the problematic features. You can also run the Densify tool with the Offset Densification Method to simplify the lines. I would also check for any multipart features that may need to be exploded using the Multipart to Singlepart tool, then use the new feature class to build the locator.  Run either the Add Geometry Attributes or Calculate Geometry Attributes tool to add the 'Number of parts' Geometry Property to the reference data. A feature with more than one part is considered a multipart feature. Note: The tools add a new field named 'PART_COUNT' to the Input Features of the tools. ... View more

I would agree with Joe in suggesting to use the Create Locator tool in ArcGIS Pro 2.3.3 to create a locator based on the Point Address role to build your locator with the 2.8M features. These locators are supported on ArcGIS Server 10.6.1 or later. There are a couple of geocoding patches for ArcGIS Server (Enterprise) 10.6.1 and 10.7. Regardless of the tool used to create the locator, when creating a locator with reference data that contains millions of features, it is necessary to have at least 3 to 4 times the size of the data in free disk space on the drive containing your temp directory because files used to build the locator are written to this location before the locator is copied to the output location. If you do not have enough disk space, the tool will fail at some point during execution when it runs out of space. Also, keep in mind that when creating very large locators, you should have a machine with enough RAM to handle large memory-intensive processes. When you created the locator with the Create Address Locator tool using the US Address - Single House Subaddress locator style did you have suggestions enabled? If it was enabled and you disable it, does the time it takes to build the locator improve? ... View more

Kimberly: I'd like to better understand the problem you are encountering. What is the error you receive? Which tool was used to create the locator you have published? Are you using the Rematch Addresses geoproessing tool or the Rematch Addresses pane? If you created the locator with the Create Locator tool, it is possible to turn off any fields you do not want in the feature class of the geocode result. This can be found in the Locator Properties on the Output fields page. Once you have modified the original locator you can overwrite the existing service using one of the following steps in ArcGIS Pro 2.5: Overwrite a locator—ArcGIS Pro | Documentation  Overwrite a geocode service—ArcGIS Pro | Documentation  ... View more

Tommy: I would suggest using the search all layers and all fields option in the Locate pane that does not require you to configure the fields you want to search for each layer in the project. Find places on the map—ArcGIS Pro | Documentation The steps found at this link are for ArcGIS Pro 2.5, if you have an earlier version search for the same topic name in the installed help as the design and functionality available is different in previous versions. ... View more

In ArcGIS Pro 2.5 it is possible to build your own locator with your own data using the Create Locator tool for the following countries using locator roles. Additional countries will be added and supported in future releases. ASM —American Samoa AUS —Australia AUT —Austria CAN —Canada DEU —Germany ESP —Spain FRA —France GBR —Great Britain GUM —Guam MNP —Northern Mariana Islands PRI —Puerto Rico VIR —U.S. Virgin Islands USA —United States UMI — Minor Outlying Islands of the United States You also have the ability to create multirole and multicountry locators with the Create Locator tool. If you have the 3-character country code and 3-character language code value defined in the reference data for each feature, select the <As defined in data> option for the Country or Region parameter and Language Code parameter. Then assign the fields from the reference data to the Country Code and Language Code locator role fields in the Field Mapping. ... View more

Josh: Currently there is no way to adjust any of the locator properties that you see in the Locator Properties dialog in ArcGIS Pro via Python. However, we are looking into adding support for modifying properties via Python for an upcoming release. It is possible to modify that properties manually in the *.loc file of the locator, but it is discouraged and not supported. ... View more

Joe: I was able to find my response from the old thread, turns out it was moved over to the current forum system. It sounds like you are still  using ArcMap or are creating classic locators in ArcGIS Pro with the Create Address Locator tool. My response was geared to the classic locators, but the same info about creating a locator with an administrative zone (city, state, postal, neighborhood, community) applies to the new locators built with the Create Locator tool.  It is strongly recommended that administrative zones are mapped when building a locator. Region and region abbreviation are also important because they are used to help create different forms of state highways that are specific to each region or state. Not mapping them can impact geocoding quality and the performance. Here are links to the last few explanations I provided about the 'match with no zones' property that answers why true ('yes') was never made the default: https://community.esri.com/message/56300#comment-270455  https://community.esri.com/message/56300#comment-270458    ... View more

The Address Inspector tool is new for ArcGIS Pro 2.5. Holding the C key while the tool is active allows you to temporarily navigate in the map while using the tool. Identify addresses and places on the map—ArcGIS Pro | Documentation  ... View more

George: Besides the side offset, what are the other locator properties for the classic locators that you used heavily when building and fine tuning your locators? What type of issues were you trying to solve by modifying the properties of the classic locators that still needs solving using the new locators created in ArcGIS Pro with the Create Locator tool? In the classic locator properties screenshot above in the Outputs section, those properties that are set as 'Yes' can be found on the Output fields page of the properties dialog of the new locators. Most of the properties in the Geocoding Options section of the classic locator properties are available for the new locators and some do not apply to the new locators. -Shana ... View more

Joel: The behavior you are experiencing is a known issue, BUG-000114925 that I have found to work under certain circumstances. If the feature class and table joined to it are in the same geodatabase. If the shapefile and table joined to it are in the same workspace. Have you tried your join scenario using the Layer Search tab of the Locate pane to search in all fields of the layers in the map? Are you using the configured layer workflow outside of ArcGIS Pro? ... View more

Josh: Yes, when registering the folder that contains the locator as a data store with the Server, the locator is not copied to the server. When you click the Analyze button on the Share Locator or Publish Geocode Service panes you should not get a warning that the locator will be copied to the server. ... View more

Gregg: Here are some details to be aware of when migrating from classic locators to new locators. New locators are built with the Create Locator tool in ArcGIS Pro. How to create a new locator It is recommended to create locators with administrative zones such as city, state, postal assigned in the field mapping. Region and region abbreviation are also important because they are used to help create different forms of state highways that are specific to each region or state.  Not mapping them can impact geocoding quality and the performance. All address elements should be broken up across multiple fields. It is recommended to use polygons instead of point geometry when building a locator for administrative areas or when building a multirole locator that allows you to search for multiple locations with a single locator like street addresses, points of interest, parcels, and postal codes. Polygons also help to provide better reverse geocoding results. https://pro.arcgis.com/en/pro-app/help/data/geocoding/benefits-of-using-polygons-versus-points-for-areas.htm Can be used in ArcMap when published as a service from ArcGIS Pro to ArcGIS Server or Enterprise 10.6.1 or newer. If Enterprise portal, then Share Locator. If stand-alone (not federated) ArcGIS Server, then Publish Geocode Service. Registering the folder that contains the locator as a data store with ArcGIS Server (federated/non-federated) before publishing the locator will help to reduce downtown when updating the service. Locators are built using locator roles instead of locator styles, an explanation of the locator role fields can be found here https://pro.arcgis.com/en/pro-app/help/data/geocoding/locator-role-fields.htm. A single multirole locator should be created instead of a composite locator in most cases. Suggestions validate the house number against the reference data. Suggestions are available for locators stored locally in the Locate pane in ArcGIS Pro as well as published as a service. Custom output fields can be easily added to the locator you create that reference other fields in the reference data used to build the locator that you want returned in the geocode results, such as fire districts, school districts, or voting districts. Output fields can be turned off and on in the locator properties to reduce the number of fields returned in the geocode result when batch geocoding. Locators that support multiple countries and languages can be created. ... View more

Josh: Is your goal to overwrite or update an existing locator service with as little downtime? Which version of ArcGIS Pro are you using? When the locator was shared to portal did you use a data store or was it just copied? The location of the locator depends on whether you used a data store or not. If a data store was not used the locator can be found here: .GeocodeServer\extracted\v101 -Shana ... View more

Yener: Geocoding is always going to return a point result. Where are you using the locator? If you are using ArcGIS Pro, have you tried configured layer search in the Locate pane or searching all layers in the map using the Locate pane?  -Shana ... View more