ArcGIS Pro 2.5.1; Single Role Street Address Locator I created a single role, street address locator and have been using it this afternoon, on a few tables.  Rematching worked just fine for the first few geocoded results, but this latest one is misbehaving.  Typically as I click through the unmatched addresses, I can make an edit to the address, hit the tab key, followed by the Apply button and get either suggestions or not.  Now, when I make the edit and then hit tab, apply, it kicks me back to the first record of the unmatched stack.  See gif below.  What is going on here? ... View more

I have published a geocode service from a composite locator which was created via the create locator tool in ArcGIS Pro 2.6.1. The Locator covers the entire state of New Jersey so it includes nearly 4 million address points along with road centerlines. With that being said maximizing performance has been a big issue. I have a table of address that I batch geocode in ArcGIS Pro as part of the performance testing. This table takes me 4 minutes and 30 seconds to complete. I noticed however, that when I leave out the state from my inputs the table takes 56 seconds to complete. The state values are all NJ in the input data used to create the locator and they are all NJ in the table I am batch geocoding. I am curious why there is such a big difference in performance and how I can assure that faster performance is achieved by our users. I could leave the state values out of my input data or provide guidance to users to not enter a state, but neither of these are ideal.  ... View more

I am using the create locator tool in Pro 2.6 and I have noticed that only the input city name and alternate city names are suggested to a user. Is there a way so that after a user has typed a house number and a street name suggestions can also be pulled from the neighborhood or zone field to better utilize initial input data rather than having to add a bunch of alternate table records?  ... View more

ArcGIS Pro 2.6 I'm having a problem when using an Alternate Name Table in the Alternate Street Name Role for a Point Address Primary Role. Here is a snippet of my alt street names table: In the 'FullAddress' field is what the actual address points have as the full address; the address points also have each of the address components parsed out in individual fields. Using the Using the locate tool, the locator seems to function as expected:  if I enter an address shown in the column called 'Alias' I get the expected returns.  However, after creating a table of just the addresses listed in the alias column above, Only 3 of 590+- return a match.  I'd be okay if none of them matched (well, not really) but why would only 3 match when everything is formatted the same way? Shana Britt‌ ... View more

I tried everything. I have a table with a common id field and can't get it work. Thinking about creating another centerline dataset to include the shape.  ... View more