Latest Contributions by ShanaBritt

If you added a definition query to the reference data used to build the locator, the Create Locator tool will only build the locator with the selected features. You would also get an indicator next to the Primary Table parameter letting you know how many features are selected. If you selected features manually, select by attributes, or select by location, the Create Locator tool would build the locator based on the selected features. No addresses outside of the selection or definition query could be found. ... View more

@ChelseaRozek The Geocode capability that you see when publishing from ArcGIS Pro 3.5 or 3.6 to ArcGIS Enterprise 11.4 or earlier means that the geocode service will support geosearch (FindAddressCandidates operation) and batch geocoding (GeocodeAddresses operation). A change was made to allow users to publish a geocode service that only supported geosearch (FindAddressCandidates capability) or to only support GeocodeAddresses operations. If both Geocode Addresses and Find Address Candidates are selected, then the service supports both by default. This change can also be seen for utility services in Online and Enterprise portals. If you published from 3.6 to 11.5 or later with the new default capabilities and went to ArcGIS Server Manager and checked the Geocode capability you would be duplicating capabilities. Can you provide more details about your application that is broken unless you check the Geocode capability in ArcGIS Server Manager? What is the application based on? What does the application do? Is the app based on an esri solution or app? ... View more

When the Rematch Addresses pane is active, what ever selections are made in the attribute table of the geocoded feature class will be reflected in the Rematch Addresses pane. So if you could query all of the records using Select By Attributes, only those selected records would be reflected in the Rematch Addresses pane. You can also use Control+F in the table attribute view to find the record number and select it in the table and have the selection be reflected in the pane. ... View more

@GeeteshSingh07 How is the locator used that you have created with the Create Feature Locator tool? Is it used as a service in a web application? Is using a feature service to search against an option for your workflow? There is the option of configuring your utility assets for search in the project, then publishing the map as a web map and using the feature services for search in the web map. https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/find-places-on-the-map.htm#ESRI_SECTION1_8D7E58B952164AFFB41E80B3D8ABF74C ... View more

If you have already done the field mapping once and run the Create Locator tool, you can go to the History pane and do one of the following: 1. Open the previously run tool and adjust the field mapping and run the tool again. 2. Right-click the previously run tool and select save as Geoprocessing package. This will package up the tool settings and data used in the tool. You add the geoprocessing package to your project and go to the History pane to see the previously run tool and open it to rerun the tool with the same data. https://pro.arcgis.com/en/pro-app/3.5/help/analysis/geoprocessing/share-analysis/use-a-geoprocessing-package.htm 3. Right-click the previously run tool and select to save as Python or a Model. https://pro.arcgis.com/en/pro-app/3.5/help/analysis/geoprocessing/share-analysis/what-is-a-geoprocessing-package-.htm https://pro.arcgis.com/en/pro-app/3.5/help/analysis/geoprocessing/share-analysis/create-a-geoprocessing-package.htm ... View more

@JohnNergeBrooklynPark The workaround I suggested does not involve using the ArcGIS Geocoding service, you would be using your custom locators for rematch in the Rematch Addresses pane. Step 2 allows you to use the existing locator and just map a new field to use for geocoding or you can select a brand new locator for the rematch/review workflow. There is no way around having extra input address fields when the composite consists of a locator created with the Create Locator tool and the Create Feature Locator tool. If you removed the extra input fields when building the composite locator, the locator would be invalid and not work as expected.  Having more context for how you are using the locator in your workflows helps to better understand  your needs and identifying a suitable workaround.  ... View more

@JohnNergeBrooklynPark @shildebrand , I was able to figure out a different workflow using the Rematch Addresses pane to address geocoding a table formatted like below using either a multirole locator or a composite locator of locators created with the Create Locator tool. In this case the multirole locator would use the  PointAddress and Parcel roles.  https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/rematch-locations-converted-from-a-table.htm 1. Geocode the table with the multirole locator using SingleField, mapping the ServiceAddress field. 2. Open the Rematch Addresses pane and Select Add or Modify Locator from the Locators drop-down menu. 3. Map the Single Line Input field to the ParcelNumber field. This maybe the IN_ParcelNumber field depending on what Output Field option was chosen when geocoding the table originally. 4. Click the back button to go to the main pane 5. Click the Menu burger button > Predefined Queries > Unmatched Addresses or create a custom query.  6. Click the Auto Rematch button to rematch the selected records. ... View more

