Locators: Why are suggestions different than Results? Make them the same.

[Anonymous User]

Brad Niemand‌ Shana Britt‌

I posted in the other threads, it looks like I have Locators figured out and working now with Suggestions and Units by using Gazetteer. You had suggested this initially for other geocoders e.g. parcel IDs but I have found it works great with house units.  

However, there is still one problem. This appears to be an issue with the way Locators work in general.  If you start typing, you get different results in the Suggestions array than you do if you simply hit Enter to submit the request. This has to do apparently with the magickey.

I will provide an example.  Let's say someone searches for '1 East Bay Street' on my property viewer www.sagis.org/map If you start typing it, the result comes up perfectly (it is actually 1 E Bay in the full address, but the Gazetteer is great, in that it is forgiving with spelling).  However.... if you paste it in or type it quickly and hit Enter... Nope.  No results found. It does find a record as you will see but that's from a completely separate locator which searches by Owner Name. It finds '501 East Bay Street LLC'.  

And remember the Ghost results bug still exists i.e. you can't have a Units locator with Suggestions which for those not fortunate enough to have a single field with Full Address to use for Gazetteer is still a roadblock to using a locator at all.

This is conceptually similar. Suggestions be exactly the same as hitting Enter. No 'ghosts'. And no leaving out correct results as I have found here. I understand the idea was to try to accelerate the result retrieval but I think that these issues trump that in 99% of cases. Perhaps it could be an option to still use the old Enter result retrieval (with its leaving out of some results, like in this post) and perhaps you could leave a legacy style of Locator with Ghosts but I want some way of fixing both of these bugs/product design issues.  For me, I would never choose to have the Results from Enter differ from Suggestions, at all, in any case. It must be the same. Locators are the most important part of nearly all my viewers. Thank you for understanding, and for your continued conversation on locators!

[Anonymous User]

Brad Niemand‌ Shana Britt I don't know if the ArcGIS Pro 2.4.3. update that just released reintroduced this bug it or if I am remembering wrong... I had thought this was fixed. It appears it does not work especially with Units.

I had thought it was working. I simply went to add Municipality and ZIP to the Pro Locator so it would display in the Suggestions so folks would know what muni a result is in. (as our address dataset usually has the most accurate data regarding municipality)  However, I went to Create Locator and mapped all the fields (prefix, suffix, Unit, etc). Unfortunately we do not have state but we do have Municipality and ZIP.  Pro 2.4.3. to server 10.6.1.

I noticed that it just plain doesn't work. It provides only one result. And no Units. This is a serious problem. https://cloud.sagis.org/arcgis/rest/services/Locators/Addressing_MAD_units_Production_Pro_Final3/Geo... 

I called Esri TS and we observed this inside Pro itself.

On the other hand, I had thought it was fixed as above at least with the Gazetteer but when I check the original Locator I published above with Gazetteer Locators/MADLocator_WithUnits_Production (GeocodeServer)  with Enable Local Search (I enabled), it has the bug where it provides completely inaccurate addresses if you enter "1 East Bay Street" and click Enter for example.  Way, way off in location, with results that aren't even spelled similarly.

So it appears either we have complete junk results when clicking Enter in certain rather common examples of what users would type OR we have no Units and only one single result. 

Neither of these scenarios work for a usable locator. This has been logged as an "Enhancement". This is an urgent bug for us I hope is a hot fix or Pro update within a few weeks; compatible with ArcGIS Server 10.6.1.

I am again noticing after adding some locators to my server it's killing my AWS instance. All it does is three sites. Fairly large traffic but it has always been fine.  Only increase in traffic since I updated a month or two back was adding locators with Suggest to it and now performance is abysmal. I will continue to investigate. I think that aspect would be solved if there was such as thing as Hosted locators. (our own locators hosted on AGOL) 

I reviewed this thread Address point role with Units   and we do not have unit types. At this point I do not have ability to add that, either. We need Pro / Server to work with Units and Suggest as soon as possible.  I strive for diplomacy but frankly our customers are not pleased with these confusing issues in terms of simply finding an Address on an Esri viewer. Nearly every city uses Units and Suggest is expected now by users.

So for now, because Gazetteer supports Units and Suggest, even though in edge cases clicking enter returns wrong results I will stick with that, until the Pro locator is finally functional and debugged. The limit of only one result makes the Pro locator unusable. For example 7804 Abercorn St. It should return however many I ask for in Web App Builder. (I set it to 6 results for both suggest and return) so ideally it should provide all the various units at the Mall.

