Latest Contributions by ShanaBritt

@jzcgis There are three different tutorials available for building locators with the Create Locator tool.  https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/tutorial-create-a-locator.htm https://pro.arcgis.com/en/pro-app/3.0/help/data/geocoding/tutorial-create-a-multirole-locator.htm https://pro.arcgis.com/en/pro-app/3.0/help/data/geocoding/tutorial-create-a-locator-with-more-than-one-dataset-of-same-role.htm   ... View more

@ScottFedak2085 Enterprise 10.9 and later supports offset settings for StreetAddress role locators. You may want to consider creating the locator with either Global Extra High or Local Extra High as the Precision Type, which is an optional parameter in the Create Locator tool. The Precision Type parameter is supported in Enterprise 10.8.1 or later. I did not see a screenshot of the locator properties showing the output fields, but I suspect you may be running into ENH-000141201, which is resolved in ArcGIS Pro 3.0 and Enterprise 11.0. ... View more

@HelenZhou Customizations to the locator roles and the default output fields are not supported for the Create Locator tool.  However, the Create Locator tool allows you to add up to 50 custom output fields that are returned in the geocode results. You could add the field names that you want returned like Streetname and assign the field from your data to the custom field that is listed in the Field Map section of the tool. In the locator properties Output fields page you can uncheck all of the fields you do not want returned in the output. When ArcGIS Pro 3.1 is released the Geocode Addresses tool will have an option that returns the minimal fields plus the custom user fields that were added when the locator was built. See step 9 in https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/create-a-locator.htm. Outside of the output field names, is there anything else you customized in the classic locator for your workflow that you are unsure is possible with the Create Locator tool? ... View more

@RandyKreuziger1 I had additional questions for you about your workflow. Are your users searching for features or just attributes in a non-spatial table? What do the users do with the result in the Find tool in ArcMap? Are the users able to search the table and database views w/o creating the in-meomory XY Event Layer? -Shana ... View more

Bryan, Thanks for the update. I did try to replicate what you described and was not able to in Pro 3.0.2. If you could provide a sample of your data, perhaps just the parcel id or the parcel id and the fields you mapped to create the locator. Are you batch geocoding when you run into this problem or search in the Locate pane? -Shana ... View more

Bryan: What you described sounds like something we would want to investigate. What version of ArcGIS Pro are you using? I would suggest opening a ticket with Support. Do you get the same behavior if you use the POI role and map the parcel id or PIN to the Place Name role field? Do you get the same behavior if you use the Create Feature Locator tool to build the locator for the parcel id? -Shana ... View more

Brad: Anytime you are using ArcPy.GeocodeAddresses() with any locator (utility service, from an ArcGIS Server connection, Enterprise portal, or local), you must include all of the input fields from the composite locator even if they are the <NULL> fields. For raw REST requests or Python code that accesses the REST API you can pass the fields that you need. So in your case for the GeocodeAddresses REST request you can use  {Ciy: "Halifax", Postal: "H0H 0H0", Country: "CAN"}. -Shana ... View more

@RyanPaquette3  The only current option I can think of is to build the locator in ArcGIS Pro, then go to the History pane and right-click the executed Create Locator tool and select Share As > Geoprocessing Package. This will create a package that includes the reference data to build the locator, plus the history of the tool that includes the field mapping and parameters used to build the locator. This package can be shared to AGOL as a file. When the geoprocessing package is added to the ArcGIS Pro project, the reference data is added to the project/Contents pane and the previously executed tool will show up in the History. From there, you can rerun the tool to create the locator. With any package you can attach files to the package, so you could theoretically attach the locator files (.loz, .loc) to the geoprocessing package if you don't want the end user with the geoprocessing package to have to run the tool to create the locator.   ... View more

@RyanPaquette3 When a locator is built with the Create Locator tool with local data or feature service a snapshot of the data is indexed and stored with the locator. This means that the locator is not connected to the source data. If the source data changed after the locator was created, the existing locator wouldn't be updated with the new data automatically. I believe I misunderstood your initial post, but hosting locators that are not services added to AGOL as items is not supported. You will have to publish the locator to ArcGIS Server or Portal and add it as an item to AGOL or as a utility service. ... View more

Frank, Glad things are working for you!   -Shana ... View more

Thanks for the additional info Randy. ... View more

@RandyKreuziger1 Do you only encounter the behavior with an event layer created from a SQL Server table view? I re-tested and was able to reproduce with a csv table. Is using the XY Table to Point tool a viable workaround for you? ... View more

@FrankMatzen There is no spelling sensitivity setting for the locators created with the Create Locator tool and there is not modifiable locator style template for the locators created with the Create Locator tool in ArcGIS Pro. I see in the example you provided that the StreetName match had a score of 93, what as the score of the StreetAddress candidate after disabling the StreetName category? You can increase the 'Minimum match score' setting in the Match Options section of the Geocoding options in the locator properties, this will affect batch geocoding (geocodeAddresses) results. Maybe try increasing the score to 95 or higher and testing in ArcGIS Pro before publishing as a service. If you increase the 'Minimum candidate score' setting this will affect findAddressCandidate results. If you do test the behavior in ArcGIS Pro using the Locate pane I would set both Minimum candidate and Minimum match score settings to the same value. Is the locator you are using a single role locator, multirole locator or a composite locator? ... View more

@FrankMatzen , The behavior you are seeing, a match to StreetName Addr_type, is expected behavior when Match out of range is false. If you only want matches to PointAddress or StreetAddress level or Street Intersections only, you need to disable the StreetName category in the locator properties > Geocoding Options > Match Options under Categories to support before publishing the service. You will be able to test this in the Locate pane in ArcGIS Pro before publishing the locator. ... View more