Short answer is if you publish a composite that contains locators created with the Create Locator from Pro to 10.9.1 you will get all of the input fields and you would not be able to change this. If you attempted to remove the unwanted fields in the composite, the locator wouldn't work as expected. The locators created in Pro with the Create Locator tool will always have the Address, Address2, Address3... input address fields, which will carry over to the composite locator because the participating locators have all of the input address fields. So if you publish the composite the contains locators created in  Pro with the Create Locator tool, you will get the input fields Address, Address2, Address3... when published to 10.9.1 or 11.4. You would see the same fields if you published one of the participating locators created with the Create Locator tool to 10.9.1 or 11.4. The locators created in ArcMap or with the Create Address Locator tool have different input fields that will show up in the composite locator. Those locators have fewer input fields that would show in the composite locator. So when the composite is published to 10.9.1, there are fewer input fields you would see on the REST endpoint page.  ... View more

@ScottFedak2085 Would the Search Within functionality described in the following blog meet your needs? The results are not suggestions, but candidates  like POIs near an address or at the same location like a shopping plaza or business park. Search Within and Uncover More Matches ... View more

@GeeteshSingh07 It would be helpful to have the data to understand what is going on with the data. Are you getting an error or warning in the Create Locator tool when building a locator with this line data? Are you not able to run the Multipart to Singlepart tool on the data, then build the locator? Logging a ticket with Support would be your test option and to include the data. ... View more

1. If you have a multirole of StreetAddress and the Parcel roles, where ParcelName is mapped to PIN, do you experience the zoom issue? 2. What is the purpose of a Parcel role locator where ParcelName is mapped to the property address "123 Main St"? Is the same parcel polygon data used for this locator the same used for the Parcel - PIN locator? Mapping the street address to the ParcelName field is not going to create an optimal locator using the Parcel role. The street address components should be broken up into separate fields. You can use the Split Address Into Components tool to parse the PROP_STREET field into individual address components . There are illustrations of what can be searched using the Parcel role. You also have the option to create the Parcel - PIN locator and set PROP_STREET as a custom output field so that when you search for the PIN, the PROP_STREET value will be included in the output. When you create the composite with a mix of multirole and single role locators you should use the Result Order option in the properties that is to order the results by role and score, which gives the same fallback as a multirole locator. ... View more

Thanks for the additional info. 1. Is the parcel data point or polygon? Are you also mapping the Parcel Name field along with STREET, CITY, STATE, and ZIP for the Parcel role?  2. When you create a multirole locator of StreetAddress and Parcel and search for an intersection you experience the zoom issue? 3. Do  you get the same behavior if t he precision type of the locator is Local Extra High or Global Extra High? 4. If you have a composite of a StreetAddress role and Parcel role locator do you encounter the zoom issue? Just to confirm, you are using ArcGIS Pro 3.5 to build the locators?   ... View more

@AaronManuel2 You can create a multirole locator using the Parcel role for the PIN and POI role for the owner name. You would be able to search for either PIN or Owner Name. You can also use your original idea of creating a Parcel role locator  for PIN and POI role for Owner Name locator and adding them to a composite locator. Is your goal for the locator to use it for single address/owner name search or for batch geocoding a table? ... View more

@Robin Have you tried with a feature class in a file gdb? What locator are you using to search for places in the Locate pane? What happens at Step 4 if you select 'Create new feature class` that is in a file gdb. ... View more

@ChelseaRozek Thanks for sharing the field mapping and coordinate system of the street centerline data used to build the locator. I see that you have a multirole locator in the screenshot, does it also include any alternate name tables that would be listed on the Alternate Name Tables tab in the locator properties? If there are no alternate name tables that are part of the locator there is no need to map the Street Join ID locator role field. Including the FeatureID role field is only necessary when you have duplicate geometry in the primary reference data that have different attributes like different street names. When you do use the FeatureID field the field  you map to it should not contain unique IDs like the ObjectID field. Mapping the FeatureID field when you do not  have duplicate features with different attributes will increase the size of the locator, impact the time it takes the build the locator, and can affect the performance of the locator. See the following topics for more info: - https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/collapse-duplicate-features-in-the-data.htm - https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/locator-role-fields.htm The Full Street Name field is also not necessary to map when building a locator for the USA as this field is not used for address matching. 1. What is the Precision type of the locator? This is on the 'About the locator' tab of the locator properties. 2. Have the side and end offsets been modified? This is on the Geocoding options tab > Match options section 3. Is the multirole locator from the screenshot added to a composite? 4. Does the same behavior occur with a single StreetAddress role locator? 5. Is all of the data used in the multirole locator in the same coordinate system? ... View more