Latest Contributions by ShanaBritt

Which tool was used to create the locators that are in the composite? The bug is related to locators based on polygon features that are published as services and not zooming to an appropriate scale or extent in the Map Viewer compared to the local composite in ArcGIS Pro. It was reported at 10.9.1. If you are up to date on maintenance you should be able to search for the bug number in myesri or the Support site. The only workaround found was to convert the polygons to points and rebuild the locator with the point data, but this might not be feasible for some.   polygon based locator published as a service and used in ArcGIS Pro and the map not ... View more

Hi  Michael. Did you resolve?  We are working with Verint,as well...and struggling. They can't seem to config our locator (Ohio State Plane) to work through the reversegeocode api.  ... View more

Exactly what I was looking for. Thank you! ... View more

I'll just drop this here. Seems like it could solve this issue if these parameters were exposed. https://community.esri.com/t5/arcgis-pro-ideas/create-locator-additional-options-when-creating/idc-p/1192654#M20349 ... View more

I just want to delete these problem locators as I just use the World Geocoding Service for everything.  And Yet every time I remove the locators, they just come back along with the annoying errors.  Is my only solution to do what @AnonymousUser23 suggested?  This has been going on for a couple of years through several Pro updates and it still isn't fixed.   ... View more

@AZendel did you or anyone here submit an Idea or Enhancement request to ESRI about this?  If so please pass along the link or Enhancement number so I can upvote and be attached to it.  Thanks! ... View more

@ChelseaRozek The new locators do not have an option to specify additional recognized input field names. I'd suggest submitting/posting an enhancement on Ideas thread.  Since it's not possible to add more recognized field names for the input field names of the locator, you will have to manually select the field that contains the data (address, parcel PIN) that you want to geocode in the table when using the Geocode Table or Geocode Addresses tool. If you build a multirole locator with PointAddress and Parcel role, the input address field is always going to be 'Address' in the batch geocoding tools. If you wanted to add recognized field names for input fields, so that Geocode Addresses tool automatically  populates the 'Address' input field, create a composite locator that contains individual role locators or a multirole locator and modify the recognized field names for 'Address'. I would also update Region to add 'State' and Postal to add 'zip' , 'zipcode' , and 'zip5', or whatever field name is used for the postal values in your data.       ... View more

Locators do not support wild card searches, that is more of a query than geocoding. Suggestions provide candidates based on the tokens (strings) that are typed at the beginning like an autocomplete of typing the beginning of the value in the data. What you have described is more like what is described in the following topic for layer search. The layer used in configured layer search can be shared as part of a web map and used for searching using the contains search mode.  - https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/find-places-on-the-map.htm - https://enterprise.arcgis.com/en/portal/latest/use/configure-feature-search.htm Another option is to create multiple Feature or POI locators based on the  zone_id, site_id, site_name, description fields and add them to a composite locator. For the description field, you would need to type the exact string or the beginning of the string to get find results or suggestions. The description could be added as a custom output field for the POI locators and this value would be returned in the geocode results. Custom output fields were added to the Create Feature Locator tool in ArcGIS Pro 3.2. ... View more

When I geocode the address '3 WEST WAY 11937' using my custom street address locator, there is a tie. The geocode service assigns a score of 100 to '3 WEST WAY' and '3 WESTWAY'. The same behavior is seen with '4 WEST WAY 11937'. When there is a tie, different ArcGIS Server instances may return different results. One server is matching to 'WEST WAY', and another server is matching to 'WESTWAY'. Both servers are assigning a score of 100 to '3 WEST WAY' and '3 WESTWAY'. Can I update my street address locator to decrease the score if a space is in the name? The attached file shows results from the address candidates endpoint. I created my locators using the ArcGIS Pro 3.2 engine, and published it to ArcGIS Server 10.9.1. ... View more

Which version of ArcGIS Pro are you geocoding the csv table in? Does the error occur via Python with a StreetAddress role based locator created with the Create Locator tool? ... View more

@AshlieVinzant Are you signed into ArcGIS Online? Do you have batch geocoding permissions in the ArcGIS Online organization?   -Shanan ... View more

I found the same behavior when Match with no zones option is set to No. This option is under Match Options. Change it to Yes solved my problem. ... View more

@jlchamber Based on the following description, what about the fields that are returned presents a problem for you? Does 'Location Only' work for your workflow? "Minimal returns 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 address table are maintained." Location Only returns the Shape field plus the original field names from the input address table.   -Shana ... View more

Hi Brad, Just want to confirm: do I still need to change this setting when I publish locator to ArcGIS Server in the new version (Pro 3.1?) Thank you, ... View more