Latest Contributions by ShanaBritt

Kevin: 1. Are the locators that are disappearing on you created with the Create Address Locator tool or the Create Locator tool? 2. What version of ArcGIS Pro did you encounter this behavior? 3. Does the locator that is rebuilt not show in the Catalog pane under the Locators folder and in the Locate pane in the Provider Settings? Are you using the Rebuild Address Locator tool to rebuild the locator? If so, do you remove the locator from the project before running the tool? -Shana ... View more

Melisa: For the intersection in question are you able to show what the values of the street components look like in the reference data (prefix direction, street name, street type, suffix direction)? ... View more

Melisa: It would be helpful to see the data and field mapping of the locator you built with the Create Address Locator tool in Pro. I'm also curious to know if you get the same behavior using the Create Locator tool with the StreetAdress role. -Shana ... View more

Brian: Locators created with the Create Locator tool in ArcGIS Pro can be used in ArcMap after the locator has been published as a geocode service from ArcGIS Pro. A locator based on the StreetAddress role built with the Create Locator tool has a default offset of 3m that cannot be changed. The locators created with the Create Locator tool do not have a spelling sensitivity property to adjust in the locator properties. The following topics discuss the geocoding options that can be adjusted in the new locators created by the Create Locator tool: Tips for improving geocoding quality—ArcGIS Pro | Documentation  Tips for improving geocoding performance—ArcGIS Pro | Documentation  Additional tuning options—ArcGIS Pro | Documentation  Are addresses not being matched by the locator you created based on the StreetAddress role that are related to misspellings? What is the reason you need to adjust the side offset of the locator based on street segments? -Shana ... View more

Joe Borgione‌ Since you first posted your problem in release 2.4, we've added some improvements such as the Parcel role (2.5) and subaddress suggestions for the full unit (2.6), below is what I would suggest doing in Pro 2.6. Create the multirole locator using the following roles: 1. PointAddress role for addresses and subaddresses using address point data 2. Parcel role using the polygon layer and map the field that contains Parcel ID to the Parcel Name locator role field. 3. POI role If you have multiple data layers that represent POI data in different categories (parks, emergency, businesses, etc), the best thing to do is add one or two fields (category and subcategory) to each data layer and populate with category details, then merge all of the layers with the same geometry type into a single feature class. Use the single feature class to build the locator with the POI role and map the category or category & subcategory fields. You will be able to search by POI name, category, POI + address, Primary locator roles—ArcGIS Pro | Documentation. A multirole locator only allows for one layer to be added for each role included. If you have multiple datasets, potentially from multiple sources, that you want to map to the same role, it is recommended that you merge all of those layers into a single layer before assigning a role when building a locator. Multirole locators created in this way will have better performance than a composite locator created with the same data. -Shana ... View more

ArcGIS Pro 2.6 is now available and includes the new ArcPy Geocoding module that will allow you to perform geocoding operations via Python and modify locator properties. A list of the properties that can be modified are listed here, https://pro.arcgis.com/en/pro-app/arcpy/geocoding/locator-class.htm#P_GUID-B617A31C-2B5E-427F-BBEB-B52C1667CC51 . ... View more

Lucas: I may have spoken with you at the UC about this issue, this time there are more details... I understand that you are already massaging the address tables and that duplicating the locator in the composite has saved some headache, but will any of the following workarounds work for you in ArcGIS Pro? Concatenate the Address1 and Address2 fields into a single field and only adding the point locator once to the composite locator. You may need to do a few select by attribute and calculate field operations to get everything into the single field. Rename the point locator if it is not a service before adding it a second time to the composite locator. Do you know if the agencies you work with that provide the locators you use are planning to transition their locators from the classic locators built with the Create Address Locator tool to locators built with the Create Locator tool? ... View more

We've addressed this issue in the next release of ArcGIS Pro when building locators with the Create Locator tool. If you are part of the early adopter program, you can use a beta version of 2.6 to test your workflows with the data you have. If you are encountering the true curve problem with the currently released software you can export the layer from the geodatabase to a shapefile and import it back into the geodatabase (file or sde), densify the existing data in the geodatabase. ... View more

How many locators in the composite? ArcGIS Server 10.8? ... View more

Here is a link to the program. Early Adopter Community | Esri Early Adopter Program  ... View more

If you are part of the beta program you can test out pro 2.6 beta as we've added a Geocoding module to ArcPy that allows you set locator properties and geocode using Python. ... View more

I'm not able to reproduce that behavior in 2.6 beta. Curious if you get the same when you geocode with zone as part of the address. If you are part of the beta program  you may want to test out some of your workflows in 2.6 beta. ... View more

Barrett: So you used the locator locally rather than as a service? Did you create the connection to the service in ArcGIS Pro or ArcMap/Catalog? Is the service on standalone ArcGIS Server or federated portal? ... View more

Joe: I mocked up some data based on your screenshot and cannot reproduce the behavior you described. I get match results for each unit whether I use # or Apt as the unit indicator. Below is the field mapping from the locator properties. Do you get different results when you compare the locators with and without the JoinID mapped? ... View more