Latest Contributions by ShanaBritt

‎06-17-2021

@JoeBorgione If there is one and one only 1234 S Main S in the reference data used to build the locator, then building the locator w/o zones would be the suggested workflow. I'd be curious to see what your results are if you build a locator w/o zones and geocoded your table of addresses to see if you get different results than with the locator that was built with zones.

‎06-16-2021

@JoeBorgione It looks like your input addresses have no zone info, but the locator was built with zones and the match with no zone setting set to 'Yes'. I'm wondering if you would get different results if you built the locator w/o zones and geocode the addresses. When the locator is built w/o zones the "match with no zone" property is set to 'Yes' by default. Is the city info required for the match candidate? To fully investigate and determine why this unmatched behavior is happening we would need the reference data, locators, and sample of just the addresses w/o any identifying info. If you want to reach out to me with this info or log a new case with Support is up to you.

‎06-14-2021

@JoeBorgione When on the Unmatched tab in the Rematch Addresses pane, does clicking the Auto Rematch button match the unmatched addresses?

‎06-11-2021

Do you only see this behavior with composite locators? Do you see the behavior with multirole locators? The jumping behavior is something we are looking into for a future release of ArcGIS Pro.

‎06-10-2021

There is a reference to a python script in the updated help topic for keeping your locator and geocode service updated with new data https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/keep-your-locator-up-to-date.htm#ESRI_SECTION1_12AA5C7DF3B44701B13DD015F6D1BA02. Perhaps try using the Updating Geocoding Services script for the scheduled task.

‎06-07-2021

Eric: Is this workflow different from what you did initially when you received the error? Are you now getting the expected results in Pro 2.8?

‎06-07-2021

Sherena: Were you attempting to add the result from the Locate pane to the XY Event layer when you were going through the tutorial in the following steps versus the feature class that gets exported to the project geodatabase in the tutorial? I'm trying to understand what you selected in the Add to Feature Class dialog while going through the tutorial and what you mean by "You have to convert the data to a geodata format." https://pro.arcgis.com/en/pro-app/latest/get-started/create-points-from-a-table.htm#ESRI_SECTION1_F51576AEF1FF47449B0DD6F1E6108368 https://pro.arcgis.com/en/pro-app/latest/get-started/create-points-from-a-table.htm#ESRI_SECTION1_DF51D1ED00B944368FB260D148708DD4 Thanks, Shana

‎05-27-2021

@StephanieBosits In San Diego there are several neighborhood districts and I've added those districts to some street segments and created a StreetAddress role locator StreetsNbrhd and mapped neighborhood, city, state, postal. I do not have an alternate name table in this case. When I search for the address and include the neighborhood I get a match returned and suggestion that includes the city. Are you looking for the suggestion and match result to include the neighborhood value? search result: Candidate details: -Shana

‎05-27-2021

@JoeBorgione That feature has been there since the tool was released in Pro 2.3 and is much easier to add custom fields than cracking open an xml file and modifying stuff. You will also see these custom output fields in the locator properties on the output fields page.

‎05-27-2021

When you build the locator with the Create Locator tool, expand the optional parameters section and enter the name of the field in your reference data that contains the data ID you want to use to join other attributes to the Custom Output Fields parameter. Then go back to the Field Mapping section and assign the reference data field to the new field added. If there are other attributes in the reference data that you would like to display as an output in the geocode results you can add up to 50 here. For example ESN, Fire District, or School District to name a few.

‎05-24-2021

Joe: The Field Mappings control is used in a few tools such as Merge (Data Management) and Create Composite Address Locator (Geocoding) tools. Unfortunately, we do not have this info documented specifically for the Create Composite Address Locator tool, but it is something we can add to the documentation for a future release. Here is documentation about mapping fields in Python, https://pro.arcgis.com/en/pro-app/latest/arcpy/get-started/mapping-fields.htm. The Python strings for Field Mappings are similar between these 2 tools. For Create Composite Address Locator, here are the parameters, plus the example you provided: Field1 New field name Address 'Field1' Alias of new field "Address or Place" true IsEditable true true Allow NULL values true false Required false 4 Length 100 Long Type Text 0 Scale 0 0 Precision 0 First Merge Rule First # Delimiter # For Merge, here are the parameters: ObjectID New field name 'ObjectID' Alias of new field true IsEditable true Allow NULL values false Required 4 Length Long Type 0 Scale 0 Precision First Merge Rule # Delimiter C:\\temp\\test1.gdb\\Hospital Source data OBJECTID Source field -1 Start Position -1 End Position I hope this helps. -Shana