To recap, Suggest works fine searching "110 East State Street" Suggest: (Locators/Addressing_MAD_units_Production_Pro_Final) 

...but no results are found from the Find Address Candidates. https://cloud.sagis.org/arcgis/rest/services/Locators/Addressing_MAD_units_Production_Pro_Final/Geoc...

So, no good.

For Units it is even worse. Even Suggest doesn't work, at all.  There are over a dozen Units that have the base address of 7804 Abercorn.  However, if you search that from the Suggest page it returns only one, single result.  

https://cloud.sagis.org/arcgis/rest/services/Locators/Addressing_MAD_units_Production_Pro_Final/Geoc...

____________

Tech Support Reply:

Hello Kevin,

This is Afiq from Esri Support Services, writing in reference to case number 02462073. I have taken ownership of the case and will be working with you to reach to a resolution.

Thank you for your time for phone call and screen share session yesterday. Based on our discussion, I understand that you need assistance with the address suggestion from Locator in ArcGIS Pro Locate pan.

During our screen sharing session, we tried to create multiple custom locator using Point address roles in ArcGIS Pro. We created a custom locator with unit number but we were not able to find any suggested address by searching for the house number and street name. For example, when searching for 7804 ABERCORN ST, the Locate pane does not provide any suggestion.

Then, we proceed to create another locator without unit number and we were able to find the suggested address in the Locate Pane. However, we did not able to find a specific address point with unit number from the suggested addresses.
 
Furthermore, I created a sample address table from my end to geocode using the locator with unit number and I am able to geocode the address with 100 match score from my end. The addresses are as the following:

• 1037 Cornwall ST.
• 18 Silver Ave #3.
• 18 Silver Ave #4.
• 18 Silver Ave #5.
• 18 Silver Ave #6.

Thus, it seems like the custom locator is working perfectly fine. Then, I proceed to discuss the issue with a senior analyst from my end. Based on our discussion, it seems like the issue occurs due to the limitation on Locator with unit number to display Units in the suggested addresses from the Locate pane.

No worries as the issue has been logged as Enhancement to our developer team. The detail description of the Enhancement are as the following:

• ENH-000124149 - Allow locators built with the Create Locator tool and a Point Address role to return candidates and suggestions for subaddresses when the base address is inputted.
• Status : In Product Plan.

Since the status of the Enhancement is In Product Plan, the capability to display suggested address with subaddress or unit number in the Locate pane in ArcGIS Pro will be implemented in the future release. However, we would like to apologize that we are not able to perovide a specific time frame for the Enhancement to be implemented in future release.

I also would like to provide ArcGIS Ideas URL on "Provide Units in Suggested Addresses" as for your reference:

