Latest Contributions by ShanaBritt

Chet: If you are trying to create a locator that supports alternate street names, the street centerline feature class must include a shapefield and the alternate name table should have an objectid. Both the street centerline and alternate name table should have a common field that is used to join the data together. What application and tool are you using to build the locator? ... View more

Eric: Thanks for sending the dmp file, hopefully we find some useful details within it. It's possible you may need to submit this problem to Support and get a bug logged and include as many steps as possible. 1. Are you able to recreate the old locators with one of your models in ArcMap? If so, do they also cause an error in Pro? 2. If you are not able to look at the properties of the old locators in ArcMap, you could open the *.loc.xml of the old locator in an XML or text editor to see the version of the old locator, below 10.7 is highlighted. -Shana ... View more

Olivia: I will need to look through the ideas to see if there is one for better navigating the Rematch Addresses pane and get back to you. It is possible to use the attribute table of the geocode results to select, sort, and navigate and see those changes reflected in the Rematch pane. The Rematch pane is contextually tied to the attribute table. Select rows or run queries directly on the table to update the records displayed in the Rematch Addresses pane. In the examples below I geocoded a table in the Geocode Table pane and started the rematch process when prompted. The Rematch Addresses pane opens and automatically opens the attribute table of the geocode result, which is new for Pro 2.6, and whatever selections you make in the attribute table of the geocode result will be reflected in the Rematch Addresses pane. 1.  2.  3. Select one record in the geocode result and it's reflected in the Rematch Addresses pane. ... View more

Part of your request exists in ArcGIS Pro. It is currently possible to create a local locator with the Create Locator tool that references data stored on ArcGIS Online or Enterprise portal.  ... View more

Part of your request exists in ArcGIS Pro. It is currently possible to create a local locator with the Create Locator tool that references data stored on ArcGIS Online or Enterprise portal.  ... View more

Kevin, when you say you rebuild the locator do you mean you create it again with the Create Locator tool or use the Rebuild Address Locator tool? ... View more

Eric: It is very odd that a locator created in ArcMap would be corrupted when used for geocoding in ArcGIS Pro.  1. Did you get an error in Pro when geocoding with the locator created in ArcMap? 2. What version of ArcMap are you using? 3. What version are the ArcMap locators? 4. Locators created with the Create Locator tool in Pro cannot be used in ArcMap in any way unless it has been published as a service and the service is used in ArcMap. The locators must be published from Pro to Portal or standalone ArcGIS Server. The error you received while trying to look at the properties of the locator created with the Create Locator tool in Pro is expected. 5. You should be able to use the Find tool in ArcMap or the geocoding toolbar to locate an address while you wait for a table to batch geocode. 6. The ArcMap model that references the new locator created in Pro will not be able to access the locator. 7. Please send your crash dump in for the crash encountered when trying to open the properties of the ArcMap locators. -Shana ... View more

Brian: I would encourage you to submit an enhancement request through Support or ArcGIS Ideas. -Shana ... View more

Marni: Are you still encountering this behavior? If you have ArcGIS Pro available to you, try creating a similar locator using the Create Locator tool and use the StreetAddress role, which is similar to the Dual Ranges locator style used in the Create Address Locator tool. You will not be able to use this locator created with the Create Locator tool in ArcMap unless it is published to ArcGIS Server. ... View more

Joe, have you tried using the Distance Marker role yet when you build a locator with the Create Locator tool? Primary locator roles—ArcGIS Pro | Documentation  ... View more

What's interesting is that I can reproduce the behavior in Pro 2.6 with a classic locator built with the Create Address Locator tool, but cannot in ArcMap 10.8.1. A locator in Pro created with the Create Locator tool does not exhibit this behavior. I do get results when I map city when building the locator with the Create Address Locator tool and use city in the search for the intersection when street type is included in the street names for the intersection. Perhaps there is some issue or difference with 'Match with no zone' in Pro versus ArcMap. We'll need to do some additional investigation to understand why this is behaving this way in Pro. That being said... Melisa, is there a reason you cannot move forward with using the new StreetAddress locator in your workflow versus the classic locator? ... View more

Chet: Just curious, what tool did you use to create the locator you are using to search for the intersections? Was it in ArcMap or ArcGIS Pro? -Shana ... View more

Shawn: Which tool did you use to create the locator you are running into this problem with in ArcGIS Pro? What is the score for the matched candidate? -Shana ... View more

John: I'm surprised you did not get the following error when building the locator with the Create Locator tool in ArcGIS Pro, as multipart features are not supported. 002957: Geometry type for '' is not supported. Supported geometry types are: ''.—ArcGIS Pro | Documentation  -Shana ... View more

Brian: Thanks for providing more details surrounding your usage of side offsets in your workflow. Is it possible to perform a spatial join between the street data and the service area polygons using the search radius parameter set to your offset value you'd like to use to join the service area attributes to the the street segments? If this is possible, when you build the locator with the Create Locator tool, you can add a custom output field in the tool under optional parameters then map the service area attribute(s) to the new custom output field in the field mapping. The value from the custom output field will show in the outputs of the geocode results when you geocode the table. -Shana ... View more