Latest Contributions by ShanaBritt

Charles, If you were going to sign into your Enterprise organization's portal in ArcMap you would use the following URL, https://gisserver.domain.com/portal. More info about portal connections in ArcMap can be found at Manage ArcMap portal connections—Help | ArcGIS Desktop .Then in ArcMap you would be able to sign in with the Enterprise credentials and the World Geocoding Service will be available in the Geocoding toolbar. If you were going to make an ArcGIS Server connection (.ags file) you would use the following URL and include the Enterprise credentials, https://gisserver.domain.com/server . ... View more

Just curious, do you get the same unexpected behavior when the csv contains 15-20 record? It's possible that there might be a value in one of the fields after record 9 that is causing a problem with the csv geocoding the locations correctly. I also noticed that another field contained a space in the name "Area Code". I would suggest removing spaces from the column headers of all the fields in the csv, even those not used for geocoding to see if you get different results. ... View more

If you had spatial features that included the GIS PIN, you could build your own locator from it using the General - Gazetteer address locator style, where the place name would be mapped to the GIS PIN field. Then you could geocode the spreadsheet based on the value in the GIS PIN field to be able to place the location on a map. ... View more

Just an update on the status post 2018 User Conference... The ArcGIS Geocoding team is currently working on a solution for improving suggest results for locators organizations build from their own data.  We are targeting the solution for release for the first half of 2019.   ... View more

The following thread has more discussion about the behavior and what is happening, which is a limitation in the current address locator technology. Composite Locator Not Properly Locating Address Points The suggestion index for address locators created with your own data that have suggestions enabled behaves as described below: The suggest index does not store the house number for performance reasons, and so the best practice is to create a composite locator with at least a Street Address or Point Address locator and a Street Name locator. The reason for this is that if the house number doesn't exist in the Street Address or Point Address locator, you will still get a match to Street Name. You do not need different data to create the Street Name locator. A Street Name locator can be created from Street Address data because the Street Name style only uses a subset of the fields required by Point Address or Street Address. The ArcGIS Geocoding team is currently working on a solution for improving suggest results for locators organizations build from their own data.  We are targeting the solution for release for the first half of 2019.   ... View more

Lee: I was able to create a parcel and zip code locator and add them to a composite using ArcMap 10.6.1 and publish the composite using ArcMap to the federated server of a 10.6.1 Enterprise portal using the copy data option. I added the composite service as a utility service to the Enterprise portal and was successful in dragging and dropping a csv file onto the map and geocoding either the postal codes or parcel PINs. Since you do have Enterprise portal and it is federated, you can add the composite locator to ArcGIS Pro and share the locator directly to the Enterprise portal as an item. The item can then be added as a utility service to be able to use it in the map viewer or in ArcGIS Pro when signed with your Enterprise credentials. Does the behavior occur if you use ArcGIS Pro to publish the composite locator to Enterprise portal? These resources should help: About sharing your locator to your portal—ArcGIS Pro | ArcGIS Desktop  Publish a locator to your portal—ArcGIS Pro | ArcGIS Desktop  Set properties on locators shared to your portal—ArcGIS Pro | ArcGIS Desktop  ... View more

Lee: Is the data for the postal codes and parcel numbers in a single field in the csv or multiple fields in the csv? Are you able to provide a screenshot of the field mapping from the map viewer when using the composite? In ArcMap when you select the Data.csv table do you map both the 'Key' and 'ZipCode' fields to geocode the table? ... View more

ArcGIS Pro does not have an option to adjust the candidate and match scores at run time like you can in ArcMap. ArcGIS Pro does not have a locator properties dialog for geocode services. There really isn't a good solution if you don't have access to the locators that were published to server.  -Shana ... View more

Brian: The feature search behavior you described that includes joining an Excel spreadsheet to a feature class and not being able to set the feature class up as a layer provider to search for features is a bug, BUG-000114925, that I've added to our development backlog for review. If you are current on your maintenance I would suggest reaching out to Support to see about getting added to this bug so that you can follow it. We've made some improvements to the way feature search works in the Locate pane at version 2.2, which went live a few days ago. You can search for features without configuring layers in the map, similar to behavior found with the ArcMap Find tool. The workflow you described in this thread will not work with the improvements either, from my testing the feature class and the table need to be in the same workspace (file geodatabase or enterprise geodatabase aka sde) if joined together. Find a feature by searching all fields in all layers in the map using the Locate pane is new for ArcGIS Pro 2.2. Excel .xls tables can be used in ArcGIS Pro, but has limitations. -Shana ... View more

