Latest Contributions by ShanaBritt

Joe: The original behavior you described seems odd to me, would you be willing to share the data you used for the behavior you encountered so that I can get a better understanding of the issue?  Also, the info I provided about the primary and alternate name table schema needing to match was specific to the classic locators created with the Create Address Locator tool. I've created a new locator with the Create Locator tool and an alternate name table and only mapped the fields that contained values in the alternate name table and was able to successfully locator the address on the alternate street name. ... View more

Susan: 1. Did you use the Create Address Locator tool to create the locator that is giving you the problem when opening the properties? Which locator style was used to create the locator? 2. Is the locator you are opening the properties for stored on your local machine or are you accessing it from a network location in your organization? 3. Do you get the same behavior with a locator that was created with the Create Locator tool? 4. Do all of the locators that have been loaded and added to the project show up in the Locators folder on the Catalog pane before you try to access the locator properties? 5. Do you get the same behavior if you access the locator properties from the Locate pane Settings tab?  ... View more

Richard: Have you attempted opening the attribute table of the geocode result while using the Rematch Addresses pane? It will help in conjunction with using selection queries and the new 'Match all selected' button, which is described here https://pro.arcgis.com/en/pro-app/help/data/geocoding/rematch-locations-converted-from-a-table.htm#ESRI_SECTION1_092AD2A116A84598A29BD5639C87AC33. The upper section of the Remtch Addresses pane updates as you make selections in the attribute table of the geocode result. I will add this request to our backlog. ... View more

ArcMap 10.5 had major changes the address the address locator styles that were included out of the box, this also added alternate city name tables. However, for the 10.5 release the Dual Ranges style did not include both sides. I believe we added the functionality at 10.6 or 10.6.1, below is a screenshot from 10.6.1. It is important to upgrade whenever possible and recreate the locators as we have fixed and made enhancements to the locator styles between releases. ... View more

Joe and Michael: It would be best that you submit your data through Support so that a bug can be logged. Without the data and the documented bug we cannot star investigating this behavior during the next ArcGIS Pro development cycle and identify why it's failing. I've tested the Create Locator tool in Pro 2.4with different datasets and not encountered this error. ... View more

Joe, Yes, I've seen people parse out the input address table they want to geocode so many times over the years. ... View more

It is weird that the Create Address Locator tool does not have an issue with the point feature class. Is the geometry type in the Shape column 'Point' or 'Multipoint'? You will likely need to submit a support ticket to send the data along for further investigation if you are not able to figure out what's wrong with those 2500 features. ... View more

Joe: The part of the matrix you circled is related to searching the address, which needs to be in a single field for batch geocoding. The reference data needs to have the address components broken up into multiple fields as illustrated in the table image in the Subaddress section of the PointAddress role. The roles matrix is no different from the styles matrix https://desktopdev.arcgis.com/en/arcmap/latest/manage-data/geocoding/commonly-used-address-locator-styles.htm. ... View more

Joe: What is the projection of the point features? Does the point feature class support m-values? Can you provide a screen shot of the field mapping? ... View more

Joe: Glad to hear that you nixed the intersection point locator for a centerline based locator. The new locators created with the Create Locator tool has improvements for intersections with the StreetAddress role. I would also encourage you to create a single multirole locator with the Create Locator tool in Pro instead of a composite to stitch together multiple locators. If you create a multirole locator, either manually create it then export the tool results to a Python script from the History tab of the Catalog pane; or build a model in Model Builder that can be rerun when reference data changes and you only have to map the fields once.There are some cases where you might need to create a composite like if it is a landmark or point of interest locator and you have multiple geometry types and need to use the same role, like POI for instance. If you are using the General - Single Field or General - Gazetteer style to create a locator with the Create Address Locator tool, you can create the same locator with the Create Locator tool using the POI role and make use of your own categories that can be used for searching specific categories or to limit the search to specific categories, similar to the ArcGIS World Geocoding Service. ... View more

Joe: It was true in the past, pre 10.x, that it was necessary to parse the street name into individual fields in the reference data before building the locator with the Create Address Locator tool, but that is not the case anymore as during the build process the street name is getting parsed into the individual components and stored in the index as parsed. A join occurs between the primary feature class and alternate name table and the number of fields need to match is what I mean by the schema. In your case the primary table had 5 fields and the alternate name table had 4 fields and the number of fields should match between the two. ... View more

Rickey: What version of Pro are you using? What are you searching for with the Gazetteer locator? What is the order of the locators in the composite locator? What version of Server was the locator published as a geocode service? If you use the Create Locator tool in Pro 2.3+ to create a locator using the StreetAddress role, similar to Dual Ranges style, you will be able to get the result you are looking for. The StreetName role allows you to search for addresses, intersections and street names. If the street segment does not have house number values associated with it or is null a street name match will be returned versus street address match. ... View more

I tried to reproduce you behavior when published to 10.5 and 10.3.1, but was not able to. Perhaps it was the way my locators were created. I see that you only have Street and Single Line Input as options for all three services. Were the Dual Range and Single House locators created without city, state, zip mapped? ... View more

Kevin: Are the locators you are going to publish to Server 10.6.1 locators created with the Create Address Locator tool or the Create Locator tool. You will only be able to solve the suggestion problem by creating locators with the Create Locator tool, which will return suggestions in the Locate pane as well as when published as a service. https://pro.arcgis.com/en/pro-app/tool-reference/geocoding/create-locator.htm https://pro.arcgis.com/en/pro-app/help/data/geocoding/introduction-to-locator-roles.htm https://pro.arcgis.com/en/pro-app/help/data/geocoding/tips-for-improving-geocoding-quality.htm ... View more