Latest Contributions by ShanaBritt

@acharko In ArcGIS Pro 2.7 or later and Enterprise 10.9 or later support for adjusting the side and end offsets, as well as custom intersection connectors in the Locator Properties dialog. https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/tips-for-improving-geocoding-quality.htm#ESRI_SECTION1_CBCA29056A7F4D7187049BECA6CC0B84 ... View more

The reverse geocoding operation does not support returning the address components in the output like the geocodeAddresses or findAddressCandidate operations do. It is not possible to return the individual address components when reverse geocoding. ... View more

We've added the ability to return a list of subaddresses and a summary of  subaddresses at an address after typing the base address to ArcGIS Pro 3.0. A feature that represents the base address is required in the reference data used to build the locator in order for the new functionality to work. A locator with the new settings enabled must be created in ArcGIS Pro 3.0 and published to ArcGIS Enterprise 11.0 . The new properties, " Show summary of subaddresses with base address suggestion" and "Suggest when base address is typed" are disabled by default and the number of suggestions displayed can be configured in the Locator Properties dialog on the Performance page. If you are part of the Early Adopter Community or have access to ArcGIS Pro 3.0 Beta1  you can test out the functionality and provide any feedback. If you were to go through the create a multirole locator tutorial , you could test the new functionality with the following addresses: - 1508 CIRCA DEL LAGO, SAN MARCOS, CA - 1616 CIRCA DEL LAGO, SAN MARCOS, CA       ... View more

@MichailMarinakis1 Are you able to provide more details about the locator? 1. Were you using the Create Locator tool to build the locator? If so, which role and country? 2. Is the full street name mapped in the field mapping of the locator? If it's possible to send the locator and a small sample of the data with just the address info that would be most helpful in trying to figure out what's going on to better answer your question. ... View more

That is correct, the locator created in Pro 2.9 with custom offsets will need to be published to ArcGIS Server 10.9 or later in order for those offsets to be honored when using the geocode service. ... View more

What tool was used to build the locator? What role was used to build the locator? How many features or suggestions are you expecting to be returned? You may want to try creating the locator with the Create Locator tool and using the POI role  and possibly use categories since you can search on the category name and get all of the places associated with that category. Another option is to configure the layer for feature searching, then save the map as a mobile map package or share as a web map and use the configured layer for searching. This would allow you to search for any part of the name if the place name field is configured with 'contains'. ... View more

What tool are you using to build the locator? As long as you have a  join id that links the primary street name to the street alias in an alternate name table there shouldn't be any conflict. However, depending on the tool used to build the locator there are ways that you can ensure the primary name is used or get results when either street name is used. If you are using ArcGIS Pro and the Create Locator tool use the following resources: Preferred Street Name Fundamentals of alternate name tables Alternate name table roles ... View more

The workflows in the following topic should help in keeping your locators and services updated. https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/keep-your-locator-up-to-date.htm ... View more

@CMV_Erik If  you have created the locator in ArcMap you will not be able to use the output field options when using geocoding tools in ArcGIS Pro. You must create the locator in ArcGIS Pro with the Create Locator or Create Feature Locator tool , then you will have the option to maintain the original input table fields using the Minimal option when geocoding the table. Essentially, you will only get the option to maintain your original table fields in ArcGIS Pro 2.7 and later if you geocode with a locator created with the Create Locator or Create Feature Locator tool. ... View more

What version of ArcGIS Pro are you using? What version of Enterprise SDE are you working with? When you say that it doesn't work, do you mean you do not get any results when searching for a string in one of the fields you configured? ... View more

@MaureenKerr Which tool did you use to build the locator you created metadata for? Are you copying and pasting in Windows File Explorer or using the Copy geoprocessing tool? ... View more

@AZendel  If you have a locator that was created with the Create Address Locator tool in either ArcMap or ArcGIS Pro, these locators do not support this output field option when geocoding, so you will always get the USER_ prefix appended to the geocode results whether the locator is local or a geocode service. If you geocode your table with a local locator or geocode service based on a locator created with either the Create Locator tool or Create Feature Locator tool in ArcGIS Pro 2.7 and published to ArcGIS Server 10.9, you will have the option to return a minimal set of output fields in the geocoding tools. You also have the option to turn off the output fields you do not want in the Locator Properties. Below is a description of the output fields options. > All— Includes all available locator output fields in the geocode results and includes the USER_ prefix on the original fields. This is the default. > Location Only—Stores the Shape field in the geocode results. The original field names from the Input Table parameter are maintained with their original field names. > Minimal—Adds the following fields that describe the location and how well it matches information in the locator in the geocode results: Shape, Status, Score, Match_type, Match_addr, and Addr_type. The original field names from the Input Table parameter are maintained. ... View more

@MichelleWilliamsERM  If you geocode a csv table with the Minimal output field option, where in your workflow of appending data do you lose your original fields or have to delete fields?  ... View more