Latest Contributions by ShanaBritt

Joe: I haven’t heard too much yet and what I have heard was about the output fields and wanting to know what they mean. -Shana ... View more

Mikkel: Do you also encounter the same behavior in runtime if using the Single Field style with the intersection points? Just to clarify when you tested the composite and individual Gazetteer locator in ArcMap was that with the local locator or the geocode service via an ArcGIS Server connection? Do you encounter the same behavior when using the composite or solo Gazetteer in ArcGIS Pro? -Shana ... View more

Have you tried using a Dual Range locator based on street lines for the intersections rather than a Gazetteer for the intersections and use the Dual Range in runtime? The Gazetteer style was not intended to address intersection searches and the geocoding rules associated with the Gazetteer style expect an exact match. Do you encounter the same behavior when the Gazetteer is the only locator used in runtime?  ... View more

Courtney: In order to determine what is causing the problem with the alternate name matches I would need to see the address locator properties that show the field mapping in the Reference data section of the locator properties dialog. One technique that I use to determine if the JoinID is working correctly with the primary feature class and alternate name table is in ArcMap create a relate between the feature class and the alternate name table based on the JoinID used when doing the field mapping when creating the address locator. Then search for the primary address with the Find Tool (locations tab) and use the Identify tool to click on the feature the address was matched to. The Identify Results window will show the related records to that feature so that you can see the associated alternate street name. ... View more

George, Is this still an issue with a more current version of ArcMap like 10.3 or higher? ... View more

Mikkel: What version of ArcGIS Desktop and Server are you using? What type of locators participate in the composite locator that was published and used in runtime? Do you get the same behavior with the composite geocode service when used outside of runtime like the map viewer for ArcGIS Online? ... View more

JK: The information in the help topic you found does contain the information that you need to include your geocode service as a default locator in ArcMap. The example just above "Editing system default locators" in the Setting default locators in ArcMap—Help | ArcGIS Desktop help topic is the format you need to use and there is no need to create a new workspace factory. Also, within the DefaultLocators.xml file there is an example for ArcGIS Server locator that you can use to setup a REST geocode service in ArcMap. Below is the example from the DefaultLocators.xml. <!-- ArcGIS Server locator--> <!-- <locator_ref> <name>MyArcGISServer</name> <display_name>My ArcGIS Server</display_name> <workspace_properties> <factory_progid>esriGISClient.AGSServerConnectionFactory</factory_progid> <ags_connection_properties> <machine>ServerMachine</machine> <user>ServerUser</user> <encrypted_password>EncryptedPassword</encrypted_password> </ags_connection_properties> </workspace_properties> </locator_ref> --> ... View more

Is it not possible for customers to use the address locators included with StreetMap Premium Europe? ... View more

Brandon: The USA_ZIP4_LocalComposite locator included with Business Analyst will return a match for just 46975-8008 in the address " PO Box 111, rochester, IN 46975-8008". There is no zip4 information associated with the PointAddress and StreetAddress locators that participate in the USA_ZIP4_LocalComposite locator. The possible candidates you would get back would be from the Zip4, PostalCode and AdminPlaces locators. -Shana ... View more

Kristi: What version are you planning to upgrade to? Are you able to provide a small subset of the data that includes the streets in question? ... View more

William: The suggestions that are returned for geocoding services are only suggestions for the street name and do not include suggestions for the house number as a suggestion index for the house number is not generated when the address locator is built. The house number suggestion that you see could be any house number that is valid for features that has the same street name. If the geocode service is based on the Single House Subaddress style, you will get suggestions for the subaddress, but the subaddress suggestions are not correlated to the house number. You would also get subaddress suggestions that are valid for the street name, for example, if you had point features that represented 123 e main st with subaddresses A-F and 150 e main st with subaddresses A-D, then typed in the address "150 e main st " to get suggestions for the subaddress , the subaddress F would show as a suggestion because it exists at 123 e main st. This is because the subaddress is not correlated to the house number, but F is considered a valid subaddress for the street name suggestion of "e main st". At version 10.5 if you select the invalid subaddress is selected in the map viewer no results are returned and if used in ArcGIS Pro, no candidates will be returned in the results list of the Locate pane. This behavior is as designed.  BUG-000090968 - US Single House Subaddress locator shows suggestions for houses with units that don't exist. BUG-000094346 - The 'suggest' operation of the REST application programming interface (API) returns a suggestion for invalid street addresses that do not exist. https://developers.arcgis.com/rest/geocode/api-reference/geocoding-suggest.htm#ESRI_SECTION1_F4600031F2F44E44ACE0989325BC9E0D BUG-000100204 - When the Suggest operation is enabled on an address locator geocode service with over 1,000,000 records, the geocode service will suggest addresses that do not exist. Creating an address locator—Help | ArcGIS Desktop  -Shana ... View more

Chelsea: If you had a FULLNAME field in the primary table and in the alternate name table and only mapped those two fields when building the address locator, you should get matches for the alternate names. The field mapping between the primary table and alternate name table need to match in order for the query between the two tables to work. Shana ... View more

Matthew: Do you get the same behavior with the Subaddress point locator in ArcMap that you do with the published service in the web app? Does the same behavior occur when the point locator is based on the US Address - Single House style and published to ArcGIS Server? -Shana ... View more

Dave: Perhaps this blog will help you better display the points.  Displaying coincident points | ArcGIS Blog  -Shana ... View more