Latest Contributions by ShanaBritt

‎12-15-2021

Do you get the same error when you publish the locator directly to Enterprise 10.9 from ArcGIS Pro without creating an sd file that gets published in ArcGIS Server Manager? https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/share-a-locator.htm Have you been able to compare the settings/configurations of the two Enterprises that are behaving differently?

‎12-15-2021

If you create a locator view, a proxy of the ArcGIS World Geocoding Service, you can specify if the match will be the rooftop or the street, see step 9, https://doc.arcgis.com/en/arcgis-online/reference/geocode.htm#ESRI_SECTION1_BC67C473527D4AD4A51F24B5D1A6860C.

‎12-15-2021

There have been several changes to the way subaddresses behave with the locators since this issue was posted back at ArcGIS Pro 2.5. @DMOB17 , what version of ArcGIS Pro are you using? If you can show a screenshot of your locator properties with the reference data field mapping, I may be able to tell if something is off. A new tutorial was added in the latest release of Pro that builds a multirole locator that includes searching for subaddress locations that you may want to check out. https://pro.arcgis.com/en/pro-app/2.9/help/data/geocoding/tutorial-create-a-multirole-locator.htm

‎12-15-2021

I cannot tell from your response, which tool was used to create the locator you are trying to publish. Was it the Create Address Locator tool in ArcMap or ArcGIS Pro, Create Locator or Create Feature Locator tool in ArcGIS Pro? Did you create the .sd file via python using CreateGeocodeSDDraft publishing function? When publishing the locator with the sd file is the locator being copied to the server or are you using a folder as a data store? Do you get the same error if you create the sd file in ArcGIS Pro, then publish it in the ArcGIS Server Manager? https://pro.arcgis.com/en/pro-app/2.9/help/sharing/overview/save-a-service-definition-for-a-locator.htm

‎12-05-2021

Why do you want to store the locator in SQL Server database? If you have Enterprise, you can publish the locator to Enterprise portal then access the the locator item in Pro from My Content on the portal. Or you can set the published locator item as a geocoding utility service that will be available in ArcGIS Pro whenever you sign in and your portal is the active portal.

‎12-05-2021

What version of ArcGIS Server are you trying to publish to? Was your locator created with the Create Address Locator tool or the Create Locator or Create Feature Locator tool? If the locator was created with the Create Locator tool, which role was used to build the locator? Are there more error details in the ArcGIS Server Manager logs?

‎12-02-2021

@CityofColumbusDepartmentofTech , unfortunately there is no setting to return the UnitName or SubAdr fields that show up in findAddressCanddates requests in reverseGeocode requests or to have it included in the 'Address' output field. From a reference data security standpoint, someone could use reverseGeocode requests to reverse engineer your reference data. One workaround to consider involves some data manipulation, but you could use Calculate Field to populate the 'Address' field in the geocode result with the value from the Match_addr or LongLabel field. Out of curiosity, what is COTS? You could submit an idea for this or an enhancement through TechSupport.

‎11-19-2021

@Anonymous User If you click on Python table of the Parameters table and scroll to the Additional Parameters description their are links to other topics about how rank is used for sorting the results and the extents are used for displaying or zooming to the geocode result. https://pro.arcgis.com/en/pro-app/2.8/tool-reference/geocoding/create-feature-locator.htm Locators created with the Create Feature Locator tool only support two categories, Feature and Coordinate System. If you only check Feature, then no results are returned if you searched for XY, MGRS, or USNG coordiantes. See https://prodev.arcgis.com/en/pro-app/latest/help/data/geocoding/tips-for-improving-geocoding-quality.htm#ESRI_SECTION1_1CC5777CE25A4D048FCC518AEC549DC6 for more details about Categories to support in Geocoding options. What were the names of the locators you created with the Create Feature locator tool? Did your map also include any layers that had fields configured for search? What are you expecting to see in the results list? If there are additional attributes associated with these points you could use the POI role to create a locator with the Create Locator tool and add up to 50 custom output fields that would show in the result.

‎11-12-2021

@BlakeTerhune Unfortunately, at this time there is no option to keep the custom output fields when the Minimal output field option is selected for the batch geocoding tools. If you are using a locator that you have created that includes custom output fields the only workaround at this time is to open the locator properties and go to the Output put fields tab and uncheck all of the fields you do not want. Then select the All output fields option in Geocode Addresses. I would submit this as an Idea or log an enhancement with Tech Support.

‎11-01-2021

@RonnieRichards Is this still a problem with input addresses that contain subunits if you have recreated the locator in a newer release of ArcGIS Pro and publish the service? Does the data to create the locator include 'STE' as a unit type or as part of the value in the unit field that was mapped when building the locator? If the value in the unit field that was mapped when the locator was built is "STE 1", then you will need to include '#STE 1' as part of the input address. If the value in the unit field mapped when the locator was built was '1', then to get the best results you should include a unit indicator like # or STE, but you do not have to include one with locators created in Pro 2.7 or later.

‎10-31-2021

@DavidAllen At Pro 2.7 and later the Rematch Addresses pane includes the ability to modify geocoding options as well as selecting a different locator than what was originally used to geocode the table. See the last two sections of the following topic, https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/rematch-locations-converted-from-a-table.htm#ESRI_SECTION1_092AD2A116A84598A29BD5639C87AC33

‎10-31-2021

@DavidButz The offset units use meters, you would need to convert the current units to meters and use the converted value in the settings.

‎10-31-2021

@HeatherScroggins The minimum match score only applies to batch geocoding and does not apply to findAddressCandidates, which is what is used in the Locate pan in ArcGIS Pro and in the search box in the Map Viewer. The minimum candidate score is currently set to 10, which means that candidates that have a score 10 or higher will be returned as candidates and of those candidates the ones with a score of 80 or higher will be automatically matched when batch geocoding.

‎10-27-2021

@Jaclyn Do you get the same behavior in the Locate pane in ArcGIS Pro when search for an address on 'Lier Rg' with any of the 3 locators you mentioned above? You should be getting the same behavior with the local locator as you do with the service. I get matches no matter what street type I use for a locator built in 2.7.3 and use in the Locate pane. Data: Locate pane:

‎10-27-2021

@Jaclyn Thanks for the additional information about the issue you are facing, but what I'm looking for is how "Lier Ridge" is formatted in the attribute table of the Civic Points and Street Lines data layers to be able to better understand what is happening with your locator. For example is 'Lier' in the street name field and 'Ridge' is the street type field or is one of the abbreviations used in the street type field? Can you share the reference data table section in the Locator Properties dialog for the locators you created or a screenshot of the record in the data layer that shows how the street name is formatted or standardized?

Online Status	Offline
Date Last Visited	Thursday

My Ideas

Latest Contributions by ShanaBritt

Re: Publish Geocode Service .sd file(service definition file) Error

Re: ArcGIS World Geocoder

Re: Proper use of Unit and Unit Type in Point Address Role

Re: Publish Geocode Service .sd file(service definition file) Error

Re: Geocoder in sql server

Re: Publish Geocode Service .sd file(service definition file) Error

Re: Reverse Geocode Returns No Subaddress

Re: Create Feature Locator questions with mmpk

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

Re: Add Find Input fields to Primary Locator Role FindAddressCandidate responses

Re: Need ability to modify Locator properties for Portal Locators

Re: ArcGIS Pro Create Locator Options need to be as capable as the "Legacy" Address Geocoders

Re: AGOL ignores minimum match score in geocoding service

Re: Add "Ridge" Alias to Create Locator Tool

Re: Add "Ridge" Alias to Create Locator Tool

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...