Latest Contributions by BradNiemand

John, I would like to know more about your workflow.  Why is your application sending 100 findAddressCandidates calls to the service within 10 seconds?  Are you instead really trying to batch geocode a set of addresses?  If you are trying to geocode a table or set of addresses we would recommend that you use the GeocodeAddresses operation instead of findAddressCandidates.  The GeocodeAddresses operation will allow you to submit up to 1000 addresses as a single input and get all of the geocoded results back for those 1000 inputs. In addition to that, if you will be storing the results in a database you should be using the GeocodeAddresses operation or the findAddressCandidates operation with the forStorage parameter set to true.  This will require a token and will consume credits.  The findAddressCandidates operation with the forStorage parameter set to false (this is the default) is meant to be used for displaying results on the map but not storing them in a database. Brad ... View more

The technical article is outdated and will be removed or updated with current best practices. ... View more

Thanks for reaching out about the issue you are having.  Categories do change from time but the upper level category "Travel and Transport" won't change.  "Travel and Transport" is the top level category that included "Cargo Center". Can your app use "Travel and Transport" instead of "Cargo Center"?  There are many other good categories in that top level category that might be useful for your application.  ... View more

This Idea has been implemented in ArcGIS Pro 3.2. Please see the What's New documentation for more new features in Pro 3.2. The Your Ideas in ArcGIS Pro 3.2 blog and video have been posted to the Esri Community blog. You can take a look at these to see your idea and all others that were implemented in this release of ArcGIS Pro. ... View more

@Mike_Quetel  You are correct in your statement above.  SingleLine is intended to be the entire input address with all relevant information, including the address, city, state, postal, etc...  It was never intended to be used with any of the multiline input fields except for CountryCode.  The fact that it worked before was not intentional and really shouldn't be used.  If you would like to use multiple fields for input, you should be using Address and City instead. You can read more about these parameters for the online service (it would function the same with custom locators as well).  https://developers.arcgis.com/rest/geocode/api-reference/geocoding-find-address-candidates.htm#ESRI_SECTION1_699C8961EDD845CAB84A46409D9E9105   ... View more

Thanks for the quick response. Suggestions are the best way to get quick results without entering the entire address and would be the suggestion from the geocoding team as the best move forward. I did look into your case and it appears that you might be hitting an issue that was already patched.  Can you have the following patch applied to your server?  https://support.esri.com/en-us/patches-updates/2022/arcgis-server-geocoding-service-quality-patch-8082 ... View more

The Create Locator tool will automatically set the "Match with no Zones" property to "Yes" if the locator is built with no administrative zones (city, state, postal, etc...).  The Create Locator tool will default the property to "No" if any administrative zone is mapped when building the locator.  Also, the tech support best practices link you refer to is for our classic ArcMap based locators that are no longer supported in Pro as of Pro 3.0.  This documentation is quite outdated and will be taken down or  updated.  It is strongly recommended to map the administrative zones when building a locator and it is also strongly recommended that the "Match with no Zones" property is set to "No".  With suggestions support in Pro the need for the "Match with no Zones" property is not as necessary because users have the ability to choose the suggested candidate without needing to enter the entire address or place.  Setting "Match with no Zones" to "Yes" should only be done if there is a specific need that requires it. ... View more

The Create Locator tool will automatically set the "Match with no Zones" property to "Yes" if the locator is built with no administrative zones (city, state, postal, etc...).  The Create Locator tool will default the property to "No" if any administrative zone is mapped when building the locator. It is strongly recommended to map the administrative zones when building a locator and it is also strongly recommended that the "Match with no Zones" property is set to "No".  With suggestions support in Pro the need for the "Match with no Zones" property is not as necessary because users have the ability to choose the suggested candidate without needing to enter the entire address or place.  Setting "Match with no Zones" to "Yes" should only be done if there is a specific need that requires it. ... View more

Thanks for posting this question.  You should be using the suggest API to get partial suggestions for input, not the findAddressCandidates API.  Once you get the suggestion you want you would pass the suggest text, magicKey, and all parameters that you passed to the findAddressCandidates API to get the full result.   Suggest API for World Geocoding Service (it will be similar to what you are doing but the software is much newer than 10.7.1 for the online service): https://developers.arcgis.com/rest/geocode/api-reference/geocoding-suggest.htm   FindAddressCandidates:  https://developers.arcgis.com/rest/geocode/api-reference/geocoding-find-address-candidates.htm   You will find some code samples in there that should give you everything you need but let me know if you have any additional questions. ... View more

@HeidiSuna1 One option would be to add those values as a custom output field for now. We can discuss the possibility of exposing Loc_name in a future but at this time it isn't in our near-term roadmap.   Brad ... View more

@HeidiSuna1  What do you use Loc_name field for?  This is mostly used as an internal field so it wasn't originally included in the minimal set of fields because of that.  We could consider adding it but I just want to understand what you use the field for right now.   Brad ... View more

One option you have is to set the Minimum Match Score higher, let's say 99, which is the score that gets used for batch geocoding.  Any candidate that has a score below 99 will be marked as unmatched and they can be reviewed in the Rematch Addresses Pane in Pro after the batch geocoding is completed.  You can keep the Minimum Candidate score lower so that you still get candidates when using interactive geocoding in the Rematch Addresses or Locate Panes. The Minimum Candidate Score controls candidates in interactive searching but does not apply to the batch geocoding process. Brad ... View more

We allow some flexibility when matching to features that are considered nearby.  These 2 postal codes are right next to each other which is why you get a result with a slightly reduced score here. Is the expectation that you get unmatched instead of a nearby candidate with a lower score? There is currently no way to disable matching to nearby results but if this is what you are requesting, an enhancement would need to be submitted through support. Brad ... View more

I would like to know more about the workflow you are using that is giving you slower performance when geocoding. Can you provide more details about the workflow including where the locator is stored when you are using it (Enterprise, local disk, network share, etc..), the size of data for your locators, and how the composite locator order was setup?  Any additional information that you can provide can help us track down why you are seeing this. Brad ... View more