warice

Web App Builder Search Widget NOT returning correct results with Composite Locator

Discussion created by warice on Aug 27, 2016
Latest reply on Apr 21, 2017 by rozekc_washtenaw

Subject:  Web App Builder Search Widget NOT returning correct results with a 10.4.1 Composite Locator for some input street intersections:

 

With our ArcGIS Online Web App Builder Applications, we use a Composite Address Locator geocoding service published from ArcGIS Server version 10.3.1.   Within the past month or so, the behavior of the Web App Builder Search Widget has changed to that the Search results are returned to the widget apparently in ASCENDING order by Match Score instead of the traditional sorting of the match results in DESCENDING order by Match Score.  The result of this change, is that when a user initiates a Search, the widget incorrectly selects and zooms in the map to the candidate with the LOWEST score!   This incorrect, broken behavior is partially improved if one uses a Composite Locator published with ArcGIS Server 10.4.1.  However, even with a 10.4.1 Composite Locator, the Web App Builder Search widget still incorrectly generates just wrong combinations of candidates for some input street intersections.  For example, in our community, if the intersection "20TH ST & 27TH AVE" is entered, the Search Widget correctly returns ONE result.  However, if I enter "7TH AVE & 12TH ST", then the Search Widget is returning such combinations as "79TH CT & 128TH ST" and "78TH AV & 126TH ST".  If the match results were returned in DESCENDING order by Match Results like they have ALWAYS been handled by ArcView 3.x and ArcMap 9.x, and ArcMap 10.x, then the Web App Builder Search Widget would have a chance at returning the correct results. 

Outcomes