Latest Contributions by ShanaBritt

Sean: I would suggest going through the steps outlined in the following technical article to disable coordinate search when using the address locator. 44182 - Disable finding latitude and longitude coordinates when using an address locator -Shana ... View more

Jeremy- What you've described is similar to suggestions that can be seen when using the World Geocoding Service in ArcGIS Online or via REST. It is possible to create an address locator at version 10.3+ with suggestions, but in order to use the suggestions the locator must be published to ArcGIS Server 10.3+ and the geocode service will allow you to use suggestions via REST. The geocode service could be used in ArcMap, but suggestions are not supported in the Find tool or Geocoding toolbar in ArcMap. Currently in ArcGIS Pro using the Locate pane you can see suggestions from the World Geocoding Service. At this time the only other offline options would be to use StreetMap Premium locators, which have suggestions built in for the 2015 Release 2 products, so if you were to publish them as geocode services to ArcGIS Server 10.3+, you would be able to make use of suggestions via REST. A local version of the World Geocoding Service called World Geocoder for ArcGIS will be available in the near future for organizations to use offline and behind their firewalls. -Shana ... View more

@David: These scenarios are addressed with the out of the box US Single House Subaddress style that was included with ArcGIS for Desktop 10.3+ and Pro. 2 out of 3 of the scenarios work at 10.3.1 and all 3 scenarios work at 10.4. The address 'A652 N Placer Way SW' is related to a bug that was submitted for 10.3 or 10.3.1, where the prefix direction is getting parsed as the address number suffix and times out and not candidate is returned or something with a score lower than 100. If the input address does not include the prefix direction a match is returned with a score less than 100. There are other threads that reference this bug and other bugs related to the Single House Subaddress style. Single House Subaddress Locator Issues - Possible Bug? Using Single House Subaddress Style Address Locator I've attached a locator package that includes the reference data if you would like to see the behavior and settings used. Use the Extract Package tool in ArcToolbox to extract the locator package and layer package. -Shana Brad Niemand​ Bruce Harold​ ... View more

Oliver, The behavior you are encountering may be related to the bug described here, NIM091041: "Rebuilding or creating an address locator fails for specific enterprise geodatabases." http://support.esri.com/en/bugs/nimbus/role/beta10_1/TklNMDkxMDQx , which was fixed at version 10.3.1. The issue is that the string that is being passed for the index name of the command 'TableCreateLongIndex' doesn't have an index name, so it defaults to the fully qualified object name. If the 16th character happens to end with a period, the index fails to create. If the joined database and owner name of the locator table is truncated to 16 characters that result with a period or any special character at the end then the locator fails to build and the _LOX table is left within the SDE database. For example, the fully qualified name of the locator index table is "CONCORD.SDE.Streets_CreateAddressLocator1_lox", but when the index name is truncated to the 16th character the result is "CONCORD.SDE.Stre", which does not end in a period or special character. The locator is created in this case. However, when the fully qualified name of the locator index table is "CONCORD.SDEUSER.Streets_CreateAddressLocator1_lox", the truncated index name is "CONCORD.SDEUSER." , which ends in a period and the locator fails to create and you are left with the _LOX table. In addition to Joe's response about not storing address locators within an SDE, it is not recommended that address locators be stored in any format geodatabase for performance reasons and if it is to be shared, it should be published to ArcGIS Server and shared as a geocode service. ArcGIS Pro does not support address locators stored in geodatabases and version 10.4+ will not either. -Shana ... View more