Latest Contributions by ShanaBritt

@RonnieRichards Looking back at your original post, I would say that you should include at least 'addr_type' to be returned from the request so that you can understand the match level of the returned candidate. What is returned in the example is a PointAddress candidate and not a Subaddress candidate. If a feature that represents this subaddress does not exist in the reference data, then locator is going to return a match at the next precise match level, which is PointAddress in this case, which is less precise than Subaddress. If you are just searching for subaddress addresses, then I would suggest adjusting the Categories setting in the locator to only search for/return Subaddress by just checking Subaddress. Do you get the same result for search when testing the same locator in Pro Locate pane? Do you see any suggestions for the subaddress as you type the address that includes the subaddress element? ... View more

In ArcGIS Pro 3.0 you should be using the new locators included with Business Analyst instead of the classic locator or composite locator with participating classic locators as the classic locators are fully deprecated at ArcGIS Pro 3.0. This was mentioned in the ArcGIS Pro 3.0 deprecation notice related to geocoding, https://support.esri.com/en/Technical-Article/000027452. The "US Business Analyst Geocoder - Local Composite" is a classic locator and you should be using the locator titled 'USA.loc' as the locator for geocoding in 3.0. ... View more

Chip: It's possible you may get better results for that situation if  you rebuild the locator with the Create Locator tool without having to create an alternate name table to account for different variations of the street name which would allow you to make use of the following property. https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/additional-tuning-options.htm#ESRI_SECTION1_663D3C8AEB0F4F2DACC721046936945E If you need to create the locator in ArcMap you will need to create an alternate name table to account for the difference in street name. https://desktop.arcgis.com/en/arcmap/latest/manage-data/geocoding/the-alternate-name-table.htm ... View more

Chip: Correct, if the address doesn't exist in the data used to build the locator then no matches or suggestions are returned. If your city's data does not account for outside address typos or addresses not in your city data, you will not get matches or suggestions. If your rematch workflow is happening in ArcGIS Pro 2.9.2 you have the ability to rematch the unmatched using a new locator as described in the 'Match with new locator' section of the rematch help topic. https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/rematch-locations-converted-from-a-table.htm You also have the ability to match a selected group of records in the geocode result and match them all to a specific address using the 'Match all selected' button. Your workflow makes sense. If you used ArcGIS Pro to geocode the table and used the default output fields setting (All), then editing the fields prefixed with IN_ in the geocode result will update the fields used to generate candidates for that record and allow you to fix the typos. If you select all of the records that you modified, you can click the Auto rematch button and it will redo the matching process. It sounds like the locator was built with the Create Address Locator tool in either ArcMap or ArcGIS Pro 2.6 or earlier, but you can confirm this by opening the Locator Properties for the locator you are using in ArcGIS Pro and look for release or version on the About the locator page. If it says 'Style release', then it was created with the Create Address Locator tool. Locators built with this tool are deprecated and will be fully deprecated in ArcGIS Pro 3.0 https://support.esri.com/en/Technical-Article/000027452 so you will want to update those locators using the Create Locator tool before upgrading to ArcGIS Pro 3.0. The locators built with the Create Locator and Create Feature Locator tools cannot be used in ArcMap unless they are published as a service to ArcGIS Server 10.9.1 or earlier from ArcGIS Pro. I would encourage you to recreate your locators with the Create Locator tool so that you can take advantage of the improvements we've made to geocoding and locators. Here are some resources for building locators and tuning the properties: https://pro.arcgis.com/en/pro-app/2.9/help/data/geocoding/create-a-locator.htm https://pro.arcgis.com/en/pro-app/2.9/help/data/geocoding/create-a-feature-locator.htm https://pro.arcgis.com/en/pro-app/2.9/help/data/geocoding/keep-your-locator-up-to-date.htm https://pro.arcgis.com/en/pro-app/2.9/help/data/geocoding/tutorial-create-a-multirole-locator.htm https://pro.arcgis.com/en/pro-app/2.9/help/data/geocoding/tips-for-improving-geocoding-quality.htm https://pro.arcgis.com/en/pro-app/2.9/help/data/geocoding/locator-role-fields.htm https://pro.arcgis.com/en/pro-app/2.9/help/data/geocoding/introduction-to-locator-roles.htm https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/display-geocode-results-on-the-map.htm ... View more

