Latest Contributions by BradNiemand

Jeff, Would you be able to provide more information about your locator and environment?  From what I can tell from the screenshot it looks like you have a composite locator and it is published to Enterprise, correct?  If so, what version of Enterprise are you using? Any information about your composite locator would also be appreciated.  One key here is what tool was used to create the participating locators?  Was it the Create Address Locator tool or the Create Locator tool? Lastly, did you retry with Pro 2.9 and if so were you successful geocoding with that version?  I see you tried with ArcMap and didn't see the same issue. Brad ... View more

Jeff, Either Shana or I will respond to you in that thread. Brad ... View more

I would like to point something out that you may not be aware of.  Minimum match score (MMS) is used for batch geocoding (Geocode Addresses, Geocode Table, etc...).  You can set MMS to 96 and then set Minimum Candidate Score (MCS) to 85 before you publish your locator.  This configuration will return more candidates in interactive geocoding but still retain a high threshold of 96 when performing batch geocoding.   Minimum Candidate score - This is used in interactive geocoding (Find Dialog with show all candidates enabled, Locate Pane with show all candidates enabled and the Rematch dialog).   Minimum Match score - This is used when batch geocoding (Geocode Addresses, Geocode Table, etc...).  It is also used as a cutoff for interactive geocoding if the show all candidates option is not enabled.   As @ShanaBritt mentioned above, some settings are exposed in the interactive rematch workflow to allow for more flexibility when rematching. ... View more

My name is Brad and I work on the geocoding team at Esri. I would be interested to find out what the reason is for not moving to the new locators at this time.  Have you had a chance to test them out yet?  They have lots of benefits over the classic locators and I would be happy to help you through the migration process if you are interested. Thanks, Brad ... View more

Dan,   What I mean by "adding an address at build time" was potentially adding a checkbox to the Create Locator tool to allow for the point address to be added when building the locator.  As mentioned above, there are some challenges with that approach that could cause unexpected or even erroneous geocoding results.   Brad ... View more

Dan,   Thanks for the feedback.  There is no requirement (although it is recommended) to have a base address when using partial subaddress suggestions or even when requiring the entire subaddress to be entered in order for the suggestion to be given.  This is also true for searching without suggestions.  The base address is only required for the new features that show a list of subaddress suggestions or the subaddress info.   The reason that the base address is required for showing a summary of the units at a base address or a list of the subaddresses at a base address is because the base address is what triggers this functionality.  The base address must exist for this to work.   There are also challenges with just adding a base address at build time.  There would have to be assumptions made when building the locator in order to add the base address at build time and could cause unexpected or even erroneous geocoding.  This is why the base address is required for this new functionality.   Brad ... View more

Rajaa, There is no way to change the input field aliases but we can take this feedback and look into integrating it into our locators.  As for removing input fields, we have a standard set of input fields for all locators built with the Create Locator tool.  We don't exclude any and there is no way to do it on the user side without writing a custom app that only exposes the fields you want shown. One other question.  Are you sure you have your operating system regional settings set to English (Canada)?  There are field aliases for State = Provence and Zip = Postal already and these should work as expected. Brad ... View more

Rajaa,   The REST endpoint you are showing above will always have the field names displayed, not the field aliases.  The REST page is meant for debugging and was never intended as something that would be localized which is why you just see the field names, not aliases.  When working in Pro you should see names that are localized based on the language pack and OS region so I would expect you would see the localized names if your operating system has Canada regional settings.   As you can see from the image below, the field aliases show up with US names instead of the generic names you see the in REST page. If you are creating your own application using the REST API, you can get the localized names for the inputs from the service description: https://geocode.arcgis.com/arcgis/rest/services/World/GeocodeServer?f=pjson Brad ... View more

I would be interested to know the workflow you are trying to accomplish in more detail.  Matches to StreetMidBlock have a specific type of input that contains "Block" or "Block of" at the beginning of the search string.  Are you essentially trying to force an unmatched result instead of a fallback to StreetName?   Brad ... View more

What do you mean by "address # suffix suggestions"?  It is not clear to me what you are asking for. Brad ... View more

Thanks for the feedback. I would like to ask some additional questions that might help clarify the workflow that you are trying to accomplish. 1. What benefit does providing a list of arbitrary units at a base address provide to the user who is typing in the address?  It would seem to me that if the user didn't know the unit that they would like to find, providing a list of units at the base address provides little benefit to the user but maybe some clarity on how this is beneficial to the user would help with this. 2. What order should the results be in if we were to support this workflow?  Should they just be the first 5, 10, 15 units at the location (depending on the max suggestions setting)?  If so, it would seem that the user would only start getting suggestions they cared about after entering in some information to whittle down the suggestions to something more applicable. 3. If the user was to set the max suggestion setting to something quite large, I would argue that they may spend more time scrolling through the suggestions to find the unit that they are looking for instead of just entering a character or two to get suggestions that were more applicable. I look forward to additional feedback related to this workflow. Brad ... View more

You are probably looking at some time in November. Brad ... View more

ArcGIS Pro enables "local search" when zoomed in to a local area.  By default I believe Web App Builder does not have this setting on.  You can enable it and suggestions and geocoding will function similar to how they work in Pro. More information can be found here:  https://doc.arcgis.com/en/web-appbuilder/create-apps/widget-search.htm  Brad ... View more

The geocoding team is constantly adding features and looking for ways to improve the existing technology so newer versions of the software may function slightly different than previous versions.  The Pro 2.8 release will function very similar to its corresponding Enterprise release which is Enterprise 10.9. The Enterprise server would need to be upgraded to 10.8.1 at a minimum or 10.9 to be similar to the Pro 2.8 version.   Brad ... View more

What version of Pro was the locator created in.  It may require you to recreate the locator to get this functionality.  If that is not the case, I think this may warrant a support issue. Brad ... View more