• Provide Units in Suggested Addresses. (https://community.esri.com/ideas/17064-provide-units-in-suggested-addresses)

Kindly review and vote up the idea to help us to support the Enhancement request.

No worries as I already attached the Enhancement number to the case and you should be able view the status of the Enhancement through My Esri > My Organization > Support > Search for the ENH-000124149

Do let me know if you have any additional inquiries or information regarding to the case, you can reach me directly by replying to this email or calling Esri Support Services at (888)377-4575 followed by your case number reference and you will be routed to me.

Looking forward to your response.

Thank you,
Mohd Afiq Ikhwan
Esri Support Services

[Anonymous User]

When the Create Locator will be fixed to work with Units and Suggest; will it be possible in the next Pro release at 2.4.4? 

[BradNiemand]

Kevin,

Adding support for suggestions for Subaddresses is on our list of work that we will be doing but it will not be in 2.4.4 nor will it be in 2.5 which is already dev-complete and will be release in early 2020.

I would like to provide some detail and background about the two operations, suggest and findAddressCandidates.

FindAddressCandidates is intended to be used with full addresses, not partial addresses.  It does support partial addresses if the entire address portion is entered but the zones (city, state, zip) are excluded ONLY when you pass in either a location or an extent as a parameter to the API.  Using either the location parameter or the extent parameter allows users to search without providing a zone.  Another way to allow for no zones to be entered is to set the property I mentioned to you above, supportsOptionalZone = true, although this property was not implemented prior to 10.7 Enterprise so it would require that version or newer.

Suggest allows for not only partial address input but partial word input as well.  You can enter "110 East St" (to use your example above) and get suggestions back that match that text input.  The two operations are performing completely different functions but do work together hand in hand.  The result returned from the suggest operation is passed in as input to the findAddressCandidates operation to give the user the address they asked for so if you were to pass in the text that you got back from the suggest call of which is "110 E STATE ST, SAVANNAH, 31401" you will actually get back the correct result.

The workaround that you are using to get suggestions back by using the Gazetteer will have limitations that you have mentioned above because that is not the intended use of that locator.

As mentioned above, we recognize that suggestions for Subaddresses is a feature that is important to your workflow and we are working hard to get that feature to you in a future release of Pro and Enterprise.

Brad

[Anonymous User]

All I can say is Suggestions and results from clicking Enter should be the exact same and Units should work. I hope locators will be a top feature update for 2.6.

[GreggRoemhildt2]

Hi Brad Niemand - do you have any guides you can recommend for migrating from the "Classic" to the "New" locators?

[ShanaBritt]

Gregg:

Here are some details to be aware of when migrating from classic locators to new locators.

• New locators are built with the Create Locator tool in ArcGIS Pro.
  • How to create a new locator
    • It is recommended to create locators with administrative zones such as city, state, postal assigned in the field mapping. Region and region abbreviation are also important because they are used to help create different forms of state highways that are specific to each region or state.  Not mapping them can impact geocoding quality and the performance.
    • All address elements should be broken up across multiple fields.
    • It is recommended to use polygons instead of point geometry when building a locator for administrative areas or when building a multirole locator that allows you to search for multiple locations with a single locator like street addresses, points of interest, parcels, and postal codes. Polygons also help to provide better reverse geocoding results. https://pro.arcgis.com/en/pro-app/help/data/geocoding/benefits-of-using-polygons-versus-points-for-a...
  • Can be used in ArcMap when published as a service from ArcGIS Pro to ArcGIS Server or Enterprise 10.6.1 or newer.
    • If Enterprise portal, then Share Locator.
    • If stand-alone (not federated) ArcGIS Server, then Publish Geocode Service.
    • Registering the folder that contains the locator as a data store with ArcGIS Server (federated/non-federated) before publishing the locator will help to reduce downtown when updating the service.
  • Locators are built using locator roles instead of locator styles, an explanation of the locator role fields can be found here https://pro.arcgis.com/en/pro-app/help/data/geocoding/locator-role-fields.htm.
  • A single multirole locator should be created instead of a composite locator in most cases.
  • Suggestions validate the house number against the reference data.
  • Suggestions are available for locators stored locally in the Locate pane in ArcGIS Pro as well as published as a service.
  • Custom output fields can be easily added to the locator you create that reference other fields in the reference data used to build the locator that you want returned in the geocode results, such as fire districts, school districts, or voting districts.
  • Output fields can be turned off and on in the locator properties to reduce the number of fields returned in the geocode result when batch geocoding.
  • Locators that support multiple countries and languages can be created.

[Anonymous User]

Shana Britt‌ are results from pressing Enter and from Suggestions the same, with new newest Locators? (In my testing it did not seem that way)

I discovered a new reason this is a problem. In our Emergency Operations software webEOC, it relies on the method of pressing Enter to get the results array. It does not support Suggestions.  I have found that Suggestions consistently provide more (ie better) results and possibilities.  Can these two lists of results finally be unified? Or is there a way or option to do so?  Thank you.  The status of locators and lack of support for quality results with Suggestions for addresses with Units is a serious issue in multiple areas for us.

[BradNiemand]

Kevin,

As I previously described above, these two operations are different but do work together.  The Emergency Operations software seems like it is using an old approach to populate geocoding results which is why you are seeing the results you describe.  Using suggestions in combination with the FindAddressCandidates API (just pressing enter) is the approach that should be used and is used in all of Esri's interactive clients for geocoding.  It seems like the Emergency Operations software needs to updates to use the interactive geocoding approach of using suggestions in combination with the FindAddressCandidates API.

With regards to suggestions for subAddresses, there is work being done to support this in the near future.

Brad

[Anonymous User]

Hi Brad, do locators still not support subaddress Suggestions in 10.8?

At the end of the day, for us, results from both methods need to be identical.  At least as an option.  Users have said they do not like having different results from the same locator, it has been a problem since 10.3. At least in our viewers and for any and all of my applications, the results need to be identical from both methods of searching. 

Meantime, yes, we need Suggestions for subAddresses and to not to get weird results in wrong locations (I know, that is a limitation on the 'classic' locators; but, they're still the best locators because they work with suggestions and subaddresses, and we will continue using them even with issue of different results from suggestion/Enter and sporadic wrong location from Enter) Also meantime I may begin exploring https://blog.batchgeo.com/open-data-open-source-geocoders/