Latest Contributions by ShanaBritt

John, Check out my responses in the following thread. https://community.esri.com/thread/230989-address-locator-106-release-fails-to-locate-intersections-of-numbered-streets#comment-847156 ... View more

Devon & Brian There have been a few issues that have gone through Support related to this issue and perhaps you can reach out to Support to get attached to either of these BUG-000119849 BUG-000111399 BUG-000105332 The reason I suggested using Pro 2.3 to create the locator with the Create Locator tool using the StreetAddress role is because this tool creates new locators that do not exhibit the problem you are running into. They also provide valid house numbers for suggestions, improved intersection and reverse geocoding results. However, I don't believe Spillman can use the new locators directly yet, which is why I suggested adding them to a composite locator. If you do choose to go the route of creating the locators with the Create Locator tool in ArcGIS Pro 2.3 and add them to a composite locator, open the composite locator properties in ArcGIS Pro and uncheck the box 'Use Multithreading'. ... View more

Lindsey: Do you know what release of StreetMap Premium you are using? Did you specify a distance value in the Reverse Geocode tool? Do you get any results using the Address Inspector with the StreetMap locator when you click on one of the points in the shapefile in ArcMap w/o ET GeoWizards? ... View more

Casey: Since you are using 10.7 to create the locators, the county field is not used for matching the address, it is returned as additional output information for the matched candidate. You could probably get away with mapping CO_NAME to the state fields from the locator style. Otherwise, the best option is to use the Create Locator tool in ArcGIS Pro 2.3 to create a locator that would use county as input for matching addresses to candidates and not just for additional output in the geocode result. Is it not possible for you to use Pro just for locator creation? The locators created with the Create Locator tool in ArcGIS Pro will allow you to return suggestions with valid house numbers locally and as a service in web applications. ... View more

Kyle: The Create Locator tool will allow you to create a single locator that references multiple datasets, but you can only use a role once in the locator. So you could have a single locator based on the PointAddress, StreetAddress (includes street ranges, street names, and intersections), and Postal roles. You would be able to test out the suggestions in the Locate pane of Pro without having to publish the locator as a service. ... View more

What version of ArcMap are you using? In the individual locators is county name field in the reference data mapped to the County field from the locator style when using the Create Address Locator tool? Are you trying to use county name as input to be used to find address candidates? Do you have access to ArcGIS Pro 2.3? When you create a locator with the Create Address Locator tool and select a locator style there is a locator field for county that you can mapped to your reference data. This field is not used for matching addresses, it is only returned as part of the output or geocode result as additional info that is part of the matched candidate. Since County is not part of the input of the individual locator, it does not have anything to map to when you add the new field. If you have access to Tech Support, it may be better to share your locators with them to see the field mapping of the individual locators and styles. ... View more

Kyle: If you would like to get suggestion behavior similar to what you are finding with the ArcGIS World Geocoding Service, I would suggest creating a locator using the Create Locator tool if you have access to ArcGIS Pro 2.3. The following resources should help with using the tool: https://pro.arcgis.com/en/pro-app/help/data/geocoding/create-a-locator.htm https://pro.arcgis.com/en/pro-app/help/data/geocoding/introduction-to-locator-roles.htm https://pro.arcgis.com/en/pro-app/tool-reference/geocoding/create-locator.htm ... View more

BUG-000120760 is specific to composite locators that contain tw or more locators that were created with the Create Locator geoprocessing tool. This is NOT an issue for locators that were created with the Create Address Locator tool, that have been added to a composite locator.   ... View more

Lindsey: Did you create the locator that is being used to reverse geocode your points? If so, which tool was used to create the locator? What application are you performing reverse geocode? What are your settings for reverse geocode? If there is no data that is referenced in the locator that is near the location of the points in the shapefile, the reverse fields will be empty. ... View more

Definitely make sure the spreadsheet name, worksheet name and field names do not contain spaces, special characters other than and underscore and do not start with a leading number. If possible, you may also want to try saving the xlsx to the older xls format and try using it in Pro. There are some limitations with using Excel spreadsheets in ArcGIS Pro that are described in the help system, https://pro.arcgis.com/en/pro-app/help/data/excel/work-with-excel-in-arcgis-pro.htm ... View more

The LocationType parameter is available in ArcMap and Pro in the Geocode Addresses gp tool as Preferred Location Type. Routing Location is equivalent to 'street' and Address Location is equivalent to 'rooftop' in the REST API. In the ArcMap example below I've made an ArcGIS Server connection to the ArcGIS World Geocoding Service and using it in the Geocode Addresses geoprocessing tool. In the Pro example below I'm signed into ArcGIS Online. ... View more

Devon: Did you get your issue resolved through Tech Support? If you have access to ArcGIS Pro 2.3 I would suggest using the Create Locator tool using the StreetAddress role and adding it to a composite locator and use it in the Spillman application. I'm not sure if the locator created with the Create Locator tool will work with their application or not, but there is no change in the composite locator that you create with the Create Composite Address Locator tool in either ArcMap or ArcGIS Pro. ... View more

Robert: Are you using the World Geocoding Service or your own geocode service? If it is your own geocode service, which tool was used to create the locator that was published? If your addresses are matched with an Addr_type of PointAddress the XY and Display XY fields will be different. The values in the DisplayXY fields will be the rooftop coordinates. If the address was matched with an Addr_type of StreetAddress the XY and DisplayXY fields will have the same values for side of street. ... View more

Jennifer: If you are using Excel spreadsheets as the input table for geocoding the following help topic will help get you on your way. https://pro.arcgis.com/en/pro-app/help/data/excel/work-with-excel-in-arcgis-pro.htm Here are some other resources for tables: http://desktop.arcgis.com/en/arcmap/latest/manage-data/tables/defining-tables.htm#GUID-C2CB2F27-352A-48A2-A863-F9E45DBD11E9 -Shana ... View more

Kevin, The 10.7 Custom Output Fields for Geocoding Patch is now live on the Support site at https://support.esri.com/en/download/7693 ... View more