Latest Contributions by ShanaBritt

@WalidAlmasri1 , When sharing or publishing a locator based on the Street Address role that supports custom offsets and intersection connectors with the Create Locator tool in ArcGIS Pro 2.7 or later, you must be signed in, with publisher or administrator privileges, to ArcGIS Enterprise10.9 or later with at least one federated server to maintain the settings. The note on the following help topic lists functionality and Server versions that support various features. https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/share-a-locator.htm The default intersection connectors like (&, @, |, and \) should work in Enterprise 10.8.1. Do you get the same results in ArcGIS Pro when searching for the intersection in the Locate Pane? What are you using as an intersection connector? ... View more

Just to clarify, you want to use the field alias for the Postal input field in your REST request or you don't want to include postal code as part of the input address? ... View more

@viaplanning You could try creating a locator in  ArcGIS Pro with the Create Locator tool using the Distance Range role, but  you may need to add the road name unless you use Roadway_ID as the street name. When you geocode the table the result will be points.  https://pro.arcgis.com/en/pro-app/3.0/help/data/geocoding/create-a-locator.htm   ... View more

@RyanBohan Does the same behavior occur if you just launch the Geocode Addresses tool from the Geocoding toolbox with the same settings and geocode the table, but then open the previously run tool from the History pane? ... View more

@BradleyMcCallum I believe the error you are getting is because when the composite was created Input fields were removed and the composite locator requires that all of the input fields from the participating locators are part of the composite input fields. When the input fields in the field map section are removed the number of input fields of the composite does not match the number of input fields in the participating locators. If the input field mapping is Multiple Fields, you will get the error, but if the full address is in a single field in the table and the Input Address Fields parameter is set to Single Field, you should not get the error. To confirm this I need to know  what the input parameters for the Geocode Table pane or Geocode Addresses tool when geocoding the table?   ... View more

What tool are you using to geocode the table? Which StreetMap Premium locator are you using in ArcGIS Pro (the name of the locator)? What version of ArcGIS Pro are you using? If you are using version 3.0, the classic StreetMap Premium locators are no longer supported as they are deprecated. ... View more

@Anthony_R_McKay Have you tried using what is described in step 4 in the Rematch tutorial for the unmatched addresses? Are you using a locator you created to geocode the locations? https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/rematch-locations-converted-from-a-table.htm   ... View more

What version of ArcGIS Server was the locator published to? Does the same behavior occur if "5001 ZEAMER AVE, 99506" is passed as the value in the 'Address' field? Does the same behavior occur when using the local version of the composite in the Locate pane of ArcGIS Pro? ... View more

@RandyKreuziger1 In ArcGIS Pro how did you create the XY Event from the Excel file? Did you use the https://desktop.arcgis.com/en/arcmap/latest/tools/data-management-toolbox/make-xy-event-layer.htm in ArcGIS Pro or the XY Table To Point (Data Management)—ArcGIS Pro | Documentation tool? In ArcGIS Pro 2.9 I can create a layer from an Excel spreadsheet using the Make XY Event Layer tool and configure fields in the layer for search and get results returned. I also get results returned when searching all layers in the map, https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/find-places-on-the-map.htm#ESRI_SECTION1_086B92BF080B46B1A414A9A98D4346E3. https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/introduction-to-finding-places-on-a-map.htm The Locate pane in ArcGIS Pro can be used to search for features either in specific configured layers or tables, all layers in the Contents pane, or addresses and locations using locators, or coordinates. It is not the same code as the Find tool in ArcMap. Can you give me more specifics on your workflow? ... View more

Has anyone in this thread moved on to building locators in ArcGIS Pro using the Create Locator tool? If so have you had better outcomes with suggestions or subaddress results? Are you still encountering the problems that you mentioned throughout this thread? Resources: Tutorial: Create a locator—ArcGIS Pro | Documentation Tutorial: Create a multirole locator—ArcGIS Pro | Documentation Tutorial: Create a locator with more than one dataset of the same role—ArcGIS Pro | Documentation Locator role fields—ArcGIS Pro | Documentation Subaddress as part of PointAddress role info  Suggestion options ... View more

@RandyKreuziger1 @Clayton-Cooley I think the issue is that database views do not have ObjectIDs and there are limitations to what you can do with data that do not have ObjectIDs such as selections and queries. Try creating a query layer and specify a virtual ObjectId or use an existing field for the ID. https://pro.arcgis.com/en/pro-app/latest/help/mapping/layer-properties/what-is-a-query-layer-.htm https://pro.arcgis.com/en/pro-app/latest/help/mapping/layer-properties/creating-a-query-layer.htm https://pro.arcgis.com/en/pro-app/latest/help/mapping/layer-properties/modifying-a-query-layer.htm   ... View more

@ScottFedak2085 The following help topic section describes the POI role and gives illustrations of the types of searches that are supported and what the result would look like in ArcGIS Pro, https://pro.arcgis.com/en/pro-app/2.9/help/data/geocoding/introduction-to-locator-roles.htm#ESRI_SECTION1_CE2B24E7AC144C71B645937363ECBCE5. More details about POI searches using REST can be found below. I would say that using the REST endpoint is for development and testing purposes and when using it you should include the location parameter as part of the requests since there is not map that location can be determined from like in ArcGIS Pro or the Map Viewer. - https://developers.arcgis.com/rest/services-reference/enterprise/find-address-candidates.htm#ESRI_SECTION1_8A422A5AB4674781BC635240F31284C4 - Search for POIs - Search using proximity - Category filtering - https://developers.arcgis.com/rest/services-reference/enterprise/suggest.htm#ESRI_SECTION2_824C2C37C4AB4F63ABD67AE3E973FE31 (see example 'Get suggestions using location' and 'Use proximity with suggestions' section) - If you have included your own categories for the POIs you can search based on the category, https://developers.arcgis.com/rest/services-reference/enterprise/suggest.htm#ESRI_SECTION2_F6AA0E35A2E94DC197D7FCFB0D804022 ... View more

@RonnieRichards The scoring for the new locators is different from the classic 10.x locators and the output component score fields are not part of the new locators. The scoring algorithm of the new locators is not something that is documented. The output fields that are returned in the output are discussed in the following topic, https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/what-is-included-in-the-geocoded-results-.htm. If you wanted to see what the original input address was you could add the full address in a single field, then set that field as a custom output field. When you search for the address the custom output field is included in the result returned. Step 9 mentions the optional custom output fields, https://pro.arcgis.com/en/pro-app/2.9/help/data/geocoding/create-a-locator.htm. In order to better understand what is happening with the input address and what is being returned I would need a sample of the data used to build the locator and the locator you have created.  Or at a minimum see the locator properties that show the reference data field mapping and geocoding options or a screen shot of the reference data that includes the feature fore the input address and the one that is returned. If a feature exists for the base address (4791 PELL DR , SACRAMENTO, CA 95838) and not for the subaddress (4791 PELL DR STE 1) ... View more