‎05-19-2021

It is also a good idea to pass location with all REST requests to improve behavior (both performance and quality). If the locator is published as a service the Location parameter should be used in the request to boost geocoding candidates based on their proximity to the location, which could be the center of the map or data used to build the locator. Candidates near the location are prioritized relative to those farther away. See the optional location parameter in the list of parameters here, https://developers.arcgis.com/rest/services-reference/enterprise/find-address-candidates.htm#GUID-39075FC0-0FDA-4622-A84D-B164DCCB1339

‎05-19-2021

In Pro 2.7 we added functionality to limit what output fields are returned in the geocode result by adding an optional Output Fields parameter to all of the geocoding geoprocessing tools and Geocode Table. The 4 fields that are disabled in the screenshot above are necessary to be able to review and rematch the geocode results. Below is a description of the available options. All — Includes all available locator output fields in the geocode results. This is the default. Location Only —Stores the Shape field in the geocode results. The original field names from the Input Table parameter are maintained with their original field names. Rematching geocode results is not available with this option. Minimal —Adds the following fields that describe the location and how well it matches to information in the locator in the geocode results: Shape, Status, Score, Match_type, Match_addr, and Addr_type. The original field names from the Input Table parameter are maintained with their original field names. Click the following link and scroll up to the last parameter, https://pro.arcgis.com/en/pro-app/latest/tool-reference/geocoding/geocode-addresses.htm#GUID-0F66B6E3-30D0-4DC2-BCB1-EEA9658BDFED

‎05-19-2021

Anna: You can currently enter '100 Main St B ' or '100 Main St B, Redlands' in the Locate pane and get suggestions that return '100 Main St B' or '100 Main St Unit B, Redlands' depending on how the locator was built. Are you saying that when you select the suggestion when the input does not include a subunit indicator (# or unit, apt, suite....) that it zooms to the wrong location? If the subunit info 'Unit B' is in a single field in the reference data, the # subunit indicator is required. The best practice is to format the reference data so that the unit type and unit id are in separate fields to get the best results. If you built your locator with zone (neighborhood, city, state, zip) mapped, do you have 'Match with no zone' set to 'YES'? If you built the locator w/o any zone mapped, the 'Match with no zone' property is set to 'YES' by default. I have seen that when this property is not set correctly that it can affect subaddress search results. -Shana

‎05-17-2021

Sherena: It looks like you were using the ArcGIS World Geocoding Service to search for the location in the Locate pane... 1. Which version of ArcGIS Pro are you using? 2. Does your organizational account have geocoding privileges? Adding or saving the results in a feature class when using the result from the ArcGIS World Geocoding Service consumes credits. 3. We resolved the issue of using the XY provider returning an error when using Add to feature class in ArcGIS Pro 2.7.

Online Status	Offline
Date Last Visited	3 weeks ago

My Ideas

Latest Contributions by ShanaBritt

Re: Address does not match but then it does in rematching

Re: Address does not match but then it does in rematching

Re: Address does not match but then it does in rematching

Re: Address does not match but then it does in rematching

Re: Script using Python API and Windows task scheduler

Re: Failed to add location to the feature layer

Re: Failed to add location to the feature layer

Re: What fields does suggest use when creating a locator?

Re: When Geocoding in Pro how do I include Reference Data ID

Re: When Geocoding in Pro how do I include Reference Data ID

Re: Field Mapping with Create Composite Locator

Re: Match with No Zone in GeoCode Service

Re: Geocoding: Limit Output fields

Re: Locate Addresses with Units

Re: Failed to add location to the feature layer

Re: Geolocate addresses tool in arcpy

Re: Composite Locator added to AGOL is no longer G...

Re: Address locator takes 20x longer to rebuild in...

Re: Pro crash-out trying to rebuild address locato...

Re: ArcGIS Server Locator Fails To Geocode Full Ad...