Latest Contributions by ShanaBritt

‎09-29-2020

Chet: Is the result you are getting from a locator built with Create Address Locator tool or Create Locator tool? If you use the Create Locator tool, there are some additional settings in the properties to account for alternate street name, Additional tuning options—ArcGIS Pro | Documentation. It would be helpful to see the field mapping in the tool for the primary and alternate table.

‎09-28-2020

Stephanie: Just to clarify, you used the Create Locator tool to create two locators and added them to a composite locator and not the Create Address Locator tool to build the locators in the composite? Do either of these locators have any alternate name tables linked to them? For better performance I would suggest creating a multirole locator with the Create Locator tool instead of multiple single locators added to a composite locator. I would also make use of the tips to improve performance described here, Tips for improving geocoding performance—ArcGIS Pro | Documentation . Can you provide any details about the field mapping and any geocoding options set in the participating locators in the composite? Are there any IDs like for street that could be used to link the points to the street centerlines? -Shana

‎09-28-2020

John: Thank you for the feedback and explanation of your use case. Currently, the offset is fixed and unchangeable, but we are targeting a future release to support editing these properties. What is the requirement for the 'Match if best candidates tie' property? Do you not want ties automatically matched? In the Rematch Addresses pane you can view only the tied results by clicking on the Tied tab and manually review only those tied. When the property set to True the ties would automatically be set as unmatched instead. You would then need to go through ALL of the unmatched records to see if any can be matched as tied instead of just looking at the tied ones.

‎09-28-2020

Chet: When you build the locator do you map the same address component fields in the primary as you do in the alternate name table? In the screenshot you posted on the 9th it looks like the alternate name table only has 'Street Name' mapped. The same number of address component fields need to be mapped in both the primary and alternate name tables in order for the alternate name table to work when using the Create Address Locator tool to build the locator, because having a miss match causes the join not to work. If you only mapped 'StreetName' and 'StreetType' in the primary and only 'AltName' in the alternate name table the join will not work, thus the alternate name table won't work. You would need to map StreetType in the alternate name table as well. I would also try to create the same locator in the Create Locator tool using the StreetAddress role and try to transition your locators to the new locators in ArcGIS Pro as 2.6 is the last release that the Create Address Locator tool will be available in Pro.

‎09-18-2020

Chet: How far off are the address matches from where they should be? Is your locator a single role or multirole locator? There are some additional options that can be set that were added to ArcGIS Pro 2.6 for preferred names for city and street names, see Preferred street name for more details.

‎09-15-2020

Ingrid: What version of ArcGIS Pro do you have installed? What version of Enterprise did you upgrade from? Is ArcGIS Pro and Enterprise Portal installed on the same machine? -Shana

‎09-11-2020

Chet: Since your data is in sde you won't be able to use the Check Geometry tool, you will have to use topology rules to check for the geometry errors that the tool looks for. If you have edit privileges or are able to edit a version of the data, you can check for multiple parts with the Must Be Single Part rule. This link also has a list of the rules for line features. If you upgrade to Pro 2.6.1 and run the Create Locator tool again with the same data, do you get a different error? -Shana

‎09-09-2020

Joshua: The Parcel Join ID field is used to link Parcel records to PointAddress records to minimize duplicate geocoding results. It sounds like you are trying to create a multirole locator that consists of the Parcel role and Point Address role and linking these two roles together based on Parcel Join ID will minimize duplicate results when you search and will not return. There are a couple of ways to get what you are looking for if I understand what you have described. 1. You can build a locator based on the PointAddress role and add a custom output field for the parcel id and map the field from the point data to the custom output field. Then when you geocode the address the parcel id will be part of the output fields. 2. You can build a locator based on the Parcel role where you map Parcel Name and the address related fields, which will allow you to search for just the parcel name (apn), the address of the parcel, or parcel name + address. If you include the address elements the output will include the address when you search for the parcel name. 3. Build a multirole locator with Parcel (optionally, you can map the address elements) and Point Address roles and link the roles based on Parcel Join ID and this will allow you to search for either parcel id or address and reduce duplicate results. For more info on locator role fields, parcel role, and linking in multirole locators see the following topics: - Locator role fields—ArcGIS Pro | Documentation - Parcel role - Combine multiple data layers into a single locator—ArcGIS Pro | Documentation