Monika: If Name, County are in a single field in the reference data, try creating a locator based on US Address—City State locator style and map the field to  Named Place. Then publish the locator. What are the results? Another locator style to consider is the General - Gazetteer to build the locator. Commonly used locator styles—ArcGIS Pro | ArcGIS Desktop   ... View more

Brian, Are you able to import the XLS into the SDE geodatabase, then use the imported table as the source of the join to the feature class. Then try to add the feature class as a layer provider.  ... View more

Brian: Can you provide a few more details about the data the participates in the join? I've found that if I have a file geodatabase that contains a feature class and a table, then join the table to the feature class I can configure the feature class for search successfully. I have found that if I joined a csv table to the feature class that I am unable to configure the feature class for search. ... View more

Kevin: Have you checked if any of the locators that are participating in the composite geocode service are running into the issue described in https://support.esri.com/en/technical-article/000011688? This is the first thing that comes to mind regarding your example when typing the street address with zip and municipality, but not getting candidates when only the street address is provided.  ... View more

Brian, Sorry for the delayed response, I've been busy with finishing up certifying the next release of ArcGIS Desktop and needed to mock up some of the data based on your screen shots to determine what was wrong and how to fix it. 1. The reason "1625 Jaywin Circle" didn't match was because of the fields you used for field mapping when building the address locator, which was based on the 'TYPE_SHORT' field. This field contained and abbreviation ('Cl') for "Circle" that was not part of the street suffix type aliases grammar in the address locator style.Aliases provide a mechanism to support word substitution beyond what is provided by spelling substitution. Whichever alias form is found in the reference or input data is treated as equivalent. Below is the alias section for Circle in the grammar for the address locator style which does not include 'Cl'. If you had used 'ROAD_TYPE_FULL' field when building the locator searching for "1625 Jaywin Circle" would have found a match in the Locate pane. Before: <def name="_ST_Circle" is_alias_list="true"> <alt>Circle</alt> <alt>Cir</alt> <alt>Ci</alt> <alt>Circulo</alt> <alt>Circ</alt> <alt>Circl</alt> <alt>Corcle</alt> <alt>Cr</alt> <alt>Crcl</alt> <alt>Crcle</alt> <alt>Crl</alt> </def> If you use this article as a guide, you can modify the address locator template to add the 'Cl' abbreviation to the Circle street suffix type to look like the following.How To: Add city aliases to the address locator style  At step 2 in the article search for "suf_type_ext" then scroll down or search for "Circle" until you get to the section I referenced above. After modifying the USAddress.lot.xml recreate the address locator and you should be able to get matches in the Locate pane and when geocoding the table if the street suffix type in the input address is 'Circle' or 'Cl'. After: <def name="_ST_Circle" is_alias_list="true"> <alt>Circle</alt> <alt>Cir</alt> <alt>Ci</alt> <alt>Circulo</alt> <alt>Circ</alt> <alt>Circl</alt> <alt>Cl</alt> <alt>Corcle</alt> <alt>Cr</alt> <alt>Crcl</alt> <alt>Crcle</alt> <alt>Crl</alt> </def> 2. Here are some screen shots to clarify my previous explanation about which fields in the reference data in your screenshots that could be used for building the locator. It is not required to map Full Street Name in order to get matches when geocoding, it is only used as an output field when batch geocoding. It's there to use for labeling if you did not had a field that could be used for labeling the geocoded point. Mock data: ---------------- Possible field mappings: --------------------------------- 3. To handle the house number suffix when using the US Address - Singlehouse Subaddress style to build a locator, concatenate the house number, house number suffix and/or house number prefix in a single field and use the new field to map to House Number when building the locator. See the difference in the mock data example for FULL_CIVIC_NUM and this example includes FULL_CIVIC_NUM. Results based on the locator field mappings above: ---------------------------------------------------------------------         ... View more