This was fixed in more recent versions of ArcGIS Pro. ... View more

@KevinKuhn At the 2.7 release of ArcGIS Pro we added the ability to rematch with a different locator than the original locator  used to geocode a table.  You could also modify some of the settings of the locator that was originally used. Please see the "Match with new locator" section of the rematch help topic. https://pro.arcgis.com/en/pro-app/2.7/help/data/geocoding/rematch-locations-converted-from-a-table.htm ... View more

Chip: For the addresses that did not have candidates in the Rematch Addresses pane, were there candidates returned for the address in the Locate pane? Are you still using ArcGIS Pro 2.6? Which tool did you use to create the locator that you are using to geocode with? I'm trying to understand why there were no candidates if the feature existed in the data used to build the locator. Thanks, Shana ... View more

The behavior you encountered was fixed in ArcGIS Pro 2.9 (BUG-000141513). ... View more

If you are still using ArcGIS 10.7.1, I think the problem is the format of the input address for the US Single House with subaddress style. If the input address was '311 Woolwich St #36' or '311 Woolwich St, 36' I would expect to get some matches as this is the address format for the USA for subaddress addresses for locators built with the Create Address Locator tool in ArcMap. If your address is in Canada or Australia, I would recommend using ArcGIS Pro to build the locator with the Create Locator tool and select the country your data is in. The resulting locator would support the address format for the country the locator was created for. The locator created with the Create Locator tool could only be used in ArcMap if it was published as a service from ArcGIS Pro. ... View more

Just curious to know if there were candidates in the Rematch Addresses pane for the address you were trying to Pick on the Map expecting to snap to the existing point. Was the existing point you were trying to snap to in the feature class used to build the locator you were geocoding with? I'm trying to understand your workflow to see if what you were trying to do is something that we would consider adding to ArcGIS Pro. The ArcMap 'Pick Address from Map' had an option to "Match to Address Location" that snapped to the nearest address returned by the locator versus "Match to Click Point"  that snaps to the location you clicked. Thanks, Shana ... View more

Based on the screenshot it looks like there are no unmatched records. How many unmatched records should be displayed here?  Do you get the same unmatched behavior when you geocode the table in ArcGIS Pro with the same composite locator on the portal? What is the format of the table that was geocoded on the portal? ... View more

It looks like the 'AllStreets_UTM' locator was created with out city, state, zip mapped based on the images provided. In the Rematch Addresses backstage where you see the Input Address Fields and the settings, what happens when you change the Input Address Fields to Single  Field instead of Multiple Fields and select the field that contains just address or intersection? What is the result when you geocode the table and select Single Field initially in the Geocode Addresses tool or Geocode Table pane? It would be helpfult if you provided a screenshot of the Reference data section of the Locator properties for the AllStreets_UTM locator. ... View more

1. Does it happen when creating a new project using the map template? 2. Does it happen when creating a new project using the catalog template then inserting a map? The locate pane is tied to the map, a locator needs to be added or loaded into the project in order to use the Locate pane. If the locators from the portal have not fully loaded in the project and the Locate pane was the last active window, the pane will not be available until the locators are loaded. In the Catalog pane under the Locators group you can see the locators that have been loaded and if you right-click the group there is an option to refresh the locators. I'm curious if you refresh the locators when you see the disabled Locate button behavior if that makes the button enabled instead of having to restart the ArcGIS Pro session. ... View more

Are you signed into arcgis.com as the active portal or are you signed into your organizations Enterprise portal? Does this behavior occur  when the active view is a map view or when the active view is a table or layout view? ... View more

@Anonymous User ,  The input address format should correspond to the postal specifications of the country you are geocoding addresses in. For the USA refer to the following publication from the USPS for acceptable street type abbreviations, https://pe.usps.com/text/pub28/28apc_002.htm. Regarding the interstate/highway name, "Hwy 40" and "I-40" are typical formats and inputs outside of this standard may not match or have a low score. ... View more