Latest Contributions by ShanaBritt

@LisaBuckleton_dtwd  You should be able to use the ArcPy Geocoding Module to create a script to update the properties of the locator and create a script tool from it that can be used in Model Builder. ... View more

@HeatherKetten2  1. Do you get the same behavior if you run the Geocode Addresses tool in the Geoprocessing pane with the same csv file? 2. Does the csv file contain any spaces or special characters in the name or field names? 3. Are you able to upgrade to the latest 2.9 patch? 4. What was the output field option you selected in Geocode Table? (All, Minimal, Location Only) 5. What is the output format of the geocode result? (shapefile, file gdb) ... View more

@MichaelVolz You do not have the ability to make a modification to the street suffix types as you did with the classic locators, however you could use an alternate street name table that contains 'La' for the street suffix type for the street name. I would suggest submitting an enhancement request through Support to get this added for evaluation for a future release of ArcGIS Pro. If there are any other enhancement or improvements you would like to see with the new locators, please submit them so that the Geocoding Development team can evaluate them or offer workarounds. I'm curious about your data as well, was it created in-house or purchased from a data vendor? ... View more

@ScottFedak2085 @IanMackenzie If you are able to use ArcGIS Pro 2.7 or later and Enterprise 10.9 or later you can modify the side and end offsets in the Locator Properties dialog and have the changes reflected in the published service. https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/tips-for-improving-geocoding-quality.ht....  If you modify the offset settings in the locator properties to 0 is that setting not being honored with the local locator or when published as a geocode service?  It sounds like the issue with the geocode service is due to the version of Enterprise. ... View more

If you create a multirole locator with the Create Locator tool using the PointAddress and StreetAddress role any address that does not have an exact match to the point data will get matched to the street based on the house number range of the street. The address is interpolated along the line based on the house number range for the street segment. The PointAddress role requires that a feature exist for the house number you  are looking for to return candidates. ... View more

Did you plan to update you classic locators (deprecated) to the new locators when moving to ArcGIS Pro 3.0? If you make a copy of an existing project, then open it in Pro 3.0 and remove the broken locators from the Locators group in the Catalog pane then save the project and close Pro, Do you still get the invalid locator message when you open the project again?   -Shana ... View more

There is no setting for what you are encountering, but it sounds like a bug. If you have maintenance, please submit this to Support. ... View more

It's possible to search for Street blocks, which is described here for StreetAddress role, https://pro.arcgis.com/en/pro-app/3.0/help/data/geocoding/introduction-to-locator-roles.htm#ESRI_SECTION2_6D3D70C9F7AA4871ABDBCD7F98D363D1. You will need ArcGIS Pro 2.7 or later to build a locator that supports searching for street blocks, for example "100 block of New York St, Redlands, CA". How do you have the block address formatted in your input address table? You will need to modify your address table to change addresses from "1234 N Main" to '1200 block of N Main' in order to get the matches you are looking for. You can also test this out using the following tutorial and the test addresses at the bottom of the tutorial. https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/tutorial-create-a-locator.htm# ... View more

Building a locator with the Create Locator or Create Feature Locator tools suppors global search for coordinates (latitude/longitude, MGRS, DD, or USNG). Support for coordinate searching is disabled or enabled under Categories to support on the Geocoding options page of the Locator Properties dialog box for the locator. What is the format of the coordinates you are using? Can you enter the same coordinates into the Locate pane and get results returned by the StreetAddress role locator you created? What is the coordinate system of the locator (the reference data)? Also, are you not able to use Make XY Event Layer to generate points from the coordinates? -Shana  ... View more

@feralcatcolonist_old What in the https://pro.arcgis.com/en/pro-app/latest/arcpy/geocoding/locator-class.htm are you not able to set when building the locator using ArcPy? ... View more

@jzcgis There are three different tutorials available for building locators with the Create Locator tool.  https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/tutorial-create-a-locator.htm https://pro.arcgis.com/en/pro-app/3.0/help/data/geocoding/tutorial-create-a-multirole-locator.htm https://pro.arcgis.com/en/pro-app/3.0/help/data/geocoding/tutorial-create-a-locator-with-more-than-one-dataset-of-same-role.htm   ... View more

@ScottFedak2085 Enterprise 10.9 and later supports offset settings for StreetAddress role locators. You may want to consider creating the locator with either Global Extra High or Local Extra High as the Precision Type, which is an optional parameter in the Create Locator tool. The Precision Type parameter is supported in Enterprise 10.8.1 or later. I did not see a screenshot of the locator properties showing the output fields, but I suspect you may be running into ENH-000141201, which is resolved in ArcGIS Pro 3.0 and Enterprise 11.0. ... View more