Latest Contributions by ShanaBritt

Unfortunately, there is nothing else that you can do to clean up what you are seeing at the REST endpoint for the geocode service that is published from a locator created with the Create Locator. The additional languages are there so if the service is used in an app that needs to be translated the input fields will show as translated. At this time when publishing a locator as a service from ArcGIS Pro the service description content is not populated, you will have to go into the ArcGIS Server Manager and edit the item description section of the geocode service, then save/restart the service to apply the update. The summary and tag information that you fill in on the Share Locator or Publish Geocode Service pane in Pro will populate the summary and tag info of the service when published.   ... View more

Joe, I just want to clarify that when you map multiple Address fields in the geocoding tools that during the geocoding process those input address fields are concatenated, so in this case it would be address + parcel id as the input address instead of address and parcel id being separate inputs. A good example of using multiple address fields is when the input table has separate fields for address and subunit, where you can map the field that contains the address to Address and the field that contains the subunit to Address2. Or if you had the house number in a separate field from the street name, the house number field would be mapped to Address and the field with street name mapped to Address2. ... View more

It looks like Mark was able to answer this question for you in https://community.esri.com/t5/arcgis-pro-questions/quot-create-locator-quot-quot-create-feature-locator-quot-error/m-p/1027425?search-action-id=12529141026&search-result-uid=1027425. Locators created with the Create Feature Locator tool or the Create Locator tool using the Parcel role and packaged in a mobile map package aren't supported in all versions of the Explorer App and you'll need to use the FieldMap App.  If you absolutely need   to use the Explorer app and include locators in  your mobile map packages, create the locator in ArcMap with the Create Address Locator tool, however Pro 2.7 is the last release these locators will be included when creating a mobile map package. ... View more

All, I have been able to reproduce the behavior in Pro 2.7 and the team will look into for a future release of ArcGIS Pro. I will look into a possible workaround workflow and post the steps.  If I am able get a suitable workaround workflow I will post it. ... View more

What version of ArcGIS Pro are you using when reviewing the geocode results? Are you reviewing a selection of the geocode results? Is Auto Apply checked in the Rematch Addresses pane? ... View more

Does the behavior occur with a custom query as well vs the defined queries like 'Matched addresses with score below 80'? Are you also using the tab key without Auto Apply checked on? ... View more

Chet: That configuration looks good. For the address matched out of range what was the value in the Addr_type field for it? If it is 'StreetAddressExt', this means you will need to turn off the Match out of range property in the Geocoding options in the locator properties. Then the input address would not be matched and you'll have to review the addresses. ... View more

Chet: If you add Street Prefix Direction and Street Prefix Type in the field mapping for Primary table it will match the same field mapping you have in the alternate name table, you should get results when searching for the alternate names in the alternate name table. The problem you are encountering is a known bug, NIM102407, which you can search for on the support site. -Shana ... View more

Chet: The problem is as I described above where  you don't have the same address component fields mapped in the primary as you do in the alternate name table (NIM102407). In the primary you have 'STREETNAME' and 'STREETTYPE' mapped, but in the alternate name table you have 4 address components mapped... prefix direction, prefix type, street name, and suffix type. You need to have the same number of component fields mapped in both primary and alternate name table. The ones in red need to be mapped in the Primary table, the values can be empty. ... View more

Robbyn: When you click the Explore drop-down, are there any options checked? If not, check one of the first three options in the list, then try to identify a feature. ... View more

Stephanie: What is the reasoning behind preferring a lower scored PointAddress? It is interesting that the PointAddress match is lower than the StreetAddress match. Given the additional information you provided about the alternate city and street name tables, I believe that an issue with linking the alternate city table in the two locators maybe the cause of the poor performance. Is the alternate city table formatted like the following or are there duplicate city names in the alternate name table? If there are duplicate records in the alternate city table it can create additional records that are not needed in the locator, which causes the locator to perform slowly because it has to search through the additional index to find the best match. This is multiplied across both locators, which causes the composite to perform slowly as well as the individual locators. ... View more

Joe, it is possible, but not recommended if you are able to combine all of your data for a single role together. Better performance is achieved with a multirole locator and being able to minimize duplicate results. ... View more

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