Latest Contributions by ShanaBritt

@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

You will likely need to create an alternate name table if you continue to use ArcMap. https://desktop.arcgis.com/en/arcmap/latest/manage-data/geocoding/the-alternate-name-table.htm If ArcGIS Pro is an option, when you build a locator with the Create Locator tool and search for an address in the Locate Pane you would get a list of suggestions as you type that you can then click and the map will zoom to the selected address.  https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/introduction-to-locator-roles.htm https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/create-a-locator.htm https://pro.arcgis.com/en/pro-app/3.0/tool-reference/geocoding/create-locator.htm https://pro.arcgis.com/en/pro-app/3.0/help/data/geocoding/tutorial-create-a-locator.htm https://pro.arcgis.com/en/pro-app/3.0/help/data/geocoding/locator-role-fields.htm   ... View more

@feralcatcolonist_old Does the Cityworks app not show suggestions the same way that ArcGIS Pro does? If your locator built with zone and 'match with no zone' set to the default of 'No' is used in ArcGIS Pro Locate pane, do you get suggestions when you enter '250 W First'? Also are zones specified for each role in the field mapping for the locator? You should have a zone assigned to each role in the multirole locator. It looks like from the screenshot that one candidate includes zone while the other does not. I cannot tell which candidate is coming from the PointAddress role or the StreetAddress role. I believe the lacking of zone for one of the roles is the cause of the behavior you are seeing when 'Match with no zone' is set to 'No'. It is possible to build a locator w/o zone and use it to batch geocode addresses w/o zones, in this case the default 'Match with no zone' property is set to 'Yes'.    ... View more

@feralcatcolonist_old Do you know what request is used in the application that is sent to the geocode service, findAddressCandidates or geocodeAddresses? You may need to use Fiddler or something like it to see the contents of the requests, but if location was included in the request I suspect they should get suggestions returned from the service. I don' t have any experience with Cityworks to know what's going on behind the scenes. ... View more

@feralcatcolonist_old If the locator is being used in what sounds like a geosearch scenario where someone just types the address, they should be getting suggestions for addresses that show the zone information and then they would just select the suggestion. So if the locator is built with zones (municipality, county, zip codes) the default setting is 'No' for 'Match with no zone'. If the locator is used in the Locate pane of ArcGIS Pro or the MapViewer, when the user starts to type the address w/o the zone suggestions are displayed. The suggestions returned are based on location and the center of the map is used for location is no zone is included. If the locator is used as a service the location parameter should be included in the requests. If the locator is used for batch geocoding, the zone is required in the address in order to get results returned with the default setting for the locator you are creating. Batch geocoding does not make use of location, the location comes from the zone. We recommend batch geocoding with at least one zone or using suggestions if you are entering an address w/o zone when the locator supports zones. Are your users using the locator in ArcGIS Pro? MapViewer? Mobile App? -Shana ... View more

@feralcatcolonist_old That is correct the "Match with no zones" property is not available in the Python Geocoding Module. However, I'd like to get a better understanding as to why you need to use it. Where will the locator be used? How will the locator be used (batch geocoding a table or single address searches in Pro, MapViewer, or some other app)? The property is a legacy property designed for locators that did not support suggestions before ArcMap 10.3 and locators built in Pro with either the Create Locator or Create Feature Locator tool automatically support suggestions so that as you type the address or place you are presented with suggestions to choose from and select to take you to the location.  ... View more

@DavidColey I would submit this issue with the 2.9 project to Support so that a bug can be logged for us to evaluate and determine the cause and if it can be resolved in a future patch. It's possible that there are still some references in the aprx to locators. If you package the 2.9 project as a project package and extract it to a new folder, do the removed locators still show up? ... View more

