Latest Contributions by ShanaBritt

@JustinMartinek Is there something that is not working with the locators you create with the Create Locator tool in ArcGIS Pro that requires customization? ... View more

@BlakeTerhune , I created a locator in Pro 2.8.2 using data similar to what you have described and was able to search for a hyphenated unit successfully. I did not use the ADDRUNTTYP field in the screenshot below when building the locator. Are you not getting matches with the local locator or when it's published as a service or both? ShanaBritt_0-1632875659182.png   ... View more

@BrianBulla  You can also open the locator properties of the ADDR_Durham_Pro locator in ArcGIS Pro to tell which tool created the locator when looking at the About the locator page of the Locator Properties dialog. If the 'Release' property is 2.3 or later and lists the 'Supported roles', it was created with the Create Locator or Create Feature Locator tool. If there is a reference to the address locator style or  version that is 10.x, it was created with Create Address Locator tool that was deprecated from Pro at the 2.6 release. I would expect to get candidates returned for the address '930 Byron Street' if the street direction is missing from the input. Are you still encountering this problem? ... View more

Brian: 1. Are you using the same locator in ArcMap that you are using in Pro? 2. What are the supported categories that are enabled in the locator properties of the Addr_Durham_Pro locator if it was created with the Create Locator tool? 3. I noticed that the candidates returned in ArcMap have an addr_type of Subaddress, but the input address is just <house number> + <street name> + <city>.  Are any candidates returned for '930 Byron Street, Town of Whitby' when enter in the Locate pane search box from your locator or the ArcGIS World Geocoding Service? 4. You would need to check that you have batch geocoding privileges in your organization to use ArcGIS World Geocoding Service, otherwise you would only be able to do geosearch or place finding (not batch). This would explain why you can see it and use it in the Locate pane, but not in any geocoding tools.  ... View more

Ingrid: 1. Are you able to provide a screenshot of the field mapping of the multirole locator you have created, I'd like to check the field mapping. 2. When you create a locator w/o any administrative zones the  'Match with no zone' property is set to 'Yes' by default and this is the recommended setting when building a locator without zone. 3. I am curious to know what the match level is of the candidate that is returned in the Locate pane. Right-click the result and select Show Details and check the Addr_type field. The following topic describes the values that are returned in the Addr_type field, https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/what-is-included-in-the-geocoded-results-.htm.  ... View more

Felix, What country or countries are you creating the locator for that has an address format of  <street_name + street_num> <village_name + village_num > <house_name+house_num> ? ... View more

Felix: The reference data used to build the locator in the Create Locator tool must use the three-character language code. Language is used to help format the output label where more than one language can be used in a country to represent addresses, as well as to identify where to apply language-specific geocoding logic to the reference data when building a locator. If language is included in the primary reference data used to build the locator, you can search for addresses or locations in the same country or region using multiple languages.   There is a screenshot of what the data should look like in the Create multicountry locators using country and language topic. ... View more

Ingrid: I would be helpful to get more details about your locator and the addresses being geocoded in the table. I have geocoded 12.5M records in a table with the Geocode Addresses tool in ArcGIS Pro, so I do not believe the number of records in your table is the issue. 1. What version of ArcGIS Pro are you using? 2. Was the locator built with any administrative zones (city, state, zip, neighborhood) mapped? 3. What is the 'Match with no zone' property set to in the locator properties? 4. Does the input address in the table include an administrative zone (380 New York St, Redlands, CA) or is it just <house number> + <street name> (380 New York St) ? ... View more

Given the data illustrated above, if you build the locator where you map Building to the Building Unit locator role field and Unit to the Unit locator role field you would be able to search for the following with the best results returned when an indicator is included, otherwise, the address is matched to the record in the data that returns the highest score: - 345 W Some Bl #A > 345 W Some Bl, Building A = Match_addr - 345 W Some Bl #1 > 345 W Some Blvd, #1 = Match_addr - 345 W Some Bl #A1 > 345 W Some Bl,  #1, Building A = Match_addr - 345 W Some Bl, A > 345 W Some Bl, Building A = Match_addr - 345 W Some Bl,1 > 345 W Some Blvd, #1 = Match_addr - 345 W Some Bl, A1 > 345 W Some Bl,  #1, Building A = Match_addr If you build the locator where you map the BuildingUnit field to the Unit locator role field you will be required to enter the subunit value with a unit indicator before the value in order to get a match. If you dropped '#' from the value in the BuildingUnit field, then mapped it to the Unit locator role field you would be able to search for the subunit with or without the indicator. We've added an option to allow subaddress suggestions before the entire unit value has been entered.  Typing in the unit type, such as Apt, Unit, Suite, # is also optional. The locator will need to be created in Pro 2.9 and published to ArcGIS Enterprise 10.9.1. This new option, Suggestions for partial subaddresses, is disabled by default but can be enabled, as well as configure the number of suggestions returned, in the Locator Properties Dialog. If you are part of the Early Adopter Community or have access to ArcGIS Pro 2.9 Beta1  you can test out the functionality and provide any feedback. ShanaBritt_0-1632808600367.png   ... View more

We've added an option to allow subaddress suggestions before the entire unit value has been entered.  Typing in the unit type, such as Apt, Unit, Suite, # is also optional. The locator will need to be created in Pro 2.9 and published to ArcGIS Enterprise 10.9.1. This new option, Suggestions for partial subaddresses, is disabled by default but can be enabled, as well as configure the number of suggestions returned, in the Locator Properties Dialog. If you are part of the Early Adopter Community or have access to ArcGIS Pro 2.9 Beta1  you can test out the functionality and provide any feedback.   ShanaBritt_1-1632515688468.png   ... View more

The behavior described in the original post where are jumped back to #1 in the Rematch Addresses Pane when geocoded records are selected during the rematch process is in our plans to address and can be tracked with BUG-000141513. If you are part of the Early Adopter Program you can test out you workflow when Pro 2.9 Beta1 is available. ... View more

@JoeBorgione Just tying up ends here since you mentioned the jumping back to #1 in the Rematch Addresses Pane here, which is in our plans to address and can be tracked with BUG-000141513. ... View more