Latest Contributions by BradNiemand

Lakshmi, How is the service configured?  In ArcGIS Server Manager on the Pooling tab, do you by chance have the "Minimum number of instances per machine" set to something less than the "Maximum number of instances per machine"?  If so, the instances will get shutdown every 30 minutes (handled by the "The maximum time an idle instance can be kept running" property) and they will need to be restarted and warmed back up.  You should always set "Minimum number of instances per machine" equal to "Maximum number of instances per machine" for geocoding services.  You will also need to ensure you have enough memory on the machine to handle this. Hope this helps. Brad ... View more

Leon, Sorry about the confusion.  I will update this thread when we have more information about standard output fields not returning when the new locators are added to a composite and published to 10.6.1 server. Brad ... View more

Leon, As mentioned above, we will not be patching 10.6.1 for custom output fields because it is new functionality that is only supported at 10.7.  The locators created from the Create Locator tool will work when published to 10.6.1 but may have some limitations for features that were not implemented until 10.7.  You will be able to see custom output fields in Pro 2.3 and when published to 10.7 server. Brad ... View more

Kevin, That is correct.  The only thing that won't work in 10.6.1 with the locators created with the new Create Locator tool are if you add custom output fields to the locator when building it.  Other than that, these locators are supported in 10.6.1. ... View more

Kevin, My statement above was contradicting and I have corrected it.  It stated that it DID work in 10.7 and we would potentially patch 10.6.1 but then stated that "Custom output fields will not be supported for 10.6.1 though as mentioned in a thread above." The quoted statement above is correct and the other comment should have been that it DIDN'T work in 10.7 either and we actually have created a patch that will go live for 10.7 in the next few days.  It is not possible to patch 10.6.1 because it is not a patch, it is completely new functionality that went in 2.3 which corresponds to the 10.7 release, not 10.6.1.  The locators will still function in 10.6.1 but custom output fields will not be supported. ... View more

Leon, I have reproduced the issue with locators created with the Create Locator geoprocessing tool and used withing a composite that is published to 10.6.1 server not displaying attributes in the standard output fields.  This is reproducible in 10.7.  We will look into the possibility of a patch to fix this issue for 10.7.  Custom output fields will not be supported for 10.6.1 though as mentioned in a thread above. Brad ... View more

Leon, The locators created from the Create Locator tool will work when published to 10.6.1 but custom output fields will not because they were not implemented until after that version of the software was already released.  You will be able to see custom output fields in Pro 2.3 and when published to 10.7 server. Brad ... View more

You can have this functionality by adding the geocoding services as Utility Services in ArcGIS Enterprise.  This must be done by the administrator but once it is done, all users will see these locators loaded by default when signed in.  More about this can be found here: Configure utility services—Portal for ArcGIS (10.6) | ArcGIS Enterprise  Brad ... View more

Are you performing the geocoding from ArcGIS Desktop (ArcMap or Pro)? ... View more

David, We made some modifications to the "Single Address with SubAddress" standardization for Pro 2.2 and 10.6.1 and it looks like from your updated post that this may have fixed your issue, is that correct?  Also, are you saying the "Single Address" style still has this issue? I am still a bit confused as to what you need to provide in #2?  Do you standardize the input tables or something else?  The process of geocoding parses out the street components and returns them as output fields and because during this process it can compare multiple permutations against the reference data to figure out the best result, the results will be much better. Maybe I still don't understand the requirement but standardization isn't a perfect science.  It can be prone to errors which is why we really have been steering users away from it and toward using geocoding as that process instead. I will also be at the UC so maybe we can sit down and talk about this. Brad ... View more

David, I have a couple questions for you. 1. Is this a new issue for 2.2?  We didn't made many modifications to the locator styles for 2.2. 2. What is the workflow that you are using that requires you to standardize you data?  The geocoding process no longer requires standardization and I would be interested to know how you are using this tool. Brad ... View more

There was a fix installed into 10.5.1 that fixes this.  Can you upgrade? Brad ... View more

You state the following but can you tell me how you went about creating your SD file? "Now, whenever I create a service definition file (without adding data into it) and publish a geocode service, the server does not recognise the locators in the registered directory." ... View more

The street level values returned by the geocoding service are broken down into the smallest level elements and returned in separate fields so the street type, "straat", is returned as part of a separate field named "StType".  You can choose to also return "StType" as another output but another option is to request "StAddr" which will contain the entire formatted string of all street components as well as the house number ("Bosstraat 166" in your case). If you need the street components without the house number, you could always post-process the "StAddr" to remove the value returned from "AddNum" from it. Brad ... View more