Latest Contributions by BradNiemand

Kyle, I think you have a few options and I will list them in order, top being best. 1. Combine the multiple reference data sets into a single featureClass.  This is an additional step but lets you take advantage of all of the new features for the new locators.  You can create a featureClass that is in a schema that works for all of the data and ETL the other datasets into that new featureClass. 2. Add all of the locators separately to the MMPK in the order that you would want them.  This works sort of like a composite but with less limitations. 3. Create locators for individual cities and combine them into a composite.  As you already know, there is a limitation to doing this. ... View more

Lindsey, We did fix this already.  You will need to create the locator again using ArcGIS Pro 2.4 and if you are publishing it to ArcGIS Enterprise you will need one of the following patches. ArcGIS Server 10.6.1 General Geocoding Patch ArcGIS Server 10.7.1 General Geocoding Patch ... View more

We have a script shared on ArcGIS.com that can be used to automate this process.  See the link below. https://www.arcgis.com/home/item.html?id=54e8aab14f6e4c61b65b9dd9ab451503  ... View more

We now have a 10.6.1 patch available for this issue: https://support.esri.com/en/download/7741 Brad ... View more

John, As you know from one of my comments above, we have a patch for 10.7.1 for the issue with using magicKey.  We will not be patching 10.7 but we are looking to create a patch for 10.6.1.  At this time nothing has been released but we are working on it now. Brad ... View more

John, Yes, this helps.  There is an issue that will be fixed in the next release of Pro (2.5) that addresses an issue with locators created with the Create Locator tool and added to a composite locator won't show suggestions locally in Pro.  If you were to publish this locator to Server, you would get suggestions. As for the classic locators, I am unsure what is going on there but if you have the ability to move to the new locators, this would be the best approach because there are many benefits to these locators, including some enhancements to suggestions such as verifying the house number for addresses and suggestions for intersections. Brad ... View more

John, I assume you used Create Address Locator to create your locators, right?  If so, what locator style did you use (US Address - Dual Ranges and US Address - City State)?  Is this composite locator published to ArcGIS Server or are both of the locators published to ArcGIS Server and the composite locator is not? Brad ... View more

John, This patch is not for locators created with the Create Address Locator tool (in ArcMap and Pro), only for locators created with the new Create Locator tool in Pro. I would need more details from you to understand what the issue you are having with, as we call them, the classic locators.  What style did you use to build the locator?  What is an example of the input data, the field mapping, the input placename you are trying to get a suggestion for? Brad ... View more

Kevin, Are your locators built withe the Create Locator tool in ArcGIS Pro or were they created with the Create Address Locator tool in Pro or ArcMap? Brad ... View more

Leon, We typically don't patch "dot" releases once a "sub-dot" release is already out with a fix or a patch (like is the case here).  That doesn't mean we can't, we just hadn't planned on it.  Is moving to 10.7.1 not an option for you? Brad ... View more

Leon, I have responded on your thread that you mention in the previous comment. Brad ... View more

Michael, Currently there is no way to modify locator properties programmatically but we have had discussions internally about supporting this via Python.  Is Python where you would want to perform this from? Brad ... View more

Currently there is no option to exclude additional output fields from the batch geocoding process for ArcGIS online or classic locators (locators built with the Create Address Locator Tool) but we will consider this enhancement for a future release of Pro. There is however a way to exclude output fields for locators created with the Create Locator tool in Pro 2.3 and newer.  To do this, you would open the properties dialog for a locator on disk in Pro (add the locator to the project, right click on the locator and select Properties).  Then you would go to the output tab in the properties dialog.  There you will be able to disable most of the additional fields that are added during the batch geocoding process.  This doesn't, however, allow you to exclude the the USER_ or IN_ fields. The IN_ fields are the fields that are mapped when performing the batch geocoding and they are used for the rematching process to make sure the fields are mapped the same way they were when the original geocoding occurred.  The USER_ fields are just a copy of the original data into the geocoded featureClass in order to keep the fields associated with the new output. Brad ... View more