Latest Contributions by ShanaBritt

‎01-05-2016

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

‎01-05-2016

Dave: I'd have to have some examples of addresses that do not work and the locator if possible to be able to answer why somethings work and others do not. If something does not work, is it both with the original locator and with the geocode service created from it? Do you have the locator style that was used to create the existing address locator? The style would be stored in the C:\Program Files (x86)\ArcGIS\Desktop10.0\Locators folder. What are the other fields that are part of the address locator below the postal codes? -Shana

‎01-04-2016

Dave: From the looks of the screen shots it looks like you are using ArcGIS Desktop 10.0 or earlier. Please post a screen shot of the dialog after clicking the Advanced button at the bottom left of the Locator Properties dialog as well as the information on the left pane below the Left Post Code. This should give an indication of the version of the address locator and help determine if the locator was customized. The address locator styles that are shipped with the product are for USA address formats only. What version of ArcGIS Server was the locator published to as a geocode service? Is the service that is returning an error publicly accessible? If so, can you provide the link? -Shana

‎12-10-2015

Michael: Unfortunately, we were not able to complete fixing this issue for the 10.4 release of the software. We are currently working on resolving the issue and target fixes for the next available release of the software. -Shana

‎12-09-2015

ArcGIS For Desktop 10.3 includes a new Single House Subaddress style that you can use and map the unit info in field A to the SubAddrUnit component when you build the address locator. http://desktop.arcgis.com/en/desktop/latest/guide-books/geocoding/commonly-used-address-locator-styles.htm#ESRI_SECTION1_7FC7CD744FDA4D379399C92D109FA67Ahttp://desktop.arcgis.com/en/desktop/latest/guide-books/geocoding/commonly-used-address-locator-styles.htm#ESRI_SECTION1_7FC7CD744FDA4D379399C92D109FA67A The subaddresses for multi-unit occupancy can be stored in 2 sets of elements – Building type/Building Unit (optional), and SubAddrType/SubAddrUnit. These components can be used for any 2 sets of subaddress components if users prefer, for example, Level 4 Unit 21, or Terrance C Door 6. It is common that only SubAddrType/SubAddrUnit is used to support simple unit information such as Apartment 101 or Unit A. Building Type (optional) – Building Unit (optional) – SubAddr Type – SubAddr Unit Examples: 30 Pecan Dr Block B Unit 105 5 Gilman Ave Apt 17

‎12-08-2015

Brian: You could use the steps outlined in the following technical article to add the domain codes to the CityAliases section of the locator grammar. You would add the city name and the alternates would be the domain values, so the input address could be the city name or the domain code. 45322 - Add city aliases to the address locator style

‎12-08-2015

Locators built with suggestions should be stored in a file folder rather than in a file or enterprise geodatabase, primarily for performance reasons. The error message 001741 shown in the second screen shot is the result of storing the locator with suggestions enabled in a geodatabase. By storing the locator in a file folder you will also be able to make use of the 'number of threads' performance setting. In the next release of ArcGIS Desktop and in the current release of ArcGIS Pro locators stored in a geodatabase is not supported. The best way to share the locator would be to publish the locator stored in the file folder as a geocode services to ArcGIS Server and use the service by making a GIS Server connection to it in ArcMap/ArcCatalog. Other options are to make the geocode service available in your portal if you have Portal for ArcGIS.

‎12-07-2015

Alex: If the upgrade does not resolve the issue, reopen your case with Esri Support Services and they can continue to troubleshoot the issue with you. -Shana

‎12-07-2015

Ia, Is the address locator being stored in SDE or in a file folder? Are you able to provide a screenshot of the tool settings or inputs for the tool? -Shana

‎12-07-2015

What is the result when you enter the address in the Full Address parameter? 2284 Flora St, 45219 What is the behavior when using the published locator in ArcMap with the Find tool, which is the equivalent to the FindAddressCandidates REST operation? -Shana

‎10-12-2015

Azizul: Have you tried saving the address locator to a file folder instead of the file geodatabase? Was there an error code when the tool failed? -Shana

‎10-07-2015

Kevin: Glad to hear everything is working as expected with the out of the box Single House Subaddress style that is new with ArcGIS for Desktop 10.3. -Shana

‎10-01-2015

Kevin: Which style did you use to build the locator that you are now having success with? US Address – Single House or US Address – Single House SubAddress? -Shana

‎09-29-2015

Jared: I looked up the address on the USPS Look up Zip code tool and received the following details for the address and it looks like the 'ND' that was returned could be some sort of Mailing Industry code for sorting the mail. Go to the following link and click the 'Show Mailing Industry Details'. https://tools.usps.com/go/ZipLookupResultsAction!input.action?resultMode=1&companyName=&address1=1725+STOUT+FIELD+EAST+D… This link to the USPS Address Information Systems product goes over most of the headings that show in the Mailing Industry Details, https://ribbs.usps.gov/index.cfm?page=address_info_system -Shana

‎09-23-2015

Tim: I'm glad I was able to help and that you were able to get what you needed to in order to be successful. Have a great day! -Shana

Online Status	Offline
Date Last Visited	Thursday

My Ideas

Latest Contributions by ShanaBritt

Re: Address locator showing up as LOX table in SDE

Re: Geocoding service not working stable, often generate error or wrong results

Re: Geocoding service not working stable, often generate error or wrong results

Re: Geocoding Houses with Units

Re: Geocoding Houses with Units

Re: Domain Values in Address Locators

Re: error 000622 and 000110 create locator address(suggestion) arcgis 10.3

Re: US Dual Ranges Address Locator ArcGIS Server Issue

Re: error 000622 and 000110 create locator address(suggestion) arcgis 10.3

Re: US Dual Ranges Address Locator ArcGIS Server Issue

Re: Geocoding: Address Locator Problem

Re: Single House Subaddress - Not Recognizing "Hwy" as "Highway"

Re: Single House Subaddress - Not Recognizing "Hwy" as "Highway"

Re: Alphanumeric Zip+4 in US?

Re: Create Address Locator in older version

Re: Geolocate addresses tool in arcpy

Re: Composite Locator added to AGOL is no longer G...

Re: Address locator takes 20x longer to rebuild in...

Re: Pro crash-out trying to rebuild address locato...

Re: ArcGIS Server Locator Fails To Geocode Full Ad...