Latest Contributions by JeffRogers

The ArcGIS Geocoding team are currently working on a solution for improving suggest results for locators organizations build from data.  We are targeting the solution for release for the first half of 2019.   ... View more

This looks like a similar issue to issue #181310. The ArcGIS Geocoding team is aware of this issue, it was a limitation of the original implementation of the suggestions capability.  We have already implemented a new suggestions strategy (which is available to test in the current release of the World Geocoding service).  The new strategy verifies the house number as you type and only shows address suggestions for addresses with a verified house number.  If the house number cannot be verified it shows a suggestion for a street name.  We are working to support this new suggestions strategy for locators that organizations build with ArcGIS.  ... View more

The ArcGIS Geocoding team is aware of this issue, it was a limitation of the original implementation of the suggestions capability.  We have already implemented a new suggestions strategy (which is available to test in the current release of the World Geocoding service).  The new strategy verifies the house number as you type and only shows address suggestions for addresses with a verified house number.  If the house number cannot be verified it shows a suggestion for a street name.  We are working to support this new suggestions strategy for locators that organizations build with ArcGIS.  ... View more

Aaron, it looks like this would be much simpler if ArcGIS locators supported suggestions offering the same out of the box capabilities as the ArcGIS World Geocoding Service.  Esri is actively working on adding suggestions capabilities for locators organizations build from their own address data.  Look for this new capability for locators built with ArcGIS 10.3 and hosted with ArcGIS Server 10.3. Jeff ... View more

If the message is just not showing up, then I haven't seen the issue before, my suggestion is to report it to Esri Customer Service so they can trouble shoot and potentially offer a solution or address it in an update. ... View more

Josh when you hear the beep do you see a message like this one...or is there just a beep? ... View more

Josh, it looks like you tried to attach an image of the issue your seeing?  I am seeing  [ATTACH=CONFIG]34422[/ATTACH], any chance you could reattach the image? ... View more

I recommend you try building the locator using the "General - Single Field" locator style. This style is more appropriate for Parcel IDs. ... View more

Josh, do you see a geocoding service description to the left of the address box?  Something like World Geocode Services?  Could you describe what you see? ... View more

Renee, tied means that there are two or more equal candidates for an address.  In Los Angeles for example there is one city name "Los Angeles" and within this city there may be 50 postal codes.  If you provide an address such as 123 Figueroa St Los Angeles, there may be 10, 123 Figueroa St in Los Angeles but each of these could be in a different postal code.  When a address includes less than all the information required to uniquely identify it, it may match to more than one candidate address.  We call this situation a tie. ... View more

Yes, we need a bit more information.  Could you please describe the locator that you are trying to geocode against.  Where it came from, if you know, how it was built? ... View more

Thanks to all who have contributed to this thread.  It looks like there is interest in better methods for filtering geocoding results.  Much of this thread is tied to the Esri geocoding fallback strategy.  If an address such as 380 New York Street Redlands California isn't matched at the point address or street address level then there is an interest in identifying this and ignoring the fallback results which might land at a postal code or city match. In these cases (postal code or city) the Esri geocoder provides a 100% match score for the postal or city part of the match, but not an overall confidence for the full address match relative to what it matched to.  So, two things the Geocoding team are working on to help "address" these challenges.  First we're developing a new parameter for the World Geocoding Service API.  The "Category" parameter will support service side filtering of results.  You'll be able to make a fine grained request to return a street address match or a city or postal code match, or any combination of address levels.  The parameter will be supported by a detailed set of categories for filtering across address, place and POI searches.  This should help reduce post filtering in your applications.  One other area we are looking at is developing an overall confidence score for a match.  If the input is 380 New York Street Redlands CA, and the match is to Redlands CA, we could return a an overall confidence confidence score scale such as 47%.  So we would be (100%) confident that we matched to the city of Redlands but less confident 47% that we matched to the full input address. We're interested if you think this would help with your current challenges or if there are any other ways you think we could improve filtering of results. Esri Geocoding Team ... View more