‎09-09-2020

Sean: If you are using ArcGIS Pro 2.6 and you set the field aliases in the reference data to build the locator to the field names listed in Locator role fields—ArcGIS Pro | Documentation topic, the Create Locator tool will assign the reference data fields to the locator role fields automatically.

‎09-09-2020

Chet: The yellow messages are warnings and if you were using Pro 2.6 I believe that warning message would have a link to a help topic for more explanation, but it looks like an issue with the street data is causing an error with building the locator, not the warning about the empty value for one of the records. Run the Check Geometry tool on your data to see if there are any geometry errors. If there are multipart features or true curves in the data, the tool will fail to build the locator. Which version of Pro are you using?

‎09-03-2020

Chet: What was the error that you received? -Shana

‎09-03-2020

Chet: You can use the following topics to help with creating the locator. The locator created with the Create Locator tool in Pro cannot be used in ArcMap unless it has been published from Pro as a service. When in the Create Locator tool you will need to use the StreetAddress role and map ID from the centerline layer to StreetJoinID. Then expand the optional parameters to see the alternate name tables parameter and chose the alternate name table role of Alternate Street Name and set Street JoinID to StreetID in the alternate name table. Create a locator—ArcGIS Pro | Documentation Create Locator (Geocoding)—ArcGIS Pro | Documentation See the preferred street name section of Additional tuning options—ArcGIS Pro | Documentation -Shana

‎09-02-2020

Chet: Sorry I misspoke, the relate is what you needed to do in order to see that the aliases were linked to the street layer. 1. If you have access to ArcGIS Pro it would be interesting to see if you are successful with creating the locator with the alternate name table and the uppercase values. 2. If the values in the alternate name table are in the same case as the street centerline data does searching for alternate names with the locator work? 3. Does your alternate name table look similar to the images in this topic for alternate street name? Fundamentals of alternate name tables—ArcGIS Pro | Documentation

‎09-02-2020

If you are still encountering this behavior, please provide your exact steps that can consistently reproduce this problem. This will be helpful for us to find a solution as I've not been able to reproduce the behavior. Based on some of the posts there look to be different paths to getting the Rematch mode to be stuck in a bad state. -Shana

‎09-02-2020

Eric: If you still have locators that were previously created in ArcMap that are similar to the locators that crashed Pro when you opened the properties, please submit them and your steps to Support as a bug. If you are unable to log a Support ticket you can direct them to me offline. It looks like this type of crash has been reported multiple times and we'd like to fix it and understand what about the locators caused the crash. -Shana

Online Status	Offline
Date Last Visited	3 weeks ago

My Ideas

Latest Contributions by ShanaBritt

Re: Does the Alias street name or alternate table need to include a shape?

Re: Including the state in input address fields significantly slows down performance when batch geocoding with the Geocode Addresses tool

Re: ArcGIS Pro, Locator Properties, Options have all but gone away

Re: Does the Alias street name or alternate table need to include a shape?

Re: Does the Alias street name or alternate table need to include a shape?

Re: Sharing Locator to Portal: Where does locator get stored?

Re: Does the Alias street name or alternate table need to include a shape?

Re: What does the Locator Parcel Role ParcelJoinID do?

Re: How do I configure address source to automatically match in Create Locator Pro tool address elements in each role?

Re: Does the Alias street name or alternate table need to include a shape?

Re: Does the Alias street name or alternate table need to include a shape?

Re: Does the Alias street name or alternate table need to include a shape?

Re: Does the Alias street name or alternate table need to include a shape?

Re: ArcGIS Pro stays in geocoder rematch mode

Re: Locators created in ArcPro/ArcMap compatibility issues

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...