Latest Contributions by ShanaBritt

Does the same error occur when geocoding the spreadsheet in ArcGIS Pro with the custom locator you created? What role did you use to build the custom locator? https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/create-multicountry-locators-using-country-and-language.htm ... View more

@JohnNergeBrooklynPark The fix for the Category parameter to work with composite locator service was addressed in ArcGIS Pro 3.2. ... View more

The input fields of the composite needs to match the input fields of the participating locators in order for the composite to be valid for batch geocoding. If you were using the single locator to search for addresses in the Geocode Table tool, the same 10 input fields would show and  the user is expected to map the relevant fields from their input table. The same applies to composites, the input fields from the participating locators are going to show as the input fields in the batch geocoding tools, but removing the input fields that will not be used for geocoding will cause the composite to be invalid and batch geocoding will fail. ... View more

@wgreen7423 Are you using ArcMap or ArcGIS Pro 2.6 or earlier to create the composite locator? It sounds like you might be using the Create Address Locator tool to build the locators in your composite, what are the locator styles used to build those locators? Does your street data only contain the street name components and no  house number ranges? If you have access to ArcGIS Pro 3.0 or later you could use the Split Address Into Components tool to split the  address in the ParcelAddr field into individual address components, then use those fields to build a PointAddress role or Parcel role locator with the same data using the Create Locator tool. If the parcel data has a parcel ID that field can be mapped to the Parcel Name field that would allow you to search for the parcel ID. If the street data doesn't have house number ranges, then only StreetName candidates will be returned by the locator when you build the locator with the StreetAddress role, which is not as precise as StreetAddress candidates. https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/create-a-locator.htm https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/tutorial-create-a-multirole-locator.htm   ... View more

Have you considered creating a multirole locator over  using a composite locator? The multirole locator will reduce duplicate results and returns the most precise candidate. A composite locator does not have this functionality and will return duplicate candidates for the same location. https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/combine-multiple-layers-into-a-single-locator.htm https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/tutorial-create-a-multirole-locator.htm     ... View more

@Craig_Eissler_Iceman Is the input table in your scenario the result of geocoding a table previously? What is your entire workflow? ... View more

Is the Parcel name the only locator role field that is mapped for the primary role? Does the primary parcel data not have address info associated with it and why you are using an alternate name table? What are the results when you search for an address in the Locate pane or geocode a table? Have you tried joining the table with the addresses to the primary parcel data using the Parcel ID, then building the locator? Then reverse geocode.   -Shana ... View more

You do run into duplicating data and would want to have IDs for the duplicates to collapse them as described in the following topic, https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/collapse-duplicate-features-in-the-data.htm. The other option is to create a PointAddress role locator with the address point layer and a PointAddress role locator with the state polygon parcel layer and then combine them in a composite locator. If the address point layer has the parcel ID you could set that as a custom output field, the same for the parcel based locator, then when  you geocode the result will have the parcel id in one of the output fields. ... View more

@JessMiller1 What locator was used to geocode your table? If you are using a custom locator based on reference data that has a projection of NAD_1983_StatePlane_North_Carolina_FIPS_3200_Feet, then the locator will output the result in that coordinate system. The coordinates in your screenshot are US Feet. There are a few things you can do : 1. In the Geocode Addresses dialog specify a different coordinate system for the output.   2. If using the Geocode Addresses geoprocessing tool, click environments button and expand output coordinate system and specify a geographic coordinate system 3. You could use the Project geoprocessing tool to reproject the geocode result to a geographic coordinate system like WGS 1984, then use the result in the Add XY Coordinates tool. ... View more

@GeoGuy99 What format are you trying to export the shapefile to? Are you getting any errors in Pro when attempting to export the shapefile? ... View more

@RobertCox87 One option is to start with a new project that contains the data you need and add the USA locator to the project, then create a project template. When you start a new project select the template you created and the USA locator will be available. ... View more

Which tool was used to create the locators that are in the composite? The bug is related to locators based on polygon features that are published as services and not zooming to an appropriate scale or extent in the Map Viewer compared to the local composite in ArcGIS Pro. It was reported at 10.9.1. If you are up to date on maintenance you should be able to search for the bug number in myesri or the Support site. The only workaround found was to convert the polygons to points and rebuild the locator with the point data, but this might not be feasible for some.   polygon based locator published as a service and used in ArcGIS Pro and the map not ... View more

In order to rename the "locator" in the web map rename the layer in the Contents pane in ArcGIS Pro before configuring it for search and publishing the map to the portal. Regarding the zoom behavior, were you experiencing this with a local locator in ArcGIS Pro or with the locator published to Enterprise portal used in the web map or? If published was the published locator used in ArcGIS Pro. If it was published was it a single role locator that referenced polygon data or a composite locator that consisted of locators based on polygon data? I'm asking to try and figure out if you are running into BUG-000162951, which is not reproducible with Enterprise 11.2. ... View more