Latest Contributions by ShanaBritt

‎01-23-2025

@LisaLowe__DOIT_1I had a few questions to get a better understanding of what is going on with your composite locator. 1. Can you provide the performance settings of the composite locator? 2. In which application were the classic locators in the composite created? 3. Which version of ArcGIS Pro are you geocoding the tables and getting better results? 4. When geocoding the tables in ArcGIS Pro are you using the local composite locator or the composite geocode service? 5. Have you attempted to recreate the locator in ArcGIS Pro with the Create Locator tool and publish it to ArcGIS Server 10.7.1 to see if you get the same behavior when the service is used in AGOL?

‎12-12-2024

@SaiKrosuri Are you able to provide examples of the addresses that return a low score or are unmatched? For the low score results what was the value in the Addr_type field? Feel free to send a private message. Do you have data to build a custom locator to use in conjunction with the ArcGIS World Geocoding Service? If you did, you could create a composite locator that that included the ArcGIS World Geocoding Service and the custom locator created with the Create Locator tool.

‎12-12-2024

Are you reverse geocoding with your own custom locator? Do you get the same results in ArcGIS Pro if you use the What's here? tool or Address Inspector tool? https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/identify-addresses-and-places-on-the-map.htm

‎12-05-2024

@WilliamBlake1 The StreetMap Premium locators are created with city, state, zip and the default setting is to require city, state, or zip when you type in the address and press enter. You should get suggestion candidates as you type the address in the search box. Are you noticing a difference in the behavior between the classic map viewer and the new map viewer in 11.3 portal? In ArcGIS Pro, if 'show all candidates' is not checked and you enter the address plus city or zip, do you get results?

‎11-20-2024

@BernardoBarrientos @JasonBessert The Locate button is a split button that will allow you to click and select Layer Search and it will open the Locate pane to Layer Search. Using the configured layer search is the best option to maintain the field search settings between sessions of ArcGIS Pro. If the fields you want search are indexed and you configure a layer or table for Locate those fields will be automatically set to a search mode. If it's a number field it will be set to exact. Configured layers are also maintained when the map is published as a web map and those layers can be used for searching in the MapViewer along with any locator that is set as a utility service in your organization or Enterprise portal.

‎11-06-2024

@dsinha Have you tried using the Match all selected button on the Rematch Addresses pane? Click Match All Selected if you have selected a group of records manually or created a selection set based on a custom query and need to match all of the selected records to a single candidate. For example, a group of records contains the same wrong city or postal code and you want to match them all to the same candidate at once. Using Match All Selected speeds up the process of rematching the geocoded feature class.

‎11-06-2024

Are you still using ArcGIS Pro 2.7 and Enterprise 10.9? Here is some info on overwriting the locator, https://pro.arcgis.com/en/pro-app/3.3/help/data/geocoding/keep-your-locator-up-to-date.htm

‎11-06-2024

@AntonSizo Have you attempted to create a locator with the cadastral data using the POI role in the Create Locator tool or with the Create Feature Locator tool using the field that contains the LLD info? The locators support searching for coordinates by default, https://pro.arcgis.com/en/pro-app/3.3/help/data/geocoding/tips-for-improving-geocoding-quality.htm#ESRI_SECTION1_1CC5777CE25A4D048FCC518AEC549DC6.

‎11-06-2024

@KadeChapman3 The is no way in ArcGIS Pro to modify the locator template to return the polygon as you could with the classic locators in ArcMap that is referenced as the solution for the original question in this post. -Shana

‎11-06-2024

@KadeChapman3 Do you get the same behavior if build a Point Address role locator versus the Parcel role locator? It is my understanding that there are some thresholds where polygons are prioritized over points and it would be helpful if you could provide me the polygon data used to build the locator and an example of where the neighboring point is returned. This can be the xy coordiante or point feature that represents the location you clicked on the map. -Shana

‎11-01-2024

@KadeChapman3 This option is not available for locators that are built with the Create Locator tool or Create Feature Locator tool. The option was only available for locators built with the Create Address Locator tool in ArcMap or ArcGIS Pro 2.6 and earlier.

‎10-29-2024

@DanielDormont Sorry for the huge delay. You can search for other geographies in Living Atlas.

‎09-25-2024

@brublanc When you use the local locator are you batch geocoding a table or are you searching for the same partial address in the Locate pane of ArcGIS Pro? Match with no zones set to 'No' means that you must include a zone or location (city, county, state, zip) with the address in order to get a match to the input address. Find Address Candidates: (StreetAddressStandalone) (shelbycounty911.org) In ArcGIS Pro the center of the map is used as location and is part of the request to the locator, so you don't have to include the zone in the Locate pane as you will get suggestions to choose from that include the zones that were mapped when building the locator. Via the REST endpoint there is no sense of location because there is no map and you would need to include a value in the location parameter in the findAddressCandidates request or include the city, state, or zip. location: Find Address Candidates: (StreetAddressStandalone) (shelbycounty911.org) with zip: Find Address Candidates: (StreetAddressStandalone) (shelbycounty911.org) I see that you have FeatureID mapped, do you have duplicate features with different attributes in the data used to build the locator? If not, the FeatureID field should not be mapped. Does the service behave differently when FeatureID is not mapped when building the locator?

‎09-17-2024

@AZendel , correct you need Enterprise 10.9 or later to use the Minimal option in the optional Output Fields parameter.

‎08-27-2024

@AntonSizo What would be the purpose of such role? What would you be mapping to build the locator with this role? What would you be searching for? How would the locator created from this role be used?

Online Status	Offline
Date Last Visited	a week ago

My Ideas

Latest Contributions by ShanaBritt

Re: Composite Locator added to AGOL is no longer Geocoding Properly

Re: How to Improve Accuracy of Address Matching in ArcGIS Pro Geocoding?

Re: Using Survey123 to Come Up with New Address Numbers

Re: Locator with suggestions not happening

Re: Set Preferences for Locate Tool

Re: geocoding - match multiple candidates to same address

Re: Locator Issues

Re: Legal Land Description locator role

Re: Reverse Geocode inside a Parcel polygon?

Re: Address Locator that reverse geocode based on point-in-polygon?

Re: Reverse Geocode inside a Parcel polygon?

Re: How to get administrative boundaries from geocoded result

Re: ArcGIS Server Locator Fails To Geocode Full Address

Re: Geo coding | DO NOT change the Field Names in conversion

Re: Legal Land Description locator role

Re: Geolocate addresses tool in arcpy

Re: Composite Locator added to AGOL is no longer G...

Re: Address locator takes 20x longer to rebuild in...

Re: Pro crash-out trying to rebuild address locato...

Re: ArcGIS Server Locator Fails To Geocode Full Ad...