Latest Contributions by BradNiemand

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

John, Please try to enter the following instead: Mile 20.1 I-83 North Mi 20.1 I-83 North I-83 North Mile 20.1 I-83 North Mi 20.1 Brad ... View more

There seems to be an error in the documentation.  Distance direction is not required and not even a field that can be mapped.  How did you map your fields in the Create Locator tool?  Try mapping just distance, distance unit, and StreetName (if you have the StreetName components parsed out in your data, it is better to map each individually instead of just mapping the FullStreetName to the Street Name field). Also, how did you enter the mile marker text when you were searching? Thanks, Brad ... View more

When you hover over the locator in the settings tab do you get a popup tool-tip with the error message?  If so, what is it? Brad ... View more

Jamal, When you open the Locate Pane, click on the settings tab and hover over the locator does it give you any type of warning or error? Brad ... View more

I don't see the extra "/" on my end.  What version of Pro are you using? Brad ... View more

Jamal, The way you describe it looks correct.  You are going to want the path to be exactly how it is when you add the locator via Pro.  Just hover over the locator in the Locators folder and you will get the full path. If you still have issues, I would say it might be time to get technical support involved. Brad ... View more

Jamal, What path is showing in Pro when you hover over the locator in the Locators folder in the Catalog Pane?  Are you using the same path when you are adding it via the SDK? For instance, when I add a locator via the Server connection: I see a path like this: C:\path\arcgis on servermachine_6080\name_of_locator.GeocodeServer Is this how you are entering the path? Brad ... View more

Jamal, What type of locator are you adding to Pro?  Can you do it via Pro without error?  When you open the Locate Pane, click on the settings tab and hover over the locator does it give you any type of warning or error? Brad ... View more

Kyle, Are you using PreferredSearchLocation and passing in the center of your map as that location in your request?  This will help give more flexible results because it will be looking at addresses that are close to your current location.  All of our apps (Map Viewer, Pro, ArcMap) use PreferredSearchLocation when getting suggestions. Brad ... View more

Kyle, I won't be able to go into any details about the geocoding process under the covers but I could potentially answer a specific question depending on what it was. There is a basic SDK that can be found here:  https://pro.arcgis.com/en/pro-app/sdk/api-reference/index.html#topic18864.html Was there something specific you were looking for in the SDK? Brad ... View more

David, So you have a use-case to have only a StreetName locator?  You don't have a separate featureClass with address ranges?  If so, you can add a new field to the StreetName featureClass that has empty values and name it something like HouseNumber.  When building the locator, map this field for all of the range fields; Left House Number From, Left House Number To, Right House Number From, Right House Number To. This was done to consolidate the locator and make the locator much smaller because typically users used StreetName locators as a fallback for a StreetAddress locator and then there would be duplicate locators that really contained all of the same information except no house number for StreetName.  Now we can build a single locator that has all of the information in one spot and only give StreetName candidates where the house ranges actually don't exist. Let me know if you have any additional questions about this. Brad ... View more

Kyle, There is no way to configure the output label. The added "USA" to the end of the output text looks like something we will want to fix.  I will enter an issue in the backlog for this. Brad ... View more

Leon, You are good at finding issues ! Yes, this is an issue but there is a workaround.  Open the composite locator .loc file with a text editor and change the following line at the bottom. UseMultithreading = True Set the value to False. UseMultithreading = False You will need to republish the composite locator. This will not affect performance of geocoding for this service so don't worry about that.  We will look to include the actual fix for this issue in the next patch we release.  Also, this will not work in Pro either unless you have 2.3.2 or later. Brad ... View more

We have a new patch for 10.6.1 for custom output fields.  It is located here: https://support.esri.com/en/download/7704 There is still a limitation where custom output fields are not returned for intersection results.  We are looking into patching this as well. Brad ... View more