@DJacobs_UNMTRU , Looking at the screenshots and info you provided I have a few questions and suggestions. Since this is just a street based locator I would make sure the Match out of range is set to 'No'. I see that just StreetName is mapped when creating the locator. Does the reference data not split up the address components into individual fields? If the street is not broken up into components in the reference data I would run the Split Addresses into Components tool and use the result to build the locator. It would be helpful to see the street values in the street data, the Addr_type field in the geocode result, and what Address categories are checked for the locator in the Geocoding options. I also see that you have the forward slash as an intersection connector along with '@' and for some of the intersections both of those characters are listed.  ... View more

@BradleyMcCallum The Create Composite Address Locator ran quickly considering the composite locator contains path references to the participating locators. Nothing complicated is happening when creating a composite locator. It is similar to how data is referenced in ArcMap and Pro project files. - It does seem like something is off about the composite. If you open the properties of the composite locator are there any warnings or anything red in the locator properties dialog? - Can you provide details about the input parameters for the Geocode Table pane or Geocode Addresses tool? Are you geocoding by country name or country code? - What version of ArcGIS Pro are you using? I understand that your goal is to work with a composite, but curious to know if you create a multirole locator of Postal Locality and City roles and use it to geocode your data if you get the same error.  If you wanted to share this data privately let me know. -Shana ... View more

It sounds like your projects contain the classic locators that were deprecated in ArcGIS Pro 3.0, so this message will pop up for each classic locator (*.loc, *.loc.xml, *.lox) that is not a service referenced in the project. These locators will need to be recreated using the Create Locator or Create Feature Locator tool (*.loc, *.loz). To avoid these errors with your projects you would need to open them in Pro 2.9 and remove them and save the project before opening them in Pro 3.0. Geocode services that are based on the classic locator can still be added to the project and used. https://pro.arcgis.com/en/pro-app/latest/get-started/migrate-2x-to-3.htm#ESRI_SECTION1_CAF5C09ED07F42AB94619FC9B19D19EB When you have opened your existing projects in Pro 3.0 and removed them from the Locators group in the Catalog pane have you saved the project and after saving you are still prompted with the invalid locator message? I would also double check for the invalid locators in the Provider Settings if you are able to access it in the Locate pane.   ... View more

@MinsooKang The locator that you received is a classic locator that was created with the Create Address Locator tool, which is no longer supported in ArcGIS Pro 3.0. The classic locators consist of three files (*.loc, *.lox, *.loc.xml) and are supported in ArcGIS Pro 2.9 or earlier. ArcGIS Pro 3.0 only supports locators created with the Create Locator tool or the Create Feature Locator tool and consist of two files (*.loc, *.loz).  Please share this deprecation notice with the entity you received the locator from so that they can recreate the locators for you using the Create Locator tool, https://support.esri.com/en/Technical-Article/000027452. The other option is to use ArcGIS Pro 2.9 if they are unable to provide you with the newer locators. Another option would be to create your own locator if they are able to provide the data they used to build the locator. Below are some resources: https://pro.arcgis.com/en/pro-app/3.0/help/data/geocoding/create-a-locator.htm https://pro.arcgis.com/en/pro-app/3.0/help/data/geocoding/introduction-to-locator-roles.htm 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   ... View more

@HXiao Locator roles cannot be customized in ArcGIS Pro. What type of customizations do you make to the address locator style in ArcMap that is missing from locators created with the Create Locator tool in ArcGIS Pro? ... View more

@GeorgeBrown1 When geocoding the table which Output Fields option did you select in the Optional Parameters section of the Geocode Addresses tool or Geocode Table tool?   ... View more

Have you tried just creating a multirole locator that uses the PointAddress and StreetAddress roles and publishing the multirole locator to ArcGIS Server instead building two single role locators and a composite locator that is published as a service? https://pro.arcgis.com/en/pro-app/3.0/help/data/geocoding/combine-multiple-layers-into-a-single-locator.htm https://pro.arcgis.com/en/pro-app/3.0/help/data/geocoding/tutorial-create-a-multirole-locator.htm   ... View more