Latest Contributions by ShanaBritt

@Jaclyn , In ArcGIS Pro 2.6.3 what tool did you use to create the locator that does not return matches for address that include Ridge as part of the street name? I'd like to clarify which tool you used since in ArcGIS Pro 2.6.3 there are two different tools to create locators with, Create Address Locator and Create Locator. Can you share how your reference data to build the locator is formatted for this street name? ... View more

Heather: The Loc_name field tells you which locator in the composite the candidates are coming from. Which locator is returning the match to Burger Street for the input of 499 Harris Street? Which locator in the composite are you expecting will have a match candidate for '499 Harris Street'? Should this address have a match based on the data used to build the locators? What are the other results that are returned in the Map Viewer when you click the highlighted link in the screenshot? Are they the same candidates you get in the Locate pane with 'show all candidates' checked or from the REST endpoint?   Does the PlaceName locator have a place name alias table associated with it? You can see this in the properties when you select the Place name alias table page.  Does the field mapping for the PlaceName locator include street info? You can see this in the properties on the Reference Data Tables page. Is your overall goal to figure out why '499 Harris Street' is matching to Burger St and not Wallis State Bank? Based on the results returned in the REST endpoint form, the composite service is returning the same candidates as in the Locate pane when 'show all candidates' is checked  I notice that the PlaceNames gazetteer style locator was based on the 10.2 version of the address locator style, are the other locators in the composite based on version 10.2 address locator styles? So many improvements have been made to the locator styles since 10.2 when compared to 10.7.1, have you considered recreating the locators in 10.7.1 or in ArcGIS Pro with the Create Locator tool? You would be able to create a single locator that referenced all of the data for the dual range (StreetAdress role), place name (POI role), site address (PointAddress role), and street name locators in your current composite locator. ... View more

Heather: In the REST end point form for the findAddressCandidates enter Loc_name,Addr_type as the input for Out Fields in the form, then you can tell which locator is returning the candidates for '449 Harris St.' and '449 Harris Street'. What locator style was used to create the PlaceNames locator? It looks like it possibly has a place name alias table associated with it. Do you get the same or different results for the two addresses when you click the 'Show more results' link in the map viewer? ... View more

The following help topic provides steps as well as a link to a sample script. https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/keep-your-locator-up-to-date.htm#ESRI_SECTION1_12AA5C7DF3B44701B13DD015F6D1BA02 ... View more

Do you get the same behavior when you access the findAddressCandidates operation at the REST endpoint for the composite geocode service and enter the address? For the output fields I would include Loc_name and Addr_type so you can tell which locator the candidate is from and the match level. ... View more

Michael: Were the locators that participate in the composite locator created using the Create Address Locator tool or the Create Locator tool. If they were locators created with the Create Locator tool, the distance parameter is ignored and you should consider using the featureTypes parameter if you want to specify the type of matches that are returned. Have you tried using the reverseGeocode REST endpoint page to help form the request? Are you looking to return intersection results or any feature type? More examples using the different parameters are illustrated in the help for the reverse geocode operation, https://developers.arcgis.com/rest/geocode/api-reference/geocoding-reverse-geocode.htm. ... View more

John: If you publish the StreetAddress role locator created with the Create Locator tool to ArcGIS Sever, you will be able to use the locator in ArcMap as a service. You would have to compare the field mapping and settings between the 10.7.1 locator and Create Locator tool locator. If possible, I would suggest transitioning your locators created in ArcMap with the Create Address Locator tool to building locators in ArcGIS Pro using the Create Locator or Create Feature Locator tool. You can create a single locator that references more than one feature class, use suggestions in the Locate pane w/o publishing the locator as a service, specify up to 50 custom output fields that are returned in the geocode results to name a few of the enhancements you can find in the new locators.    ... View more

If you have created a locator with the Create Locator tool based on the Street Address role and have modified the intersection connectors property in the locator properties in Pro 2.7 or later to include the slash (/), you must publish to Enterprise 10.9 or later to make use of the modified intersection connectors, side offset, end offset settings. https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/tips-for-improving-geocoding-quality.htm#ESRI_SECTION1_8BB6427CAC1B4CCD95BDF0619CA00DC2 ... View more

@JohnNergeBrooklynPark What are the geocoding option settings of your locator? Did  you build the locator in ArcMap with city or zip code? Are the addresses in the table being geocoded in multiple fields or a single field? Do the addresses include city or zip code? Do you experience the same behavior with a locator created in Pro with the Create Locator tool using the StreetAddress role? ... View more

Josh: 1. The input fields are fixed for all locators created with the Create Locator tool regardless of the role the locator is based on. If it is just zip code, you should be able to use the SingleLine input field. Is the purpose of using the geocode service at the REST endpoint for development purposes to verify results or will the geocode service be used in an application? 2. To limit the output fields returned by the locator, turn off the unwanted fields in the Locator Properties of the locator in ArcGIS Pro on the Output fields page of the dialog. Then overwrite the service using the modified locator. 3. It's not possible to remove or customize the localized names for the locators created with the Create Locator or Create Feature Locator tools that are published as services.   ... View more

In ArcGIS Pro 2.7 and later you have the option to specify the output fields  you want returned in the geocode results. It sounds like you need to make use of the Minimal Output Fields option. A brief description can be found at step 6d. of the Convert a table to locations on the map help topic and more details can be found in the parameters section of the Geocode Addresses geoprocessing tool.   The default behavior is to return all of the output fields of the locator used to geocode the table, which includes the User_ fields, which are a copy of the original fields from the input table. More details about what is returned in the geocode result can be found here: https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/what-is-included-in-the-geocoded-results-.htm. ... View more

@Egeiser27 If you have access to the local locator the services were published from, do you continue to get the error geocoding the csv table? If not, then I would say there is an accessibility or permission issue with the locators in your organization's portal. Are others in your organization able to use these locators successfully? ... View more