Latest Contributions by ShanaBritt

Brian: I apologize for the delay, I've been working to meet some deadlines for Pro development and haven't been able to circle back to this issue. I have an idea I need to test out and will try to get a response to you this week. What I believe is happening is that the abbreviation you are using for 'Circle' in the reference data is not part of the logic in the locator style, so it doesn't know what to do with it. A quick note about the field mapping of the locator in your most recent screen shot... The 'Full Street Name' locator field is not used for address matching, so it is not necessary for it to be mapped to a field in your reference data. The content of the field when mapped is written to the geocode result for labeling if needed. You have a few options for field mapping based on the fields in your reference data. If the "ROAD_FULL" field in the reference data contains all of the street components, it can be mapped to the 'Street Name' field from the locator with no other components mapped (directions, prefix type, suffix type), then map the zone fields like city, state, zip code. If using the US Addresses - Single House Subaddress map "ROAD_FULL" to 'Street Name' and the "UNIT TYPE" and "UNIT NUMBER" fields to 'SubAddr Type' and 'SubAddr Unit'. In the existing locator properties, you could also use the "ROAD TYPE FULL" field to map to 'Suffix Type'. -Shana ... View more

Martin, Are you using Voll, Plz, and Ort fields as the input fields when geocoding? Are you able to show the table field mapping in the geocoding tool you are using so that I can see what fields are being used? ... View more

Are you using Geography or Geometry as the data type for the reference data that is used to build the locator? Does the same behavior occur when building a locator with the Dual Range locator style or General - Gazetteer? ... View more

Rachel: Are you able to provide a screen shot of the locator properties (geocoding options, reference table)? What do the input addresses look like? Are they just the street address (380 New York St) in a single field similar to the illustration in this help topic? http://pro.arcgis.com/en/pro-app/help/data/geocoding/about-geocoding-a-table-of-addresses.htm  ... View more

Martin: Can you show an example of the table you are not able to geocode with the Esri World Geocoder? Perhaps a screen shot of a single row and all of the fields in it. -Shana ... View more

Dave: To clarify, in 10.4.1 are you creating the locator with sql db features as the reference data, but the locator is stored in a folder? Or are you using the data and storing the locator in sql db? If you are storing the locator in the sql geodatabase, it is recommended that you store the locator in a file folder. Which locator style are you using to create the Locator? -Shana ... View more

Brian, For the address that is circled in the screenshot is the street type in the field "CL" or "ci"? I think the value is an uppercase "i" versus a lowercase "L" , which is shown in the locate pane. I created a table with the address in question and found that "jaywin ci" doesn't match in either the table when batch geocoding or in the Locate pane. ... View more

There is a default set of locators that get loaded when you launch ArcMap. These default locators are stored in the DefaultLocators.xml file, where there is a system version and a user specific version. You could add your locator on the network to the list of default locators in the DefaultLocators.xml file, then deploy this file to the end user machines and add it to their system or user location. Once added each time you launch ArcMap the new default locator will be loaded and available for your users in the Find Tool. This also applies to ArcReader and it is recommended that you do not store your address locators in any geodatabase format (file, personal, sde). For more details see this help topic, Setting default locators in ArcMap—Help | ArcGIS Desktop . ... View more

About how many features are in the shapefile that contain all of the streets for all of the counties in the state? What version of ArcMap are you using?  Do you have 64-bit Background Geoprocessing installed? Background Geoprocessing (64-bit)—Help | ArcGIS Desktop , Foreground and background processing—Help | ArcGIS Desktop  The reason I ask about 64-bit Background Geoprocessing is because if you are working with millions of features it is best to run the Create Address Locator tool in the background with 64-bit geoprocessing installed. ... View more

What happens if you just add locator 'E' to the composite by itself? Are locators A-E using the same locator style? ... View more

Bug BUG-000105837 is more of the Server/Enterprise documentation not telling you of the suggestions limitation with geocode services that you create from your own locators. The suggestion limitation was resolved in the Esri World service last June. We will be including info about the limitation for customer created geocode services in the documentation for the 10.6.1 release. Bug BUG-000094346 is regarding invalid house numbers and suggestions, this behavior exists for all of the out of the box locator styles that search for house addresses in 10.5.1 & 10.6, more discussion and details can be found at https://community.esri.com/thread/164282#comment-717731. We are actively working on making the suggestion fixes in the Online service available to customers when they create their own locators and services, but do not have a time frame for when it will be released. If you want to be able to search just on street name and get suggestions for street names, it's recommended to use the Street Name style. I have not seen any reports regarding the geocode service memory leak based on a Single Field locator w/o suggestions. I would still suggest using the Gazetteer locator style to build a locator with suggestions and use it as a geocode service to make use of the spelling logic that is not in the Single Field style. The leak for the Single Field style based geocode service is not resolved for 10.5-10.6. You may find this info helpful for creating a Gazetteer locator https://community.esri.com/people/cdufault-esristaff/blog/2018/03/02/gazetteer-geolocator-best-practices-and-ram-requirements  ... View more

Brian, It would be more helpful if you could provide the locator you created or a screen shot of the Durham locator properties Reference data tables page like the one below and the 'About the locator' page from the properties. You could create a locator package if you wanted to share it here or send it to me in private message. ... View more

Joe, The Match without zone property is the same for Pro. The US Address and General styles are essentially the same in Pro as in ArcMap. There may be times where the Pro version of the style template might be more current than the style included with ArcMap because of the development and release cycle of Pro. ... View more